OZW (ZWave) Control Panel "Refresh Node Info"
Posted: Monday 09 January 2017 23:00
Hi,
As ZWave nodes gets corrupted for me unknown reasons (poor transmission data checksum or data parsing issues?) additional ghost endpoints, may appear more or less frequent over time. This is trashing the zwcfg_xxxx.xml file with junk data that OZW need to read over and over making system just slower and slower. More and more junk data may also be a reason for accelerating the amount of corrupt Node endpoints showing up "system having problem to keep up its tasks in a snow ball effect"?
Anyway, least complicated (not very user friendly) way to restore Node endpoints as today is to stop Domoticz service and delete the problematic node in the zwcfg_xxxx.xml file (this xml file was/is meant to be a Cache file i understod after studying OZW developer area, from Domoticz side it feels very static anyway??).
Next step, after starting Domoticz again, is to use a function in the OZW Z-Wave Control Panel "Controler Drop Down list" selecting "Refresh Node Info". This action asks the selected Node for its Endpoints/Config again. BUT Only if the Node was fist deleted in .xml file). If Node was not first manually deleted the only thing that happens is that Node values/states are refreshed, any corrupt or ghost endpoints will not be fixed!
So, one "half perfect solution" (meanwhile hopefully also a better OZW "node/endpoint handler" may be born) I strongly suggest that the action "Refresh Node Info" could be improved to first clear the node from .xml Cache file.
Please note that the Node itself is always kept/remembered by the Z-Wave Controler! So it is safe to delete/refresh it in the zwcfg_xxxx.xlm Cache file, even the Node generated devices inside Domotics "Devices List" are still associated to its Node in Controller, it will not damage anything in the system or setup if you delete nodes OZW just write them back into the .xml Cache file.
Thanks!
As ZWave nodes gets corrupted for me unknown reasons (poor transmission data checksum or data parsing issues?) additional ghost endpoints, may appear more or less frequent over time. This is trashing the zwcfg_xxxx.xml file with junk data that OZW need to read over and over making system just slower and slower. More and more junk data may also be a reason for accelerating the amount of corrupt Node endpoints showing up "system having problem to keep up its tasks in a snow ball effect"?
Anyway, least complicated (not very user friendly) way to restore Node endpoints as today is to stop Domoticz service and delete the problematic node in the zwcfg_xxxx.xml file (this xml file was/is meant to be a Cache file i understod after studying OZW developer area, from Domoticz side it feels very static anyway??).
Next step, after starting Domoticz again, is to use a function in the OZW Z-Wave Control Panel "Controler Drop Down list" selecting "Refresh Node Info". This action asks the selected Node for its Endpoints/Config again. BUT Only if the Node was fist deleted in .xml file). If Node was not first manually deleted the only thing that happens is that Node values/states are refreshed, any corrupt or ghost endpoints will not be fixed!
So, one "half perfect solution" (meanwhile hopefully also a better OZW "node/endpoint handler" may be born) I strongly suggest that the action "Refresh Node Info" could be improved to first clear the node from .xml Cache file.
Please note that the Node itself is always kept/remembered by the Z-Wave Controler! So it is safe to delete/refresh it in the zwcfg_xxxx.xlm Cache file, even the Node generated devices inside Domotics "Devices List" are still associated to its Node in Controller, it will not damage anything in the system or setup if you delete nodes OZW just write them back into the .xml Cache file.
Thanks!