* test
* Update workflow.yaml
* t
* makes
* Update drv_simpleEEPROM.c
* Update drv_simpleEEPROM.c
* ber
* Update workflow.yaml
* tt
* ber
* charts
* owm
* tt
* rem charts
* smaller
* test
* test
* fixes
* test
* charts
* comments
* test
* tt
* test
* add file to proj
* try to add pin 13 as ADC (testing in progress)
* test
* test
* MAX7219 simulator HACK
* final fixes
* Update drv_max72xx_internal.c
* restore
* fx
* add support for frequency variable in AddChangeHandler
* bl0942 frequency variable rounding correction
* move frequency to last args for VCPPublishThreshold
* frequency selftest precision adjustments
---------
Co-authored-by: kcstonacek <stonacek@stonacek.nz>
a DST switch should fix the upcomming sunset/sunrise events
(which were calculated before the switch, hence with "old" time.)
Added one simple test case
* 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
---------
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"
