-
Notifications
You must be signed in to change notification settings - Fork 41
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
Lighting schedule doesn’t work properly #74
Comments
Same here, beta 4 also affected. |
I found a possible solution, it seems that relay has inverted logic in script. Turn off manual control edit fruxe script with sudo nano /var/www/html/actions/fruxepi.py Lights
#I have edited this line original in this section are ON i have changed in OFF #Same here i have switched OFF to ON Same here i have inverted on to off and vice versa: Lights OFFdef lightsON(gpioPIN, reverseRelay): Lights ONdef lightsOFF(gpioPIN, reverseRelay): Now my cron job work perfectly but i dont think cron is the best way to do this if you switch to manual and you try to back in automatic light remain off until cron call the program to say lights ON It need more code for better automation. |
Could the same be applied to fans? |
Running 0.3-beta and have been fighting with it. It doesn’t seem to follow the schedule no matter what I try. Also the listed time until lights on or off always just reflects the current time.
I’m pulling it today to try out some other automation software because having a proper light schedule is critical.
The text was updated successfully, but these errors were encountered: