es73 set date and time does not work

[SpaceTeddy]

dear all,
I tried to update the date/time setting (type 0x06) via web interface first time. I noticed, that my Sieger es73 controller does not save the change.
Attached log of changing date/time setting.

May somebody check if the date / time change basically works, or is it a problem with my Thermostat controller? Thanks a lot.

001+22:23:12.595 I 235: [command] Calling thermostat command 'datetime', value 09:12:19 18/10/2021, id is default 001+22:23:12.595 I 236: [thermostat] Date and time: 18.10.2021-09:12:19 001+22:23:12.595 I 237: [thermostat] Setting date and time 001+22:23:12.663 D 238: [telegram] Sending write Tx [#144], telegram: 0B 10 06 00 15 0A 09 12 0C 13 48 7F 001+22:23:12.707 D 239: [emsesp] Last Tx write successful 001+22:23:12.707 D 240: [telegram] Sending post validate read, type ID 0x06 to dest 0x10 001+22:23:13.334 D 241: [telegram] Sending read Tx [#145], telegram: 0B 90 06 00 20 001+22:23:13.484 D 242: [emsesp] Last Tx read successful

[proddy]

I can't as my thermostat does not support this. @MichaelDvP could you test with your RC3x0?

[MichaelDvP]

I think day-of-week and daylight-saving is missing. Check format here.
I've checked with RC35, but normally i only use datetime NTP.

[SpaceTeddy]

Hi Michael,

I tried NTP update as well, but unfortunatly no update of the time:

'''
Log level: debug
ems-esp:# call thermostat datetime NTP
002+00:31:36.292 I 6: [command] Calling thermostat command 'datetime', value NTP, id is default
002+00:31:36.292 I 7: [thermostat] Date and time: 2021-10-18T11:20:26+0200
002+00:31:36.292 I 8: [thermostat] Setting date and time
002+00:31:36.410 D 9: [telegram] Sending write Tx [#149], telegram: 0B 10 06 00 15 0A 0B 12 14 1A 00 03
002+00:31:36.533 D 10: [emsesp] Last Tx write successful
002+00:31:36.533 D 11: [telegram] Sending post validate read, type ID 0x06 to dest 0x10
002+00:31:36.833 D 12: [telegram] Sending read Tx [#150], telegram: 0B 90 06 00 20
002+00:31:36.934 D 13: [emsesp] Last Tx read successful
002+00:31:36.984 D 14: [mqtt] Publishing topic ems-esp/thermostat_data (#55442, retain=0, retry=1, size=724, pid=1)
002+00:31:40.014 D 15: [mqtt] Publishing topic ems-esp/boiler_data (#55443, retain=0, retry=1, size=731, pid=1)
002+00:31:40.115 D 16: [mqtt] Publishing topic ems-esp/boiler_data_ww (#55444, retain=0, retry=1, size=474, pid=1)
002+00:31:40.216 D 17: [mqtt] Publishing topic ems-esp/thermostat_data (#55445, retain=0, retry=1, size=724, pid=1)
ems-esp:# log info
'''

[MichaelDvP]

I tried NTP update as well, but unfortunatly no update of the time:

Sad, we had the same with RC30, the time was not writable. The es73 was set to rc35 compatible, but i think we should choose rc30 mode.

[SpaceTeddy]

no, please do not change it.
i changed { 76, DeviceType::THERMOSTAT, F("ES73"), DeviceFlags::EMS_DEVICE_FLAG_RC35}, // 0x10 to { 76, DeviceType::THERMOSTAT, F("ES73"), DeviceFlags::EMS_DEVICE_FLAG_RC30}, // 0x10
but after that I do receive only date time and error codes. nothing else.

[MichaelDvP]

Use RC30_N.

[SpaceTeddy]

I did this as well. I received almost all messages like with RC35 setting, only boiler_data_ubauptime is not transmitted via mqtt. Time and dates is not writable via web interface.

[MichaelDvP]

boiler_data_ubauptime is no thermostat value and is not influenced by thermostat setting.

Time and dates is not writable via web interface.

Yes, because RC30 does not accept writing the time (like your ES73), it's useless and misleading to implement a command that does not work. But RC30 have some other settings not in RC35, one is clock calibration value. Maybe this can be used. I dont know how it works.

[SpaceTeddy]

ok, understand.

we can close the issue