Moduline 400: Missing holiday settings about ems-esp32

[MichaelDvP]

We expect the holiday and vacation dates in telegram 0x3F, offset 87- 98, but here the telegram ends in offset 86.
RC30Timer(0x3F), data: 90 E7 90 01 00 00 (offset 81)
If the thermostat have such a setting it is stored elsewhere and you need to change it on the thermostat and log the telegrams.

[proddy]

@sciurius could you find out?

[sciurius]

I must admit I am not familiar with this. All I can do is make some changes in the vacation program settings and include the resultant logging. Is it only the RC30Timer messages you are interested in?

BTW: What would be the difference between vacation and holidays? The thermostat only has one setting "Vakantie" (=vacation). holiday dates would imply a list of (national/regional/religious) holidays.

[MichaelDvP]

Yes, log all and change the vacation dates on the RC30.

In RC35 vacation is "away from home" (use night temp) and holiday is "at home" (use day temp).

[sciurius]

Attached is a logfile fragment consisting of some normal message sequences. I entered a vacation (program 1, from 30.04.24 to 01.05.24) and then the ?(0xA9) messages appeared.

ems1.log

Line ?(0xA9), data: FF 1E 04 18 01 05 18 FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 1E 01 0F 1E 01 has recognizable 1E 04 18 (30 04 24) 01 05 18 (01 01 05).

After setting vacation 2 to 03.05.24-05.05.24 the message becomes:

?(0xA9), data: FF 1E 04 18 01 05 18 FF 03 05 18 05 05 18 FF 01 01 00 01 01 00 FF 1E 01 0F 1E 01

So apparently it is FF day month year day month year FF ...etc... Empty (not set) is 01 01 00 01 01 00.

When cancelling the programs:

Apr 29 21:39:06 ems-esp emsesp 005+10:01:50.523 T 2211: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: FF 01 01 00 01 01 00 FF 03 05 18 05 05 18 FF 01 01 00 01 01 00 FF 1E 01 0F 1E 01
Apr 29 21:39:07 ems-esp emsesp 005+10:01:50.896 T 2212: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: 0F FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 01 01 00 01 (offset 27)
Apr 29 21:39:07 ems-esp emsesp 005+10:01:51.457 T 2213: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: 01 00 1E (offset 54)
Apr 29 21:39:18 ems-esp emsesp 005+10:02:01.897 T 2219: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 1E 01 0F 1E 01
Apr 29 21:39:18 ems-esp emsesp 005+10:02:02.271 T 2220: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: 0F FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 01 01 00 01 01 00 FF 01 01 00 01 (offset 27)
Apr 29 21:39:19 ems-esp emsesp 005+10:02:02.956 T 2222: thermostat(0x10) -B-> All(0x00), ?(0xA9), data: 01 00 1E (offset 54)

[sciurius]

Was this useful? Anything else I can do?

[MichaelDvP]

So you have up to 8 vacation periods. Is it useful to add 8 entities for this? RC30 has only one hc, so we do not run out of memory.
Or add it like the switchtimes, use only one entity with no,command 0:01.05.2024-10.05-2024, etc. and command with single switches the index? For first test i've added only read/write first vacation-period.

[sciurius]

As opposed to switchtimes, vacation periods are explicitly numbered (1..7) so it is probably better to use vacation1, vacation2, ...