-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issue with arm/disarm #3
Comments
The link you provided is for custom Alarm integration. It does not have any relations to alarm panel integrations/entities. Is this issue exist in latest version v1.0.1? |
I set 15sec sync time on integration. This problems exists because in HA alarm panel state changed after call arm service, but real security system still disarmed and it arm only after several seconds. If integration call Eldes API in this short interval we get disarmed state |
Thanks for info, but still haven't received all answers from you. Integration version? Why this is important? Because I have made some fixes in v1.0.1 for state updates. |
version 1.0.1 For example create automatic to unlock door after Alarm system disarmed. Door unlocked but system still armed. You open and alarm systemd trigger alarm. |
Oh you use from state. I try your solution. Possible it works for me too. |
It works. I do not knonw about arming and disarming states. |
I will update documentation with usage examples later. I just was too lazy to do that earlier. 😀 |
Not working your solution if you lock with Eldes app |
And it wont work, because Eldes is limited with 3 states - armed_home, armed_away and triggered. While my integration has 5 states - arming, disarming and same as eldes. So no way to handle via state trigger. I’m only using HA, so this is not a case for me. |
I have small kids and they using direct keyboard. I must use both. |
I will check possibility to trigger by device not state. This would support both ways. I will write about update 🙂 |
I arm with HA and state changed to armed_away but armed status still false. After several seconds it change to true. If I disarm state change to disarmed bus armed still true. Another problem left that sometimes state changed to unavailable. I think if Eldes cloud do not send response. I set condition on automatic to check from_state != unavailable and fix it. |
I created Pull Request. Now wait status from Eldes cloud. It works a little better because do not show wrong state while alarm system action not completed |
I investigated this issue today. I also set up my automations to use device trigger (should trigger by alarm keyboard or Eldes app) and it works unexpected. Alarm turns on & turns off lights in no reason after automation is triggered. Also Eldes app starts showing incorrect state. I also checked your changes, but basically it does not solve the problem completely. What I found that Eldes API returns HTTP status which was unexpected. I need to handle this correctly. So I will make more investigations and will try to fix that. Until then, feel free to modify it for your needs. |
Yes it do not solve this problem but it solve wrong status. You have wait status from API or send req to API after set actionl. |
You try arm and set arming on HA, but one motion sensor or door is trigered and Arm failed. Eldes always return disarmed and thats all. I can not found way how to know failed action or not. In eldes application you get notification that one zone is trigger and maybe you want disable it. |
You arm or disarm alarm system. It show state but after response from cloud reset to state before. After some time get new response and show again new state. Maybe possible add arming_time? https://www.home-assistant.io/integrations/manual#arming_time
The text was updated successfully, but these errors were encountered: