* fix handling of "sunset" events:
Old code was
if (e->sunflags & (SUNRISE_FLAG || SUNSET_FLAG)) {
This will ignore sunset events ( SUNSET_FLAG = 1 << 1)
for the or of two values ( 1 || 2) is always true
and will result in testing (sunflags & 1)
so never true for sunset (2 & 1) is false.
probaly meant
if ((e->sunflags & SUNRISE_FLAG) || (e->sunflags & SUNSET_FLAG))
but it's sufficient to check is "sunsetflags" is not 0, so simple fix:
if (e->sunflags){
Additionally added code to change liste vents ("listClockEvents") so it also shows if a time is derived from sunset or sunrise:
before the output would be like:
Info:CMD:Ev 32 - 7:31:0, days 0xff, cmd setChannel 0 0
Info:CMD:Ev 31 - 19:7:0, days 0xff, cmd setChannel 0 1
and you won't see this is an "dynamic" time. Now it's (I also used %02i to fix time format)
Info:CMD:Ev 32 - 07:31:00 (sunrise), days 0xff, cmd setChannel 0 0
Info:CMD:Ev 31 - 19:07:00 (sunset), days 0xff, cmd setChannel 0 1
* forgot to commit fix for time display using "%02i" for hours, minutes and seconds
* create a ChType_Enum to go with SetChannelEnum
* resolve build errors for ChType_Enum PR
* fixing build errors for simulator and others for cmd_enums.c
* added ChType_ReadOnlyEnum and assocaited enum selftests
* ChType_Enum simulation and memory error corrections
* ChType_Enum documentation updates
* ChType_Enum autoexec example corrections
---------
Co-authored-by: root <root@stonacek.nz>
Co-authored-by: kcstonacek <kcstonacek@stonacek.nz>
* create a ChType_Enum to go with SetChannelEnum
* resolve build errors for ChType_Enum PR
* fixing build errors for simulator and others for cmd_enums.c
* added ChType_ReadOnlyEnum and assocaited enum selftests
* ChType_Enum simulation and memory error corrections
* ChType_Enum documentation updates
---------
Co-authored-by: root <root@stonacek.nz>
* first try to set sensor output like tasmota, but add "name"
* Use extended tasmota style: Name + Tasmota-Id
* switch to "plain" tasmota style (only tasmota-Id aditionally to temperature)
* fix numbering - Tasmota starts with "DS18B20-1" not with "DS18B20-0"
* first try for DS1820 sensors
* fix windows build
* Fix wrong comment format
* Fix code
* fix missing includes
* fix missing defines (only check if driver is included)
* Add DS1820 to sensors in "DRV_IsSensor
Fix string might be not empty
* fix output for long string in case of many DS1820 sensors
* ENABLE DMX on ESP
* test
* s
* Update hal_uart_espidf.c
* Update obk_main.cmake
* w
* test
* Update hal_uart_espidf.c
* Update drv_dmx512.c
* test
* test
* test
* w
* t
* c
* t
* test
* T
* Update drv_dmx512.c
* test
* test
* try flush
* try wait
* ticks w
* t
* fx
* 100 ms
* SIM fx
* Update cmd_newLEDDriver.c
* test 2x
* tests
* fixes
* free
* fix
* misc
* b
* hal
* s
* Update workflow.yaml
* pin
* fin
* test
* Update hal_uart_espidf.c
* t
* ENABLE DMX on ESP
* test
* s
* Update hal_uart_espidf.c
* Update obk_main.cmake
* w
* test
* Update hal_uart_espidf.c
* Update drv_dmx512.c
* test
* test
* test
* w
* t
* c
* t
* test
* T
* Update drv_dmx512.c
* test
* test
* try flush
* try wait
* ticks w
* t
* fx
* 100 ms
* SIM fx
* Update cmd_newLEDDriver.c
* test 2x
* tests
* fixes
* free
* fix
* misc
* b
* hal
* s
* Update workflow.yaml
* pin
* fin
* test
* Update hal_uart_espidf.c
* fix getcommands.js
Fix parsing
don't overwrite source files but generate alternate file
* Fix comments so "getcommands.js" won't complain.
Hpoe I got descriptions right ...
* Some more comments to fill "qqq" fields ...
* Fix getcommands.js generatind fn-entries for registered commands
Fix all source files with wrong "NULL);" as fn
* add some more tests to getcommands.js to verify commands:
check filename of command
check fn called
some more fixes to documentation commands as result from above tests
