I have added support for Ruuvi Air in openHAB
This expands the support of Ruuvi Gateway MQTT binding and Ruuvi Bluetooth binding
EDIT: now code is merged in 5.10 Snapshot!
Please report any feedback!
( PR reference [bluetooth.ruuvitag] Ruuvi Air support by ssalonen · Pull Request #19638 · openhab/openhab-addons · GitHub )
@siest4 would you like to try this out?
Moi, yes definitely, thank you! I’m having OH 4.3 currently but if upgrade is needed, I can try the latest via Docker.
Yes I suppose it is hard to try out with a older version…
Moi,
now I found the time to try this out. It seems to me that installation went ok (only tried the gateway version, not bluetooth). Listing the running bundles gives me:
openhab> bundle:list -l | grep ruuvi
306 x Resolved x 80 x 5.1.0.202511110426 x mvn:org.openhab.addons.bundles/org.openhab.binding.bluetooth.ruuvitag/5.1.0-SNAPSHOT
318 x Resolved x 82 x 5.1.0.202511110428 x mvn:org.openhab.addons.bundles/org.openhab.binding.mqtt.ruuvigateway/5.1.0-SNAPSHOT
350 x Active x 80 x 5.1.0.202511091035 x file:/openhab/addons/org.openhab.binding.mqtt.ruuvigateway-5.1.0-SNAPSHOT.jar
However when adding a new Thing under MQTT binding, it only gives me RuuviTag smart beacon. Should Air appear in the list as well?
I haven’t installed JAR bindings manually since 2.x, so it might be that I’m missing something important as well.
moi!
@siest4 good question! I should have linked the READMEs. The readmes are now linked to the github release page.
It is kept as a single thing for now so indeed it is the same. Only the channels that are sent by the device have values.
Discovery should work automatically with both bluetooth and mqtt…although at least on my computer the whole bluetooth discovery was flaky (I concluded it unrelated to the ruuvi, more likely a system issue with my computer).
When adding manually, you need to create the thing using the bluetooth MAC address of the sensor.
Hi!
Tried it now - seems I confused the thing types initially because I had both versions of the binding running and didn’t see Air’s measurement channels there. Now it seems to work! I didn’t manage to get scanning working, so I added the thing manually with Air’s MQTT topic.
Very good, fast and efficient job, thank you!
Hmm odd that diacovery is not working for you…
What is your topic name? Does it start with "ruuvi/”?
Yes, it’s the default one, ruuvi/. I can try it again later if you like. I just didn’t invest too much time in it as it’s so easy to configure manually.
Code has been merged in main - early adopters can use the snapshot version!