-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fade feature causes flash writes #7262
Labels
duplicated
Result - Duplicated Issue
Comments
Already solved. Please update to the latest Tasmota in the development branch (thehackbox.org/tasmota/tasmota.bin) Thanks. |
I would rephrase to "soon to be solved" instead of "already solved". |
s-hadinger
pushed a commit
to s-hadinger/Tasmota
that referenced
this issue
Dec 20, 2019
6 tasks
arendst
added a commit
that referenced
this issue
Dec 20, 2019
Fix Fade would ignore ``savedata 0`` and store to flash anyways (#7262)
Now solved. Thanks for reporting. |
Nice work. Thanks! |
marius
pushed a commit
to marius/Tasmota
that referenced
this issue
Dec 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PROBLEM DESCRIPTION
With all
flash save
options turned OFF andfade
turned ON any RGB change is still written to Flash.REQUESTED INFORMATION
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:TO REPRODUCE
reset 5
backlog poweronstate 1; savedata0; setoption0 0; restart 1;
backlog fade 1; speed 10; restart 1
EXPECTED BEHAVIOUR
If
setoption0 0
andsavedata 0
are set no flash writes should occur.SCREENSHOTS
N/A
ADDITIONAL CONTEXT
I prefer to keep smart-lights functional for ordinary light switches, so when they are turned off by cutting the power they should return to their pre-saved RGBW value the next time they are turned on. Basically when the light is turned on it can be controlled thought MQTT but when the power is cut it should restore to it's normal light intensity the next time it's turned on by reapplying power.
The text was updated successfully, but these errors were encountered: