ESP32 based BLE, 433mhz & IR gateway bidirectional with MQTT --> OpenMQTTGateway

[Hans_Lree (DigiH)]

@DrRSatzteil

The trouble is that my wife likes to switch off the WiFi during nighttime.

I hope you haven’t told her that Bluetooth is also a 2.45 GHz radio protocol, otherwise the SwitchBot Meters will be off during bedtime as well

Joking aside, depending on where you have Ethernet, you could also install OpenMQTTGateway on a WT32-ETH01.

@DrRSatzteil

Actually I just noticed that from time to time all the item states are set to null instead of actual values. After a couple of minutes everything goes back to normal/actual values.

I added the thermostat with the homeassistant discovery (OH autodiscovery is set to ON).

Don’t get me started on OH MQTT discovery I just vented my frustration with it in a little rant in the OH5 thread

Ideas and Discussion: What Features Do You Want in openHAB 5.0?

Full disclosure: having become pretty disillusioned and disappointed with the general development of openHAB, and OH3 in particular, when I tested it with looking to upgrade when it came out, and openHAB GitHub issues tracking and addressing, or the lack thereof, I’m still running OH2 here, and with realising that it’s best to rely as little as possible on particular bindings, I very early on turned to MQTT compatible implementation for all the Govees, Inkbirds, Qingpings, Xiaomis, SwitchBots,…

Any states being set to null should be addressed there, as it doesn’t have anything to do with OpenMQTTGateway and the MQTT messages it publishes.

You’re best off to keep defining your things manually from my experience.

@DrRSatzteil

For all the other thermostats I own I’ve always set up the things as generic mqtt things. I noticed that sometimes the messages received from the thermostats come in empty (no measurements)

These messages are actually correctly displayed of broadcasts the devices send out, occasionally without their actual properties, for some manufacturers these are pairing messages to make the devices discoverable to proprietary apps or some sending out multiple protocol messages. This should however not affect the existing values displayed in OH.

The user who helped me imp0lement the initial Meter Pro decoder actually found that if the Meters are connected to the own SwitchBot app such ‘empty’ messages are a lot more frequent, while correct value messages were constant once he deleted the Meters from the SwitchBot app. So not sure if oyou also have yours paired with the app or not.

Let us know how you gt on.