I’m trying to use HASS as a secondary z-wave controller to my Qolsys IQ panel so that I can control the only z-wave device in my house, the door lock. I’m using a Zooz ZST10. I moved my Pi right next to my z-wave lock while I test things, to ensure range isn’t the issue.
I can’t seem to get it to work, it doesn’t even reflect the status of the lock, just showing as locked. I have tried using all the variations of network security keys as shown in Z-Wave PC Controller (there’s Network Key S0, Unauthenticated, Authenticated, Access, LR Authenticated, LR Access and Last Used Temp shown when I press the shield icon in the PC software), I even paired the stick to the panel and unticked all the security options except for Access as none of my previous attempts to use these keys in HASS worked.
When I test the lock in Z-Wave PC Controller, I can successfully lock and unlock, but every time I try it in HASS I get a timeout in the logs. I’ve tried this with ZWaveJS, ZWaveJS2MQTT, Open Z-Wave and even the deprecated Z-Wave integration. They all show timeout errors.
My process is this:
- Pair to Qolsys panel via Z-Wave PC Controller
- Test (success)
- Plug stick into Raspberry Pi running HASS OS
- Enter network security key into whichever z-wave integration/addon I’m trying and interview nodes, lock entity is visible
- Test ← this is where things fail
I am fairly new to using Home Assistant, so maybe I’m doing something incorrectly? Maybe there’s another place I should be looking for the network security key? Clearly my Zooz stick works as a secondary hub, as Z-Wave PC Controller can operate my lock securely. In my current test, using ZWave2MQTT, under the secure column in the web ui, it says “no” which I’m assuming is an indication that I’m doing this wrong.