[SOLVED]heating panel / linked device problem

[Edb 1]

hello. Ive been using the heating panel for my heating. the set up ive got is

fibaro motion sensor

230v normally closed actuator heat on all my radiators controlled by a fibaro single relay wired into the mains

 and another single fibaro relay controlling the boiler  ( just using it as a switch live output when its turned on)

the heating panels set up so nothing is on durning the day

 

for each room in the linked devices there is a fibaro motion sensor for temp , the relay controlling the radiator actuator and the boiler relay to call for heat

the problems im having are, during the day when all the zones are turned off a couple of the relays controlling the radiators are still on, even though they should be off.

and ive noticed that the boiler doesnt stay on for any length of time. with a room calling for heat, the radiator valve are switched on, the boiler comes on for a minute or so, then goes off, then comes on etc

has anyone got any ideas why this is happening?

many thanks

Please login or register to see this attachment.

Please login or register to see this attachment.

 

[Dave_H 52]

Here's a starter for 10 for you then 

 

This scene (hopefully) works by turning on the boiler switch whenever any of the radiator switches has been turned on by the Heating Panel.

 

Please login or register to see this code.

 

You'll need to change the list of device ids in the properties section of the scene header - one for each of your radiator valves:

Please login or register to see this code.

 

This list should also be configured in the radiatorValves variable:

Please login or register to see this code.

And the boiler switch device id will also need to be configured:

Please login or register to see this code.

 

Let me know if it works.

 

Dave

[T.Konopka 8]

So you have a couple of heating schedules and they differ from room to room?

Is any of the switches added in more than one "Linked Devices" settings?

[Edb 1]

Hello, ive got 12 rooms set up, each with a different time and temp. generally all rooms except one are off durning the day. each room has its own radiator valve and motion sensor for temp. the only common linked device is each room has the boiler control ( seen in screen shot above) so the boiler can be turned on as off when the room is calling for heat, otherwise every room is totally independant of the other rooms with no shared devices.

[Edb 1]

Hello, ive timed the cycling of the boiler. When single or multiple radiators are calling for heat the boiler switch comes on for 1 min, then off for 1 min, then on for 1 min etc.. and it carries on like that. The radiator valves are on all the time durning the time the boiler is cycling.

Thanks ed

Edited December 9, 2017 by Edb

[Dave_H 52]

Hi @Edb

 

I don't have any linked devices configured, but AFAIK, they are intended to pair a single temperature sensor with a single heating device.  So what I think is happening in your situation is that one linked device is turning on the boiler because the room that that device is associated with needs heat, but shortly afterwards one of the other linked devices associated with a room that doesn't need heat is turning the boiler off.

 

I think that you'll need to remove the boiler switch from the linked devices.  Just let the linked devices control the radiator valves.  And then you'll then need to write a scene to turn on the boiler switch whenever any of the rooms needs heat.

 

Dave

 

 

[Edb 1]

38 minutes ago, Dave Harrison said:

Hi @Edb

 

I don't have any linked devices configured, but AFAIK, they are intended to pair a single temperature sensor with a single heating device.  So what I think is happening in your situation is that one linked device is turning on the boiler because the room that that device is associated with needs heat, but shortly afterwards one of the other linked devices associated with a room that doesn't need heat is turning the boiler off.

 

I think that you'll need to remove the boiler switch from the linked devices.  Just let the linked devices control the radiator valves.  And then you'll then need to write a scene to turn on the boiler switch whenever any of the rooms needs heat.

 

Dave

 

 

makes perfect sense. TBH i would have thought that when fibaro put a " heating Panel" out with the option to control individual room then they would have left a solution to this problem as well, rather than now having to write a script to finish the job off.

many thanks Dave, now all i have to do it ...learn lua !!!! lol

that brings me to my next point.if i got it working  I would love to use your script for multi room call for heat BUT... seeing that im using switch controlling actuators as radiator thermostats there isn't the option in the controlled devices section in the advanced tab in devices to make it a thermostat. Ive asked fibaro it this can be added cause, surly, im not the only person to have this set up or need.

Is there a way of adjusting your script to use a switch instead of looking for the default thermostat?

 

[Edb 1]

just tried it.. seem to work fine. boiler stays on and then turns off when the rads turn off. Ill monitor over the next few days and see how it goes. its nice to have hot rads , before with the boiler cycling every min then took such a long time to get hot,

many thanks

 

