2.0.1-rc15 released: Alaram sensor not updated
2.0.1-rc15 released: Alaram sensor not updated
After update to 2.0.1-rc15, noticed that Alarm Sensor Trigger Time of Fibaro FGMS is not updated in Expert UI(although the packets recieved and data is OK).
- Attachments
-
- Z Wave Expert UI - Alarm Sensor not updated2.png (44.14 KiB) Viewed 5337 times
-
- Z Wave Expert UI - Alarm Sensor not updated.png (54.26 KiB) Viewed 5337 times
Razberry B+ 2.0.1-rc25 on ZW500 + 15 devices / Razberry B 2.0.1-rc25 on ZW300 for test
Re: 2.0.1-rc15 released: Alaram sensor not updated
It was never said that parent updateTime should (and will) be updated whenever any child updateTime is updated! If it was so, /ZWaveAPI/Data/<timestamp> would include entire tree, not only changed leafs.
Should be UI issue.
Should be UI issue.
Re: 2.0.1-rc15 released: Alaram sensor not updated
Here are screen shots from the same FGMS sensor - why for SensorBinary report updated all the tree but for Alarm only leaf?
- Attachments
-
- Z Wave Expert UI - Alarm Sensor not updated3.png (44.17 KiB) Viewed 5322 times
-
- Z Wave Expert UI - Alarm Sensor not updated4.png (41.65 KiB) Viewed 5322 times
Razberry B+ 2.0.1-rc25 on ZW500 + 15 devices / Razberry B 2.0.1-rc25 on ZW300 for test
Re: 2.0.1-rc15 released: Alaram sensor not updated
It always was that way, not only in rc15.
Okay, it will be fixed in next release (for a consistent behavior).
Okay, it will be fixed in next release (for a consistent behavior).
Re: 2.0.1-rc15 released: Alaram sensor not updated
Ok, good, it's not a major problem found just while tring to discover a reason of never changing state of Alarm Sensor, but, anyway, consistent and predictable behavior is a good thingpofs wrote:It always was that way, not only in rc15.
Okay, it will be fixed in next release (for a consistent behavior).
Thanks
Razberry B+ 2.0.1-rc25 on ZW500 + 15 devices / Razberry B 2.0.1-rc25 on ZW300 for test