Smanar / Domoticz-deCONZ

deCONZ plugin for Domoticz (Zigbee application)
GNU General Public License v3.0
36 stars 27 forks source link

add Device SPZB0001 ( thermostat) #31

Closed salopette closed 4 years ago

salopette commented 4 years ago

https://www.amazon.de/gp/product/B077GCDDBY/ref=ppx_yo_dt_b_asin_title_o06_s01?ie=UTF8&psc=1

https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1098

2019-10-09 13:51:47.256 Error: (CDevice_update) deconz - SPZB0001: Failed to parse parameters: 'nValue', 'sValue', 'Image', 'SignalLevel', 'BatteryLevel', 'Options', 'TimedOut', 'Name', 'TypeName', 'Type', 'Subtype', 'Switchtype', 'Used', 'Description', 'Color' or 'SuppressTriggers' expected. 2019-10-09 13:51:47.256 Error: (deconz) 'CDevice_update' failed 'TypeError':'an integer is required (got type str)'.

Hi, I have a thermostat Domoticz does not want to take it? Can you include that?

THX

salopette commented 4 years ago

hmmm where should i replace it?

Smanar commented 4 years ago

line 1008 to 1011.

I m making a better version ATM, but this patch will help you, time for me correct this bug.

salopette commented 4 years ago

off- is without function Heat- = Boost Auto = normal as I have set it at the thermostat or in domoticz

sshot-2019-10-11- 1

Smanar commented 4 years ago

Yep heat is boost from deconz issue Auto = normal, it's the mode with heatpoint. But off do nothing ? It don't stop it ?

BTW, I have corrected your previous bug > https://github.com/Smanar/Domoticz-deCONZ/commit/80143af572f9278f39a295c33a2734de8dc9fae1#diff-66c71ea3faaa52c277917c951aa67921

Edit: Ha yep, I see the problem with off . I m on it.

salopette commented 4 years ago

I have just checked the functions on the thermostat. It can be at least 5 degrees and a maximum of 30 degrees. And only boost function (on is displayed).

Maybe like this:

off = 5 boost = 30 auto = adjustment

PS:

I will be back tomorrow!

Smanar commented 4 years ago

The problem is from domoticz, when you select "off" it make an "off" event, but for other it's a "set level" event, thought it was only 'setlevel".

New version > https://github.com/Smanar/Domoticz-deCONZ/commit/914d17b1fc5a655f087e38acf6bbc5590a1b801f#diff-66c71ea3faaa52c277917c951aa67921

Good night ^^.

I will make a better code for tomorrow.

But if you set it to 5°, it's not off, it will work if you have 4° in your home, I need to read the doc, but I realy think there is an off mode.

salopette commented 4 years ago

2019-10-12 05:47:51.244 Status: (deconz) ### Create Device 00:15:8d:00:01:92:38:83-01-0201_mode > SPZB0001 (Thermostat_Mode) as Unit 94 2019-10-12 05:47:51.329 Status: (deconz) Launching websocket on port 443 2019-10-12 05:47:51.245 Error: (deconz) 'onHeartbeat' failed 'NameError':'name 'v' is not defined'. 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 852 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function onHeartbeat 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 348 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function onHeartbeat 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 405 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function ManageInit 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 748 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function SendCommand 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 789 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function UpdateBuffer 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 537 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function NormalConnexion 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 616 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function ReadConfig 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 405 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function ManageInit 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 748 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function SendCommand 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 789 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function UpdateBuffer 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 546 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function NormalConnexion 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 405 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function ManageInit 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 748 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function SendCommand 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 789 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function UpdateBuffer 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 543 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function NormalConnexion 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 489 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function InitDomoticzDB 2019-10-12 05:47:51.245 Error: (deconz) ----> Line 984 in '/home/pi/domoticz/plugins/Domoticz-deCONZ/plugin.py', function UpdateDevice 2019-10-12 05:48:00.801 (deconz) ### Request sensors

salopette commented 4 years ago

