Replies: 3 comments 4 replies
|
Add this filter to your partition state in your esphome yaml. This will send "disarmed" instead of "not_ready" to home assistant. |
2 replies
|
The esp8266 is supported but you need to convert your yaml config to the new format. |
1 reply
|
You will need to remove the device from home assistant /esphome add-on and re-add it since the entity names are different now due to the esphome changes. The log looks fine. Edit: I had a look at your code and it's still showing the wrong format for the zones. The platform needs to be "dsc-alarm-panel" and not "template" old format: New format: |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Recently i have noticed the bellow error in the logs. I did not change anything to the code except esphome update.
What i can do to fix it?
Thanks!
Logger: homeassistant.components.template.alarm_control_panel
Source: components/template/alarm_control_panel.py:295
integration: Template (documentation, issues)
First occurred: 01:02:28 (2267 occurrences)
Last logged: 21:03:49
Received invalid alarm panel state: not_ready for entity alarm_control_panel.safe_alarm_panel. Expected: armed_away, armed_custom_bypass, armed_home, armed_night, armed_vacation, arming, disarmed, pending, triggered, unavailable
All reactions