Hey,
I have just set up everything with the Nikobus and i have the same issue… No status update after physical button click.
I would also like to see if there is a fix/workaround for this…
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
I will try some more keep you posted!
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
"
Received: #N961626
2018-12-08 00:44:17.380 [TRACE] [kobus.internal.core.NikobusInterface] - Received: #N9
2018-12-08 00:44:17.405 [TRACE] [kobus.internal.core.NikobusInterface] - Received: 61626
2018-12-08 00:44:17.490 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=#N961626, repeats=2]
2018-12-08 00:44:17.494 [TRACE] [nding.nikobus.internal.config.Button] - Processing command #N961626
2018-12-08 00:44:17.494 [TRACE] [ding.nikobus.internal.NikobusBinding] - Sending command with ack $101266444853D1
2018-12-08 00:44:17.497 [TRACE] [s.internal.core.NikobusCommandSender] - Sending command $101266444853D1
2018-12-08 00:44:17.496 [TRACE] [ding.nikobus.internal.NikobusBinding] - Sending status update to PB_GF_Keuken_LB : ON
2018-12-08 00:44:17.499 [DEBUG] [kobus.internal.core.NikobusInterface] - Sending : $101266444853D1
2018-12-08 00:44:17.540 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=$0512, repeats=1]
2018-12-08 00:44:17.540 [TRACE] [kobus.internal.core.NikobusInterface] - Received: $0512
2018-12-08 00:44:17.544 [TRACE] [obus.internal.core.NikobusAckMonitor] - Processing nikobus command $0512
2018-12-08 00:44:18.084 [TRACE] [kobus.internal.core.NikobusInterface] - Received: $1C664400FF
2018-12-08 00:44:18.109 [TRACE] [kobus.internal.core.NikobusInterface] - Received: 000000000017DD1
2018-12-08 00:44:18.134 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=$1C664400FF000000000017DD1B, repeats=1]
2018-12-08 00:44:18.134 [TRACE] [kobus.internal.core.NikobusInterface] - Received: B
2018-12-08 00:44:18.137 [TRACE] [obus.internal.core.NikobusAckMonitor] - Processing nikobus command $1C664400FF000000000017DD1B
2018-12-08 00:44:18.140 [TRACE] [obus.internal.core.NikobusAckMonitor] - Received expected ack '$1C664400FF000000000017DD1B'
2018-12-08 00:44:19.348 [TRACE] [kobus.internal.core.NikobusInterface] - Received: #N961626
2018-12-08 00:44:19.379 [TRACE] [kobus.internal.core.NikobusInterface] - Received: #N961626
2018-12-08 00:44:19.425 [TRACE] [kobus.internal.core.NikobusInterface] - Received: #
2018-12-08 00:44:19.449 [TRACE] [kobus.internal.core.NikobusInterface] - Received: N961626
2018-12-08 00:44:19.535 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=#N961626, repeats=3]
2018-12-08 00:44:19.539 [TRACE] [ding.nikobus.internal.NikobusBinding] - Sending command with ack $101266444853D1
2018-12-08 00:44:19.539 [TRACE] [nding.nikobus.internal.config.Button] - Processing command #N961626
2018-12-08 00:44:19.542 [TRACE] [s.internal.core.NikobusCommandSender] - Sending command $101266444853D1
2018-12-08 00:44:19.544 [TRACE] [ding.nikobus.internal.NikobusBinding] - Sending status update to PB_GF_Keuken_LB : ON
2018-12-08 00:44:19.545 [DEBUG] [kobus.internal.core.NikobusInterface] - Sending : $101266444853D1
2018-12-08 00:44:19.572 [TRACE] [kobus.internal.core.NikobusInterface] - Received: $0
2018-12-08 00:44:19.597 [TRACE] [kobus.internal.core.NikobusInterface] - Received: 512
2018-12-08 00:44:19.597 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=$0512, repeats=1]
2018-12-08 00:44:19.603 [TRACE] [obus.internal.core.NikobusAckMonitor] - Processing nikobus command $0512
2018-12-08 00:44:20.109 [TRACE] [kobus.internal.core.NikobusInterface] - Received: $1C66
2018-12-08 00:44:20.134 [TRACE] [kobus.internal.core.NikobusInterface] - Received: 4400FF00000000F
2018-12-08 00:44:20.158 [TRACE] [kobus.internal.core.NikobusInterface] - Received: F092D96
2018-12-08 00:44:20.158 [DEBUG] [internal.core.NikobusCommandReceiver] - Received NikobusCommand [command=$1C664400FF00000000FF092D96, repeats=1]
2018-12-08 00:44:20.163 [TRACE] [obus.internal.core.NikobusAckMonitor] - Processing nikobus command $1C664400FF00000000FF092D96
2018-12-08 00:44:20.166 [TRACE] [obus.internal.core.NikobusAckMonitor] - Received expected ack '$1C664400FF00000000FF092D96'Hi davy,
Is there a way that you can help the Nikobus users?
We would really appreciate this 
I started a issue in github
(https://github.com/openhab/openhab1-addons/issues/5600#event-2022798065)
I just get the nikobus trace logs to work (I do not see any button presses in it but the rest seems to work) an wil post the result soon.
Is there a possibility to start an OH2 binding?
Thanks in advance!
1 Like
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.
Rhonny, Are you running Nikobus binding on OH2 without any issues? Status is always updated?
If yes, can you share which versions you are running?
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
Thanks for your swift reply.
Which version of Nikobus binding are you running?
don’t know just load it through the addons.cfg file in the addons line
binding = nikobus1, …HERE GO MY OTHER BINDINGS…
You should be able to find the version in your /addons folder
under bindings addons it says binding-nikobus1 - 1.13.0
So 1.13.0
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
Switch NB_RB_eetplaatstafelboven_BP1_C {nikobus="#N276A77[09B9-2]"}
If I don’t do that states get out of sync as the binding does not know when you press a wall switch otherwise.
So maybe that’s what you are refering to ?
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.
Hi all there’s a poll running for keeping OH1 compatibility in OH3. Please vote for nikobus!
1 Like
Where is the poll? Can’t seem to find it.
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!