Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

Climate Zone control from QA


Guest

Question

Guest

I have several zones which is turned off from time to time. This can be a couple of days and it can be weeks.

On HC2 I have a VD with buttons which set the thermostat to off/heating

 

In HC3 Scenes I can see the below but these do not work in QA, any suggestion what to use? (And also what us the last nil in the arguments?second last is temperature..)

 

fibaro.homeCenter.climate.setClimateZoneToManualMode(9, 'Off',"Hold", nil, nil)
 
fibaro.homeCenter.climate.setClimateZoneToScheduleMode(9)
Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

I have tried all the variables shown in the Swagger. It doesn't work.

I think it is not allowed to set your zone to manual mode from the API.

This is the code, that was written according to variables shown in Swagger.

 

Please login or register to see this code.

 

If you chage the Plan from Scheduled to Manual only 2 relevant variables are changing in swagger.

The "handSetpointheating" and the "mode". 

 

But for some reason, if you try to change these variables in a API call like above, it has no effect. Plan doesnt change to Manual at all.

 

So this remains for me still a mistery..How can a user change the temperature on his radiator from the YUBII..no only for x hours, but permanently.? The short answer is NOT POSSIBLE...

 

 

Link to comment
Share on other sites

  • 0

With the handMode propertie of the climate api you can set it in manual mode and set temperature and timer for the manual mode.

With "mode": "Off" you can set it to Off.

 

Here how I used it in a scene but should also work in QA.

 

 

Please login or register to see this image.

/monthly_2022_02/image.png.053f4483c37045e741117c5071d4b341.png" />

On 12/23/2021 at 2:58 PM, Neo Andersson said:

I have tried all the variables shown in the Swagger. It doesn't work.

I think it is not allowed to set your zone to manual mode from the API.

This is the code, that was written according to variables shown in Swagger.

 

Please login or register to see this code.

 

If you chage the Plan from Scheduled to Manual only 2 relevant variables are changing in swagger.

The "handSetpointheating" and the "mode". 

 

But for some reason, if you try to change these variables in a API call like above, it has no effect. Plan doesnt change to Manual at all.

 

So this remains for me still a mistery..How can a user change the temperature on his radiator from the YUBII..no only for x hours, but permanently.? The short answer is NOT POSSIBLE...

 

 

 

The api properties mode from the climate panel doesn't support the state "Manual"

image.png.6d70761f6b32c5be14f01d235cf63754.png

 

The mode of the climate schedule is a different state then the mode you can set in het properties.

Link to comment
Share on other sites

  • 0

Aaaargh, that's insane, I've spent many hours figuring this out but - if anyone needs it - this is how you can do it using the api, works in HC3 in QuickApps:

 

    local climate_id = 12
    local climate=api.get("/panels/climate/" .. climate_id)
    climate.properties.handSetPointHeating = 22
    climate.properties.handSetPointCooling = 70 --needs to be bigger than Heating value
    climate.properties.handTimestamp = 4294967295   --forever, but you can put the unix epoch timestamp for example in 2h from now, so it will go back to schedule
    climate.properties.currentSetpointTimeStartHour = null --these need to be nulled, otherwise it just won't work
    climate.properties.currentSetpointTimeEndHour = null 
    climate.properties.currentSetpointTimeStartMinute = null 
    climate.properties.currentSetpointTimeEndMinute = null 
    climate.mode = "Manual"
    --self:debug(json.encode(climate)) --in case you want to see the json ;-)
    api.put("/panels/climate/" .. climate_id, climate)   
 
 
Edited by yoozef
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...