Sound great news. However, as the binding is currently reviewed, I will fix the review point to get it to the official OH release first. If I start now implementing new features, the binding will stay SNAPSHOT for ever. But of course I can look into the new API for the future improvements…
Especially the push sounds interesting, but will introduce some questions.
- As far as I understand, the OH2 architecture team does for some reason not like if a binding exposes its own HTTP endpoint. But maybe the mower can be configured on what exact URL to call, and with a bit of luck the official REST API would already work!?
- Also I read there something about MQTT. That would be probably even a better alternative. And also here the robonect binding is not important anymore, as MQTT should theoretically be generic enough. The drawback is, one needs to setup a mqtt broker to use it.
- But what happens if the mower is out of WIFI Range… So far the binding was able to detect this more or less reliably.
- Still the binding will be useful to actually send commands to the mower like starting a job.
don’t you have a running project with these guys? : https://www.robotshop.com/en/robot-snow-blowers.html