-
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
Disabling DST? #8528
Comments
To enable dst and std times you need to use command timezone 99. As you have set timezone -3, dst is not used. |
As long as timezone is NOT set to 99 it doesn't use DST. SO althought it is displayed it makes no use of it. |
Ah we just crossed. |
Closing this issue as it is duplicated. Sorry. Please, read the Contributing Guideline and Policy. Thanks. Support Information (Guide)See Wiki for more information. |
PROBLEM DESCRIPTION
I've just flashed a new device, and while configuring the basics (ie changing my timezone to -3 and entering my lat/lon coordinates), I noticed the DST entries set and I couldn't find any reference in the docs https://tasmota.github.io/docs/Commands/ on how to disable them (my country abandoned DST years ago) and I just didn't want to "disabling" DST effects just by inputing 0s if not documented as workaround.
12:00:43 RSL: STATUS7 = {"StatusTIM":{"UTC":"2020-05-24T15:00:43","Local":"2020-05-24T12:00:43","StartDST":"2020-03-29T02:00:00","EndDST":"2020-10-25T03:00:00","Timezone":"-03:00","Sunrise":"07:46","Sunset":"17:53"}}
Any tip?
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
DST to be allowed being disabled if no Savings rules exist for the country.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: