I’ve pulled your image and am testing it with a SmartCom and an Elite 64. Looks good so far - it connects to the alarm, the autodiscovery works nicely and it pulls all of my sensors in correctly (I haven’t tried arming the alarm as I’m not brave enough to risk waking kids up!).
As there’s no GitHub repo for it it would probably be useful to have 1 forum post for feedback, questions & suggestions.
Glad to hear it’s working I’m really keen to get feedback from people such as yourself using the bigger panels as there are some API differences between the panel types.
I’ve pushed an update to the container which should fix the areas issue. Can you try deleting the add-on completely and re-adding? Hopefully it should all work
there might be a slight problem with the areas, some of them are duplicated. see log below:
2020-09-13 22:43:18 - INFO: Fetched area 1: House
2020-09-13 22:43:18 - INFO: Fetched area 2: Detached Garage
2020-09-13 22:43:18 - INFO: Fetched area 4: Area D
2020-09-13 22:43:18 - INFO: Fetched area 2: Area B
2020-09-13 22:43:18 - INFO: Fetched area 4: Area D
2020-09-13 22:43:18 - INFO: Updating all zone states
2020-09-13 22:43:18 - INFO: Updating all area states
Ah, sorry about that. I’ve pushed another fix which should fix the issue for you. I think you’re the first person to run the app on one of the larger panels so you’re unearthing a few bugs
But in the front end it shows buttons for “Arm Away” & “Arm Home”, I think it should come up with .“Arm Away” & “Arm Night”, for that config. Unless I’ve missed something.
Unfortunately the frontend is configured separately and the app can’t control it. You’ll just need to change the ‘states’ config within the Lovelace card: https://www.home-assistant.io/lovelace/alarm-panel/.
ah didn’t know about the Alarm Panel card until now, thanks for pointing it out.
I’ll let you know if I find anything else…
I don’t know what anyone else thinks, but i think it would be nice if there was a config option for Entity IDs so that they use just zone numbers and area numbers.
That way any changes in automaions and lovelace configs etc are not affected if the panel names are updated or changed.
Any thoughts about allowing outputs to be controlled with this? It looked like it was possible from the docs, and not just the “pc control” outputs either … unless I read them wrong.
I’ve just noticed a small problem with my Elite 168 the Texecom2mqtt code. I have an outdoor sensor set to “Latch Key” type, which chimes the panel but doesn’t arm with the alarm, In home assistant the entity for this zone is not triggered, I know it is outputting because it did work before with my previous integration in node red by i.j. levick from here - http://texecom.websitetoolbox.com/post/nodered-flow-for-texecom-elite-simplecrestron-protocol-10294046?&trail=15
Daniel, any chance you could look at this please?
sorry I posted this somewhere else but cant find it now…