Battery or AlarmSensor not available for logging
Posted: 01 Feb 2017 13:56
Hi,
this is the 2nd (or 3rd) time it happens to me that SensorValueLogging (and some of the previous incarnations of the module), stops being able to handle Battery or AlarmSensor values.
While I understand (and like) how batteries are shown apart both in the Expert and SmartHome UIs... for me it's really important to get those values logged (for being used with some integration with other non-z-wave devices and main controller). Specially the AlarmSensor one (used for tamper/manipulation by some - old - devices) are critical here (security-wise).
Is there any reason for keepig them (and surely others) out from logging? Right now I've the module edited to accept them (and it seems to work, despite I cannot edit the sensor name anywhere and get the default zway-xxx-yyy-zzzz naming from them), but for sure will lose those customizations with next upgrade.
IMO the most classes that can be used there, in logging, and also be freely named the better. Maybe I'm wrong.
For your consideration, TIA and ciao
this is the 2nd (or 3rd) time it happens to me that SensorValueLogging (and some of the previous incarnations of the module), stops being able to handle Battery or AlarmSensor values.
While I understand (and like) how batteries are shown apart both in the Expert and SmartHome UIs... for me it's really important to get those values logged (for being used with some integration with other non-z-wave devices and main controller). Specially the AlarmSensor one (used for tamper/manipulation by some - old - devices) are critical here (security-wise).
Is there any reason for keepig them (and surely others) out from logging? Right now I've the module edited to accept them (and it seems to work, despite I cannot edit the sensor name anywhere and get the default zway-xxx-yyy-zzzz naming from them), but for sure will lose those customizations with next upgrade.
IMO the most classes that can be used there, in logging, and also be freely named the better. Maybe I'm wrong.
For your consideration, TIA and ciao