We have moved at community.getvera.com

Author Topic: Thermostat update fails  (Read 428 times)

Offline mullermn

  • Newbie
  • *
  • Posts: 8
  • Karma: +0/-0
Thermostat update fails
« on: January 10, 2018, 02:48:55 pm »

I have some PLEG logic controlling a 'Secure' thermostat. It seems that sometimes the messages get lost on route. I know they are sent, because the logic also sends push messages to my phone at the same time, and these arrive.

Most of the time, if a message goes missing it is the 6am 'turn on' setting, though it has been known to miss the 9pm 'turn off' periodically too.

Vera and the thermostat are in the same room, so there's no risk that the message is not able to get through. My best guess is that vera is trying to send its initial message as well as any retries all within one of the gaps between the thermostat's wakeups (300 seconds). Is this plausible? I don't really know much of how Vera/Z-wave works so it's just guesswork on my part.

Anyway, does anyone have any idea what might be causing this, and what I could do to try and stop it happening, please? Can I increase the number of retries / retry period, for example?

Many thanks for any help

Offline kwieto

  • Hero Member
  • *****
  • Posts: 624
  • Karma: +27/-15
Re: Thermostat update fails
« Reply #1 on: January 11, 2018, 03:53:14 am »
In general, if request is sent to the battery operating device in time between wakeup, system waits till next wakeup to pass the request.
If you look at the device in the system, you'll see message "waiting till wakeup to send commands" message at the bottom (see attached screenshot).

So it shouldn't be any problem if reqest is sent in between wakeups.
There may be various reasons why device is not responding to requests, i.e.  the device may be malfunctioning or Vera reloads luup engine between sending command and device's wakeup (then the reqest may be lost).