Input for values

#34

Hi
Using a thermostat in a home automated system without any schedule just doesn’t make any sense in
my opinion.I think a big majority of people (with intelligent home systems installed) do have schedules.
What would they do with a thermostat in an intelligent home without a schedule?
They would set just one setpoint for always and if needed they would change it manually?
Yes, it can work, but this is not a home automated system i think. On the other hand.

If I dactivated shcedules, Fibaro still requires to supply a lenght of time, however it can be zero, and in this case i think this setpoint will be used until I change it back to schedule mode or I change the setpoint, or the timeframe. I did’t test it for longer periods, i just deactivated schedule and tried to set up some setpoint. It always asked for some lenght of time, but in PC interface it allowed me to set it with 0 second, so a saved it, and waited a couple of minutes if it jumps back. It didn’t.

Anyway I would really like to have heating in HR, so i will do the following.

Right now i have set all my schedules as following.
Livingroom(Heatit) - 20° all the day
Office(Fibaro) - 20° all the day
Bedroom(Danfoss) - 18° all the day

Now I have just deactivated all three schedules.

At this point i have set the following values on thermostats. (set it manually in PC interface)

Livingroom Heatit - 23 - timeframe 0
Bedroom Danfoss - 17 - timeframe 0
Office Fibaro - 23 - timeframe 0

Downloading Jsons…Will name the accordingly.

Then I re-activated all the schedules.
At this point i have set the following values on thermostats. (set it manually in PC interface)
Livingroom Heatit - 25 - timeframe 2 hours
Bedroom Danfoss - 19 - timeframe 2 hours
Office Fibaro - 25 - timeframe 2 hours

Downloading Jsons…Will name the accordingly.
474_Without_Shedule_SetTo23.txt (5.3 KB)
609_Without_Shedule_SetTo23.txt (3.9 KB)
328_Without_Shedule_SetTo17.txt (2.7 KB)
328_With_Shedule_SetTo19_for_2hours.txt (2.7 KB)
609_With_Shedule_SetTo25_for_2hours.txt (3.9 KB)

474_With_Shedule_SetTo25_for_2hours.txt (5.3 KB)

I hope this helps.

#35

There’s nothing I can find in the JSON that indicates the schedule is disabled. Can you describe how you disabled the schedule in Fibaro? Can you attach a screenshot of the setting you disabled?

#36

The other day I had you run the setHeatingThermostatSetpoint API command on all of your thermostats except the Office.

What does Office Fibaro do if you try to run the command below while the schedule is active?

Set OFFICE FIBARO to 19 degrees:
http://IP_ADDRESS/api/callAction?deviceID=609&name=setHeatingThermostatSetpoint&arg1=19
Result: ???

Set BEDROOM DANFOSS to 19 degrees:
http://IP_ADDRESS/api/callAction?deviceID=328&name=setHeatingThermostatSetpoint&arg1=19
Result: Value on thermostat changes to 19 for 15 minutes.

Set LIVINGROOM HEATIT to 21 degrees:
http://IP_ADDRESS/api/callAction?deviceID=474&name=setHeatingThermostatSetpoint&arg1=21
Result: Value on thermostat jumps to 21 for a second. Then it jumps back.

#37

hr1
hr13440×1440 340 KB

hr2
hr23440×1440 234 KB

hr3
hr33440×1440 95 KB

hr4
hr43440×1440 147 KB

#38

Please install Designer version 4.4.8.0. You should now be able to change the setpoint for all 3 devices. It will automatically place a 2 hour hold each time you make a change.

I’ve added support for the ThermostatHold capability to the Fibaro integration. This allows you to track whether the thermostat is following the schedule or has a hold. And if it has a hold, you can track the time it expires. You can clear a setpoint hold & force it to resume schedule by setting the ThermostatHoldState to NoHold.

Resync your devices & the default templates. I made a minor change to ThermostatDetails.xaml. Not every thermostat hold menu option is compatible with Fibaro. The “Hold Until Next Period” & “Permanent Hold” options are not compatible. They will throw an error.

Let me know if this works. If it does, I’ll begin the process of rolling it out to the stores.

image
image575×1153 28.6 KB

#39

Side question:
How is your HR logic gettin a thermostat temperature value?
Are you looking for a Child ID in the device api call, then posting another API call with the (received ID) for the temperture value?

#40

hr6
hr62068×900 39.3 KB

And if trying to select something from the combo:
In case of first two options i am getting “Specific method is not supported…” error
In case of the last .“Response status code does not indicate success”

#41

You need to be using the parent id in order for the temperature to work. Your device object definition should look exactly like this. Please look at it closely.

image
image619×542 9.3 KB

#42

Do the changes I made work I not? Are now able to change setpoints? Does it set a 2 hour hold time?

#43

I just uploaded Designer version 4.4.9.0. This should fix the issue you had with the “No Hold” option. Please test to confirm it works.

#44

Hi, the temeprature is shown already.But the time-options in dropdown dont work.

hr8
hr83440×1440 99.2 KB

when trying to sleect any of HOLD options

HR9
HR91338×904 21 KB

#45

and when trying to select 17:08

hr10
hr101155×862 19.7 KB

#46

Did you read what I wrote earlier?

#47

The only Hold option that is compatible with Fibaro in that drop-down is “No Hold”. And you need to update to Designer version 4.4.9.0 for that to work.

So everything that I have said should work does work? Can you please verify? You still haven’t told me whether changing setpoints works.

#48

“Hold until…” --is a feedback for us about what is the current state of the thermostat. It means, in Fibaro interface the heatingSetpoint has been set with some time window, and saved. Thats what we can see. But if i am right, we can’t change it right? I can’t change the time, i can just track the situation right?

“No hold” - it forces the thermostat to go back to schedule mode if there’s any existing. Right?

“Hold until next period, and Hold permanently” - are not supported, did I get it right?

#49

Actually none of my thermostats can recognize any of those hold options in the dropdown.
Nor the Danfoss neither the Heatit brand. So its not only Fibaro that doesn’t support these options.

#50

So nothing works? Is that correct?

#51

Changing setpoint works.

#52

Quit selecting those invalid hold selections. Stop the simulator & restart it. Now try to resume schedule by selecting the “No Hold” option. That should work.

#53

No hold works. I will test it with other thermostats also. Give me 1 min pls.