Today I received a brand new LilyGo RTL_433 board and flashed it with the latest Lilygo binary available from the OMG site. Based on everything I read before my purchase and especially after some six hours of troubleshooting I have to give up and ask help.
Am I totally wrong if I say that based on the all documentation, the autodiscovery of 433 devices is by default “ON” in the latest OMG firmware?
The flashing to my Lilygo was successful, my HA found the device and configured it - it is visible in HA with 1 device, 8 entities as it should, but none of the nearby 433 devices are populating to HA automatically. With the MQTT Explorer I can see that the “RTLCnt” counter is alive and numbers are growing, so Lilygo indeed hears weather stations and other 433 devices.
I then downloaded the latest binary package from the OMG GIT and checked the configuration parameters. From the root folder README.md it is said that the Build definition for the mqttDiscovery is following:
This is what I can see from MQTT Explorer - Lilygo has been on for some half an hour. There are several weather stations nearby and I’ve been playing around with cheap 433MHz NEXA remote control, but nothing has been picked by the Lilygo.
The Autodiscovery has been set to “ON” in the HA integration.
@OH1MAC I had excluded the Nexa device decoder due to its resource usage, as it caused resource exceptions with the port to ESP32. With further updates will monitor this, and hopefully it changes in the future.
I’m in the same boat. Nexa is ubiquitous in Nordic countries. I bought this Lilygo T3, installed it today just to find only my thermometers are found. No Nexa nor Somfy
Today I use a rfxcom but its placement (USB device) is not optimal. Lilygo, because is Wi-Fi, would be the perfect solution to decommission my rfxcom.