razberry expert ui config issues (bug?)
Posted: 21 Dec 2014 22:19
hello.
i've discoverd a few issues with the expert ui and how the config parameters is displayed for some devices.
an example:
i have a fibaro motion sensor and some of the settings under configuration is displayed wrong.
for example option 14 & 16 is used to decide how the basic on and off commands should be sent.
if you look at the device at: http://www.pepper1.net/zwavedb/device/601
the on state is listed as -1 but according to the manual on should be 255.
result is that when you read the parameters from the device option 14 & 16 is empty, none of the 3 choices is set.
if you are not observant this results in saving the wrong settings back to the device.
technically -1 is 255 if you convert an signed byte value to unsigned byte but i bet the expert ui doesnt know this or handle it properly.
i also suspect this is a problem in other areas of the config too because above is just one example of where the settings is displayed wrong compared to what is actually saved in the device.
any advice what to do?
i suspect this is a bug
i've discoverd a few issues with the expert ui and how the config parameters is displayed for some devices.
an example:
i have a fibaro motion sensor and some of the settings under configuration is displayed wrong.
for example option 14 & 16 is used to decide how the basic on and off commands should be sent.
if you look at the device at: http://www.pepper1.net/zwavedb/device/601
the on state is listed as -1 but according to the manual on should be 255.
result is that when you read the parameters from the device option 14 & 16 is empty, none of the 3 choices is set.
if you are not observant this results in saving the wrong settings back to the device.
technically -1 is 255 if you convert an signed byte value to unsigned byte but i bet the expert ui doesnt know this or handle it properly.
i also suspect this is a problem in other areas of the config too because above is just one example of where the settings is displayed wrong compared to what is actually saved in the device.
any advice what to do?
i suspect this is a bug