How to use com.fibaro.hvacSystemAuto?

[PeterV959 11]

There are new properties associated with this device. Is there any documentation on how to set up this device using a QuickApp to interface with a cloud based thermostat? Specifically I want to know what the method autoThermostatSetpoint property is intended to do? I would expect it to contain two values but when I examine the device info there is only one value and it is certainly not a realistic value for a thermostat.

 

Here's a screenshot of the swagger device dump:

 

Please login or register to see this image.

/monthly_2024_07/image.png.7e6fb6f74269f138dd7c22848c5ec8f6.png" />

 

This would appear to be not fully implemented or I'm just ignorant on discovering its use.

 

I am running version 5.160 and I've been having fits getting the two setpoints to update because of the way they get updated from the Climate panel.

 

Thank you in advance.

 

Peter

[jakub.jezek 370]

18 minutes ago, PeterV959 said:

autoThermostatSetpoint property

That is which desired temperature QA is set to.

 

Basically Setpoint == Desired temperature.

[Neo Andersson 230]

@jakub.jezekdoes this affect the other API calls ? They did not have the "auto" prefix if i remember correctly.Maybe i am wrong. Will the old commands and properties still work?

Edited July 11, 2024 by Neo Andersson

[jakub.jezek 370]

1 hour ago, Neo Andersson said:

Will the old commands and properties still work?

Dunno, only way to check is to test it.

[Brors94 115]

I think the autothermostatsetpoint is what value u want it to stay on.

 

and this too sets the hystiresis.

Please login or register to see this code.

 so if you set the hysteresis too 2 and auto setpoint too 24 it will start cooling above 26 and if the temperature fall below 22 it will start heating? 
this is just a guess  But is what seems logical too me

 

 

[PeterV959 11]

So I guess it begs the question, how do I use these properties in lieu of the coolingThermostatSetpoint and heatingThermostatSetpoint properties? I am using the climate schedule panel to control my HVAC and none of those auto properties are referenced anywhere. There are also two actions I don't recall seeing before: setAutoThermostatModeAndSetpoint and setAutoThermostatSetpoint. And I don't see evidence of their being accessed either. I find it frustrating that so little integration information comes from Fibaro. Most of what I can find comes from experienced users or integrators who have fiddled with stuff until it works. I had hoped that the setAutoThermostatModeAndSetpoint would pass the mode and the heating & cooling setpoints in a table. But now I think you are right that it uses a single setpoint and the two hysteresis values instead. I can go either way. I have issues with the way the climate panel updates the thermostat since it sends each setpoint individually without regard to setting the first setpoint to an invalid state (new heating temp higher than the old cooling setpoint) which resolves when the second setpoint is sent.

 

Thanks for your insights.

 

Peter

Edited July 12, 2024 by PeterV959

[Brors94 115]

Yeah I got explained that the climate panel in fibaro sets all the values when updating the thermostat (mine have only cooling and heating).

Even when it is set to heating only. 

And this somtimes fucked up the thermostat 😅

[PeterV959 11]

I am using a good QA for my Nest Thermostat by someone from France. Since he wrote it for himself, he only concerned himself with heating and his displays were in ℃. I'm in the southeast USA and we have air conditioning and heating, plus we think in ℉. I was able to update the code to better use Auto mode and display the temperature in ℉. Furthermore, the Nest Thermostat uses ℃ for its setpoints. So there needed to be a conversion between the two units. All was fine until I began to play with the climate panel. I kept having issues with one of the setpoints not updating and struggled with that for a while before I realized a couple things. First, the heat SP is sent as an action, followed immediately by the cool SP. However, in auto mode, the Nest cloud requires both setpoints to be sent. I went round and round before I realized that. So when I would send an initial heat SP which was above the old cool SP, it would throw an error. And, since I didn't know (or, more properly, I programmed defensively) whether the cool SP would be coming, I made sure that the new heat SP would be accepted by sending a new cool SP that would work. I relied on the cool SP being sent soon enough afterward that it would be a "momentary" blip. Now it seems to work fine. I wish I could get both SPs in one event message when Auto mode is used.

 

I will say that @jgab's fibemu has been invaluable for diagnosing the above. And my Nest Thermostat QA is on github. The author is Guillaume Waignier (GuillaumeWaignier on github). He has since added support for Nest motion detector and camera although those haven't interested me.

 

I did just look at my climate panel and when in heating or cooling mode it only has entries for one SP.

 

Have a great weekend.

 

Peter