Hi, everyone.
I’m running OpenHAB 3.3.0. I have a Netatmo relay and 4 valves.
I’m wondering what the possible values of the Home (Bridge) Mode channel are. I want to change it with some DSL rules but I don’t see the values in the old or new documentation .
I also realized that the home channels were even removed from the documentation of v3.3.
My goal is to set the whole home to a different mode on special occasions (e.g., when away), so I don’t have to set the temperature of each valve individually. Especially, taking into account that setting the temperature manually is only applied temporarily.
I have been experimenting with the values set when I change the settings on the Netatmo Energy App to no avail. “Comfort”, “Away”, “Night”, and “Frost-guard” don’t seem to be supported.
“away”, “schedule”, and “hg” are not supported either, contrary to what’s mentioned in the Netatmo documentation.
These are my items:
//Home items
Number:Time Netatmo_Home_Setpoint_Duration "Setpoint Duration" { channel="netatmo:home:de-muc-01:XXXXX:energy#setpoint-duration" }
String Netatmo_Home_Planning "Planning" { channel="netatmo:home:de-muc-01:XXXXX:energy#planning" }
String Netatmo_Home_Mode "HVAC Mode" { channel="netatmo:home:de-muc-01:XXXXX:energy#mode" }
DateTime Netatmo_Home_Mode_End "Mode End" { channel="netatmo:home:de-muc-01:XXXXX:energy#end" }
I traced (as debugging doesn’t provide much information) the data in the Karaf Console and got the following when I changed the value of the Home item to the Frost-guard mode using the default values provided by the Main UI:
12/27/2022 16:12:18.242 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri POST https://api.netatmo.com/api/setthermmode?home_id=XXXXXXXXXXXXXXXXX&mode=hg
12/27/2022 16:12:18.384 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri returned : code [200 OK] body {"status":"ok","time_exec":0.00996708869934082,"time_server":1672153938}
When changed to Away:
12/27/2022 16:31:23.206 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri POST https://api.netatmo.com/api/setthermmode?home_id=XXXXXXXXXXXXXXXXXXX&mode=away
12/27/2022 16:31:23.278 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri returned : code [200 OK] body {"status":"ok","time_exec":0.018159866333007812,"time_server":1672155083}
When changed to Schedule:
12/27/2022 16:31:57.855 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri POST https://api.netatmo.com/api/setthermmode?home_id=XXXXXXXXXXXXXXXX&mode=schedule
12/27/2022 16:31:57.914 [TRACE] [tmo.internal.handler.ApiBridgeHandler] - executeUri returned : code [200 OK] body {"status":"ok","time_exec":0.010953187942504883,"time_server":1672155117}
The value is passed as the last parameter.
However, when I send a command to set the mode item to “away” with a test rule, I get the following error:
12/27/2022 20:29:00.799 [WARN ] [l.handler.capability.EnergyCapability] - Command 'away' sent to channel 'mode' is not a valid setpoint mode.
The same result happens with all the other values.
This is the rule:
rule "test"
when
Time cron "0 29 20 * * ? *"
then
Netatmo_Home_Mode.sendCommand("away")
end
Nonetheless, the JSON returned as a response to the GET by the APIBridgeHandler when changing the mode using the Main UI shows that “therm_mode” was set to “hg”, “away”, etc.
I wonder if there is another channel that updates the mode (therm_mode).
By the way, does anyone know why were the Home channels removed from the documentation and why were they not documented in the section on breaking changes in the official release notes of v3.4?
