I’ve looked around, but I’m not sure how to scrape the Z2M log for the WiserHeatUserRejoin
string. It’s possible to scrape the system log but logs for add-on seems more difficult.
But let’s just take a step back here: what are we trying to do / prove?
Demonstrate a link between WiserHeatUserRejoin
and resetting to 20°C
I think we’ve done that. Here are the logs from the past eight days. Remember that the TRV had the ‘hack’ in place between the first and second entries (five days) and was working normally. As soon as it was reset, the messages appeared again and the setpoint kept changing back to 20°C:
[core-ssh ~]$ cd config/zigbee2mqtt/log/
[core-ssh log]$ grep "WiserHeatUser" * -r -h
debug 2022-12-01 16:56:50: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,23162940,4240"}' from endpoint 1 with groupID null
debug 2022-12-06 10:32:55: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserJoin,30936,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 13:01:38: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserJoin,39517,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 13:02:58: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserJoin,25110,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 15:14:21: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3874,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 17:25:44: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3872,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 19:37:03: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3875,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 21:48:22: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3870,9063"}' from endpoint 1 with groupID null
debug 2022-12-06 23:59:43: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3876,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 02:11:05: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3878,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 04:22:28: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3878,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 06:33:48: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3872,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 08:45:07: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3876,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 10:56:30: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3877,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 13:07:51: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3873,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 15:19:13: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3876,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 19:41:53: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3876,9063"}' from endpoint 1 with groupID null
debug 2022-12-07 21:53:13: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3872,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 02:15:55: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3877,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 04:27:18: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3878,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 06:38:37: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3872,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 08:49:58: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3876,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 11:01:20: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3877,9063"}' from endpoint 1 with groupID null
debug 2022-12-08 13:12:43: Received Zigbee message from '0x50325ffffxxxxxxx', type 'attributeReport', cluster 'wiserDeviceInfo', data '{"deviceInfo":"NWK,WiserHeatUserRejoin,3873,9063"}' from endpoint 1 with groupID null
I haven’t always changed the temperature from 20°C every time, but when I have it has always changed back around the time that WiserHeatUserRejoin
is logged.
(Incidentally, I’ve also noticed that the TRV motor has been running around that time - even when the setpoint was still 20° and no change was necessary)
We want to find a workaround
So far we have two:
-
@madbobmcjim’s workaround, which maintains the desired setpoint by repeatedly setting it
- The hack I put together with your help, @GSzabados, which seems reliable but doesn’t explain the behaviour
It will help with further research into the underlying cause
In which case I’m happy to keep going, although I’m not sure how to proceed from here