Hey,
I have tested some bindings and I can now see in the log a status update butt the update is not being showt in the habpanel. On the wall pushbutton I use 2 buttons for one lighting point ( A is on and B is off ) butt the log says with both pushes that the light state updated to ON
Same here. it has never worked in OH2 and Raspberry pi. I can confirm that in windows (server 2016) it was working. But I want to move to pi, because my server is really power hungry and i want to implement WOL to wake the beast when i need him. Who maintain the binding?
Here are some logs:
The action i executed was OFF ON. I can see from the trace log he reports twice "Sending status update to PB_GF_Keuken_LB : ON
"
I would love a stable nikobus binding working on OH2 as well.
Currently I have an old nikobus binding running on a separate OH1 SLAVE instance.
Commands and status is being synced to a OH2 MASTER instance via MQTT (eventbus).
Would be great if I could merge both OH instances into one.
Pascal i used to have huge issues as well when running on pi but I have to say that ever since I migrated to a docker setup on my Synology NAS it runs much better.
2.4 but till recent on 2.3. As said running OH in docker container on NAS, used to run it before on a Pi and had massive issues as well, similar to what you describe, once a status update failed the status updates stopped. But don’t experience that any more now
One thing I have done though is configured all of my physical buttons correctly with the link to the modules so that when I press a physical button the binding will know it need to refresh the module
Maybe I was a bit too positive, I noticed issues this morning after months of flawless operation. I have been doing some MQTT config changes and have recently upgraded to OH2.4. So will keep a close eye on this.
Anyway Openhab is the ONLY way for me to connect remotely to my nikobus. In the case that nikobus support drops, If needed, I’m willing to pay someone for development.
For now there are only 3 people that voted for Nikobus, so not sure this will be enough to get it supported. There must be much more people using it.
If support is dropped I will probably look into setting up a seperate entity with just Nikobus and MQTT (possibly even on OH1.8 eventhough I never had 1.8 before). I read somewhere in the forum that it’s really stable and read posts of people downgrading to 1.8 just for nikobus.
Such OH dedicated entity will in essence become a Nikobus to MQTT gateway.
Just added my vote as well. I have read on the forum that a OH2/3 binding for Nikobus is under development? Hopefully this is another way to solve our problem …
Thanks for the good work!
Just to add my two cents - nikobus was the sole reason to start using OH and having latest status was not that super important for me, important was to be able to manipulate switches, dimmers, …
For some reason this stopped working a couple of weeks ago while not touching the OH env for months.
Please let me know if there is any ongoing effort in order to support nikobus binding using v2 and I can help/contribute to make it happen …