I have a simple rule that uses a sensor to control the closet light. It works fine all day, but not at night. What I have discovered is that the comm for the switch is routed through a device in the den (device 06). When I look at that device, at “miraculously,” about the same time of day, it has a set of errors. Every day.
The thing that causes DenLamp to turn off is a basic rule that turns off a number of devices when a switch is pressed. It seems to work correctly except for this, and the other devices being turned off don’t have the same errors.
What errors? There are none in your screenshot. There is some debug logging, which shows more raw Z-Wave (in this case) data before the driver parses them into standard events on your hub, like the level and switch events your "info" logs hint at (which are also not errors but, well, information). You can turn off either or both of these if you want. It's common to have at least debug logging disabled unless you are troubleshooting driver behavior. Both are normal and show no problems.
How did you determine this? There is also nothing in your logs to show this. As a guess for what you might have misinterepreted: "device: 06" is the Z-Wave node ID for this device itself. (You can verify this in Settings > Z-Wave Details or look at its Device Network ID on its device detail page. The Settings > Z-Wave Details page might show the actual last route if you are interested, too.)
That being said, it sounds like you have actual problems, so I'd start by gathering some information that may be useful. This support doc offers some general tips, like enabling logging for whatever app/automation you're using to automate this in the first place:
Since your device is Z-Wave, this specific advice may also be handy (if you've ruled out the app and narrowed it down to the device, per the above, or just want to check): How to Troubleshoot Z-Wave | Hubitat Documentation
But to answer your question about the path, I just looked at the path in Zwave stats under settings. Perhaps my explanation was confusing, but the problem device is routed through device 06 And then I noticed what looked to me to be potentially an issue. I thought that because I did not see those lines on other devices that were involved in the same event.
And I just discovered that by unplugging device 06, everything works fine. And the problem switch is now routed directly to the hub.
