Automating Daylight Savings Adjustments for NTP with Scripting or driver update

randomalias324 2607 60

#61 21597196 04 Jul 2025 09:26

4N6nerd 4N6nerd

Level 2

Helpful post? (0)

Post #61
21597196 04 Jul 2025 09:26

>>21597185
OUCH! so sorry! I checked my post with my actual code and it's not '&&' that is missing but ' ' that is missing

My post says "31-$mday $day<=6" while it should be "31-$mday+$day<=6"

I'll repair my previous post right away.

Thanks for the heads-up! "Dankjewel"

Edit: + signs get removed on initial post. After editting it back it stays.
ADVERTISEMENT
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Topic summary

The discussion centers on automating daylight savings time (DST) adjustments for devices using OpenBeken firmware with NTP time synchronization relayed via TuyaMCU. The default NTP driver lacks built-in DST support, requiring manual offset changes twice yearly. Users explored scripting solutions in autoexec.bat to dynamically adjust the ntp_timeZoneOfs parameter based on date and time conditions, leveraging available logical operators (&&, ||), nested if statements, aliases, and clock events. Examples include scripts for Sydney and CET time zones that calculate DST start and end using weekday and month rules. Advanced users shared custom driver code and pull requests adding DST commands and automatic adjustments with minimal flash overhead. Testing revealed that MQTT connectivity affects device stability, with resets occurring when MQTT is disabled; setting a default WiFi state in TuyaMCU mitigates this. The firmware supports clock events for scheduled actions, and recent updates separate clock functions from NTP for modularity. Various hardware platforms (BL602, LN882H, W600, ESP32 variants, TR6260, RTL87X0C) were tested for NTP and clock event functionality, with XR809 lacking support. Documentation on the scripting language is limited; it supports if statements, aliases, labels, goto, and backlog for multiple commands but lacks general variable support. The community continues to refine DST handling and clock features in OpenBeken firmware to improve usability for time-displaying IoT devices.
Summary generated by the language model.

FAQ

TL;DR: OpenBeken can change to - and from - Daylight-Saving Time without manual edits. Use either the new Clock/DST firmware branch (adds ≈1 kB flash and switches zone automatically) or a short autoexec.bat script that combines "&&"/"||" logic with addClockEvent. Both approaches cut bi-annual maintenance to zero [Elektroda, max4elektroda, #21364166].

Quick Facts

• DST engine size: +0.9-1.6 kB per firmware (all MCUs except XR809) [Elektroda, max4elektroda, #21364166]
• Boolean operators: &&(AND) ||(OR) ! (NOT) supported since v1.17.689 [Elektroda, miegapele, #21301498]
• Base offset command: ntp_timeZoneOfs ±HH[:MM] (e.g. ntp_timeZoneOfs 10:00) [Elektroda, randomalias324, #21301007]
• Up to 64 virtual channels usable as script variables [Elektroda, miegapele, #21306272]
• Wi-Fi reset fix for TuyaMCU devices: tuyaMcu_defWiFiState 4 [Elektroda, p.kaczmarek2, #21310759]

How do I enable automatic DST in one command?

Flash a build that includes PR #1483 (Clock split). Then send Clock_SetConfig TZ Hem W1 M1 D1 H1 Tstd W2 M2 D2 H2 Tdst. Example for Australia: Clock_SetConfig 99 1 1 4 1 3 600 1 10 1 2 60 [Elektroda, max4elektroda, #21306789].

Can I keep the release firmware and use a script instead?

Yes. Put a script like miegapele’s Sydney example into autoexec.bat. It waits for the first NTP sync, evaluates $month, $mday and $day, and calls ntp_timeZoneOfs 10 or 11 accordingly [Elektroda, miegapele, #21304679].

Which logical operators are available in scripts?

The parser accepts && (AND), || (OR) and parentheses. Nested IF, goto, backlog and labels are allowed. There is no direct variable keyword; use channels to store numbers [Elektroda, miegapele, #21306272].

Where is the scripting language documented?

Command, constant and example lists live in docs/commands-extended.md, constants.md and commandExamples.md. No full grammar exists yet; forum examples are the authoritative source [Elektroda, randomalias324, #21306212].

Why does my LCD reset every few minutes when MQTT is disabled?

TuyaMCU pulls the Wi-Fi CEN pin low if it never sees state 0x04. Add tuyaMcu_defWiFiState 4 to autoexec to spoof “cloud connected” and stop the resets [Elektroda, p.kaczmarek2, #21310759].

Does the DST driver work on every MCU?

It builds for BK72xx, RTL87X0, LN882H, BL602, W600 and ESP32 families. XR809 still lacks NTP/Clock support [Elektroda, divadiow, #21398354].

How accurate is the internal clock if NTP goes offline?

With the improved device-clock code the drift is ≈1-2 s /day, versus the earlier 2 min /day of g_secondsElapsed [Elektroda, max4elektroda, #21374542].

Can I trigger actions at sunrise or sunset?

Yes. addClockEvent accepts SUNRISE/SUNSET keywords once ENABLE_EXPAND_CONSTANT is compiled. Example: addClockEvent SUNSET 0xff 1 Relay1 1 [Elektroda, max4elektroda, #21374542].

What happens if I change ntp_timeZoneOfs at runtime?

The offset applies on the next successful NTP sync. If Clock_SetConfig is active, its rules override manual ntp_timeZoneOfs after each DST switch [Elektroda, max4elektroda, #21302925].

Is there a standard database of time-zones onboard?

No. To keep flash small OpenBeken relies on user-defined rules instead of the 600 kB IANA TZ database [IANA, 2024].