# Gradually Rolling out Firmware for Handling DST Adjustment **URL:** \ **Category:** Announcement & tutorials\ **Tags:** dst\ **Created:** [March 6, 2025, 9:42am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984 "2025-03-06T09:42:10Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![emma23](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/emma23/32/2990_2.png) [@emma23](https://forum.ewelink.cc/u/emma23)\ **Post date:** [March 6, 2025, 9:42am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/1 "2025-03-06T09:42:11Z")
We understand how frustrating Daylight Saving Time (DST) transitions can be. You’ve probably encountered issues where device timers don’t operate as expected—whether it’s the coffee machine starting an hour late or the lights turning on early. These glitches can make your eWeLink-supported devices feel less “smart,” even somewhat clumsy. #### **Why don’t devices automatically adjust when DST changes?** That’s exactly what we’re aiming to fix! We are deeply aware of that. Starting March 2025, firmware updates will gradually roll out to eligible devices to automatically handle DST changes. Once updated, your devices will perform more reliably during DST transitions. Here’s how to get your devices ready: #### **What You Need to Do:** To ensure a smooth transition into DST and avoid issues with device timers, please follow these steps: 1. **Update the App** - - Make sure you’re using the **eWeLink** **App version 5.13.1 or later** before the DST transition. This update ensures compatibility with new features, especially by conveying the correct time zone parameters to the device firmware. 1. **Check Your Time Zone Settings** - - Go to **Profile \> Settings \> Time Zone** and check that your time zone is set as you want. ![](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/8/8a06d11535693c1dbcfb8bb27f85bb5b5058599d.png) 1. **Update Your Device Firmware** - - Visit the eWeLink home page and click on the banner to check for available firmware updates. ![](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/f/f1c7dbc0b572238a1e9b9ee619347f6b0ebce053.png) #### **1 Month of Free eWeLink Advanced Plan** We understand that many of you have a bunch of devices, and updating them individually can be time-consuming and frustrating sometimes. To help with this, we’re offering **1 month of free [eWeLink Advanced Plan](https://vip.ewelink.cc/)** to users affected by DST. You don’t need to make any purchases or subscriptions. This allows you access to eWeLink [WEB](https://web.ewelink.cc/#/ota) and the ability to manage firmware updates for all your devices simultaneously, saving time and effort. **Who is eligible?** To assist affected users in keeping their devices updated, we’re offering 1 month of eWeLink Advanced Plan for free to non-subscribers who meet both of the following conditions: 🔹 Your eWeLink account is registered in a region that observes DST 🔹 You have devices eligible for the DST firmware update (See the rollout plan below) Please note that the Advanced Plan benefits will be gradually granted. If you haven’t been able to access it yet, we appreciate your patience as it is being made available in batches. #### **What You Might Encounter:** Here are some potential issues you may face during the DST transition: 1. **Firmware Update Failures:** - **Offline Devices:** If your device is offline, the firmware update won’t be completed. Please make sure your devices are online before attempting the update. - **Firmware Upgrade Duration:** - - **Wi-Fi devices** usually take around **5 minutes** to update. - **ZigBee devices** may take longer, varying by device. For example, updating the **water valve** or **radiator valve may** take **1 hour due to the Zigbee mechanism**. - **Stuck at “Updating”:** If the update gets stuck, try **deleting and re-adding** the device to resolve the issue. - **Older Devices:** Some older devices might be limited by the chip’s capabilities and have trouble with firmware updates. _Note: Manually adjusting the device timers is also available. If you don’t want to update the firmware or have other thoughts, check this guideline_ [_HERE_](https://ewelink.cc/why-do-ewelink-timers-go-off-schedule-when-dst-ends/)_._ 1. **DST-related Timer and Data Issues:** - **Incorrect Timer Execution:** If the firmware and eWeLink app are not updated as suggested before DST, your device might use the wrong time, causing timers to run at the wrong time. - **Power Consumption Logging Issues:** Devices without the latest firmware may log energy consumption with a time discrepancy of one hour (e.g., showing 7:00 PM instead of 8:00 PM), leading to inaccurate charts. - **Device Sharing:** Timers for shared devices will follow the **owner’s time zone**. Any changes made by the owner will be reflected for all shared users. 1. **Mismatch Between Timer Actions and App Time Display:** - If your phone’s time zone is changed (e.g., due to travel), the change won’t affect device functionality. However, the local time for device timer actions may not match the time shown in the app due to the discrepancy. 1. **DST Timer Execution:** - If you have timers set around or exactly at the time of the DST transition, they may not execute exactly as expected on the transition day. #### **Firmware Rollout Plan:** As you may know, firmware development is a time-consuming process, so updates will be rolled out in stages. We appreciate your patience and understanding. The firmware for all devices below will gradually be available: | **ID** | **Firmware Model** | **Firmware Version for DST** | **Eligible Device Models (Examples)** | | 1 | SN-NG-ZBP-01 | 2.4.0 | SONOFF ZBBridge-P | | 2 | SN-ESP32C3-S60-01 | v1.2.0 | SONOFF S60TPF SONOFF S60TPG | | 3 | SN-ESP32D0-THR3-01 | v1.3.0 | SONOFF THR316D SONOFF THR320D SONOFF THR316 SONOFF THR320 | | 4 | E32-2SW-P0 | v1.6.1 | SONOFF DUALR3 SONOFF DUALR3 Lite | | 5 | SN-ESP32D0-POWR3-01 | v1.2.0 | SONOFF POWR320D SONOFF POWR316D SONOFF POWR316 | | 6 | SN-ESP32C3-BASICR4-01 | v1.1.0 | SONOFF BASICR4 | | 7 | SN-ESP32D0-POWCT-01 | v1.3.1 | SONOFF POWCT | | 8 | PSF-B01-GL | v3.8.0 | SONOFF BASICR2 SONOFF S26R2 Series SONOFF T0/T1/T2/T3 Series (1C) SONOFF RFR2 SONOFF RE5V1C SONOFF S55 Series SONOFF SlampherR2 CKCZ-006 CKCZ-005 | | 9 | PSF-BD1-GL | v3.8.0 | SONOFF MINIR2 SONOFF BASICR3 SONOFF RFR3 PSF-xD1 | | 10 | PSF-B04-GL | v3.8.0 | SONOFF T0/T1/T2/T3 Series (2C/3C) SONOFF 4CHPRORR2/3 SONOFF 4CHR2/3 SONOFF DUALR2 SONOFF iFan02 | | 11 | PSA-B01-GL | v3.8.0 | SONOFF S26 Series SONOFF BASICR2 SONOFF SV SONOFF S31 Lite Series SONOFF RFR2 CKCZ-001 | | 12 | PSA-BHA-GL | v3.6.0 | SONOFF TH16R2 SONOFF TH10R2 SONOFF TH16 SONOFF TH10 PSA-BHA-GL | | 13 | ITA-GZ1-GL | v3.8.0 | SONOFF BASIC SONOFF RF | | 14 | PSC-B67-GL | v3.7.0 | SONOFF POWR2 SONOFF S31 Series PSC-B67-GL | | 15 | SN-ESP32D0-MINIR4-01 | v1.2.0 | SONOFF MINIR4 | | 16 | PSF-BRA-GL | v3.6.0 | SONOFF RF BridgeR2 SONOFF RF Bridge PSF-xRA | | 17 | PSF-B67-GL | v3.6.0 | SONOFF IW101/100 Series PSF-X67 | | 18 | E32-MSW-NX | v1.6.0 | SONOFF NPanel-EU/US | | 19 | SN-BL602-S40-01 | v1.5.0 | SONOFF S40 Series | | 20 | ESP32D0-MSW-T5 | v1.3.0 | SONOFF M5 Series | | 21 | BL1-ALL-LED | v1.7.0 | SONOFF B05-BL-A60/A19 SONOFF B02-BL | | 22 | SN-ESP32D0-T5-01 | v1.5.0 | SONOFF T5 Series | | 23 | BL1-S04-01 | v1.5.0 | SONOFF MINIR3 | | 24 | PSF-BLD-GL | v3.6.0 | SONOFF D1 | | 25 | PSF-P76-R3 | V1.2.0 | SONOFF POWR3 | | 26 | PSF-BFB-GL | v3.6.0 | SONOFF iFan03 SONOFF iFan04 Series | | 27 | SN-MG22-TRVZB-01 | v1.3.0 | SONOFF TRVZB | | 28 | SN-MG22-SWV-01 | v1.0.3 | SONOFF SWV-NH/BSP | | 29 | CK-BL602-4SW-HS | v1.6.0 | May be the same as the Firmware model | | 30 | CK-BL602-SWP1-01 | v1.3.0 | | 31 | CK-BL602-4SW-WH | v1.3.0 | | 32 | CK-BL602-4SW-AY | v1.4.0 | | 33 | CK-BL602-5PWM-01 | v1.5.0 | | 34 | CK-BL602-IIC-ABC-04 | v1.3.0 | ---
**Author:** ![emma23](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/emma23/32/2990_2.png) [@emma23](https://forum.ewelink.cc/u/emma23)\ **Post date:** [March 6, 2025, 9:49am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/2 "2025-03-06T09:49:11Z")
---
**Author:** ![eerke](https://avatars.discourse-cdn.com/v4/letter/e/eb9ed0/32.png) [@eerke](https://forum.ewelink.cc/u/eerke)\ **Post date:** [March 8, 2025, 7:31pm UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/3 "2025-03-08T19:31:38Z")
What about the firmware on the iHost? I have some local automations there which run wrong during the winter? Also, they’ve been talking for decades about here (U.K.) staying on BST all year. Not sure it’ll actually happen. But if the U.K. has a permanent BST will it be moved time zone? ---
**Author:** ![yitie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/yitie/32/3613_2.png) [@yitie](https://forum.ewelink.cc/u/yitie)\ **Post date:** [March 10, 2025, 3:07am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/4 "2025-03-10T03:07:36Z")
The iHost have the DST auto-adjustment feature when manufactured, doesn’t need a firmware update. May i know more details about this > [@eerke](#): > > I have some local automations there which run wrong during the winter? ---
**Author:** ![ociepa.ekotox](https://avatars.discourse-cdn.com/v4/letter/o/c68b51/32.png) [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)\ **Post date:** [March 10, 2025, 7:21am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/5 "2025-03-10T07:21:00Z")
> [@emma23](#): > > **PSF-B04-GL** > > v3.8.0 > > SONOFF T0/T1/T2/T3 Series (2C/3C) > > SONOFF 4CHPRORR2/3 > > SONOFF 4CHR2/3 > > SONOFF DUALR2 > > SONOFF iFan02 Will the Sonoff 4CH Pro ( **PSF-A04-GL** ) version get updates? ---
**Author:** ![eerke](https://avatars.discourse-cdn.com/v4/letter/e/eb9ed0/32.png) [@eerke](https://forum.ewelink.cc/u/eerke)\ **Post date:** [March 11, 2025, 12:05am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/6 "2025-03-11T00:05:38Z")
I have a flow in Node Red (iHost Docker) that runs at 23:55 and checks the temperature of a TH Elite and if it is low I get alerted before bed so can boost the heating for an hour. In winter it runs an hour early. Where do docker images get the time? I had assumed it got the System Time. ---
**Author:** ![emma23](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/emma23/32/2990_2.png) [@emma23](https://forum.ewelink.cc/u/emma23)\ **Post date:** [March 12, 2025, 2:59am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/7 "2025-03-12T02:59:09Z")
Hello, firmware development is a time-consuming process. The update for this PSF-A04-GL version is currently in the pipeline but may take some time. It is expected to be completed before daylight saving time ends. If you are experiencing timer inaccuracies due to the DST switch, we recommend manually adjusting the timers. Please refer to this guide: [Why Do eWeLink Timers Go Off-Schedule When DST Ends?](https://ewelink.cc/why-do-ewelink-timers-go-off-schedule-when-dst-ends/). Thank you for your understanding. ---
**Author:** ![emma23](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/emma23/32/2990_2.png) [@emma23](https://forum.ewelink.cc/u/emma23)\ **Post date:** [March 13, 2025, 6:55am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/8 "2025-03-13T06:55:14Z")
Hi. Node RED uses your browser time, while Docker images use UTC time. ---
**Author:** ![eerke](https://avatars.discourse-cdn.com/v4/letter/e/eb9ed0/32.png) [@eerke](https://forum.ewelink.cc/u/eerke)\ **Post date:** [March 13, 2025, 2:29pm UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/9 "2025-03-13T14:29:13Z")
Thanks. If the browser is not connected I guess the automations use the UTC time with no DST. Looking online it seems I need to add a delay of 1 hour if there is summer time but this is not built in to the standard trigger node. I will make a subflow with this function. ---
**Author:** ![john.e.dixon](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/john.e.dixon/32/1626_2.png) [@john.e.dixon](https://forum.ewelink.cc/u/john.e.dixon)\ **Post date:** [March 15, 2025, 7:42pm UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/10 "2025-03-15T19:42:03Z")
I use Node-red quite exensively and I have to compensate 1 hour on inject nodes on, both devices that come into my Smartthings hub from the iHost Matter bridge, and those paired to the Smartthings hub. Routines on either platform follow local time. I have read quite a few threads on the Node-red forum but can’t seem to find a way around it. ---
**Author:** ![eerke](https://avatars.discourse-cdn.com/v4/letter/e/eb9ed0/32.png) [@eerke](https://forum.ewelink.cc/u/eerke)\ **Post date:** [March 16, 2025, 12:02am UTC](https://forum.ewelink.cc/t/gradually-rolling-out-firmware-for-handling-dst-adjustment/143984/11 "2025-03-16T00:02:33Z")
if the iHost gets it right we could just set up an iHost scene to run a virtual device at iHost midnight and a trigger node to run at UTC midnight and if they run at the roughly same time it isn’t summer time, but this feels a bit like cheating. It is a bit suprising NR doesn’t compensate but then most of the world doesn’t use summer time and it is different in different places so I can see why.