OK, I remember that I did not use the script, when I tested the new ESP command “ohdiscovery” in April. That’s clear now. I tested again with the unmodified environment of lilygo-rtl_433 from gitpod.io. My supported sensor AmbientWeather-TX8300 was discovered, the OH thing was created automatically and is working correctly. OMG is sending the messages with the correct topic. Here are both config messages. Left is rtl_433 and right is from rtl_433_ESP included in OMG:
The FSK support is already included in the actual version 1.6.0 of OMG and I compiled the package using these compiler options, so that the modulation is switched to FSK:
Here I have some Jansite-Solar TPMS sensors for testing. They are working well as FSK modulated with the native rtl_433 software. When I change the pressure of my pressure test bottle, the data is recognized and decoded by OMG, but no OH thing gets created in my inbox. Here are both config messages from rtl_433 native (left panel) and from OMG (right panel) and I added the base message payload in the lower area of both panels:
From my point of view the state_topic is composed incorrectly. The first line in the right panel (red background colour) shows the topic that is used by OMG to send the messages from this sensor:
OMG/OMG_lilygo_rtl_433_ESP/RTL_433toMQTT/TPMS/Jansite-Solar/8a8e6a
But the state_topic (stat_t) is:
+/+/RTL_433toMQTT/Jansite-SolarSolar/8a8e6a
The fourth topic level TPMS, which is the sensor type is missing and the next level, which is the model, is created as Jansite-SolarSolar, while it should be only Jansite-Solar.
When I create the thing and its channels manually, the item data is shown as expected.
Regards Christoph