just manually turned of the  rads rather than wait for the temp to turn them off andf got this bebug...

11:00: *** Keep heating on
[ERROR] 19:11:00: Cannot query interpreter state

 

its carried on and is working fine again, just maybe was havign a fit cause i turned them off.. 

thanks

 

[Dave_H 52]

1 hour ago, Edb said:

11:00: *** Keep heating on
[ERROR] 19:11:00: Cannot query interpreter state

 

This seems to

Please login or register to see this link.

, something to do with multiple concurrent executions of a scene by the looks of things.

[Edb 1]

hi dave. its been working fine. ive got to 4.151 and havent checked the error but the house is toasty warm ( where it should be) and they all turn off. I solved the heating panel not turning off a rad problem by setting it to 10 degrees rather than off and that seems to cure it. thanks fo rthe script and if fibaro update their devices so i can use a switch as a thermostat ill use your other script and get some window sensors.

thanks for the help

Ed

[Dave_H 52]

Great!  Glad to hear that it's working 

[Rudolph 8]

Hi guys, I just upgraded (after 4 long years) from a Vera to a HC2 (4.150 ), and am migrating existing actuators, sensors & logic. I am trying to use existing Horstmann HRT4-ZW thermostat, originally paired with HRT4 ASR-ZW receivers.But as the latter keep breaking and on the Vera were unreliable showing their state I thought of linking them with Fibaro relay switches. Well, I tried several times, also tried the association route, but while I can control the HRT4's fine from the HC2 (set point can be ste and actual temps show up correct ) the relay switch does nada.

 

Now I read somewhere that 4.150 has an issue in this area, but could not find if it was solved. In another  thread I found a potential issue with templates, but the device shows:

 

 

Device kind:com.fibaro.thermostatHorstmann

 

Producer:Horstmann Controls Limited

 

Version:5.0

 

Configuration:Device configured

 

If a link is a problem I can go the LUA route, but I struggle to get more out of the thermostat than setpoint and actual temperature. How do I extract the value (I assume 0 or 1) that is send to the boiler receiver to start/stop the boiler?????

I played with below scene to see if I could find the answer, but I have to admit I am not fluent in LUA, I tend to copy and modify the nice examples I find on forums:)

Anybody any suggestions ?

 

 

--[[
%% properties
%% events
%% globals
--]]

fibaro:call(17,"setTargetLevel", "24")
local val=(fibaro:getValue(17, "value"))  -- curr temp
local setp=(fibaro:getValue(17, "targetLevel"))  -- target temp
local interval=(fibaro:getValue(17, "interval"))
local mode=(fibaro:getValue(17, "operatingMode"))
local log=(fibaro:getValue(17, "log"))
fibaro:debug(val)
fibaro:debug(setp)
fibaro:debug(interval)
fibaro:debug(mode)
fibaro:debug(log)

 

response:

[DEBUG] 17:51:33: 24
[DEBUG] 17:51:33: 24
[DEBUG] 17:51:33: nil
[DEBUG] 17:51:33: nil
[DEBUG] 17:51:33: WAITING_FOR_WAKEUP_TO_CONFIGURE

 

[Dave_H 52]

Hi @Rudolph

 

You might find that it's the 'mode' property that will tell you whether or not the boiler receiver is on or off, eg:

Please login or register to see this code.

Take a look at my

Please login or register to see this link.

.  There's a good possibility that this will work with the Horstmann thermostat and receiver.

 

Dave

[Rudolph 8]

Hi Dave,

 

Thanks for the reply and your code, seems spot on to replace the thermostat function of the HR4 ZW in LUA. Will try ASAP  and let you know.  And I will use your above code for Fibaro thermostatic valves the moment I will add them to the system

 

I am still curious WHY it does is not possible to link the HR4 ZW  direct in the HC2  with a regular Fibaro relay actuator ???.

 

And I always assumed as it was a thermostat the logic to compare set point and actual temperature would be in the HRT4 and it would send a simple 1 or 0 signal to the SR302 if it did or did not need the boiler on. How to get this signal read in the HC2 ???

 

Anyway, I am still very happy to find how much easier things are with the HC2 compared with the VERA!!

 

Ruud

 

 

[LordOfFalcons 5]

i had exactly the same problem and used the solution here as well as the script. just wanted to say thanks.

 

also, out of curiousity. why is it that the device IDs have to be declared twice? both up top as propoerties. and then again below when the array is loaded into the device list? is it not enough to define the device id's by loading the array? (i'm new to lua, so apologies for stupid question)

