Getting Zooz stick to work with zwave JS? New install

Configuration Z-Wave
1

I waited for the new Zwave-JS before installing my Zooz stick.
Zwave JS service is running.
Add-on is installed and sees the “s2 usb stick controller” by “zooz” model “ZST10”.
But it won’t include or exclude anything.
Pardon the lengthy log but I’m getting this below. Is the Zooz no longer supported??

                    · undefined (0x2e)
                    · undefined (0x2f)
                    · undefined (0x37)
                    · undefined (0x38)
                    · UNKNOWN_FUNC_ClearNetworkStats (0x39)
                    · UNKNOWN_FUNC_GetNetworkStats (0x3a)
                    · UNKNOWN_FUNC_GetBackgroundRSSI (0x3b)
                    · undefined (0x3c)
                    · UNKNOWN_FUNC_RemoveNodeIdFromNetwork (0x3f)
                    · GetNodeProtocolInfo (0x41)
                    · HardReset (0x42)
                    · FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
                    · FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
                    · AssignReturnRoute (0x46)
                    · DeleteReturnRoute (0x47)
                    · RequestNodeNeighborUpdate (0x48)
                    · ApplicationUpdateRequest (0x49)
                    · AddNodeToNetwork (0x4a)
                    · RemoveNodeFromNetwork (0x4b)
                    · FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
                    · FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
                    · undefined (0x4f)
                    · FUNC_ID_ZW_SET_LEARN_MODE (0x50)
                    · FUNC_ID_ZW_ASSIGN_SUC_RETURN_ROUTE (0x51)
                    · FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
                    · FUNC_ID_ZW_SET_SUC_NODE_ID (0x54)
                    · FUNC_ID_ZW_DELETE_SUC_RETURN_ROUTE (0x55)
                    · GetSUCNodeId (0x56)
                    · UNKNOWN_FUNC_SEND_SUC_ID (0x57)
                    · UNKNOWN_FUNC_AssignPrioritySUCReturnRoute (0x58)
                    · FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
                    · undefined (0x5f)
                    · RequestNodeInfo (0x60)
                    · RemoveFailedNode (0x61)
                    · IsFailedNode (0x62)
                    · ReplaceFailedNode (0x63)
                    · UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
                    · UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
                    · UNKNOWN_FUNC_UNKNOWN_0x78 (0x78)
                    · GetRoutingInfo (0x80)
                    · UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
                    · UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
                    · UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
                    · UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
                    · FUNC_ID_APPLICATION_SLAVE_COMMAND_HANDLER (0xa1)
                    · UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
                    · UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
                    · UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
                    · UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
                    · UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
                    · UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
                    · UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
                    · UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
                    · UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
                    · FUNC_ID_ZW_SET_PROMISCUOUS_MODE (0xd0)
                    · FUNC_ID_PROMISCUOUS_APPLICATION_COMMAND_HANDLER (0xd1)
                    · UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
                    · UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
                    · UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
                    · undefined (0xee)
                    · UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)

14:33:07.029 CNTRLR finding SUC…
14:33:07.064 CNTRLR SUC has node ID 1
14:33:07.104 CNTRLR querying node information…
14:33:07.240 CNTRLR received node information:
controller role: primary
controller is a SUC: true
controller is a slave: false
controller supports timers: false
nodes in the network: 1
14:33:07.258 CNTRLR [Node 001] trying to load device config
14:33:07.272 CNTRLR [Node 001] device config loaded
14:33:07.283 CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
14:33:07.305 CNTRLR serial API timeouts overwritten. The old values were: ack = 1000 ms, byte = 15
0 ms
14:33:07.306 CNTRLR Interview completed
Starting server on port 3000
14:33:07.323 CNTRLR [Node 001] Beginning interview - last completed stage: RestartFromCache
14:33:07.326 CNTRLR [Node 001] not pinging the controller
ZwaveJS server listening on port 3000
Server listening on port 3000
14:33:07.337 CNTRLR [Node 001] Interview stage completed: CommandClasses
14:33:07.338 CNTRLR [Node 001] trying to load device config
14:33:07.345 CNTRLR [Node 001] device config loaded
14:33:07.346 CNTRLR [Node 001] Interview stage completed: OverwriteConfig
14:33:07.347 CNTRLR » [Node 001] requesting node neighbors…
14:33:07.411 CNTRLR [Node 001] The node is alive.
14:33:07.413 CNTRLR [Node 001] The node is ready to be used
14:33:07.414 CNTRLR All nodes are ready to be used
14:33:07.415 CNTRLR « [Node 001] node neighbors received:
14:33:07.415 CNTRLR [Node 001] Interview stage completed: Neighbors
14:33:07.416 CNTRLR [Node 001] Interview completed
New client
14:36:29.613 CNTRLR starting inclusion process…
14:36:29.669 CNTRLR handling add node request (status = Ready)
14:36:29.670 CNTRLR the controller is now ready to add nodes
14:36:51.488 CNTRLR stopping inclusion process…
14:36:51.565 CNTRLR handling add node request (status = Done)
14:36:51.566 CNTRLR done called for 0
14:36:51.567 CNTRLR the inclusion process was stopped

2

By the way, when I try to use Z-wave JS to mqtt, I get “Driver: Failed to initialize the driver: Timeout while waiting for an ACK from the controller”
I’m confused, how can zwave-JS broker be communicating with the S2 stick, if the driver isn’t working?

3

Can anybody help me??

4

Is this the older ZST10 stick by Zooz or the newer ZST10 with 700 series chip?

5

I think I have the same stick and it’s working correctly. I migrated from z-wave 1.4 on the same stick. What do you have set for the device and network key?

Edit: make sure you have no other z-wave add-ons installed. I thought I had removed my z-wave 1.4 add-on, but it kept coming back after each restart - I think because I also had an entry for it in configuraion.yaml in order to set a refresh and delay option for finicky Jasco dimmer.

S2 USB Stick Controller
Device info
ZST10
by Zooz

device
/dev/serial/by-id/usb-0452_0100-ie00
 
network_key
D7FB192E65D30870A27C039CFD476F7C
6

It’s the older 500 series. Zooz thinks zwave-JS the integration is broken.

7

Is the network key the same as what you show? Where do you find the correct network key?
Thanks!

8

I modified that key before I posted it as I wasn’t sure if there was any security issues with making it public. I got the key from the file /config/.storage/core.config_entries using the migration instructions for Zwave 1.4 to Zwave JS.

If you never had the Zwave 1.4 installed you should follow the instructions below. It looks like the key is automatically generated if you don’t provide one from a previous Zwave network.

9

Thanks everyone. It’s working now. Of all things, my SSD/Sabrent drive was going bad! Don’t ask me how it stopped my Zooz from working but it did.

10

Glad you got yours working. I have the 700 series model of the same stick and I’m suddenly running into the same “cannot include or exclude issue” It’s really bizarre - it worked fine for about 8-10 devices then nada.