Improvement: Add holiday mode to bosch compress 3800i ew about ems-esp32

[MichaelDvP]

read 8? or read 10 269

Youre right, read from thermostat 0x10.
Funny communication, the gateway sets 01.01.2009 as off, and the controller (0x09) corrects to 01.01.2018. But i think we can write any date in the past.
I'll add a single entity for the rego thermostat, only dates as for RC35/RC30.

[proddy]

yes, if you've confirmed it's working

[MichaelDvP]

See #275, the next bytes are heating mode,temperature, dhw mode, and assign to hc/dhw circuits and this for 5 holiday entries.
All in all its 50-75 entities, depending what info we combine. Too much for RAM and mqtt-heap usage.
RC300 switchprograms and holiday settings are often discussed, but in the actual data structure is not easy to implement.
And this are settings very rarly changed.

[mattfro]

Ok I see...
But couldn't it be that if you set that date then rest will be set automatically?
Because, only parameter I can set in the pump for holiday is, a start date end date.
And if I want to turn it off, it's just reset.

Seems in holiday mode, it's set to fixed 17C.

But according to that ticket it seems not to be the case... Oh well, was hoping it would be a easy thing :)
Anyways, I could do my own "holiday/vacation" setup instead in hass. Just lower the temperature and some other small tunings like warm water etc.

[MichaelDvP]

Yes, seems to be a shortend telegram.
thermostat(0x10) -B-> All(0x00), ?(0x0269), data: 18 05 03 18 05 05 02 11
means 03.05.2024-05.05.2024, fixed temperature mode (02), 17°C
Can you check in terminal read 8 269, read 8 26A, ... read 8 26D to check the length and if there are also 5 dates.
It seems the the info to heatingcircuits and dhw are missing in this telegram, Do this setting affect dhw or is there a additional setting?

[mattfro]

@MichaelDvP read 8? or read 10 269
If I do read 8 269, 26A and 26D it's always empty
ems-esp:# read 8 269
000+03:23:26.362 N 81: [emsesp] boiler(0x08) -W-> Me(0x0B), ?(0x0269), data:
ems-esp:# read 8 26A
000+03:23:34.434 N 82: [emsesp] boiler(0x08) -W-> Me(0x0B), ?(0x026A), data:
ems-esp:# read 8 26D
000+03:23:42.745 N 83: [emsesp] boiler(0x08) -W-> Me(0x0B), ?(0x026D), data:

if I check read 10 before I set vacation:
ems-esp:# read 10 269
000+03:34:16.485 N 89: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x0269), data: 12 01 01 12 01 01 02 11
ems-esp:# read 10 26A
000+03:35:34.816 N 90: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x026A), data:
ems-esp:# read 10 26D
000+03:35:45.216 N 91: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x026D), data:

and this is when I set vacation:
ems-esp:# read 10 269
000+03:36:15.699 N 92: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x0269), data: 18 05 03 18 05 05 02 11
ems-esp:# read 10 26A
000+03:36:19.829 N 93: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x026A), data:
ems-esp:# read 10 26D
000+03:36:22.929 N 94: [emsesp] thermostat(0x10) -W-> Me(0x0B), ?(0x026D), data:

[mattfro]

btw. when I took the logs for setting vacation in the first place, I used my phone app, so you can see it comes from the gateway 0x48.

Tried again using the app and set date:
000+03:57:56.335 N 309: [emsesp] gateway(0x48) -W-> thermostat(0x10), ?(0x0269), data: 18 05 03 18 05 05

and when doing reset or removing the date:
000+03:58:22.886 N 312: [emsesp] gateway(0x48) -W-> thermostat(0x10), ?(0x0269), data: 09 01 01 09 01 01

not sure if that helps... I wonder if you could test to use that as a custom entity to try to see if it would work. Set only those?

[MichaelDvP]

Have you already tested if you can change the holiday temperature with custom entity:
device 0x10, type 0x0269, offset 7,factor 1

[mattfro]

@MichaelDvP Oh... I think we got a misunderstanding here :)
I thought you where going to add it in the next build...
So... I did not test that,.

I have a few question in this case

should I use int8?

And how should the value be sent, what format?

[MichaelDvP]

I thought you where going to add it in the next build...

Yes,the dates, for temperature i'm not sure because you wrote

Seems in holiday mode, it's set to fixed 17C.

this value range int8 and uint8 is the same, does not matter. It takes a minute until the value show up.
Just enter a temperature different from 17 maybe 15 or 18 degrees and check if it changes, You can log the telegrams while changing to see the protocol. Maybe the controller overwrite like the off-dates.

[mattfro]

I meant in what format should I send the value in?
Raw or as a date?
18 05 04 18 05 05 or 240504240505
and why does it have a value 17?

Is it correct offset?

[mattfro]

