forum

Hi guys,

I'm operating a z-wave network since 2-3 years.
Since a year or so I started having the following problems:

short version:
I can not reliable set a thermostat-temperatur from the UI, it jumps back to the old value or to other values.
I can set the temperature at the thermostat itself and it gets reflected correctly to the UI.

Long version:

Hardware: Raspberry 3B and raspberry board.
Software: OS Raspbian 10 Buster, Firmware v3.2.3, UI 1.13.5


I can set a thermostat temperature in the ui. But after a while 10-30min, sometimes even at once - it would get reset to the value it was - just before.
For example when I'm traveling, I set everything down to 16C. A day before I get back I set it to 20C. When checking after 10-30min, I get 16C again.
Sometimes I have to try for 10x times until the thermostat finally changes it temperature to something.
Sometimes I have to go to extremes, to set it to MAX (40C in UI), for it to jump 'back' to something like 23C.

This happens on all or most of the 6 thermostats (4 are Devolo, 2 are Danfoss).

What I've tried:
-always fresh batteries in the thermostats, with 66% or more reported in UI
-excluding and re-including devices
-all device interviews are complete
-no errors are reported in expert UI
-deleted contents of /var/log/ (it was full, I was using log2ram-package to reduce SD-card--wear-down)
-unplugged an usb-audio device, that was connected to the PI and was sometimes causing "undervoltage" reports in 'dmesg'
-connected the PI to a better USB-powersupply with more amps.
-logged off all other sessions of my user, that I had on other devices (second PC, mobile phone)

My idea is, that something with the UI is wrong or maybe got corrupted with sudden power-losses of the PI during construction works in my apartment.

I'm thinking about starting all over again and set up a fresh SD-Card with Raspbian 11, install a fresh z-wave.me etc.
I'm planning on also not using the backups and instead include the devices freshly.
Should I exclude them first from within the old system?
Is there a way to preserve/backup some kind of network-ID or Home-ID, so I maybe have less work re-including the thermostats (asking this because I have one switch-device inside a wall, which is difficult to access in case that I need to reset it or so)

Any ideas are apreciated.
Thanks in advance.


NotARobot

Check the log and locate the packet being delivered to the thermostat. Maybe there is some error around it?

Thank you, for the answer.

Ok, here is what I've done:
I used a curl commandline to set a thermostat to 15C

Now /var/log/z-way-server.log said:
Question: is this

removing duplicates

normal?

I have the same issue.
I have Danfoss radiator valves, on 20 minute Battery saving cycles.
1st attempt disappears, 2nd attempt normally works. That's using z-way UI.

Also, why don't thermostats work on Alexa anymore, they worked before 4.0.

I have observed the same issue. If I change the thermostat value in the interface i need to make sure that the value is indeed set. Sometimes it takes a few tries.

micky1500 wrote: ↑

11 Dec 2022 22:42

I have the same issue.
I have Danfoss radiator valves, on 20 minute Battery saving cycles.
1st attempt disappears, 2nd attempt normally works. That's using z-way UI.

My cycles seem to be around 1800s (30min) for each device.
Do you think I should set them lower?
Also one should be able to wake them up, by pressing the middle button.

Actually the trouble seems to have started the day, when I added 2 Danfoss to the existing 4 Devolo.
Then suddenly also the Devolos started not waking up, when I was pushing their buttons.
Also I cannot completely interview them (Version is alway missing) without excluding and re-including.

I've now completely reinstalled z-way onto a new SD-Card and booted up.
The UI knew about the existence of the devices (so this info must be stored in the razberry-hardware or the hardware still knows it's home-id), but I had to re-interview all of them.

Things have become quite impredictable and not reproducible.

@notarobot
If you are happy waiting up to 30 minutes, don't change it.
If you want a quicker response change it lower, but it will shorten the battery life.
Pressing the button does work for immediate update. Not my plan for Home Automation to go around pressing buttons.

Even though I have had cold rooms after I thought I had set the thermostat previous to this issue appeared.
3 days of checking and it has not failed to set the correct temperature on many thermostats.
It fails to report correctly, making it look like the setting failed to register, after a while it corrects itself.

The device log shows the wrong value (28) 2 minutes after I had set it to 9

07:51 Radiator Bedroom1 : 9 °C Bedroom1
07:49 Radiator Bedroom1 : 28 °C Bedroom1
07:47 Radiator Bedroom1 : 9 °C Bedroom1
13.12. - 19:39 Radiator Bedroom1 : 28 °C Bedroom1

I'm more annoyed as to why thermostats aren't on Alexa anymore !
About to try setting up some SCENES as a workaround on Alexa