ZWave initialisation

[mike9665]

With the domoticz upgrade to 2024.1 I have migrated from openzwave to zwavejs-ui in a docker running on rpi 4 with bullseye. After a few difficulties with the conversion I am happy with the set up excepts that with open z wave I used to run a domoticz start event that called some python code that checked the zwave hardware via json to verify that the zwave devices were all queried and the code would then email me the results of the query. I can't seem to find an alternative approach with zwavejs ui. I have tried using the status timestamps of the mqtt date for each device but the status timestamps for each device are earlier than the execution time of my python code and therefore are meaningless in regard to my needs.

Does anybody have any suggestions as to how I can verify that mt zwave network is fully initialised following a restart of domoticz.

Mike

[waltervl]

As Zwave-JS-UI is seperated from Domoticz, in contrary of Openzwave, there is probably no need for your script.

[lost]

As Zwave-JS-UI is seperated from Domoticz, in contrary of Openzwave...

That's not the single exemple of what could be done from dz APIs linked to OZW. See alarm wiki and zwave jamming detection stuff I wrote years ago when anyone could edit the wiki. With zwavejs being out and missing such derived use of existing HW, would just jave to forget this!
Problem is this thing proved useful, with 2 or 3 jam detects in deep night hours when no-one was at home!

[waltervl]

See alarm wiki and zwave jamming detection stuff I wrote years ago when anyone could edit the wiki. With zwavejs being out and missing such derived use of existing HW, would just jave to forget this!
Problem is this thing proved useful, with 2 or 3 jam detects in deep night hours when no-one was at home!

Currently the show your projects subforum viewforum.php?f=38 combined with a GitHub repository is the best way to share your special scripts.