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

Actions take time to trigger vs. using automation with Home assistant triggers. #987

Open
2 tasks done
VNRARA opened this issue Jun 29, 2024 · 8 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@VNRARA
Copy link

VNRARA commented Jun 29, 2024

Checklist

  • I am using the latest version of Alarmo (latest version can be found here)
  • I checked for similar existing requests (both open and closed) before posting.

Alarmo Version

v.1.10.3

HA Version

2024.6.3

Bug description

Actions created in the action tab take significantly longer to start vs. just doing it myself using Home Assistant automation:

I've setup actions for 'alarm triggering', 'almost triggering' and 'stop triggering' and 'turning off' scenarios. But they were so slow to fire, even in my own home. After I realised I could also make an automation to debug what is happening, I found that the automation is instant when triggering the same simple script vs. doing it native in Alarmo.

I found that just pressing test wouldn't replicate the issue and also fire instantly.

Steps to reproduce

Created an action {alarmo/actions}.
Enable alarm
Let action get triggered by correct scenario happening.
I have to wait for script to get called but it can take up to 30 sec to actually do something.

(vs the automation method is instant).

Relevant log output

Logs don't show much i guess.
@VNRARA VNRARA added the bug Something isn't working label Jun 29, 2024
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jul 30, 2024
@VNRARA
Copy link
Author

VNRARA commented Jul 30, 2024

Still an issue / haven't seen a fix

@trantoriana
Copy link

And here i am considering moving my automations into event triggers.

While not fixed, it would be nice to see an acknowledgement if this is reproduceable.

@github-actions github-actions bot removed the Stale label Jul 31, 2024
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Aug 30, 2024
@VNRARA
Copy link
Author

VNRARA commented Aug 31, 2024

Haven't seen a fix

@github-actions github-actions bot removed the Stale label Sep 1, 2024
@VNRARA
Copy link
Author

VNRARA commented Sep 20, 2024

Dudes gone dark it seems..

@nielsfaber
Copy link
Owner

Sorry for the lack of response from my side, but frankly I don't know how to speed up the automations.
There is no delay in the code, and automations should be executed instantly and in parallel (if multiple are triggered), so things are configured to be as quickly as possible.
If you have any experience with python, feel free to suggest code improvements (see automations.py file).
My knowledge about asynchronous programming may be lacking here.

Perhaps this could be due to your own configuration? Is there some automation triggered with internal waiting time?

@VNRARA
Copy link
Author

VNRARA commented Oct 24, 2024

Thanks for getting back to me. I remade the same automations using the native way and with the same yaml and it's immediate. Any way to make it implement it differently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants