Popp radiator thermostat parameter

Information about specific Z-Wave devices
Post Reply
JuanUil
Posts: 243
Joined: Friday 22 May 2015 12:21
Target OS: Raspberry Pi
Domoticz version: 2.xx
Location: Asten NB Nederland
Contact:

Popp radiator thermostat parameter

Post by JuanUil » Monday 12 December 2016 11:31

Hi there,

I have two Popp radiator thermostats.
In the control panel Z-wave I see a parameter "Override Setback" which is 127.
Could anybody tell me what this parameter stand for?

Tnx in advance
Jan
Your mind is like a parachute,
It only works when it is opened!

User avatar
felix63
Posts: 100
Joined: Monday 07 December 2015 10:30
Target OS: Raspberry Pi
Domoticz version: 3.8275
Location: Gouda
Contact:

Re: Popp radiator thermostat parameter

Post by felix63 » Wednesday 14 December 2016 10:30

Hi,

I have the same question as you. I have Danfoss LC13 thermostats which are the same or vary similar. Since upgrading Domoticz to the latest beta I get:

Code: Select all

2016-12-14 08:39:34.262 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: CLIMATE CONTROL SCHEDULE, Label: Override State, Instance: 1
2016-12-14 08:39:34.265 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: CLIMATE CONTROL SCHEDULE, Label: Override Setback, Instance: 1
So apparently Z-wave for these devices has a class CLIMATE CONTROL SCHEDULE which uses amongst others an 'Override Setback' and 'Override State'. It is intended to define some sort of time based scheduling for the thermostats which is not used or implemented as far as I can tell.

Cheers,
Lex

ropske
Posts: 248
Joined: Tuesday 12 August 2014 5:37
Target OS: Raspberry Pi
Domoticz version: V3_8394
Location: Rumbeke,Belgium
Contact:

Re: Popp radiator thermostat parameter

Post by ropske » Thursday 19 January 2017 7:21

Anyone find out more on this?
Where does it stand for?

You also have override state

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest