Starting after 2022.02 I have had some issues with my ZWave network - the controller looks as though its working. I use Zwavejs2mqtt for management and upon looking at a high frequency reporting device such as an energy meter it shows static (last value) for some time. It took me a while but this appears to be happening just after a full snapshot that I have scheduled to run at 2 AM every other day.
I thought the add-on that ran the backups was the issue, but when I did a manual Full Snapshot it occurred again.
In terms of correction - sometimes I can simply restart zwavejs2mqtt add-on and other times it locks up and requires a pull-plug restart.
I am running Hassio inside of a docker - I know USB can be “finicky” sometimes. I am not sure why the supervisor is trying to disconnect/reconnect USB while doing a snapshot but the zwavejs2mqtt does not appear to like it…
Can you see if disabling the Soft Reset function within the Z-WaveJS2MQTT helps? It can be found within the Z-WaveJS2MQTT webinterface under Settings > Z-Wave > Soft Reset.
Rick, Thanks! I did in fact see this solution in another post and disabled it but it occurred afterwards. This seems to be directly connected somehow to whatever Hassio does during the backup process. Its hard to reproduce but I am a bit surprised I am not seeing more of this as I think the key factors are: 1) Hassio inside of docker, 2) Zwavejs 2 MQTT (Not sure if this happens with vanilla ZWJS) and 3) Full/Partial backups. The latter being the triggering element - and perhaps there are not many out there that maintain backups as I do (?)
I do know docker containers do not take kindly to USB removals while in use (due to the soft reset topic you brought up) I am just concerned there is an element triggering that feature. I am going to disable automated backups for a bit and see.
You may have seen this warning when doing a soft reset:
USB modules will reconnect, meaning that they might get a new address. Make sure to configure your device address in a way that prevents it from changing, e.g. by using /dev/serial/by-id/... on Linux.
This method may cause problems in Docker containers with certain Z-Wave stick. If that happens, you may need to restart your host OS and docker container.
How can the suggest path to the USB be determined?
I’ve actually never performed a soft reset on a z-wave controller - I usually just rebooted to be honest…so I am not familiar with that message - its a bit confusing (is “this method” the device naming or soft reset…?)
You should be able to find the ACM0 (or similar) linkage by using this command in terminal:
ls -al /dev/serial/by-id
I will give this a try, but I’m not too hopeful this problem only started recently and these are from 2019/2020 - I would have thought this was deprecated by this point and able to use the tty device name. Or maybe this just helps the zwave subsystem “survive” the momentary disruption.