Set Serial to COM3, pasted in my S0 and generated the S2 entries
Disabled Statistics
Disabled MQTT Gateway. Oddly had it on and when I turned it off my devices disconnected for a bit from HA so thought maybe it was needed but they came back.
Under Home Assistant enabled WS Server
Saved.
In Home Assistant
I already had left over Z-wave stuff so will be different but
Went to Settings > Devices & Services > Add Integration
Type in Z-Wave and select
Selected Z-Wave
Unchecked Use the Z-Wave JS Supervisor add-on
Entered my server info which was ws:\<server_ip>:3000
In my case my existing install was just updated instead and everything started working again.
Now to try out making a service and to figure out what I need to move as I did this in c:\temp which isn’t the best place for it.
Moved the exe and the store folder to another location and did use nssm to create the service. sc wouldn’t work with it. Did put my admin account as the runas not sure I needed to.
Didn’t need to open the firewall for port 3000 as apparently the virtual can access it where I can’t outside of the Hyper-V server. Will need to open 8091 though if I want to access the Z-WaveJS UI GUI remote.
Looks like I spoke to soon. It was working great and now it looks like it’s timing out. Things kind of still turn on and off but super slow and the gui doesn’t reflect the changes. Currently not seeing anything in the home assistant logs. In the Z-Wave JS serve rlogs seeing a lot of t his:
2023-01-28T21:27:14.463Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-01-28T21:27:14.571Z SERIAL » 0x01070080120000006a (9 bytes)
2023-01-28T21:27:14.572Z DRIVER » [REQ] [GetRoutingInfo]
remove non-repeaters: false
remove bad links: false
2023-01-28T21:27:15.572Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-01-28T21:27:16.682Z SERIAL » 0x01070080120000006a (9 bytes)
2023-01-28T21:27:16.683Z DRIVER » [REQ] [GetRoutingInfo]
remove non-repeaters: false
remove bad links: false
2023-01-28T21:27:17.687Z CNTRLR [Node 018] requesting the node neighbors failed: Timeout while waiting for an
ACK from the controller (ZW0200)
2023-01-28T21:27:17.687Z CNTRLR Turning RF on...
2023-01-28T21:27:17.688Z SERIAL » 0x0104001001ea (6 bytes)
2023-01-28T21:27:17.688Z DRIVER » [REQ] [SetRFReceiveMode]
enabled: true
2023-01-28T21:27:18.704Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-01-28T21:27:18.814Z SERIAL » 0x0104001001ea (6 bytes)
2023-01-28T21:27:18.814Z DRIVER » [REQ] [SetRFReceiveMode]
enabled: true
2023-01-28T21:27:19.826Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-01-28T21:27:20.926Z SERIAL » 0x0104001001ea (6 bytes)
2023-01-28T21:27:20.926Z DRIVER » [REQ] [SetRFReceiveMode]
enabled: true
2023-01-28T21:27:21.926Z CNTRLR Error turning RF on: Timeout while waiting for an ACK from the controller (ZW0
200)
Let’s keep in mind same stick in same place as when I was running this thru VMware Workstation. Just a different setup with the Z-Wave JS server running on the Hyper-V server and HA running in a Hyper-V virtual.
Note if I stop and start the Z-Wave JS service I get:
Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from
Note I rebooted the entire main Hyper-V server and things went back to normal for a few hours. Then started having issues again with timeouts and updates not showing in HA itself. I’ve tried disabling the ability for the OS to turn off the port but no joy. Also made sure to install the Aeotec driver for the device but that didn’t seem to help either.