I have been using Smartthings for years and just got a Raspberry Pi 4 and have setup Home Assistant 2023.6.3 (Operating System 10.3) nicely and seems to be running. I’ve added some integrations like Ring and Nest and am ready to start moving my Z-wave devices over from Smartthings to Home Assistant.
I got a Aeotec Z-Stick 7 Plus Z-wave stick and before I got going, I updated the firmware to 7.19.2 using PC Controller 5. All went well and it seems to be running.
I was able to add the Z-wave JS add-on and then the Z-wave integration with the stick just fine, but for the life of me can’t add any of my Z-wave devices that were working fine on Smartthings.
I successfully excluded the devices on Smartthings (and smartthings confirmed they were removed), but when I try adding a new device on Home Assistant after entering pairing mode on HA I just got get stuck with " Searching for devices…" until it times out.
I’ve restarted HA several times, unplugged and plugged in the z-wave dongle, tried re-excluding the devices on BOTH smartthings and HA (even though they were never added to HA), removed and reinstalled the z-wave add-on and integration but never once do I see HA recognize a new device. The devices are all inches aware from the hub. I’ve tried these devices and none show up:
GE GE Z-Wave Wireless Smart Lighting Control Lamp Module, Dimmer, Plug-In, White, Works with Amazon Alexa, 12718 (aka Jasco ZW3103)
NEO Z-Wave Plus Smart Mini Power Plug Z Wave Outlet with Smart Energy Monitor Home Automation
Make sure it’s not plugged into a USB3 port, (not the blue ports) and use at LEAST a half meter usb extension. Preferably a powered USB2 hub.
Then, find the USB bus on a Pi isn’t the quiet place as far as RF interference is concerned. And while you’d expect it to interfere with Zigbee it also plays a number on most ZWave coordinators too.
I have also found it’s helpful to watch the ZWaveJS_UI debug log while trying an exclude / include to see what’s going on. The JsUI network map is also surprisingly helpful now.
refrain from screenshots - those things end up tiny on phone screens -
HOWEVER the relevant section says: zwave driver not init - not configured. How did you setup Zwave in the first place? Are you using builtin ZwaveJS or are you using the ZwaveJS_UI addon?
settings > devices and services > add integration >z-wave >z-wave> Select connection method / Do you want to use the Z-Wave JS Supervisor add-on? select “Use the Z-Wave JS Supervisor add-on” > submit > Success! / Created configuration for Z-Wave JS. / We found the following devices: 700 Series-based Controller ZST10-700 (Silicon Labs) > finish
2023-06-28T04:21:45.700Z CNTRLR Performing soft reset…
2023-06-28T04:21:45.949Z DRIVER no handlers registered!
2023-06-28T04:21:46.723Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-06-28T04:21:47.056Z DRIVER no handlers registered!
2023-06-28T04:21:47.836Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-06-28T04:21:49.166Z DRIVER no handlers registered!
2023-06-28T04:21:49.959Z CNTRLR Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-06-28T04:21:49.961Z CNTRLR Waiting for the controller to reconnect…
2023-06-28T04:21:51.465Z CNTRLR Waiting for the Serial API to start…
2023-06-28T04:21:56.466Z CNTRLR Did not receive notification that Serial API has started, checking if it respo
nds…
2023-06-28T04:21:56.514Z CNTRLR Serial API responded
2023-06-28T04:21:56.561Z CNTRLR querying version info…
2023-06-28T04:21:56.611Z CNTRLR received version info:
controller type: Bridge Controller
library version: Z-Wave 7.19
2023-06-28T04:21:56.612Z CNTRLR querying protocol version info…
2023-06-28T04:21:56.648Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 7.19.2
appl. framework build no.: 190
git commit hash: 30303030303030303030303030303030
2023-06-28T04:21:56.651Z CNTRLR supported Z-Wave features:
· SmartStart
2023-06-28T04:21:56.651Z CNTRLR querying controller capabilities…
2023-06-28T04:21:56.695Z CNTRLR received controller capabilities:
controller role: primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2023-06-28T04:21:56.696Z CNTRLR querying serial API setup capabilities…
2023-06-28T04:21:56.725Z CNTRLR supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetLRMaximumTxPower
· SetPowerlevel
· GetLRMaximumTxPower
· GetPowerlevel
· GetMaximumPayloadSize
· GetLRMaximumPayloadSize
· SetPowerlevel16Bit
· GetPowerlevel16Bit
· GetRFRegion
· SetRFRegion
· SetNodeIDType
2023-06-28T04:21:56.726Z CNTRLR Enabling TX status report…
2023-06-28T04:21:56.756Z CNTRLR Enabling TX status report successful…
2023-06-28T04:21:56.756Z CNTRLR Querying configured RF region…
2023-06-28T04:21:56.786Z CNTRLR The controller is using RF region Europe
2023-06-28T04:21:56.787Z CNTRLR finding SUC…
2023-06-28T04:21:56.818Z CNTRLR This is the SUC
2023-06-28T04:21:56.819Z CNTRLR querying additional controller information…
2023-06-28T04:21:56.854Z CNTRLR received additional controller information:
Z-Wave API version: 1 (official)
Z-Wave chip type: EFR32ZG14 / ZGM130S
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
nodes in the network: 1
2023-06-28T04:21:56.904Z CNTRLR Interview completed
Starting server on 0.0.0.0:3000
2023-06-28T04:21:56.953Z CNTRLR [Node 001] Beginning interview - last completed stage: None
2023-06-28T04:21:56.955Z CNTRLR [Node 001] new node, doing a full interview…
2023-06-28T04:21:56.956Z CNTRLR » [Node 001] querying protocol info…
ZwaveJS server listening on 0.0.0.0:3000
2023-06-28T04:21:57.077Z CNTRLR « [Node 001] received response for protocol info:
basic device class: Static Controller
generic device class: Static Controller
specific device class: PC Controller
node type: Controller
is always listening: true
is frequent listening: false
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2023-06-28T04:21:57.079Z CNTRLR [Node 001] Interview stage completed: ProtocolInfo
2023-06-28T04:21:57.127Z CNTRLR [Node 001] Embedded device config loaded
2023-06-28T04:21:57.128Z CNTRLR [Node 001] Interview stage completed: OverwriteConfig
2023-06-28T04:21:57.128Z CNTRLR [Node 001] Interview completed
2023-06-28T04:21:57.130Z CNTRLR [Node 001] The node is ready to be used
2023-06-28T04:21:57.131Z CNTRLR All nodes are ready to be used
2023-06-28T04:21:57.134Z CNTRLR [Node 001] The node is alive.
New client
Client disconnected
Code 1000:
New client
2023-06-28T04:36:52.556Z CNTRLR Starting inclusion process with strategy Default…
2023-06-28T04:36:52.606Z CNTRLR The controller is now ready to add nodes
2023-06-28T04:38:11.997Z CNTRLR stopping inclusion process…
2023-06-28T04:38:12.035Z CNTRLR The inclusion process was stopped
I tried reflashing the firmware of the dongle to both the latest and a previous version and both failed, although I successfully flashed to the latest firmware previously. The flash failed.
I got a Zooz stick today and it instantly worked has allowed me to add devices. Either Aeotec stick is NFG or I messed it up on the original fimware update. So I guess this is closed.
I think I’m in the same situation as yours, I’ve tried to install z-wave JS UI and with this tool it’s seems I can add my z-wave devices. But I have conflict with z-Wave JS and it’s not clear for me how I can add devices with z-wave JS UI.