oh are you saying latest build has already holiday in it?
I have latest.. and I don't have any holiday or vacation settings. Only date settings is the "normal" one.

[MichaelDvP]

I'm working on it, it's not yet implemented. If you like to use custom entitiy its:
holidaydate: device 0x10, type 0x269, offset 0, type RAW, length 6 with data 18 05 04 18 05 05
holidaytemp device 0x10, type 0x269, offset 7, type UINT8, UOM °C with data 17

[mattfro]

Did not try holiday temp...
But otherwise it worked fine, checked both the pump UI and phone app, it was on holiday mode when setting that value.
Also I did reset it with these values, as the app used to send: 09 01 01 09 01 01

So for my point of view it works fine what I could see...attached logs for this also.
holiday.log

activated holiday:
ems-esp:# 000+20:31:07.685 I 133: [command] Calling command 'custom/holiday' (set custom value on ems) with value 18 05 04 18 05 05

reset holiday:
ems-esp:# 000+20:33:11.683 I 761: [command] Calling command 'custom/holiday' (set custom value on ems) with value 09 01 01 09 01 01
later on it changes to this:
ems-esp:# 000+20:33:13.840 T 785: [emsesp] controller(0x09) -W-> thermostat(0x10), ?(0x0269), data: 12 01 01 12 01 01 00 11

[mattfro]

And also, I don't see any point of changing the holiday temp to anything else than 17. According to the manual, you should not set it under 17C anyways. The heatpump would not work under those temperatures...at least in a way it would save any energy.

[MichaelDvP]

Please check dev9: https://github.com/MichaelDvP/EMS-ESP32/releases

[mattfro]

@MichaelDvP tried it already:

maybe fix the name :)
and it's setting the year wrong:
000+00:16:14.856 T 270: [emsesp] boiler(0x08) -B-> All(0x00), MenuConfig(0xF7), data: D1 00 00 07
000+00:16:15.100 I 271: [command] Calling command 'thermostat/holiday' (Urlaub) with value 04.05.2024-05.05.2024
000+00:16:15.152 T 272: [emsesp] Me(0x0B) -W-> thermostat(0x10), RC300Holiday1(0x0269), data: 04 05 18 05 05 18
000+00:16:15.212 T 273: [emsesp] thermostat(0x10) -B-> All(0x00), RC300Holiday1(0x0269), data: 04 05 18 05 05 18 02 11
000+00:16:15.521 T 274: [emsesp] controller(0x09) -W-> thermostat(0x10), RC300Holiday1(0x0269), data: 12 01 01 12 01 01 00 11
000+00:16:15.641 T 275: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Holiday1(0x0269), length: 25
000+00:16:15.661 T 276: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Holiday1(0x0269), data: 12 01 01 12 01 01 02 11
000+00:16:15.844 T 277: [emsesp] boiler(0x08) -B-> All(0x00), MenuConfig(0xF7), data: D1 00 00 07

year first, then month and day. I think

[MichaelDvP]

Oh, sorry, yes, Bosch changes the order for RC30/RC35 and RC300/Rego, Updated my dev.

[mattfro]

@MichaelDvP
works fine now:
000+00:04:25.565 I 27: [command] Calling command 'thermostat/vacations' (vacation dates) with value 04.05.2024-05.05.2024
000+00:04:25.604 T 28: [emsesp] Me(0x0B) -W-> thermostat(0x10), RC300Holiday1(0x0269), data: 18 05 04 18 05 05

and setting date to yesterday to reset it:
000+00:05:35.523 I 76: [command] Calling command 'thermostat/vacations' (vacation dates) with value 02.05.2024-02.05.2024
000+00:05:35.859 T 88: [emsesp] Me(0x0B) -W-> thermostat(0x10), RC300Holiday1(0x0269), data: 18 05 02 18 05 02
000+00:05:36.067 T 89: [emsesp] Me(0x0B) -R-> thermostat(0x10), RC300Holiday1(0x0269), length: 25
000+00:05:36.107 T 90: [emsesp] thermostat(0x10) -W-> Me(0x0B), RC300Holiday1(0x0269), data: 18 05 02 18 05 02 02 11
000+00:05:37.294 T 100: [emsesp] thermostat(0x10) -B-> All(0x00), RC300Holiday1(0x0269), data: 18 05 02 18 05 02 02 11
000+00:05:37.603 T 101: [emsesp] controller(0x09) -W-> thermostat(0x10), RC300Holiday1(0x0269), data: 12 01 01 12 01 01 00 11
000+00:05:37.857 T 106: [emsesp] thermostat(0x10) -B-> All(0x00), RC300Holiday1(0x0269), data: 12 01 01 12 01 01 02 11

[mattfro]

Seems it was much easier on mine that the other ticket you had. :)

[mattfro]

@MichaelDvP now when it works, shall we close this ticket?