Skip to content
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

[Enhancement] Question about Toggling ArmedStatus #70

Open
jimboca opened this issue Jun 25, 2023 · 0 comments
Open

[Enhancement] Question about Toggling ArmedStatus #70

jimboca opened this issue Jun 25, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@jimboca
Copy link
Contributor

jimboca commented Jun 25, 2023

Is your feature request related to a problem? Please describe.
Yes

Describe the solution you'd like
Not sure how to handle this

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Here's the issue, seems like this is how ELK handles it, but just wondering if you have any advice. When I disarm the system, the callback is called with the disarm, but then right away it's called again with the previous arm status, then called again with disarm.

I disarm:

2023-06-25 13:52:06,292 Command    udi_interface      INFO     Area:cmd_set_armed_status: area_1:Home: elk.arm(0,****

Then I get these:

2023-06-25 13:52:06,326 ELK-55966  udi_interface      INFO     Keypad:callback: keypad_1:Master Bedroom: changeset={'last_user_time': datetime.datetime(2023, 6, 25, 20, 52, 6, 326132, tzinfo=datetime.timezone.utc)}
2023-06-25 13:52:06,369 ELK-55966  udi_interface      INFO     Area:callback: area_1:Home: cs={'armed_status': <ArmedStatus.DISARMED: '0'>, 'timer1': 0, 'timer2': 0}

Then this

2023-06-25 13:52:06,409 ELK-55966  udi_interface      INFO     Area:callback: area_1:Home: cs={'armed_status': <ArmedStatus.ARMED_STAY: '2'>}

And finally:

2023-06-25 13:52:06,449 ELK-55966  udi_interface      INFO     Area:callback: area_1:Home: cs={'armed_status': <ArmedStatus.DISARMED: '0'>, 'arm_up_state': <ArmUpState.READY_TO_ARM: '1'>}

In the end this is all fine, it just causes me other issues with it toggling back and forth.

@jimboca jimboca added the enhancement New feature or request label Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants