Danfoss thermostat protection not working

pos · November 10, 2017

Hi

Running 4.140

Trying to lock my Danfoss/Popp thermostat by clicking in the HC2 GUI. It immediately goes back to OFF state. Looking at the json object I can se no change...

Is this by design or a bug?

Please login or register to see this image.

Please login or register to see this attachment.

I.Srodka · November 10, 2017

Hi @pos,

Is this Danfoss LC-13 in version 1.1 or 1.0?

pos · November 10, 2017

It is 1.0.

And if I remember it right it worked in earlier releases....

{

"id": 894,

"name": "Termostat",

"roomID": 16,

"type": "com.fibaro.thermostatDanfoss",

"baseType": "com.fibaro.hvac",

"enabled": true,

"visible": true,

"isPlugin": false,

"parentId": 893,

"remoteGatewayId": 0,

"interfaces": [

"battery",

"zwave",

"zwaveProtection",

"zwaveWakeup"

],

"properties": {

"batteryLevel": 61,

"parameters": [],

"pollingTimeSec": 0,

"wakeUpTime": 300,

"zwaveCompany": "Danfoss",

"zwaveInfo": "6,3,67",

"zwaveVersion": "1.0",

"RFProtectionState": "0",

"RFProtectionSupport": "1",

"batteryLowNotification": "true",

"configured": true,

"dead": "false",

"defInterval": "0",

"deviceControlType": "0",

"deviceIcon": "34",

"emailNotificationID": "0",

"emailNotificationType": "0",

"endPointId": "0",

"liliOffCommand": "",

"liliOnCommand": "",

"localProtectionState": "0",

"localProtectionSupport": "5",

"log": "",

"logTemp": "",

"manufacturer": "",

"markAsDead": "true",

"maxInterval": "0",

"minInterval": "0",

"model": "",

"nodeId": "59",

"parametersTemplate": "803",

"productInfo": "0,2,1,21,160,16,1,0",

"protectionExclusiveControl": "0",

"protectionExclusiveControlSupport": "false",

"protectionState": "0",

"protectionTimeout": "0",

"protectionTimeoutSupport": "false",

"pushNotificationID": "0",

"pushNotificationType": "0",

"remoteGatewayId": "0",

"saveLogs": "true",

"serialNumber": "",

"smsNotificationID": "0",

"smsNotificationType": "0",

"stepInterval": "0",

"targetLevel": "15.50",

"timestamp": "1510277166",

"unit": "C",

"useTemplate": "true",

"userDescription": "",

"value": "15.50"

},

"actions": {

"reconfigure": 0,

"setInterval": 1,

"setTargetLevel": 1,

"setTime": 1

},

"created": 1509915266,

"modified": 1509915266,

"sortOrder": 148

}

I.Srodka · November 10, 2017

Hi again @pos!

Since I didn't know at first which version you have, I've tested both, however on the v.4.141:

Danfoss 1.1

Please login or register to see this attachment.

Danfoss 1.0

Please login or register to see this attachment.

Please login or register to see this image.

/monthly_2017_11/5a05828bf2f65_Danfoss1.0.png.a860b4b5cd8c350a03c985e849e668d3.png">

And then local protection:

Please login or register to see this attachment.

But please remember to wake up the device after you click save in the Home Center interface.

I do have to admit that I used HC with 4.141 version so some fixes could be applied.

pos · November 10, 2017

Hi @I.Srodka

I have tried to wake up the device as well. It simply does not work! I use 4.140. I usually do not use betas....

What is your opinion on 4.142? Is that beta stable enough to try ?

!´ll try it... U could always do a restore

/Peo

I.Srodka · November 10, 2017

@pos, well... it's beta as you said.

If you have time to restore the backup in case of any problems, you can always try ; )

pos · November 10, 2017

Hi again @I.Srodka

Now I have upgraded to 4.142. Did not see any immediate problems with 4.142. Looks ok. I have tried to wake the device several times. This knob goes back to OFF! I have also soft reconfigured the thermostat device. Same problem. The device works as is should, but the "Local Protection" knob is not working. Could be 1.0 vs 1.1 issue. I am not that good in the the firmware differences.

Any suggestions?

I.Srodka · November 10, 2017

Could you exclude and include the device?

pos · November 10, 2017

Hi @I.Srodka

Will do and get back

Hi @I.Srodka

No I have done that. So no it is new and assigned to "unassigned". I have done the same procedure change value, save, wake device. It does not work. Shouldn't the value when setting local protection to ON at least be saved in the HC2 gui and stored in the json object until the device is waked up? It almost seems like a gui problem...

I.Srodka · November 10, 2017

33 minutes ago, pos said:

Shouldn't the value when setting local protection to ON at least be saved in the HC2 gui and stored in the json object until the device is waked up? It almost seems like a gui problem...

GUI shows the actual state.

So it shows off until the device is woken up and reports otherwise.

pos · November 10, 2017

I set to ON and save.... Then when I wake the device it can take a new temp from the HC2 but never the lock state.

I tried to connect the device temporarily to a Danfoss Link. There the lock works against the thermostat. Assigning it back to the HC2 still gives nothing at all. You know... it worked in an earlier HC2 release if I am not misstaken.

So... What do you think is the way forward here?

I.Srodka · November 10, 2017

2 minutes ago, pos said:

Then when I wake the device it can take a new temp from the HC2 but never the lock state.

How do you know it's not in the lock state? Did you try to change the temperature manually?

Quote

So... What do you think is the way forward here?

I think it's not version dependent since it works for me.

pos · November 10, 2017

According to Danfoss the lock state is 100% tied to the fact that you have a lock in the display. But I tried that as well now.. Does not work.

Can you log in to my box?

I would appreciate if you could take a look into my box if possible....

Please login or register to see this attachment.

Sorry. I forgot that the file names cannot be seen.. The pictures are in order. So here is the info...

Please login or register to see this attachment.

I.Srodka · November 10, 2017

Could you provide a little bit taller screenshots? Together with the device data, just as I posted above.

pos · November 10, 2017

Is this ok?

Please login or register to see this link.

pos · November 10, 2017

Hi again @I.Srodka

When I try to change lock state on the thermostat and click save, I can see in the HC2 GUI that the temperature sensor is waiting for wake up, not the thermostat???? In fact, I have tried to change this lock state on the master as well as on the slave devices (thermostat+temp sensor) with no success.

Could this be a template issue with the Popp thermostat, an issue that appeared in newer releases as it has a reporting temp sensor in the device, which is not the case for the std LC13. If you have tested with an 1.0 device and with the same HC2 version, I cannot come up with anything else.

You are very welcome to log in to my system and check... Can you do that?

/Peo

I.Srodka · November 13, 2017

On 10.11.2017 at 2:19 PM, pos said:

Is this ok?

Please login or register to see this link.

I meant screenshots with device name and picture (the first section from top).

On 10.11.2017 at 4:36 PM, pos said:

Could this be a template issue with the Popp thermostat, an issue that appeared in newer releases as it has a reporting temp sensor in the device, which is not the case for the std LC13. If you have tested with an 1.0 device and with the same HC2 version, I cannot come up with anything else.

Sure, that could be an issue because as you said, I didn't have additional temperature sensor.

pos · November 13, 2017

Hi again @I.Srodka

I think of buying 15 more Popp.... The locking is not that critical. But of course I want it to work... Especially as I have kids with big fingers

One fishy thing is that no matter what you change on the Popp thermostat, the temp sensor slave is waiting for wakeup, not the thermostat slave...

Is there anything I can give you that could help solving this?

Or can we schedule a login to my system so you can look?

Tnx

/Peo

pos · November 15, 2017

@I.Srodka

It worked in an earlier HC2 release if I am not misstaken (not 100% sure though).

Is it perhaps something with the templates?

I *quess* you have Product type="8005" id="0001" OR Product type="0005" id="0004" on your Living Connect whereas I have Product type="0115" id="a010" on the Popp version as you can see below.

<zwaveData>
       <basicClass>04</basicClass>
       <manufacturerID>0002</manufacturerID>
       <productType>0115</productType>
       <productID>A010</productID>
       <zLibraryType>06</zLibraryType>
       <zProtocolVersion>03</zProtocolVersion>
       <zProtocolSubVersion>43</zProtocolSubVersion>
       <applicationVersion>01</applicationVersion>
       <applicationSubVersion>00</applicationSubVersion>
       <routing>true</routing>
       <flirs>false</flirs>
   </zwaveData>

Can you please check this up. As I cannot go under the hood on the HC2 it is a little bit tricky for me to track this down myself. I am dependent on you

Many thanks in advance

Peo

pos · November 17, 2017

Hi again @I.Srodka

In an earlier post I wrote: "One fishy thing is that no matter what you change on the Popp thermostat, the temp sensor slave is waiting for wakeup, not the thermostat slave..."

I *guess* the problem could be here. Is it possible for you to check this or log this problem?

Regards

Peo

pos · November 24, 2017

@I.Srodka

What can I do to help track this down so these devices work with the locking function ?

/Peo

Welcome to Smart Home Forum by FIBARO

Danfoss thermostat protection not working

Question

pos 22

21 answers to this question

Recommended Posts

I.Srodka 4

pos 22

I.Srodka 4

pos 22

I.Srodka 4

pos 22

I.Srodka 4

pos 22

I.Srodka 4

pos 22

I.Srodka 4

pos 22

I.Srodka 4

pos 22

pos 22

I.Srodka 4

pos 22

pos 22

pos 22

pos 22

Join the conversation

FORUM

KNOWLEDGE

DOWNLOADS

SUPPORT