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

Bug? Script is turning off Devices when run by another automation #50

Open
t0bse opened this issue Jan 29, 2024 · 2 comments
Open

Bug? Script is turning off Devices when run by another automation #50

t0bse opened this issue Jan 29, 2024 · 2 comments

Comments

@t0bse
Copy link

t0bse commented Jan 29, 2024

Hi,
i tested the script with my LED light in the kitchen. It turned the light on, like i expected it, but the script is also turning the light off after it ran / no more PV power

see the screenshot, today morning (no pv power yet) the motion detector is turning on the light, but the script turns it off

image

@stefan73
Copy link
Contributor

stefan73 commented Feb 6, 2024

That is by ddesign. The script will turn the appliance off, if there is not enough power. This is indepentend on why the automation got turned on. If you want to override this, you need to disable the automation. Then you / another automatism can control again till you enable the automation again.

@zbuh
Copy link

zbuh commented Apr 24, 2024

Also happens to me.
The script should only turn off, when it was turn on previously by it.
managing the automations, implies turning on/off with certain conditions(which ones? solar production ?)
And when turning them off, are the controlled devices off or on??

This will lead to uncertain behaviours...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants