I’ve been diving into the world of Z-Wave integration with Home Assistant, and I wanted to share my experiences and some troubleshooting tips that might help others facing similar challenges.
Recently, I decided to give Z-Wave a try, and I must say, the setup process has been both exciting and a bit frustrating. I’m running Home Assistant 94.3 via Docker on my Synology NAS, and I decided to go with the Aeotec Z-Stick Gen5. The stick itself seems to be working fine, and the NAS recognized it without any issues. I updated my Docker setup and added the necessary path /dev/ttyACM0 to Home Assistant through the UI. So far, so good!
However, things got tricky when I tried to pair my Aeotec Dome DMMS1 Motion/Light sensor. I followed the instructions to click “Add Node Secure” in Home Assistant, but I didn’t get any confirmation that the process had started. The Z-Stick kept its disco lights on, which I assume is normal, but I wasn’t getting the visual notifications in the lower left corner of the Home Assistant UI that I saw in some YouTube tutorials. This lack of feedback was a bit confusing.
After some digging, I noticed a few log entries that suggested the Z-Stick was attempting to add the device:
plaintext
2019-06-26 20:36:17.336 Detail, Queuing (Controller) Add Device
2019-06-26 20:36:17.336 Info, Add Device
I pressed the three-button combo on the sensor as instructed, but instead of the expected five blinks, the sensor only blinked with each button press. This was frustrating, as it seemed like the sensor wasn’t entering pairing mode properly. I tried resetting the sensor by holding the button until the lights blinked, and then I attempted the pairing process again. This time, the sensor successfully paired and appeared as Node 3 in my network. But here’s the kicker: almost 24 hours later, the state still says “initializing.” The entities are there, but only one of them has changed its value from the initial state. The binary sensor motion detector was “On” for the first 19 hours but inexplicably changed to “Off” about 4 hours ago. We’ve walked by the sensor multiple times, and it does blink with motion, but the state in Home Assistant doesn’t seem to update consistently.
I’ve been checking the logs, and they show some activity, but almost all the messages indicate that the value hasn’t changed. Here’s a snippet of what I’m seeing:
plaintext
2019-06-27 13:47:09.310 Info, Node003, Received SensorBinary report: Sensor:12 State=On
2019-06-27 13:47:09.310 Detail, Node003, Refreshed Value: old value=true, new value=true, type=bool
2019-06-27 13:47:09.310 Detail, Node003, Changes to this value are not verified
2019-06-27 13:47:09.310 Detail, Node003, Notification: ValueChanged
It’s puzzling because the sensor is only about 4 feet away from the Z-Stick and NAS, so distance shouldn’t be an issue. I’m wondering if there’s something I’ve done wrong in the setup or if I’ve hit a bug in the Z-Wave integration. Could it be a faulty sensor or stick? Or maybe a configuration issue on my end?
If anyone has experienced similar issues or has some troubleshooting tips, I’d love to hear from you! I’m really excited about the potential of Z-Wave, but this hiccup has been a bit of a roadblock. Let’s keep the conversation going and help each other navigate this awesome (but sometimes tricky) technology!
Cheers,
[Your Name]