help implementing Programms (Heating, Fan, WarmWater)

[Dobbiiey]

Next implementation I'd like to add for LWZ403 would be the Programs ( I only use Mo.-So. Prog1 )

Example:
// '14a0' // HK1 Programm Mo.-So. // x=5: DayStart15 [min] x=6: NightStart15[min]
and:
// '17a0', // Warmwasserprogramm Mo.-So.
// '1da0', // Lüfterprogramm Mo.-So.

Maybe et_time_domain is correct Type, but "how to work with it"?
PROPERTY(HEIZPROG_HK1_MO_SO_TAG_ENDE, 14a0, Type::et_time_domain);

Is there any example-code for et_time_domain ?

I just know, that this one address '14a0' handles both values StartDay & StartNight...
And writing to the address means always: "writing both values" ;-))

Are these 2 values controlable by 2 template - number in the end?

[kr0ner]

Hi @Dobbiiey
I never looked too closely at those settings. There are so many problems arising when you want to automate stuff in HA and the heatpump switches from day to night setting. So I ended up using https://github.com/nielsfaber/scheduler-card which is a great piece of software. So now I can set the schedules in HA and not having to use this weird heat pump display ^^
IMO this whole thing only makes sense once you can set the schedule of the heatpump with a nice UI in HA similar to the one from nielsfaber

[kr0ner]

If you still want to have this supported I'd need let's say 10 samples of schedules set in the heatpump and the corresponding raw values on the bus 😉

[zimbo86]

may I add some information that could be useful here:

This is the code from fhem, so 14a0 is correct

  "programHC1_Mo-Fr_0"		=> {cmd2=>"0B1480", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Mo-Fr_1"		=> {cmd2=>"0B1481", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Mo-Fr_2"		=> {cmd2=>"0B1482", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Sa-So_0"		=> {cmd2=>"0B1490", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Sa-So_1"		=> {cmd2=>"0B1491", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Sa-So_2"		=> {cmd2=>"0B1492", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Mo-So_0"		=> {cmd2=>"0B14A0", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Mo-So_1"		=> {cmd2=>"0B14A1", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programHC1_Mo-So_2"		=> {cmd2=>"0B14A2", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},

There was a comment behind these lines:

#1 is monday 0 is first prog; start and end; value 1Ch 28dec is 7 ; value 1Eh 30dec is 7:30

I just know, that this one address '14a0' handles both values StartDay & StartNight... And writing to the address means always: "writing both values" ;-))

In my opinion this are not StartDay and StartNight, its StartDay and EndDay.

So from the above examle 1C1E would be 7:30 Uhr

I will fetch some data later on the WP directly

[zimbo86]

I think this is pretty hard to handle, because all programs needs to be checked when saving a new program (no overleaps etc.)
I just set "programFan_Mo-So_1" on the WP directly.

  "programFan_Mo-So_0"		=> {cmd2=>"0A1DA0", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programFan_Mo-So_1"		=> {cmd2=>"0A1DA1", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},
  "programFan_Mo-So_2"		=> {cmd2=>"0A1DA2", argMin =>  "00:00",	argMax =>"24:00",	type =>"7prog",  unit =>""},

The logs shows that in this case all programs of this type are updated (programFan_Mo-So_0, programFan_Mo-So_1 and programFan_Mo-So_2)

In my config programFan_Mo-So_0 is 00:00-16:30 (which was already there),
i added programFan_Mo-So_1 (see a and b examples)
programFan_Mo-So_2 is empty.

The following data was received:

a) 17:15 - 18:15

0x1da0 raw value: 66
0x1da1 raw value: 17481
0x1da2 raw value: 32896

b) 18:00 - 19:00

0x1da0 raw value: 66
0x1da1 raw value: 17484
0x1da2 raw value: 32896

[zimbo86]

okay, its getting closer.
00:00 - 02:00 returns "8"
00:00 - 01:00 returns "4"
00:00 - 16:30 returns "66"

so with a beginning of 0:00 its pretty easy, as the values are quarters (like they can be set manual on the WP display)

02:00 = 2 hours = 8 quarters
16:30 = 16 hours = 64 quarters, 30 minutes = 2 Quarters = 66 quarters

[zimbo86]

01:00 - 02:00 returns "1032"
1032 bytewise is 0x0408 => 04 08 => Start: 4 quarters , End: 8 quarters
02:00 - 03:00 returns "2060"
2060 bytewise is 0x080C => 08 0C => Start: 8 quarters , End: 12 quarters

That works for "small" values.

However when I use
18:00 - 19:00 17484
0x445C => 44 5C => Start: 68 quarters , End: 92 quarters which makes no sense..
But correct would be 0x484C (dec 18508, 72 quarters, 76 quarters.

17:15 - 18:15 17481
0x445C => 44 49=> Start: 68 quarters , End: 73 quarters..
But correct would be 0x4549 (dec 17.737, 69 quarters, 73 quarters.

[kr0ner]

Good job finding this stuff out :)

How do you plan to visualize and schedule the date/times ?
I faced the same problem in the beginning and then decided to drop the idea and use https://github.com/nielsfaber/scheduler-card instead.
It could also be "hacked" to send the schedule to the heatpump instead of scheduling the stuff in HA

[Dobbiiey]

01:00 - 02:00 returns "1032" 1032 bytewise is 0x0408 => 04 08 => Start: 4 quarters , End: 8 quarters 02:00 - 03:00 returns "2060" 2060 bytewise is 0x080C => 08 0C => Start: 8 quarters , End: 12 quarters

That works for "small" values.

However when I use 18:00 - 19:00 17484 0x445C => 44 5C => Start: 68 quarters , End: 92 quarters which makes no sense.. But correct would be 0x484C (dec 18508, 72 quarters, 76 quarters.

17:15 - 18:15 17481 0x445C => 44 49=> Start: 68 quarters , End: 73 quarters.. But correct would be 0x4549 (dec 17.737, 69 quarters, 73 quarters.

This is strange - I was pretty sure, that it's working "reliable with the logic"... (but I had times like 7:00 - 18:00 // 9:00 - 15:00)
I will do tests similar to your examples in the next week...

@zimbo86 : you are right with: "StartDay and StartNight, its StartDay and EndDay" -> we are talking about the same. Sorry not beeing precise ;-)
(StartDay = TimeAtDayStarts // EndDay = TimeAtDayEnds && TimeAtNightStarts)

Do you have progress to "write the programs with HomeAssistant/ESP32"?

[zimbo86]

some more values....

[zimbo86]

hmm I dont get the logic after 12am. Maybe someone else has a clue? It seems that the starting time always matches. But the second value differs in hours, minutues are fine.

[Dobbiiey]

Hi @zimbo86 , could you please verify/check dec2hex calculation ? (My excel shows different values).
thanks

[zimbo86]

Hi @zimbo86 , could you please verify/check dec2hex calculation ? (My excel shows different values). thanks

wtf, that costs me hours. Thank you!
i put all the data in chatgpt and it calculated the hex wrong starting at 12:00

So the solution is pretty simple...
Now we need a logic to write this to WP (and I think this was the basic question of this issue, sorry)

Basically
If we intially limit the programs to Mo-So for fan, hc and dhw:

Input field in format
HC_DAY_0 = "XX:XX - XX:XX"
HC_DAY_1 = "XX:XX - XX:XX"
HC_DAY_2 = "XX:XX - XX:XX"
When one of them changed:
=> Convert to quarters to decimal, send to 0B14A0 ,0B14A1 and 0B14A2

Pretty inconvenient..