The configuration is very easy, you only give the username/password of the broker running on the emoncms add-on…
Critics and feedback are welcome. It is actually just a proof of concept, in order to see how to run in container a tool like emonhub without being in privileged mode…for ttyAMA0, things are simple, it will be a little more complicated with ttyUSB* as you can connect/reconnect the device many times…but it is possible using cgroups with docker, so why not in home-assistant…
The container is build for 3 archs with the github actions : amd64/armv7/aarch64
It can work as a standalone docker container and is available on my docker profile : https://hub.docker.com/r/alexjunk/emontx_sniffer
My RFM setup is a really old RFM69 & TX 3.2 (I think) on fairly original firmware. I do also have a later TX3 connected by serial to a Pi (as a test setup) and an EmonPi (also a testbed). I’ve not tried any of the different RFM firmware options.
It needs tidying up, but I’ll probably end up with just the TX with serial/WiFi connection feeding to MQTT and my PVE emoncms.
The HA emoncms though is really interesting especially as the Wi-Fi TX4 would be my preferred setup if I was going for it from scratch. A TX4, Wi-Fi, and emoncms on HA is extremely simple and relatively cheap (compared to other options).
Yes and no. You need the additional dongle and the add-on is a bit experimental so if you are willing to fiddle and risk data loss, yes. If the data is important to you, then I’d leave alone (ain’t broke, don’t fix).
Possibly also depends on what you are running HA on as well.
The emoncms addon is not so experimental but the emontx_sniffer yes…datas streamed through MQTT are not really organized in the emonhub way, it is something more raw…
Anyway, there is a emonhub docker container which could be a drop in replacement but it is not packaged as a addon in home assistant…but for docker compose users, it can be something interesting…
from log I can see that RF packets are received… but no mqtt threads are wrotten, see logs:
2026-01-25 18:28:08,554 INFO MQTT_HOST : 192.168.1.13 - MQTT_PORT : 1883
2026-01-25 18:28:08,612 INFO timezone Europe/Rome fixed
2026-01-25 18:28:14,819 INFO no end of line received - incomplete packet
2026-01-25 18:29:12,575 INFO no end of line received - incomplete packet
2026-01-25 18:29:31,193 INFO no end of line received - incomplete packet
you expect data in emoncms addon or somewhere else ? you did not specify any MQTT_USER and PASSWORD ?
maybe you use the anonymous option in the emoncms addon conf ?
conf for the emoncms addon