From 2dc615acd5bfbf732490713a9c74f1671632de7a Mon Sep 17 00:00:00 2001 From: Tyler Szabo Date: Mon, 6 Apr 2020 09:33:13 -0700 Subject: [PATCH] Add Z-Wave troubleshooting for udev device file naming (#12725) --- source/_docs/z-wave/installation.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/z-wave/installation.markdown b/source/_docs/z-wave/installation.markdown index bfd703af5ea..e3effd00110 100644 --- a/source/_docs/z-wave/installation.markdown +++ b/source/_docs/z-wave/installation.markdown @@ -287,3 +287,7 @@ WARNING: Checksum incorrect - sending NAK ``` If you see any of these messages repeated in the log then _probably_ you've got something else running that's also using the Z-Wave controller. That might mean you've also got the OpenZ-Wave control panel (ozwcp) running, a second instance of Home Assistant or something else. You need to stop that other process to resolve this. + +### Changing device paths + +Configurations using `udev` can experience race conditions in creating device paths such that they change on reboot. This can cause a device to appear to change between `/dev/ttyACM0` and `/dev/ttyACM1` after reboot. In this case using the symlinks created for device IDs can ensure the correct device is used, for example: `/dev/serial/by-id/usb-0658_0200-if00` for Aeotec Z-Stick.