Alarm from Home Assistant MQTT format into MSR
-
Hi everyone and happy new year!
I've recently moved to an alarm integration that's using HASS MQTT format but I'm not pushing it to HASS as I've just mapped it as MSR entities.
security_mode
capability has less options and I'm wondering what's the best way to map other statuses. Is adding my own values considered safe or should we ask for more default statuses? Paging @toggledbits here, because I'm not sure a new ticket on mantis at this point is preferred instead of a post.Then, I'm just double checking what's everyone using regarding alarm panels.
I'm using
string_sensor.value
to save the zone that's been armed/disarmed andkeypad
to keep track of the code/users/actionsFor the siren I'm just using a
binary_sensor
, withstring_sensor
in the same device to get the zone that's been triggered.What are you guys doing? Thanks!
-
Reactor doesn't restrict attribute values to only those declared in a capability. You can set an entity attribute to any value you want. I will happily add values to the standard definition if they seem universal; having them defined by the Z-Wave or ZigBee specs also contributes a vote.
-
I don't have a Zwave/Zigbee Alarm, so I really don't know. I tried to search for something, but these alarms are not common. Right now, I'm just setting the same value coming from the payload.
I had a virtual AlarmPartition under Vera and it was not mapped to security_mode, but that's fair, because I'm quite sure this capability was used in plugins and not by real devices.
EDIT: since we're at this, is it safe to assume that the values reported in the docs (http://msr.bochicchio.it/docs/Standard-Capabilities/#other) are lower case instead of the case reported in the doc page? Thanks @toggledbits
-
T toggledbits locked this topic on