Failed to execute controller command after 1/3 attempts

[jriker1]

If i was getting the error in the subject on Windows 2022 with the Hyper-V role in the logs plus delays in responsiveness, and now I am not (going to be sorry I said that) was there something between release 8.8.0 and 8.8.3 that would have made a difference?

[jriker1]

Nevermind still broken just ran a couple days without failing.

[robertsLando]

What stick are you using? Are you using an extension usb cable?

[jriker1]

It is an Aeotec Z-Stick Gen5 with firmware 1.2. It does have an active extension cable on it.

It worked fine originally for years. I have recently moved my HA environment, which I don't think is relevant to a new Hyper-V virtual and setup the Z-WaveJS components with your install on the Windows 2022 server with Hyper-V host. Think the second part is relevant.

After moving from a Linux virtual on VMware workstation to this started having issues. Sometimes will work for a day sometimes a couple hours before devices respond slowly or not at all and the interface in Home Assistant stop displaying the status of things like lights. Removing the stick and putting it back in or rebooting helps for a short period. From what I understand the thought is it is related to this:

https://github.com/zwave-js/node-zwave-js/issues/5024

Thought the last update here fixed it as I went from:

zwave-js-ui: 8.8.0 zwave-js: 10.4.0

to the current 8.8.3 release. Two days later started acting up again. Attached are the current logs. zwavejs_2023-02-04.log z-ui_2023-02-04.log

Hard for me to follow the logs as think one is GMT and maybe one is local? The z-ui file is odd as at some point it stops reporting info completely. Light and stuff can turn on and off still, just sometimes they react right away and sometimes they don't however that error is all over.

Note I've:

• Updated the firmware from 1.1 to 1.2
• Updated this component as mentioned above.
• Rebooted which helps briefly where the old setup went years with no issues.
• healed all devices
• Installed the Aeotec driver
• Reset the COM port settings in Windows to default.

[robertsLando]

@AlCalzone any updates on https://github.com/zwave-js/node-zwave-js/issues/5024 ?

[AlCalzone]

Nothing new. This is a bad interaction between the serialport library on Windows and something else, possibly xstate.

Although the logs above look like something else - first it works, then the stick suddenly stops responding. Might be related to VM configuration?

[jriker1]

If we are talking about my logs not sure but ZWave-JS UI is running on the host and it's known to my dislike that Hyper-V doesn't interact or passthrough USB ports. Not even an option to select one in the admin screens.

I can say that in the Device Manager the port is still active and shows no functional issues. If when it's not working and I stop and start the ZWave JS UI exe again it will fail to load the driver within the ZWave JS UI console.

[jriker1]

Note I changed some settings in the gui like Disable DNS Discovery, disabled statistics, and disabled soft reset. Saw this on some posts. System ran for a couple days and then started acting up again.

Note the stick still shows in device manager

And the stick is still functioning just slow however no data being reported back to HA. So Alexa again can turn lights on and off just slow to reply.

Haven't done it but historically if I stopped and started ZWaveJS UI it would fail to load the driver.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

[github-actions[bot]]

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.