as you know, everything can be integrated into Openhab, sometimes you just need to write a binding
Same applies for my new BBQ thermometer, the WlanThermo. It started as a DIY project, but can now be bought online as a ready-to-use product. I was tired of always loosing the connection to my bluetooth device, so I bought this Wifi version.
Of course, the next step was to integrate it into Openhab. There were some approaches to use the general HTTP/MQTT binding, but all of them seemed to complex or did not provide the features I was looking for. Besides, I wanted to tackle the challenge of writing my own first binding…
Therefore, I proudly present the WlanThermo binding!
The binding is accessing the device locally via HTTP. Providing the login credentials is optional, if omitted, all channels are read-only.
It provides the data of all temperature channels (current temperature, min/max alarm threshold, …) as well as some general data of the device itself (state of charge, signal strength, …). Additionally, there are some alarm channels you can use in your rules.
Here are some screenshots of the bindings data in BasicUI:
For further details, please refer to the WlanThermo Binding Docs.
You will find examples for the .items and .sitemap file over there as well.
It has been tested with WlanThermo Nano V1+ and Mini. Pitmaster support is currently only available for WlanThermo Mini.
I’d be happy to receive your feedback!
- Since Openhab 2.5.9, the WlanThermo Binding can be installed directly via PaperUI!