State key setpointHeat not defined

So I started to monitor all errors in my Indigo Server console by using the SQL Logger. Probably a rabbit hole I shouldn't have gone but it's a bit too late for that...

Today I caught this weird error:

Code: Select all

   Z-Wave                          received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
   Error                           device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Error                           device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)


Now this "Boiler Relay Hot Water" device is a 1 Channel Boiler Actuator (SSR303 / ASR-ZW) which explains why it doesn't have a setpointHeat state. This device works in tandem with the Radiator Thermostat (HRT4-ZW) which is the one that has the setpointHeat state. It's not quite clear to me why the relay device would report a heat setpoint temperature. Could this be an ID confusion?

Thanks,
Christian

[matt (support)]

That is really strange. The first ("received") line definitely means Indigo received that temperature/setpoint from that device. I'm not sure how the HRT4-ZW could possibly spoof the relay's (SSR303) address like that. Is this a one-off occurrence or does it happen frequently?

Hi Matt, I searched all my Indigo logs since 2019 and I have had this error 8 times but the frecuency seems to have increased now to about once a month:

Code: Select all

  Z:\Library\Application Support\Perceptive Automation\Indigo 7.4\Logs\2020-04-03 Events.txt (2 hits)
   Line 1335: 2020-04-03 05:18:46.324   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 1336: 2020-04-03 05:18:46.324   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 7.4\Logs\2020-08-08 Events.txt (2 hits)
   Line 6320: 2020-08-08 12:44:50.088   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 6321: 2020-08-08 12:44:50.088   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2021.1\Logs\2021-06-30 Events.txt (2 hits)
   Line 12649: 2021-06-30 15:46:11.600   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 12650: 2021-06-30 15:46:11.600   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2021.2\Logs\2022-02-18 Events.txt (2 hits)
   Line 7191: 2022-02-18 12:47:50.424   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 7192: 2022-02-18 12:47:50.424   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2021.2\Logs\2022-03-15 Events.txt (2 hits)
   Line 2526: 2022-03-15 05:38:40.504   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 2527: 2022-03-15 05:38:40.504   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2021.2\Logs\2022-04-25 Events.txt (2 hits)
   Line 1867: 2022-04-25 06:10:05.438   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 1868: 2022-04-25 06:10:05.439   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2022.1\Logs\2022-05-30 Events.txt (2 hits)
   Line 19905: 2022-05-30 20:29:03.006   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 19906: 2022-05-30 20:29:03.006   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
  Z:\Library\Application Support\Perceptive Automation\Indigo 2022.1\Logs\2022-06-16 Events.txt (2 hits)
   Line 17485: 2022-06-16 18:48:53.958   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
   Line 17486: 2022-06-16 18:48:53.958   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)


Is it possible that maybe the relay is trying to forward the setpointHeat on behalf of the thermostat? Now here is another weird thing I can't understand. On the 8 times I had this error it is always preceded and succeeded by a Radiator Thermostat sending it's battery status update and it's heat setpoint, here is a sample:

Code: Select all

2022-06-16 18:48:53.940   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-06-16 18:48:53.957   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
2022-06-16 18:48:53.958   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
2022-06-16 18:48:53.958   Error   device "Boiler Relay Hot Water" state key setpointHeat not defined (ignoring update request)
2022-06-16 18:48:54.050   Z-Wave   received "Radiator Thermostat Living Room" heat setpoint is 21.00 °C


Furthermore the timestamps of the two events are extremely close in all cases, within some miliseconds:

Code: Select all

2020-04-03 05:18:46.323   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2020-04-03 05:18:46.323   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
2020-08-08 12:44:50.085   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2020-08-08 12:44:50.086   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
2021-06-30 15:46:11.363   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 44%
2021-06-30 15:46:11.599   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 21.00 °C
2022-02-18 12:47:50.288   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-02-18 12:47:50.424   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
2022-03-15 05:38:40.462   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-03-15 05:38:40.504   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 31.24 °C
2022-04-25 06:10:05.228   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-04-25 06:10:05.438   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C
2022-05-30 20:29:02.988   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-05-30 20:29:03.005   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 31.24 °C
2022-06-16 18:48:53.940   Z-Wave   received "024 - Radiator Thermostat Living Room" status update battery level 5%
2022-06-16 18:48:53.957   Z-Wave   received "Boiler Relay Hot Water" heat setpoint is 20.96 °C


How is this even possible? It can't be a coincidence that these 8 errors are preceded by another device sending an update within a few miliseconds every time. This Radiator Thermostat Living Room device has nothing to do with the Secure HRT4-ZW Wireless Room Thermostat and is in fact from a different manufacturer (Danfoss Living Connect Radiator Thermostat LC-13). It's also worth noting that on most cases the heat setpoint is 20.96 which doesn't seem to be a random value and it's not even a valid temperature setting on the thermostat which goes by whole degrees (ie no decimals).

A couple of more tidbits:

- The Radiator Thermostat Living Room sends battery updates roughly every 5 mins so it doesn't seem to generate an error every time
- This particular device type seems to preffix the device ID on the battery status update. I don't think any other of my Z-wave devices does that, so I am guessing there is some inconsistency on the device code that handles the status update message.

[matt (support)]

Unfortunately, I am puzzled by this. Indigo is just reporting the incoming commands it is receiving. I don't know if the Z-Stick is scrambling some messages and delivering packets to Indigo with the incorrect node ID, or if the problem is coming from the modules themselves. Regardless, I'm 99% confident the problem isn't Indigo – it is just reporting what it is receiving (garbage in, garbage out).

This particular device type seems to preffix the device ID on the battery status update. I don't think any other of my Z-wave devices does that, so I am guessing there is some inconsistency on the device code that handles the status update message.

That is just a flag Indigo is using (to add the node ID as a prefix) for that particular log message. I've updated it now to be consistent with most other messages (and not show the node ID). That isn't related to the root problem at all though.