-
Notifications
You must be signed in to change notification settings - Fork 120
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
enable/disable no longer possible after update to 2024.6.1 #972
Comments
You should call the service "alarmo.disarm" from now on and not "alarm_control_panel.alarm_disarm" |
Hi Omrizn, thanks for getting back on this! How can I do this? The control panel currently has this code for example:
Also, if I have a look on my entities, they are still called like before
So what do I have to change to use alarmo.disarm on my different zones? Also, was this change in the release notes and I've overseen it? Thank you again and cheers |
Please share a screenshot of the mode settings for the ‘erdgeschoss’ area in alarmo and a screenshot of the properties of the corresponding alarm_control_panel entity in the Developer Tools - states panel. |
Same problem here : "No se pudo llamar al servicio alarm_control_panel/alarm_disarm. AlarmoBaseEntity.async_alarm_disarm() takes 1 positional argument but 2 were given" |
@TheChosenOne1984 |
Hi @nielsfaber , I've put this to disabled this morning as I was not able to deactivate the alarm. I was hoping this would help and forgot to enable this again.
|
@TheChosenOne1984 you can fix that issue yourself by updating alarmo. I don’t spend time on bug issues from users who use outdated versions. |
@nielsfaber , So, sorry again and thank you! |
Alarmo Version
v1.10.0
HA Version
2024.6.1
Bug description
After updating to 2024.6.1 its no longer possible to enable or disable the alarm.
Not via a control panel in the browser gui or android app and also not via sonoff nspanel (esphome).
If you need further information, let me know.
Thanks a lot!
Steps to reproduce
Try to enable or disable the alarm.
The attached error message is shown.
Relevant log output
The text was updated successfully, but these errors were encountered: