-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entities suggestion #3
Comments
It's a tough one. There a multiple events/states that AMC is providing: Group/Area:
Zone:
I already struggled to map those to HA entities - you will see zones as If I replace groups with, say, multistate selector users will loose the ability to see if group is ready or not. Or some other subtleties. I can make that selector as additional template entity, and demote groups to diagnostic level. |
Hi, sorry if I'm back to the topic after some months. I now understand the issue for the groups/areas, so it's ok to keep it as it is. Just a suggestion for Zones: maybe they should be managed using "HA logic" instead of "AMC logic"; e.g.:
I know this would add a lot of entities, but it would uniform the logic management within HA of sensors from AMC and from other devices (E.g. zigbee). |
Hi, thanks for the great work - tested on x824.
May I suggest to re-organize some of the entities? Almost everything now is an alarm control panel with one state.
For example, for the four G1-G2-G3-G4 alarm activations possible (the Groups), there are four alarm control panels, named with the Gx labels, each with "away" and "disabled" states. In fact it should be one alarm control panel, with five possible activations states, named as in the labels plus a disabled state. Groups are mutually exclusive so this doesn't apply to Areas, which could be kept as separate alarm control panels.
The text was updated successfully, but these errors were encountered: