You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to set the Party start and end time via Nodered 2.1.3 to a HmIP-eTRV-2 (Heizkörperthermostat). If I set PARTY_TIME_START for example to 2021_10_30 08:00 the PARTY_END_TIME jumps to "1999_11_30 00:00".
If I set the PARTY_END_TIME to my desiered value, the start time jumps to "1999_11_30 00:00":
I use the latest version 3.4.2 of node-red-contrib-ccu and a Homematic CCU2 with the latest firmware 2.59.7.
Has anybody a hint for me?
Thanks,
Ben
The text was updated successfully, but these errors were encountered:
partyModeTemperature needs a dot notation, e.g. 24.0
StartTime / StopTime in 30 minute intervals and given in minutes, e.g. 21:30 would be 1290
StartYear / StopYear only two digits, e.g. 21 and not 2021
Not tested and I also do not own HmIP devices.
The behavior you are seeing has been reported before and seems to be an issue of the HmIP devices and not of the CCU or RedMatic.
Hello,
I try to set the Party start and end time via Nodered 2.1.3 to a HmIP-eTRV-2 (Heizkörperthermostat). If I set PARTY_TIME_START for example to 2021_10_30 08:00 the PARTY_END_TIME jumps to "1999_11_30 00:00".
If I set the PARTY_END_TIME to my desiered value, the start time jumps to "1999_11_30 00:00":
I use the latest version 3.4.2 of node-red-contrib-ccu and a Homematic CCU2 with the latest firmware 2.59.7.
Has anybody a hint for me?
Thanks,
Ben
The text was updated successfully, but these errors were encountered: