Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
PowerSave 1
ntp_setServer 192.168.1.12
startDriver ntp
ntp_timeZoneOfs 11
ntp_setLatlong <lat> <long>
alias high_lights backlog led_temperature 300; led_dimmer 30; led_enableAll 1; echo lights_set_high
alias low_lights backlog led_temperature 500; led_dimmer 5; led_enableAll 1; echo lights_set_low
alias off_lights backlog led_enableAll 0; echo lights_set_off
addClockEvent sunset 0xff 1 high_lights
addClockEvent 21:00 0xff 2 low_lights
addClockEvent 23:00 0xff 3 off_lights
waitFor NTPState 1
// Set initial light state to match the above clock events
// sunset - 21:00 lights set to high
// 21:00 - 23:00 lights set to low
// 23:00 - sunset lights turned off
if ($hour>$sunset_hour||($hour=$sunset_hour&&$minute>=$sunset_minute))&&$hour<21 then high_lights
if $hour>=21&&$hour<23 then low_lights
if $hour>=23||($hour<$sunset_hour||($hour=$sunset_hour&&$minute<$sunset_minute)) then off_lightsp.kaczmarek2 wrote:Hello, are all the self-tests passing now?
p.kaczmarek2 wrote:Did you add the new autoexec sample to the JSON source file of docs?
// autoexec for mini smart switch
PowerSave 1
addEventHandler OnHold 8 SafeMode
startDriver ntp
ntp_timeZoneOfs -8
ntp_setLatlong 44.002130 -123.091473
// pins are defined for my device already
// setPinRole 1 WifiLed
// setPinRole 24 Btn_Tgl_All
// setPinRole 14 TglChanOnTgl
// setPinChannel 14 0
// setPinRole 15 Rel
// setPinChannel 15 0
removeClockEvent 12
removeClockEvent 13
waitFor NTPState 1
addClockEvent sunrise 0x7f 12 POWER2 OFF
addClockEvent sunset 0x7f 13 POWER2 ON
ntp_setLatlong 44.002130 -123.091473
ntp_timeZoneOfs -8
// I'm the entrance/Hallway switch with 2 relays, Hallway(1) and Balcony(2)
// short press means turn all on
// 2 second press means turn all off
// First turn off/on Balcony by Sunrise/set
PowerSave 1
startDriver ntp
// must be corrected
ntp_timeZoneOfs -8
// must be corrected
ntp_setLatlong 44.002130 -123.091473
removeClockEvent 12
removeClockEvent 13
waitFor NTPState 1
addClockEvent sunrise 0x7f 12 POWER2 OFF
addClockEvent sunset 0x7f 13 POWER2 ON
// adjust button timing for hold, from 4 seconds to 1 second
SetButtonTimes 10 3 3
// program all on and all off actions
addEventHandler OnClick 24 startScript lights_on.bat
addEventHandler OnHold 24 startScript lights_off.bat// I'm the entrance/Hallway switch with 2 relays, Hallway(1) and Balcony(2)
// short press means turn all on
// 2 second press means turn all off
//
// adjust button timing for hold, from 4 seconds to 2 seconds
SetButtonTimes 20 3 3
// program all on and all off actions
addEventHandler OnClick 24 startScript lights_on.bat
addEventHandler OnHold 24 startScript lights_off.bat
//
// turn off/on Balcony by Sunrise/set
PowerSave 1
startDriver ntp
// must be corrected
ntp_timeZoneOfs -8
// must be corrected
ntp_setLatlong 44.002130 -123.091473
removeClockEvent 12
removeClockEvent 13
waitFor NTPState 1
addClockEvent sunrise 0x7f 12 POWER2 OFF
addClockEvent sunset 0x7f 13 POWER2 ON
omniron wrote:Question: Is it possible to use this sunrise/set function in a way so that the device sets the right condition after each reboot, not just during transitions? For instance, after a long power outage (missing the transition from day to night), it should turn on if "night" condition.
omniron wrote:Unless a variable, something like "set manually already" was set, so it would not constantly override it if one had prior set it manually. For instance, it is "day" but really dark outside and you manually turn it on, then, after a power outage or reboot it should not turn it off but respect your prior manual override. And vice versa.
TL;DR: OpenBK7231 sunrise/sunset NTP events are now fully functional, add about 1 minute of typical timing error, and were described as "fully acceptable" in self-tests. This FAQ helps BK7231N/BK7231T users automate relays at dawn and dusk, avoid autoexec timing mistakes, and document or submit the feature correctly. [#20869623]
Why it matters: Sunrise/sunset scheduling solves a real automation problem: lights and relays follow local daylight instead of fixed clock times, with workable accuracy and known startup limits.
| Approach | Best use | Main requirement | Known limitation |
|---|---|---|---|
addClockEvent sunrise/sunset |
Daily daylight-based switching | Valid timezone, latitude/longitude, NTP sync | First-day edge cases can occur after initial setup |
Fixed-time addClockEvent HH:MM |
Stable manual schedules | Only local clock time | Does not track seasonal daylight changes |
addRepeatingEvent after sunset |
Simple delay like +30 minutes | Sunset event must run first | Reboot during delay loses the pending action |
Key insight: Put timezone and location in
autoexec.bat, then wait for NTP before creating sunrise or sunset events. That ordering prevents wrong-time calculations and makes the feature reliable after daily rescheduling. [#20823027]
atanf and sinf. [#20828276]recv may fail without indicating a firmware fault. [#20824897]autoexecExamples.json, not by editing Markdown directly. [#20854291]autoexec.bat to start NTP, set timezone and coordinates, wait for sync, then add the events. 1. startDriver ntp and ntp_timeZoneOfs .... 2. Set ntp_setLatlong <lat> <long> and run waitFor NTPState 1. 3. Add addClockEvent sunrise ... and addClockEvent sunset ..., for example event IDs 12 and 13. A working sample turns POWER OFF at sunrise and POWER ON at sunset after the wait step. [#20828244]NTP offset set, wait for next ntp packet to apply changes, so a sunrise or sunset event created right away can use the wrong timezone. That produces the wrong local event time until the next NTP packet arrives. [#20823018]waitFor NTPState 1 is a script gate that pauses execution until NTP is live. Use it before any command that depends on correct local time, especially addClockEvent sunrise and addClockEvent sunset. In this thread, it was recommended specifically to fix startup ordering in autoexec.bat. [#20823027]OnHold event for it. Enter it by doing 5 quick power off/on cycles, which makes the extra addEventHandler OnHold 8 SafeMode line unnecessary for normal sunrise/sunset automation. [#20950287]recv fails. One user noticed the messages arriving in groups of 10, but that alone did not indicate a firmware bug. [#20824897]addClockEvent sunrise 0x7f 12 POWER2 OFF and addClockEvent sunset 0x7f 13 POWER2 ON, preceded by timezone, coordinates, and waitFor NTPState 1. That is better than hard-coded times when daylight changes through the year. [#20950188]$hour and $minute with $sunset_hour and $sunset_minute to choose the correct startup mode. "Time constants" are runtime variables that expose computed clock values, including next solar event times, so scripts can restore state after reboot instead of waiting for the next transition. [#20878116]docs/autoexecs, add its metadata to docs/json/autoexecExamples.json, and then run the docs generation step. The maintainer said commands.md is autogenerated from JSON comments, so direct Markdown edits are not the preferred path. [#20854291]403 happened because direct push access to openshwprojects/OpenBK7231T_App.git was denied. After pushing to the personal fork, the contributor successfully created PR #1001 from branch sunrise_sunset_NTP. [#20865847]autoexec.bat to avoid changing the persistent config structure size across firmware versions. The maintainer warned that if config size changes, downgrade compatibility breaks. He recommended globals or statics and simply setting latitude and longitude on every startup through autoexec.bat. [#20843876]