Then locate two buttons that turn your light (output 8) to ON and OFF and link those two button’s channels to items:
All my wall buttons are single pushbuttons to switch the lights ON or OFF since the led in the button reflects the status if the light is ON or OFF.
Can i anticipate on this to match your example? Or should i change my setup or …
gBasement_HomeOffice_PushButton_Light_Toggle - is linked to button channel of your Nikobus push-button thing that has the same address as your Nikobus physical button used to turn channel-8 ON and OFF and
gBasement_HomeOffice_Light_Ceiling_Powered - is linked to channel-8 of your switch module, which above button control.
Looking at UID: nikobus:rollershutter-module:2f0a674788 there seems to be missing bridge id in the UID - compare with UID: nikobus:push-button:ead36cb534:1028F2 - so no ead36cb534. I would expect something like
I can reproduce the same if I create a new thing (i.e. rollershutter module) and select bridge after thing is created. Can you please try removing the rollershutter module and create it again, just make sure to select the bridge before creating the thing and let me know how it goes?
That was indeed the catch. Thx for the quick reply.
I had that on one module before and then I found it, but I guess I must be overlooking. The config for OH3 is sometimes overwhelming but a big leap forward compared to OH2.3 where I come from.
Hello
I have Nikobus installation in my house since 2007
I’m playing with domotics such as esp8266, mqtt, and others stuff like pi, 1-wire… (domoticz on pi in the past) . Mainly for collecting data to grafana for charting
I don’t use OH for the moment , never installed it , total dummies
I’m interested to control some basic features of my Nikobus and this plugin for oh seems the only existing solution
My idea is to pose on/off some lights and control my sun blinds automatically via mqtt or http from an esp8266 that would send commands as I don’t want to configure oh for all my sensors and system
Is that easily possible with your plugin and default oh?
Just install OH on a rpi4.
All you want is possible with OH. Some learning curve, but once running it works flawlessly.
As far as I know is OH the only system that integrates Nikobus.
To be able to control Nikobus, be aware that you need a PC-Link or PC-Logic module
I’ve migrated to OpenHAB3 and Nikobus V2, everything is working fine but breaks after a restart of OpenHAB for Nikobus Button linked trigger.
Here is the Button / Trigger definition. Basically, I use one physical Nikobus button trigger to a rule that opens and another one that closes my Velux.
If I redo the Button trigger after OpenHAB restart, everything works as expected. Restart OpenHAB breaks to button definition with HANDLER_CONFIGURATION_PENDING
I’ve check without the rules, same behavior of the trigger channel on the nikobus button. All fine and working until I restart openhab where I then get HANDLER_CONFIGURATION_PENDING
Can you try adding delay: 0 so your yaml will look something as below (copied your setup but bridge name is different in example below so please do not just copy+paste the whole yaml):
Thank you ! That’s resolved the issue. When you create the trigger in the UI the delay is displayed by default with “0” but it’s not reflected in the code unless you manually input the 0.