Closed igorlopez closed 2 years ago
Ok, some further studies into why the start of the network shows this:
2021-08-11 15:02:43.470 Always, OpenZwave Version 1.4.3428 Starting Up
I checked in my open-zwave repo where I did build the libs and there I can see in the source that it should have been:
2021-08-11 15:02:43.470 Always, OpenZwave Version 1.6-1930-ga8aa6341 Starting Up
instead so it looks like that when I start the network from my python application it somehow uses a lib (not named libopenzwave.so) that is for version 1.4 which I know lacks support for Central Scenes so I think this issue can be closed and I need to find out what lib the python module is actually talking to.
I have the FGPB-101 button connected to a Rasberry PI3 with a RaZberry Hat. The button is found during initialisation of the network but when I press the button I am getting the following response:
I am running latest master built on the Pi and am using the openzwave python repo to interface with nodes and the python callbacks does not happen for SIGNAL_VALUE_CHANGED but it does so with another node.
Pasting in part of what is written to the console when my python app is starting(running debug level for python logger):
Comparing the different ValueAdded blocks between the Fibaro button and the Telldus Power Outlet gives diff in supported commandClasses (regarding switch) FGPB101 Button
TZWP-102 Plug-in Switch
And I have seen a lot of issues with handling of central scenes.
What can I do to debug deeper? Since I have not read the Z-Wave specification I do not now how the system is supposed to work.
Another diff between the nodes is that the FGPB-101 goes into sleep mode but awakes when button is pressed, e.g. one can see the message being sent to the controller but no notification/callback was issued. When I press the button on the Telldus power outlet I get a lot more info in the console: