Upps, coffee level was too low this morning, here we go:
For now I didn’t find any cure to my problem.
More then that I also found that my item didn’t update when I change my Physical button. (After log time the real state is update with the power consumption)
I try update z-wave binding to latest snapshot version
I try rest my fibaro device
I run openhab from eclipse trying to debug it but still same issue.
I has other 3 roller shutter fibaro device who report every thing just fine.
But in this case (FGS223) something is still missing
The only direct update I get is for
zwave:device:abd624d5:node8:switch_binary
zwave:device:abd624d5:node8:meter_watts
zwave:device:abd624d5:node8:meter_kwh
other
zwave:device:abd624d5:node8:switch_binary1
zwave:device:abd624d5:node8:switch_binary2
zwave:device:abd624d5:node8:meter_watts1
zwave:device:abd624d5:node8:meter_watts2
zwave:device:abd624d5:node8:meter_kwh1
zwave:device:abd624d5:node8:meter_kwh2
get update after a long time (more then hour) or after I restart openhab (sometimes it’s also update when I change some item configuration in items file)
It’s look like something with the multi channel.
I take this issue few steps forward and contact Vesternet tech support (because the openhab second button not update when I change and not because to consumption issue)
they told me "it’s a compatibility problem with OpenHAB that they’ll need to resolve"
and
It happens in other Z-Wave controllers too - http://forum.micasaverde.com/index.php/topic,38961.0.html
I need to your help to double check your openhab second button update when you change your physical button status.
and If you are also using “Z-Wave Plus Aeotec Z-Stick USB Controller”
I also try using Domoticz application to confirm it’s not openhab issue and also check with serial port monitor to confirm no message coming on change.
so before I ask then to replace my Fibaro FGS223
Can you confirm you getting update when you change status on physical button?
Thank you.
Confirmed, everything is working fine:
Pressing the two physical buttons:
2017-10-19 14:16:58.389 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from OFF to ON
2017-10-19 14:16:59.612 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from OFF to ON
2017-10-19 14:17:01.638 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from ON to OFF
2017-10-19 14:17:02.988 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from ON to OFF
Pressing the software buttons in BasicUI:
2017-10-19 14:23:18.715 [ome.event.ItemCommandEvent] - Item 'FibFGS223_1_Sw_1' received command ON
2017-10-19 14:23:18.727 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from OFF to ON
2017-10-19 14:23:23.036 [ome.event.ItemCommandEvent] - Item 'FibFGS223_1_Sw_1' received command OFF
2017-10-19 14:23:23.051 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_1 changed from ON to OFF
2017-10-19 14:23:24.795 [ome.event.ItemCommandEvent] - Item 'FibFGS223_1_Sw_2' received command ON
2017-10-19 14:23:24.818 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from OFF to ON
2017-10-19 14:23:28.708 [ome.event.ItemCommandEvent] - Item 'FibFGS223_1_Sw_2' received command OFF
2017-10-19 14:23:28.735 [vent.ItemStateChangedEvent] - FibFGS223_1_Sw_2 changed from ON to OFF
Firmware version of FGS223:
openHAB build #1061
, zwave development binding version 20171017
So no issues with this device in openHAB!
Edit:
No, zwave.me usb stick
Many thanks @sihui
so it’s not good enough I need to check it with same controller
For now just yo update
I saw this post (hope no one will kill about putting “home-assistant” post here )
I will try it later after I change controller setting
And update here
I’m using razberry v1. No problem with updates.
Regards S
HI
I keep debug this issue and find there is problem with the endpoint
still don’t know how it fix it but this what I change in order to make it work
Changes:
Association Groups.1 = > openHAB Controller
Association Groups.2 = > openHAB Controller
Association Groups.4 = > openHAB Controller
And play with parameter: 31,36 (change parameters to 254 and 253 Although ui show the default parameter (255 and 255))
don’t know how it’s fix it but now it’s work
Thanks for help guys
My guess is that this is related to the use of the multichannel association class which I’m looking at. This is probably changed in newer versions of the software.
I’m reading this in my phone so it’s a bit difficult to check everything but I would suggest to use the development version if you’re not already doing so as that is where the fix is being processed.