How to capture telegrams for clock program

[HansRemmerswaal]

The EMS-ESP32 supports most of the menu options of my boiler / thermostat, great job! The only (?) option missing is the clock program for hot water. I always assumed that this option is missing in EMS-ESP32 as this clock program was not published on the EMS bus. But I was wrong. I installed Bosch EasyControl and via the related app I can read and change the clock program. So there are telegrams to read and update this clock program.

I monitored the EMS bus while changing the clock program, but there are so many messages on the EMS bus that I have no clue how to find the ones triggered by the changes I did.

1. If I figure out the telegrams, is this then something you want to implement in the EMS-ESP32?
2. What is the best way to monitor the specific telegrams? How to filter, how to interpretate the telegrams?

Below is how it looks like in the Bosch EasyControl app. This is showing and updating the clock program in the Enviline itself.

emsesp_system_info.json

[proddy]

Getting EMS-ESP as close to the Bosch App has always been one of my goals, so yes, if we can build the clock feature we should.

The issue, though, has always been whether the Master (boiler) actually holds the clock schedule, or is just the Bosch App syncing with the Bosch Cloud and then instructing the CT200/Easy thermostat to switch on/off at the right times. I think the later.

[MichaelDvP]

see #1594, #1918 and some more..
I had a branch with the timer- and holiday-scheduls published as extra json, but deleted it after 2 years.
For normal implementation with each value as entity it's too much entities (42 datasets with day, time, mode, temperature, hcs, dhw).

For telegrams see https://emsesp.org/ems-library 0.02C3, 0x02FF, 0x0309, 0x043F, 0x0449, 0x0683, 0x068D

[HansRemmerswaal]

Getting EMS-ESP as close to the Bosch App has always been one of my goals, so yes, if we can build the clock feature we should.

The issue, though, has always been whether the Master (boiler) actually holds the clock schedule, or is just the Bosch App syncing with the Bosch Cloud and then instructing the CT200/Easy thermostat to switch on/off at the right times. I think the later.

It updates directly in the boiler. When I change something then I do see the change when I navigate to the menu option.

[HansRemmerswaal]

see #1594, #1918 and some more.. I had a branch with the timer- and holiday-scheduls published as extra json, but deleted it after 2 years. For normal implementation with each value as entity it's too much entities (42 datasets with day, time, mode, temperature, hcs, dhw).

For telegrams see https://emsesp.org/ems-library 0.02C3, 0x02FF, 0x0309, 0x043F, 0x0449, 0x0683, 0x068D

Why do we need extra JSON if this is stored in the Boiler itself?
Looks like that in the 0x02FF it's already mapped out. So not needed for me to investigate.

[proddy]

@MichaelDvP we could start by reading the clock programs and displaying them in the WebUI?

(moving to a discusion)

[MichaelDvP]

Every few month someone ask for timers/holiday schedules. I've made an approach to publish the lot of data and made a test build two years ago. Implemented mqtt, api, command. I alsways point to the testbuild and ask for feedback. Mostly there was no feedback at all, the others only complain missing HA implentation. So WebUI will not help.

Keep in mind that every thermostat uses a different format and it's up to 1000 entities.

Thomas (tp1de) mentioned, that it's much easier to use thermostat in manual mode and update the values via HA. No need to show/edit the timers in thermostat.

[soderdaen]

I'd like to see this feature for completion and happy to test.
Would it still be a RAM issue for ESP32-S3 with 8MB RAM and 8MB PRSAM?

I am using the BC400.

[VlastiBroucek]

I would suggest this is almost impossible to actually fully implement as EMS-ESP tries to support so many different devices. For example, in my installation, DHW mode is same as heating mode (i.e. COMFORT or ECO) with exception of DHW COMFORT mode starting 30 minutes before heating COMFORT mode and ending 30 minutes after... All this is controlled by my room controller, and the 30min difference seems to be hardwired... Nothing stored in boiler afaik.

My point is - @proddy and @MichaelDvP would need to implement every bloody boiler/heat pump and every bloody controller/thermostat separately. This is IMHO humanly impossible for two men team.

[HansRemmerswaal]

I do recall that ems-esp systems with less memory might have a problem with that many new entities?

I'm trying to think of the use case of having this all in the ems-esp, apart from that it would just be great to have "everything" in the ems-esp. Typically the program is fixed. The only use case I have is to dynamically change the clock program (via home assistant) depending on the moment that energy is cheap or free (solar). But there might we other ways to manage this.