Das Problem ist von domoticz, wenn Sie "off" wählen, wird ein "off" -Ereignis erzeugt, aber für andere ist es ein "set level" -Ereignis, obwohl es nur "setlevel" war.

Neue Version> 914d17b # diff-66c71ea3faaa52c277917c951aa67921

Gute nacht ^^.

Ich werde einen besseren Code für morgen machen.

Aber wenn Sie es auf 5 ° setzen, ist es nicht aus, es wird funktionieren, wenn Sie 4 ° in Ihrem Haus haben, ich muss das Dokument lesen, aber ich denke wirklich, dass es einen Aus-Modus gibt.

https://github.com/ebaauw/homebridge-hue/issues/426#issuecomment-461920956

Smanar commented 4 years ago

New version (again), this time, was a big error, sorry for you. Good link, I will check it later, I m just wake up ATM.

Smanar commented 4 years ago

So better result ?

salopette commented 4 years ago

Hi, is not working right yet.

at off it goes to 5 degrees, is also changed in Domoticz on the thermostat image.

With Heat it goes to 30 degrees (maybe rename HEAT in Boost 30 ° ??)

and at car is also set to 30 degrees, which does not remember when I z.b. previously set to 21.

salopette commented 4 years ago

Sorry is wrong with having watched! Seems to work, only it lasts until the status comes to domoticz.

Smanar commented 4 years ago

I m reading your link, and I have found some other information

I found that switching from Boost mode to Off or v.v., the original value for HeatSetPoint is lost. Not sure if that's easily worked around."

Oddly enough, it works as expected for auto->off->heat->auto.

It's a big problem because I m reading the heatsetpoint from the thermostat.

For boost mode it's not a problem, because it works for 15mn, and after return to auto mode itself ? So it will set the good value in domoticz itself.

And yep can rename heat at boost, right.

salopette commented 4 years ago

Is it possible to do this by choosing the heatsetpoint value from any thermostat? For example, from a Xiaomi sensor by ID entry?

Smanar commented 4 years ago

Yes and no. Lot of ways to do that. For exemple if the temperature of one sensor go under X°C increase the thermostat value. But I think it can be set during working mode, with usage, setting one more or one less °C on the heatpoint value.

In my (brief) experience, it's best to leave "mode": "auto" and change config.heatsetpoint for the target temperature (e.g. 2100 when at home and 1500 when not). Use state.on to show whether the thermostat is heating or not.

But You can't send a temperature sensor value to the thermostat, to have a better regulation (the thermostat use algorithm to calcule it) Was a good idea but not working yet.

I found that as well, but it doesn’t give me clue as to how to link the external temperature sensor. I tried setting this attribute and binding the TRV to a Temperature Measurement cluster of one of my Hue motion sensors, but no joy.

salopette commented 4 years ago

I have now installed last version, seems to run until now, I keep watching! Thanks for the work!

PS: Did you perhaps workaround with the virtual domoticz thermostat looked? There was something with different ID's there

sshot-2019-10-13- 1

Smanar commented 4 years ago

Yeah, I know this plugin (I think it's you that have showed it to me) Realy good one, it use an algorythm like the thermostat, but it will work only with on/off device. You can send on/off command to the zigbee thermostat and by-pass the integrated one (boost is a timed action) There is a "valve" field, but this field is read-only.

salopette commented 4 years ago

Hi, can you tell me how I can rename the thermostats? In the Phoscon app they are unfortunately not displayed, only in VCN Viewer.

The party can start !!

sshot-2019-10-16- 1

Smanar commented 4 years ago

Lol. You can change them in deconz with the gui if you have it, but as is battery powered device, you need perhaps to wake it up during process or wait for an update.

If it don't work I will explain you using curl command and the API.

salopette commented 4 years ago

is the Deconz Gui ???

sshot-2019-10-16- 1

Smanar commented 4 years ago

Yep, It's yours ? Select a node, in the node panel, you can edit the name, but I have tried for Xiaomi cube without succed.

You can too with the API https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/ Or with curl, something like

curl -H 'Content-Type: application/json' -X PUT -d '{"name":"Living Room 1"}' http://192.168.178.93/api/7B77BF4B99/sensors/48

Smanar commented 4 years ago

You have finally found ?

salopette commented 4 years ago

curl -H 'Content-Type: application/json' -X PUT -d '{"name":"Living Room 1"}' http://192.168.178.93/api/7B77BF4B99/sensors/48

Yes, I just tried. It changed my thermostat in Living Room 1!

Does the old one in Domoticz need to be deleted and re-added?

2019-10-17 18:54:52.316 Error: (deconz) Unknow MAJ{'id': '48', 'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 't': 'event', 'r': 'sensors', 'e': 'changed', 'name': 'Living Room 1'}

sshot-2019-10-17- 1

Smanar commented 4 years ago

Nope.

As domoticz use device name for script, the plugin NEVER change device name in domoticz itself (to don't broke your scripts) So you can have a different name in deconz and domoticz. And you can change the name in domoticz without impact on deconz. Domoticz use the uniqueid to reconize the device (its made with the MAC adress) not the name.

So if you don't like the actual name, just change it in domoticz. You can too delete it, at next startup it will be re-crated with the deconz name, but it can broke yours scripts, or you can loose all your domoticz log for this device.

salopette commented 4 years ago

Thank you so much!

salopette commented 4 years ago

I am a long way from lua and DzVents. have now made about Blokly small script:

When door or window is open, thermostat is turned off (5 °) and when back to auto (as previously set)

Seems to work!

Maybe someone needs it too?

sshot-2019-10-20- 4

I have not found any examples for the boost function for me?

Smanar commented 4 years ago

Domoticz check for state change or just state ? the test "Eingagns TUr = open" works only when you open the door, or during all time the door is open ?

You wana boost when temperature go under a values or at some time ?

salopette commented 4 years ago

Domoticz always looks when the door is open or closed. It is a Xiaomi door contact.

Temperature is held automatically (depends on the setpoint value?)

Smanar commented 4 years ago

So thx for script ^^.

And yep, your themostat use it's own algorytm with the ambiant temperature to active or not the valve.

For the boost value, idk what can be usefull, if you have a good regulation, you don't need boost feature. If you are away, active boost when you come back ?

salopette commented 4 years ago

I have not dealt with comming and laving home yet. I think it makes sense to realize such a thing to get more money! But one by one!

  It was important to me first that does not heat the heating when ventilating, because my wife and children like to keep the windows open for a long time -

If you still have good ideas / suggestions, I like to listen to you !!!

Smanar commented 4 years ago

Lol, I realy don't see big utility at boost feature. The only situation where I m using this kind of feature, it's after a long absence, because the heating/cooloing was off, so hard to automate it, because it's not regular.

salopette commented 4 years ago

That's right, I'll think over time how I do it best. If necessary, you can make a group where all the boosts are from all the thermostats and then turn on at short notice.

PS: I use Google translator: -), hope you understand me.

Smanar commented 4 years ago

Yep, and I have see you are using "google translate" , lol , it s something visible, but no problem for comprehension My english is bad too.

salopette commented 4 years ago

Hi, Last night I came across a problem with my circuit.

My door was about 10 minutes on and of course after the script, the thermostat has been switched to 5 °.

And this value was written in the automatic, so when I had the door, was not set 21.5 ° but 5 °.

And it was very fresh this morning- :-)

Do you know where the mistake could be?

Smanar commented 4 years ago

I don't think it's coming from your code. When you select "auto" the script send too the value stored in the thermostat. So domoticz set "auto mode" AND set a heatpoint There is something too in the deconz code that do same thing, but I don't think the problem come from their code.

Perhaps a bad return and domoticz have memorised a bad heatpoint.

I can purpose you 2 things:

salopette commented 4 years ago

Hi, so far I have not been able to reproduce the mistake. I keep watching! If you make changes in the beta, can you write it anywhere that was done exactly? Then I can always update and test. Always want to be up to date!

Smanar commented 4 years ago

ATM I m improving the shutter command. I will make the version official in 1 or 2 weeks, time to test.

salopette commented 4 years ago

A ok, Shutter I do not have in Zigbee, is there cheap ???   I use shelly 2.5 for that. I have many Tradfri and Osram lights, as well as thermostats! :-)

Smanar commented 4 years ago

Not realy cheap ^^ we are using this one https://www.amazon.fr/commande-sans-fil-roulant-connect%C3%A9/dp/B07HQRSBPH?source=ps-sl-shoppingads-lpcontext&psc=1

I think it will be easy to find cheaper. If you already have the material Shelly is a good solution I think too.

And yes, lol, I have see all your thermostats, tell me if you have problem, I can make a version with logs easier to read, will be sad if a so big installation can't work corrctly.

salopette commented 4 years ago

Hi, today was again heater failure.

But in Domoticz I do not see any mistakes. Can I somehow log the comonikaition between thermostat and deconz?

Smanar commented 4 years ago

Deconz log are realy "talkative" ^^. Tommorow, I can make you a special version, that log importants informations in "status log" on domoticz. And if you have too much logs to see then, it's possible too write the information on a file (but not realy good for SD card)

Smanar commented 4 years ago

Hello, try this file > https://github.com/Smanar/Domoticz-deCONZ/blob/debug/plugin.py With it you will have in status log

Now need to check if you have for exemple

But as I can't test it on my side, tell me if it works.

salopette commented 4 years ago

2019-10-30 20:26:44.124 Status: User: Admin initiated a switch command (4025/deconz - Wohnzimmer/Set Level) 2019-10-30 20:26:44.162 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'off', 'transitiontime': 0} 2019-10-30 20:26:44.243 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 95, 'mode': 'off', 'heatsetpoint': 2200, 'on': False, 'offset': 0}, 'id': '48'} 2019-10-30 20:26:44.191 Error: (deconz) Connexion problem (1) with Gateway : 400 2019-10-30 20:26:59.201 (deconz) onCommand called for Unit 109: Parameter 'Set Level', Level: 10, Hue: 2019-10-30 20:26:59.159 Status: User: Admin initiated a switch command (4025/deconz - Wohnzimmer/Set Level) 2019-10-30 20:26:59.202 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'heat'} 2019-10-30 20:26:59.283 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 95, 'mode': 'heat', 'heatsetpoint': 2200, 'on': False, 'offset': 0}, 'id': '48'} 2019-10-30 20:27:00.534 EventSystem: Event triggered: Bad-Licht-Nachtlicht_4 2019-10-30 20:27:00.555 (Virtual) Light/Switch (BAD-Links LED) 2019-10-30 20:27:00.570 (Virtual) Light/Switch (BAD-Untere LED) 2019-10-30 20:27:00.584 (Virtual) Light/Switch (BAD-Rechts LED) 2019-10-30 20:27:12.593 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 95, 'mode': 'heat', 'heatsetpoint': 3000, 'on': False, 'offset': 0}, 'id': '48'} 2019-10-30 20:27:12.652 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2078, 'on': True, 'valve': 255, 'lastupdated': '2019-10-30T19:27:12'}, 'id': '48'} 2019-10-30 20:27:20.061 (deconz) onCommand called for Unit 109: Parameter 'Set Level', Level: 20, Hue: 2019-10-30 20:27:20.013 Status: User: Admin initiated a switch command (4025/deconz - Wohnzimmer/Set Level) 2019-10-30 20:27:20.061 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'auto'} 2019-10-30 20:27:20.153 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 95, 'mode': 'auto', 'heatsetpoint': 3000, 'on': False, 'offset': 0}, 'id': '48'}

Smanar commented 4 years ago

Nice, so if you go in log, status panel, you will see only theses messages (and somes others from domoticz) with time. I think checking for 'heatsetpoint' is enought to see a problem, because:

So if you see at a moment heatsetpoint = 5 you will have more information about your bug (I hope)

salopette commented 4 years ago

Hi, somehow there is always an error as soon as the command OFF comes from Domoticz.

off:

2019-10-31 06:34:03.158 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/58/config with {'mode': 'off', 'transitiontime': 0} 2019-10-31 06:34:03.237 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:d0:34-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'battery': 100, 'mode': 'off', 'heatsetpoint': 2100, 'on': True, 'offset': 0}, 'id': '58'} 2019-10-31 06:34:03.186 Error: (deconz) Connexion problem (1) with Gateway : 400

Boost:

2019-10-31 06:34:36.856 (deconz) onCommand called for Unit 136: Parameter 'Set Level', Level: 10, Hue: 2019-10-31 06:34:36.842 Status: User: Admin initiated a switch command (4154/deconz - WC/Set Level) 2019-10-31 06:34:36.857 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/58/config with {'mode': 'heat'} 2019-10-31 06:34:36.928 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:d0:34-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'battery': 100, 'mode': 'heat', 'heatsetpoint': 2100, 'on': True, 'offset': 0}, 'id': '58'} 2019-10-31 06:34:39.438 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:d0:34-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'battery': 100, 'mode': 'heat', 'heatsetpoint': 3000, 'on': True, 'offset': 0}, 'id': '58'} 2019-10-31 06:34:39.489 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:d0:34-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2131, 'on': True, 'valve': 34, 'lastupdated': '2019-10-31T05:34:39'}, 'id': '58'}


Auto:

2019-10-31 06:35:10.941 (deconz) onCommand called for Unit 136: Parameter 'Set Level', Level: 20, Hue: 2019-10-31 06:35:10.923 Status: User: Admin initiated a switch command (4154/deconz - WC/Set Level) 2019-10-31 06:35:10.941 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/58/config with {'mode': 'auto'} 2019-10-31 06:35:10.973 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:d0:34-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'battery': 100, 'mode': 'auto', 'heatsetpoint': 3000, 'on': True, 'offset': 0}, 'id': '58'} 2019-10-31 06:35:17.979 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:b8-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2131, 'on': True, 'valve': 30, 'lastupdated': '2019-10-31T05:35:17'}, 'id': '66'}

Smanar commented 4 years ago

Ok so first, for your bug (error 400 = bad request) was my fault, I m trying something for a special switch, here you have a rollback > https://github.com/Smanar/Domoticz-deCONZ/blob/debug/plugin.py

BTW, I m seing a problem, every time you change a mode with boost or off, you have a return heatsetpoint = 3000 or heatsetpoint = 500, and this value is memorised in domoticz as new value. So I have make that > https://github.com/Smanar/Domoticz-deCONZ/commit/d2e064132546d3ccdebeb0b342eb1b4b6d0a71f1#diff-bdcab2f88505f588ed66a949d4e6dc92

It's a little "hacky" bu I think no-one can set 5°C or 30°C on a thermostat !

So with this hack even if you change the mode, domoticz never forget your heatpoint value.

So, you can continue to check for you bug, but with this hack, if the bug is from the thermostat, like domoticz memorise the godd value, it's possible for me making a code to force a heatpoint in same time than the "auto" mode.

salopette commented 4 years ago

Thanks, have it installed now and will watch it!

salopette commented 4 years ago

I think that works even worse.

Now I have the door open and later closed, then the setting went as desired to 22 °, but a short time later, the thermostat is off, even though the door was closed?

Do you still have ideas?

2019-11-01 11:55:40.158 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 44, 'lastupdated': '2019-11-01T10:55:40'}, 'id': '48'} 2019-11-01 12:04:47.029 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 44, 'lastupdated': '2019-11-01T11:04:46'}, 'id': '48'} 2019-11-01 12:11:11.688 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 61, 'lastupdated': '2019-11-01T11:11:11'}, 'id': '48'} 2019-11-01 12:13:11.885 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 49, 'lastupdated': '2019-11-01T11:13:11'}, 'id': '48'} 2019-11-01 12:15:42.076 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 49, 'lastupdated': '2019-11-01T11:15:42'}, 'id': '48'} 2019-11-01 12:24:48.934 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 49, 'lastupdated': '2019-11-01T11:24:48'}, 'id': '48'} 2019-11-01 12:33:13.654 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 49, 'lastupdated': '2019-11-01T11:33:13'}, 'id': '48'} 2019-11-01 12:35:19.818 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 66, 'lastupdated': '2019-11-01T11:35:19'}, 'id': '48'} 2019-11-01 12:35:43.876 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 66, 'lastupdated': '2019-11-01T11:35:43'}, 'id': '48'} 2019-11-01 12:37:19.997 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 50, 'lastupdated': '2019-11-01T11:37:19'}, 'id': '48'} 2019-11-01 12:44:50.654 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 50, 'lastupdated': '2019-11-01T11:44:50'}, 'id': '48'} 2019-11-01 12:49:55.428 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'off'} 2019-11-01 12:49:55.510 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 90, 'mode': 'off', 'heatsetpoint': 2200, 'on': False, 'offset': 0}, 'id': '48'} 2019-11-01 12:49:57.943 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 90, 'mode': 'off', 'heatsetpoint': 500, 'on': False, 'offset': 0}, 'id': '48'} 2019-11-01 12:49:57.946 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2113, 'on': True, 'valve': 50, 'lastupdated': '2019-11-01T11:49:57'}, 'id': '48'} 2019-11-01 12:49:57.949 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2140, 'on': True, 'valve': 50, 'lastupdated': '2019-11-01T11:49:57'}, 'id': '48'} 2019-11-01 12:50:03.974 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2140, 'on': False, 'valve': 0, 'lastupdated': '2019-11-01T11:50:03'}, 'id': '48'} 2019-11-01 12:50:53.110 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'auto'} 2019-11-01 12:50:53.183 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 90, 'mode': 'auto', 'heatsetpoint': 500, 'on': False, 'offset': 0}, 'id': '48'} 2019-11-01 12:52:05.166 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'state': {'temperature': 2052, 'on': False, 'valve': 0, 'lastupdated': '2019-11-01T11:52:05'}, 'id': '48'}

Smanar commented 4 years ago

2019-11-01 12:49:55.428 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'off'}

These one is domoticz that ask for off state.

2019-11-01 12:49:57.943 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 90, 'mode': 'off', 'heatsetpoint': 500, 'on': False, 'offset': 0}, 'id': '48'}

Then your thermostat set his own own heatpoint to 500

2019-11-01 12:50:53.110 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'auto'} 2019-11-01 12:50:53.183 Status: (deconz) Thermostat debug : {'uniqueid': '00:15:8d:00:01:92:38:83-01-0201', 'r': 'sensors', 't': 'event', 'e': 'changed', 'config': {'reachable': True, 'locked': False, 'battery': 90, 'mode': 'auto', 'heatsetpoint': 500, 'on': False, 'offset': 0}, 'id': '48'}

After that domoticz change the mode to auto BUT your thermostat don't retreive his old setpoint and continu with a heatpoint = 500.

It don't return back to 2200 after some time ? like for boost ?

Smanar commented 4 years ago

Ok, so I have make a post on deconz issue about this device to ask if its something normal.

And like now domoticz memorise the heatpoint value too https://github.com/Smanar/Domoticz-deCONZ/commit/02f4b59f5aac5e63760caa381ab4208430e5a580#diff-66c71ea3faaa52c277917c951aa67921

Now when you use your switch "mode" and set it to auto you will have something like this

2019-11-01 12:50:53.110 Status: (deconz) Thermostat debug : /api/30B09157F5/sensors/48/config with {'mode': 'auto','heatpoint':2100}

So if I m right, your thermostat can forget the value, domoticz never (except if you restart domoticz during a bad state of thermostat.