do not use °C and try again
-
Max! plugin Questions
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
removed the °C in the rule and in the variable - same error
btw: I just realized, that the “°C” doesn’t work as a unit for the variable, it’s simply not saving the unit, probably because ° is not supported.
-
in my rules it works with
then set temp of Hzg-Bad to $heizenbad
ah whats value has your variable?
15,5 is in pimatic 15.5!
-
I tried to narrow the issue down, without success. This is what I tried:
- I executed the rule with a dummy switch
- I changed the name of the thermostat device (removing the brackets to avoid any issues there)
- I tried another thermostat device
Next step: I will try to setup a new window contact, after that I believe I ruled out all hardware related issues…
-
OK, different window sensor and thermostat and still same issue.
@chris this is exactly how I set it up for my second rule, that fires when I close the window. There it works perfectly fine. The hex string error only pops up on the open window rule.
-
so i just tested
{ "id": "testguybrush", "name": "testguybrush", "rule": "when every 10 seconds then set $testguybrush to $Hzg-Bad.temperatureSetpoint", "active": true, "logging": true }
works fine
-
so maybe just delete the variable and the rule and begin from start again
sometimes it’s just a cup of coffee and some minutes distance what helps
-
hehe, I know - that’s exactly what I did. I also reduced the rule to the bare minimum - the issue even comes up if I only say “then set temp of Schlafzimmer (Fenster) to 5°C” or “then set temp of Schlafzimmer (Fenster) to 5”. To me it looks like the device “Schlafzimmer (Fenster)” can’t handle the temperature setting… Is there something wrong with my hardware setup? Changing the temperature in the interface on the device itself works perfectly fine…
{ "rfAddress": "0888ec", "guiShowModeControl": true, "guiShowPresetControl": true, "guiShowTemperatureInput": true, "guiShowValvePosition": true, "id": "schlafzimmer-fenster", "name": "Schlafzimmer (Fenster)", "class": "MaxHeatingThermostat", "comfyTemp": 21, "ecoTemp": 17, "vacTemp": 14 }
-
Hui,
{ "id": "Hzg-Bad", "class": "MaxHeatingThermostat", "name": "Hzg-Bad", "rfAddress": "07cebd", "comfyTemp": 23, "ecoTemp": 16.5 },
this is my device
-
hmmm… thanks for sharing. I don’t see any significant difference. Very weird. I’ll give up for today and hope to figure it out tomorrow. Probably some very simple issue I just don’t see the Wald vor lauter Bäumen.
-
already tried name “Schlafzimmer (Fenster)” without brackets? >> “Schlafzimmer -Fenster” …
-
Yep, already tried, no success…
Any idea what “invalid hex string” usually means? The only hex string I could think of is the ID of the thermostat… -
courious…
check if the Thermostat device was in manual mode…
-
nope, all set to “Auto”. and changing the temperature with the thermostat device interface in pimatic works flawlessly…
-
my thermostat “receives” the setpoint only if they are in manual mode, in auto mode i got the same error
in manual mode they will worl flawlessy
-
that’s weird - looks like a bug that might be related to the issue I’m seeing…
-
in auto mode i could set temperatures >=7.5°C, below i got the hex-error.
maybe @sweetpi knows whats the difference between auto and manual and could answer that
-
Another interesting finding: It works for one thermostat but not for all the others!
If I use this thermostat it works:
{ "rfAddress": "0107ab", "id": "temperatur-kuche", "name": "Küche", "class": "MaxHeatingThermostat" }
however it doesn’t work for example for this thermostat:
{ "rfAddress": "007b85", "id": "schlafzimmer-tur", "name": "Schlafzimmer (Tür)", "class": "MaxHeatingThermostat" }
-
i can confirm, the auto mode does not admit temperatures lower then 7.5 degrees.
here’s some more detailed debug.
another thing that i need to complain is that if you try to insert a temp manually you are only having some milliseconds for the input of the numbers. the time for the submission of the input field should be extended to at least 2 seconds!
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !