Add support for POPP Smart Thermostat

[SwoopX]

See #5278.

[J-N-K]

Is there something blocking this PR? I have several requests for support from my application‘s users.

[Mimiix]

@J-N-K Manups time.

[Pe-MaKer]

@manup @Mimiix
sorry for poking you. Is there any chance of getting this merged soon?
I'm sitting on eight of these thermostats for my entire house and can't control them. The winter is coming. 🥶
I tried to compile it from @SwoopX branch by myself but it's already 500 commits behind the master which brings other troubles.

If I would know how to put the definition for this Popp derivative of the Danfoss Ally in a DDF, then it would be fine for me as well.

Without your support I'm screwed and the WAF of our new home is at 0.

[Pe-MaKer]

@manup @Mimiix
I don't want to be a pain, but it would ruin our Advent season if I don't finally master the thermostats.
My wife will ensure there's a fire🔥 otherwise.

Can you please take care that this commit by @SwoopX will make it in the next beta?
@J-N-K did you managed to get a solution by yourself?

[Mimiix]

@Pe-MaKer there's more PR s that are waiting longer. So it isn't fair to prioritize above...

[Mimiix]

I'll ask Manuel, but no promises.

[SwoopX]

@Pe-MaKer You can program the thermostats meanwhile via deconz GUI and set weekly schedules via the thermostat cluster. You probably should do that with my branch, as it should ensure the RCT on the device gets synced (check the time cluster attributes to be sure).

What you need to know is that you only have 6 transitions per day at your disposal. The time which needs to be entered is minutes since 00:00, heat set point must be multiplied by 100. The last temperature set on a day will be taken over to the next day until the next change is programmed.
The example below has two periods with comfort temperature set, ending up with 4 transitions and applies for Mon - Fri with the following times:

05:50 -> 21°
09:00 -> 17°
17:00 -> 22°
21:00 -> 17°

When the schedule is programmed by pressing exec, you need to activate the schedules on the thermostat. This can be done by setting attribute 0x0025 as per below.

You can override the scheduled temp anytime manually on the device and this will remain until the next transition.

My recommendation would be to overshoot the aimed comfort temperature by 2° in the schedule for the beginning, so set 24° if you want to have 22°.

[Pe-MaKer]

Thank you @SwoopX for the detailed information.
I have made my own and current fork of the master, and incorporated all the changes from your commit there.
https://github.com/Pe-MaKer/deconz-rest-plugin/tree/POPP

Unfortunately, the time sync does not seem to work, as you can see from the screenshots.
If the local time is given as Unix Epoch, the time of the termostat is about 35 years
off.

This makes the use of time schedules a challenge ;)

[SwoopX]

That more feels like the time sensor has not been created. Can you enter sensor search in Phoscon again and read the attributes of the basic cluster? After that, the sync should directly kick in and I know from own experience that it can be annoying like hell.

Edit:
Oh, an I just saw that you haven't applied all changes covered by the PR to your fork. The part allowing for creation of the time sensor is missing in de_web_plugin.cpp.