Ah yes, it’s a bug . You can either get the updated yaml or just remove the alarm_panel:: suffix from line 464 in the yaml. I’ve updated the repository with the fix.
Go it. But both panels are still not showing any data.
I tried to see if I have any javascript loading errors but nothing shows up.
Any clues?
Js file and resources are ok.
Make sure that the fields you use in the card lovelace configuration match what you have setup in your esphome yaml. If using the dev branch,use the lovelace config from dev since the example field names differ. You can double check what is set in HA by doing a search for the services in the developer section of HA.
Ok got it. The entities get created like this binary_sensor.dsc_alarm_ac_status whereas the panel yaml contains this binary_sensor.dscalarm_ac_status.
There is an underscore _ in the entity ID.
Thanks.
Hi Alain,
I’m uncertain whether this is a coincidence or if something actually occurred, as everything was functioning well for a few weeks. However, I’ve noticed that the partition status briefly shows ‘not_ready’ again for a few days when disarming, which shouldn’t normally happen between ‘armed_home’ and ‘disarmed’.
At the same time a see this as partition status message:
Edit: I need to add, that it’s not happening every time. This wasn’t the case today, when the status went straight from armed_home to disarmed and didn’t have the invalid BF code in as a partition message.
Do you know why is this occurring?
There is no way for me to know unless I see logs. Please post esphome logs during disarming so we can see what is going on. It could be it gets input during a disarm sequence, etc. Hard to know. I can’t duplicate it.