home.social

Search

1000 results for “mqtt”

  1. Today's IT project was to install an MQTT broker on my #SelfHosting #HomeLab. After a bit of shenanigans with DNS and certificates I've got it working. I'm using the Caddy proxy to generate me a certificate, and a shell script to copy the certificate to my docker host for use by the #Mosquitto #MQTT broker. My router and DNS server make sure the messages end up on the docker host, and a test application on my home desktop is able to subscribe and receive messages from the broker.

    The real fun starts now... writing an app that receives my location data from #OwnTracks on my phone, stores it in a database, and ultimately does all sorts of pretty geospatial stuff.

  2. Fallo en el backend de DJI dejó expuestos ~7.000 robots aspiradores en 20+ países: un ingeniero en Barcelona podía suscribirse por MQTT y ver cámaras, micrófonos y mapas del hogar. Ya está corregido. aidoo.news/noticia/Wljnzr

    #Privacidad #Vulnerabilidades #DJI #Domotica

  3. curl

    Daniël Stenberg

    facts and praise

    I'm fortunate that I am allowed to follow Daniël, lead programmer of the mightycurl. The reason I formulated the line in this way, is because only through the power of the FediVerse I've gotten a boost from someone I follow, who found a post of the lead programmer or curl interesting

    stats:

    install base => 20000*106 devices

    20 billion+ installations!

    curl is used in command lines or scripts to transfer data. curl is also libcurl, used in:

    • cars
    • television sets
    • routers
    • printers
    • audio equipment
    • mobile phones
    • tablets
    • medical devices
    • settop boxes
    • computer games
    • media players

    Curl is THE Internet transfer engine for countless software applications in over twenty billion installations!

    curl is used daily by virtually every Internet-using human on the globe!

    curl is 30 years old

    Let that sink in!

    Opinion

    curl is mature critical network infrastructure software that we all need to have our internet powered software / hardware to function in respect to data transfer.

    The syntax to use curl in simple implementations is IMHO quite easy. In case you need to know an extra option, the executable and libcurl have excellent documentation. End users normally interact with curl using the (elf) binary on Linux based POSIX operating systems. The more mature BSDs have another binary format

    Just type curl to get an initial output which looks like this on my current system

    curl
    curl: try 'curl --help' or 'curl --manual' for more information

    then type

    curl --help
    Usage: curl [options...] <url>
    -d, --data <data> HTTP POST data
    -f, --fail Fail fast with no output on HTTP errors
    -h, --help <subject> Get help for commands
    -o, --output <file> Write to file instead of stdout
    -O, --remote-name Write output to file named as remote file
    -i, --show-headers Show response headers in output
    -s, --silent Silent mode
    -T, --upload-file <file> Transfer local FILE to destination
    -u, --user <user:password> Server user and password
    -A, --user-agent <name> Send User-Agent <name> to server
    -v, --verbose Make the operation more talkative
    -V, --version Show version number and quit

    This is not the full help; this menu is split into categories.
    Use "--help category" to get an overview of all categories, which are:
    auth, connection, curl, deprecated, dns, file, ftp, global, http, imap, ldap, output, pop3, post, proxy,
    scp, sftp, smtp, ssh, telnet, tftp, timeout, tls, upload, verbose.
    Use "--help all" to list all options
    Use "--help [option]" to view documentation for a given option

    When you type curl --manual|less you get the manpages which I delimited with less through a vertical pipe

              _   _ ____  _
    ___| | | | _ \| |
    / __| | | | |_) | |
    | (__| |_| | _ <| |___
    \___|\___/|_| \_\_____|
    NAME

    curl - transfer a URL

    SYNOPSIS

    curl [options / URLs]

    DESCRIPTION

    curl is a tool for transferring data from or to a server using URLs. It
    supports these protocols: DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP,
    HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP,
    SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS.

    curl is powered by libcurl for all transfer-related features. See
    libcurl(3) for details.

    URL

    The URL syntax is protocol-dependent. You find a detailed description in
    RFC 3986.

    I can also type man curl to get a nice output:

    curl(1)                                         curl Manual                                        curl(1)

    NAME
    curl - transfer a URL

    SYNOPSIS
    curl [options / URLs]

    DESCRIPTION
    curl is a tool for transferring data from or to a server using URLs. It supports these protocols:
    DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S,
    RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS.

    curl is powered by libcurl for all transfer-related features. See libcurl(3) for details.

    URL
    The URL syntax is protocol-dependent. You find a detailed description in RFC 3986.

    If you provide a URL without a leading protocol:// scheme, curl guesses what protocol you want. It
    then defaults to HTTP but assumes others based on often-used hostname prefixes. For example, for
    hostnames starting with "ftp." curl assumes you want FTP.

    You can specify any amount of URLs on the command line. They are fetched in a sequential manner in
    the specified order unless you use -Z, --parallel. You can specify command line options and URLs
    Manual page curl(1) line 1 (press h for help or q to quit)

    The reasoning behind curl --manual is simple. On a machine without the manual system you still need access to the full manual. This is one of the reasons why man curl is also implemented as curl --manual

    An important RFC is echoed to my terminal in the man curl output which is RFC 3986

    A Uniform Resource Identifier (URI) is a compact sequence of
    characters that identifies an abstract or physical resource. This
    specification defines the generic URI syntax and a process for
    resolving URI references that might be in relative form, along with
    guidelines and security considerations for the use of URIs on the
    Internet. The URI syntax defines a grammar that is a superset of all
    valid URIs, allowing an implementation to parse the common components
    of a URI reference without knowing the scheme-specific requirements
    of every possible identifier. This specification does not define a
    generative grammar for URIs; that task is performed by the individual
    specifications of each URI scheme.

    I shall not quote the whole RFC 3986 here. You can read all about it on the RFC site (see sources)

    As you can see curl is thorougly documented, has all the features a simple end user needs to fetch all kind of data, scaled up all the way to the extensive complex features router hardware et all, needs to transfer data.

    programming route

    I came to this toot when I saw that certain external feature code, which lives in stable external libraries, is now being removed from curl. I should say the code is depreciated then phased out.

    This is a logical step

    • It takes resources to maintain external code
    • If the (shared) libraries are stable and mature, it's much better to just call those libraries and be done.
    • The more external code you can remove from your project the better it is for all the programmers

    The same is also happening in the Linux kernel, they are following in the footsteps of curl

    Conclusion

    There is a treasure trove of information in the sources. Just reading the pages on RFC 3986 will keep you occupied for hours.
    Have fun and keep reading / learning and programming!

    sources:

    curl.se/

    rfc-editor.org/rfc/rfc3986

    curl.se/mail/lib-2026-03/0026.

    #curl #programming #mathematics #linear #algebra #libcurl #Linux #BSD #freeBSD #openBSD #netBSD #POSIX #bash #csh #ksh #sh #fish #radio #TV #smartTV #router

  4. @akkudoktor.bsky.social @m_hundhausen Meine ganze Heizungsanlage hängt komplett cloud-frei auf ähnliche Art an #HomeAssistant - via #RaspberryPi Zero 2W am Raumthermostat-Anschluss.

    Hab es hier in dem Thread beschrieben: i.cymaphore.net/@cymaphore/113

    #Daikin #Heizen #MQTT

  5. Die Heizung (#DAIKIN Altherma 3 H HT ECH2O) an #HomeAssistant anbinden hat sich für uns gelohnt.

    Mit meiner Zusatzregelung erreicht das ganze jetzt gravierend verbesserte Wirkungsgrade in der Übergangszeit. Bin gespannt ob das über die Heizperiode anhält.

    Gateway ist ein #RaspberryPi Zero 2W mit PiCAN Zero mit anderem DC-DC-Wandler und extremer Konfiguration, damit ichs komplett am 24V / 30mA Raumthermostatanschluss betreiben kann.

    @homeassistant @Raspberry_Pi

    #Wärmepumpe #MQTT #Heizung

  6. Smart Wave = ocean telemetry at scale 🌍
    RELIANOID = keeping it secure, fast, and always-on ⚡

    Just dropped a tech guide on how we load balance Smart Wave:
    🔹 MQTT + REST + Web UI
    🔹 mTLS + WAF + DoS protection
    🔹 Prometheus + Grafana ready
    🔹 Handles satellite links like a breeze

    Read it → relianoid.com/resources/knowle

  7. Smart Wave = ocean telemetry at scale 🌍
    RELIANOID = keeping it secure, fast, and always-on ⚡

    Just dropped a tech guide on how we load balance Smart Wave:
    🔹 MQTT + REST + Web UI
    🔹 mTLS + WAF + DoS protection
    🔹 Prometheus + Grafana ready
    🔹 Handles satellite links like a breeze

    Read it → relianoid.com/resources/knowle

  8. Hah score! Managed to push data from #HomeAssistant to #MQTT using the MQTT Publish action in HA, then github.com/hikhvar/mqtt2promet picks it up and services it up to #Prometheus for use in queries. Will need to switch my #Keda scale object from a #RabbitMQ one to a Prometheus query. But will first let this metric sit there for a few days to make sure it behaves as expected.

  9. Как устроен Meshtastic, зачем он нужен и как я подключил его к локальной модели на ноутбуке

    Практический эксперимент с Meshtastic: две Heltec ESP32 LoRa 32 V4, связь на 702 м в городской среде, разбор LoRa-настроек, ролей нод, MQTT и Python-мост к локальной LLM через Ollama.

    habr.com/ru/articles/1030872/

    #Meshtastic #LoRa #meshсеть #Ollama #локальная_LLM #Python #Heltec_ESP32_LoRa_32_V4 #MQTT #offgrid #IoT

  10. ganz unglücklich bin ich leider nicht, ist ein erstes #mystrom device defekt.
    (wifi plus; das sind nur smart plugs, keine messung).
    Die firmware ist leider grauenhaft. Updates funktionieren (wenn es denn welche gibt) kaum ohne die Handy app. die devices befragen den DNS server beinahe all 5 sekunden nach der phone-home adresse (dass die geräte zum mittlerweile kostenpflichtigen cloud service verbinden will, lassen wir mal beiseite....). und den NTP Server, der im DHCP angeboten wird, wird auch ignoriert, weitere treffer auf port 123 auf der firewall :/
    ich werde in zukunft wohl eher alternativen kaufen. z.b. bin ich mit den #hue smart plugs via #MQTT ganz zufrieden <3
    #homeautomation

  11. heise+ | Home Assistant: Smart Home mit dem PC steuern – und als Steuerzentrale nutzen

    Der Hass Agent vernetzt Windows-Systeme mit Home Assistant. Wir zeigen die Einrichtung, um den PC als Präsenzmelder, Mediaplayer oder Steuerzentrale zu nutzen.

    heise.de/ratgeber/Home-Assista

    #Automatisierung #GoogleAssistant #Homeoffice #IT #MQTT #SmartHome #Windows #news

  12. Der Senvolon Präsenzmelder ist ein echtes Must-Have für jedes Smart Home. Lokale Verarbeitung ohne Cloud-Zwang und präzise Erkennung machen ihn zum perfekten Partner für meine Automationen. Klar, bei mehreren Personen hapert's manchmal, aber das Gesamtpaket stimmt. #SmartHome #MQTT hobbyblogging.de/senvolon-prae

  13. Es gibt eine neue Version von meinem github.com/jedie/victron-ble2m Projekt: Hab die vorgeschlagene installation vereinfacht. Nun einfach per #pipx installieren ;)

    """
    Emit MQTT events from Victron Energy Solar Charger via victron-ble bluetooth lib
    """

    #VictronEnergy #SmartSolar #Python #MQTT #HomeAssistent

  14. Ich habe mich gefragt, wie ich mein Balkonkraftwerk besser auswerten kann. Mit Shelly und ioBroker ist das ein Kinderspiel! Die Verbindung über MQTT ist einfach und macht Automationen zum Kinderspiel. Wer noch nicht mit Shelly arbeitet, sollte das unbedingt testen! hobbyblogging.de/iobroker-shel #SmartHome #ioBroker #MQTT

  15. Upgraded Home Assistant from 2026.2.2 to 2026.3.3 last night and it stopped reading the status of my zigbee devices via MQTT.

    I'm running HAOS in a proxmox VM and zigbee2mqtt 2.1.1 in a docker container hosted in a different physical with a ConBee2 radio.

    To check connectivity issues I had the integration listen for # and saw state updates for my zigbee sensors.

    What finally fixed it was going into zigbee2mqtt's settings and disabling and re-enabling Home Assistant integration.

    #homeAssistant #zigbee2mqtt @homeassistant #mqtt

  16. Um não tão novo post: do Blink para o controle remoto real — ESP32 + MQTT + Mosquitto local + app no celular.

    O modelo pub/sub do MQTT encaixa bem em embarcados: o ESP32 não abre porta, não conhece o IP do cliente, só mantém conexão com o broker e reage a mensagens. O firmware fica event-driven, sem polling.

    Documentei a arquitetura, o código completo em C com ESP-IDF, e os problemas que apareceram.

    riverfount.dev.br/posts/contro

    #ESP32 #MQTT #IoT #Embarcados #C