[Dave_H 52]

On 9/4/2018 at 9:22 PM, LordOfFalcons said:

also, out of curiousity. why is it that the device IDs have to be declared twice? both up top as propoerties. and then again below when the array is loaded into the device list? is it not enough to define the device id's by loading the array? (i'm new to lua, so apologies for stupid question)

 

Hi @LordOfFalcons

 

Sorry for the long overdue reply.  The reason for declaring them twice is because the block at the top isn't really part of the lua code...this is a comment block which is picked up by the HC2.  This comment block is used to define the triggers that initiate the scene.  In this case, the scene will run whenever the 'value' property of any of those devices in the %% properties section changes value.

 

You're then able to use the following code to find out which device triggered the scene:

Please login or register to see this code.

 

[LordOfFalcons 5]

took me a while to process, but just added those lines to the code and it's very handy. 

 

thanks again!!!

Edited September 24, 2018 by LordOfFalcons

[stomko 0]

I have Secure SSR 301. However I am struggling to understand the difference - when I paired the device, it shows up twice with 2 different IDs, one as a simple on/off switch, the other with off/heat ("setMode", "0" or "1") switches. The difference is that while with on/off commands, it stays on/off until next state change, when setting it ON with setMode, it has fail-safe mode which will turn off after about 60 minutes (so that it doesn't heat forever). However, when failsafe is triggered, mode still stays "1" so I can't really read "mode" and compare it and if 0, turn it on, as I would get message that it is already on... it was, but it is now in failsafe.

I want to use it for heating, to turn on/off heatpump. Scene will be triggered by the state change of relays that control circuits. Should I be using simple on/off switch, or setMode. How to correctly handle "setMode" behavior?

 

Thanks for guidance.

 

Please login or register to see this image.

/monthly_2018_11/image.png.abff2c4bb78c819ffc6feff89b1f8eaa.png" alt="image.png.abff2c4bb78c819ffc6feff89b1f8eaa.png" />

 

 

 

 

 

 

[mikeshep 1]

On 12/10/2017 at 5:30 PM, Dave Harrison said:

Here's a starter for 10 for you then 

 

This scene (hopefully) works by turning on the boiler switch whenever any of the radiator switches has been turned on by the Heating Panel.

 

Please login or register to see this code.

 

You'll need to change the list of device ids in the properties section of the scene header - one for each of your radiator valves:

Please login or register to see this code.

 

This list should also be configured in the radiatorValves variable:

Please login or register to see this code.

And the boiler switch device id will also need to be configured:

Please login or register to see this code.

 

Let me know if it works.

 

Dave

Hi Dave,

 

Thank you you very much for this but I’m obviously doing something wrong as it is only turning the boiler on but not off. 

I have Fibaro multi sensors detecting the temperature in each room but not linked to the boiler switch in linked devices. Is this correct? 

Please help, thanks in advance,

 

Mike

[Dave_H 52]

7 hours ago, mikeshep said:

Thank you you very much for this but I’m obviously doing something wrong as it is only turning the boiler on but not off. 

 

Hi @mikeshep

 

What type of switches do you have on your heating devices?  The scene is expecting the value to change from zero when the switch is off, to a positive value when it's on, as indicated by this bit of code:

Please login or register to see this code.

If you haven't got switches for the heating devices but TRVs instead on your radiators, then take a look at this scene: 

Dave

[mikeshep 1]

On 12/10/2017 at 5:30 PM, Dave Harrison said:

Here's a starter for 10 for you then 

 

This scene (hopefully) works by turning on the boiler switch whenever any of the radiator switches has been turned on by the Heating Panel.

 

Please login or register to see this code.

 

You'll need to change the list of device ids in the properties section of the scene header - one for each of your radiator valves:

Please login or register to see this code.

 

This list should also be configured in the radiatorValves variable:

Please login or register to see this code.

And the boiler switch device id will also need to be configured:

Please login or register to see this code.

 

Let me know if it works.

 

Dave

Hi Dave,

 

Thank you you very much for this but I’m obviously doing something wrong as it is only turning the boiler on but not off. 

I have Fibaro multi sensors detecting the temperature in each room but not linked to the boiler switch in linked devices. Is this correct? 

Please help, thanks in advance,

 

Mike

Yes I’ve got Danfoss TRVs so that’ll be why. I’ll try the other scene you linked to. Many thanks for your time and skill.