node-zwave-js: [question] Is it expected that device status does not persist between reboots?

I’m using zwavejs2mqtt through Docker. I have a problem that, when I bring the image down and back up, several devices, inconsistently, have to be manually refreshed. Before reboot, all devices have a date in the Last Active column and report appropriate capabilities.

After reboot, some devices, which includes mains connected devices, report Never as the Last Active time and lose their capabilities. For a particular device, before reboot and after a manual RefreshValues, the capabilities are:

Values
Multilevel Switch >
Central Scene >
Manufacturer Specific >
Version >

After reboot, the entire Values section disappears until manually refreshed, meaning that the device stops working entirely. This has resulted in me calling RefreshValues on most nodes after reboot in order to get back to a stable system.

I’m considering writing an integration that detects missing values and automatically calls RefreshValues, but I’m wondering if there’s a way to avoid needing this.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (10 by maintainers)

Most upvoted comments

Followed the troubleshooting guide to turn log levels up to “Silly” and write log files. I verified that the files were being emitted, shut down, captured the logs, captured the cache, and started back up. After starting back up, I verified that multiple nodes were in the Unknown state and refreshed one. I then captured the startup logs. All files attached: