ZwaveJS is this normal? Failed to execute controller command after 1/3 attempts. Scheduling next try in 100 ms

I have this all the time… is this normal?

2021-12-06T07:55:05.376Z CNTRLR   [Node 032] The node is now asleep.
2021-12-06T07:55:12.561Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T07:56:12.323Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T07:57:39.194Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T07:57:39.611Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:02:48.453Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:02:48.556Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-12-06T08:02:48.900Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-06T08:03:00.237Z CNTRLR   [Node 028] Timed out while waiting for a response from the node (ZW0201)
2021-12-06T08:03:00.500Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:03:05.389Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:03:09.250Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-06T08:03:10.542Z CNTRLR « [Node 012] received wakeup notification
2021-12-06T08:05:53.504Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:05:53.867Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:05:53.994Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-12-06T08:14:29.984Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:17:27.755Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:17:27.960Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:17:28.275Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:18:28.217Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:19:13.077Z DRIVER   Dropping message with invalid payload
2021-12-06T08:21:25.356Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:22:25.441Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:22:57.076Z CNTRLR « [Node 030] received wakeup notification
2021-12-06T08:22:57.076Z CNTRLR   [Node 030] The node is now awake.
2021-12-06T08:22:58.079Z CNTRLR » [Node 030] Sending node back to sleep...
2021-12-06T08:22:58.134Z CNTRLR   [Node 030] The node is now asleep.
2021-12-06T08:23:25.361Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:23:25.819Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:24:25.860Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:25:25.719Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:25:26.103Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:26:25.426Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:29:25.367Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:29:25.775Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:30:25.504Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:30:52.467Z CNTRLR « [Node 057] received wakeup notification
2021-12-06T08:30:52.467Z CNTRLR   [Node 057] The node is now awake.
2021-12-06T08:30:53.468Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-06T08:30:53.532Z CNTRLR   [Node 057] The node is now asleep.
2021-12-06T08:31:34.602Z CNTRLR « [Node 052] received wakeup notification
2021-12-06T08:31:34.603Z CNTRLR   [Node 052] The node is now awake.
2021-12-06T08:31:35.603Z CNTRLR » [Node 052] Sending node back to sleep...
2021-12-06T08:31:35.669Z CNTRLR   [Node 052] The node is now asleep.
2021-12-06T08:32:25.414Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:32:25.518Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-12-06T08:33:25.869Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:36:25.403Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:38:25.441Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:40:25.941Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:44:25.601Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:44:25.796Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:45:25.452Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:45:25.823Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:45:26.213Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:47:25.365Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:49:25.622Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T08:50:25.548Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

Are you running a re-interview or command on a battery operated device perhaps? It’s best to manually wake the device to deliver commands and re-interviews. In such cases you can safely ignore these kind of messages. Otherwise it seems like a bad route to the device it’s trying to reach. (Either due to a bad path or signal strength)

Hi Rick,

thanks for taking the time to respond. Nothing special running here. Did not re-interview and device. What device do you think “it” (what is it?) trying to reach?

the latest logs as it’s always doing this…

2021-12-06T09:28:25.915Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:31:13.396Z CNTRLR « [Node 057] received wakeup notification
2021-12-06T09:31:13.396Z CNTRLR   [Node 057] The node is now awake.
2021-12-06T09:31:14.397Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-06T09:31:14.402Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:31:14.555Z CNTRLR   [Node 057] The node is now asleep.
2021-12-06T09:32:25.495Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:34:25.603Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:35:25.836Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:36:25.527Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:39:25.548Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:39:25.739Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:39:25.941Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:40:25.584Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:43:25.680Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:44:25.603Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:44:26.027Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:46:25.753Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:48:25.490Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:48:25.720Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:49:25.989Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:49:55.637Z CNTRLR « [Node 009] received wakeup notification
2021-12-06T09:49:55.638Z CNTRLR   [Node 009] The node is now awake.
2021-12-06T09:49:56.638Z CNTRLR » [Node 009] Sending node back to sleep...
2021-12-06T09:49:56.971Z CNTRLR   [Node 009] The node is now asleep.
2021-12-06T09:50:25.416Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:51:25.658Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:52:25.532Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:53:23.344Z CNTRLR « [Node 007] received wakeup notification
2021-12-06T09:53:23.344Z CNTRLR   [Node 007] The node is now awake.
2021-12-06T09:53:24.346Z CNTRLR » [Node 007] Sending node back to sleep...
2021-12-06T09:53:24.446Z CNTRLR   [Node 007] The node is now asleep.
Client disconnected
Code 1000: 
New client
New client
Client disconnected
Code 1000: 
2021-12-06T09:56:25.665Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:56:25.854Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:56:26.110Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:56:26.340Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:58:25.401Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T09:58:26.045Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:01:25.988Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:03:08.510Z CNTRLR « [Node 012] received wakeup notification
2021-12-06T10:03:25.807Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:03:26.005Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:03:26.630Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:05:26.066Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:06:26.044Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:08:26.008Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:08:26.210Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:10:26.057Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T10:12:23.119Z CNTRLR « [Node 031] received wakeup notification
2021-12-06T10:12:23.119Z CNTRLR   [Node 031] The node is now awake.
2021-12-06T10:12:24.121Z CNTRLR » [Node 031] Sending node back to sleep...
2021-12-06T10:12:24.170Z CNTRLR   [Node 031] The node is now asleep.
2021-12-06T10:12:25.973Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

“Failed to execute command on controller” mean zwavejs could not connect to Zwave controller I believe

Is usb disconnecting?

I read NUT sensor can cause some condition that halts usb to controller but I not sure?

It look like it’s temporary condition but happen often. I have same issue and eventually crash and process restart. I think for you this will cause slow network correct?

whats that?

how can I troubleshoot that?

Hm… not sure… I have not noticed that. Only when I switch of a lot sometimes it lags a bit… (1s).

No clue

Having same issue with controller errors
Just giving info in hopes you get somewhere

do you passthrough your usb via esx?

Are you using Z-WaveJS or Z-WaveJS2MQTT addon? Any other USB devices and/or addons using USB devices on your system? It seems very consistent behavior, nearly each exact minute.

Hi Rick,

ZwaveJS (addon & integration)
image

Deconz with conbee2 stick
DSMR smart meter reader

Some more:

2021-12-06T11:27:10.139Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:31:10.029Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:31:56.129Z CNTRLR « [Node 057] received wakeup notification
2021-12-06T11:31:56.132Z CNTRLR   [Node 057] The node is now awake.
2021-12-06T11:31:57.133Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-06T11:31:57.205Z CNTRLR   [Node 057] The node is now asleep.
2021-12-06T11:32:09.821Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:32:10.033Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:38:09.975Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:39:10.256Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:40:10.233Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:42:10.057Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:42:10.545Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:45:09.922Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:50:10.126Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:53:10.093Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T11:57:10.093Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:00:10.005Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:01:10.012Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:02:10.310Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:02:52.657Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-06T12:03:06.186Z CNTRLR « [Node 012] received wakeup notification
2021-12-06T12:03:07.934Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-06T12:04:10.056Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:04:10.560Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:05:10.068Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:08:10.208Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:09:10.292Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:09:10.655Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:10:07.528Z CNTRLR « [Node 029] received wakeup notification
2021-12-06T12:10:07.529Z CNTRLR   [Node 029] The node is now awake.
2021-12-06T12:10:08.530Z CNTRLR » [Node 029] Sending node back to sleep...
2021-12-06T12:10:08.581Z CNTRLR   [Node 029] The node is now asleep.
2021-12-06T12:11:20.245Z CNTRLR   [Node 065] Timed out while waiting for a response from the node (ZW0201)
2021-12-06T12:14:10.142Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:14:10.583Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:15:10.288Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:16:09.942Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:19:02.413Z DRIVER   Dropping message with invalid payload
2021-12-06T12:21:09.947Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:21:10.278Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:24:10.083Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:25:10.209Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:30:10.018Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:30:10.605Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:32:09.944Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:32:17.965Z CNTRLR « [Node 057] received wakeup notification
2021-12-06T12:32:17.965Z CNTRLR   [Node 057] The node is now awake.
2021-12-06T12:32:18.968Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-06T12:32:19.054Z CNTRLR   [Node 057] The node is now asleep.
2021-12-06T12:33:10.312Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:33:49.827Z CNTRLR « [Node 052] received wakeup notification
2021-12-06T12:33:49.827Z CNTRLR   [Node 052] The node is now awake.
2021-12-06T12:33:50.828Z CNTRLR » [Node 052] Sending node back to sleep...
2021-12-06T12:33:50.888Z CNTRLR   [Node 052] The node is now asleep.
2021-12-06T12:34:10.012Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:34:10.217Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:35:10.242Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:37:09.952Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-06T12:37:10.625Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.

How is the DSMR being read? Do you run an addon, implement it in your configuration/integrations, other options? Would it be possible to temporarily disable the DSMR component for like 5 or 10 minutes to see if it resolves the Z-Wave controller messages? It looks like it’s performing some sort of USB reload/lock every 60 seconds.

Via a USB “slimme meter kabel”, nowadays via an official integration:
image

I see there’s an update as well today:
image

I will disable the slimme meter USB for a while and observe.

did you migrate from some other zwave solution? i remember having this when moving between zwave js and mqtt and other fiddling.
now running the mqtt addin with normal zwave js integration and i dont have the errors since long.
So somehow a conflict on usb concurrent driver usage might be underlying. Whats your setup (OS etc)

image

the stick used to be connected to the deprecated OZW (beta) but I moved about a week or 2/3 to ZwaveJS and observed this disconnect behavior lately. I have not other zwave related stuff anymore in my homeassistant instance.

Disable for about 1hr… no difference:

021-12-07T09:39:45.698Z CNTRLR « [Node 057] received wakeup notification
2021-12-07T09:39:45.698Z CNTRLR   [Node 057] The node is now awake.
2021-12-07T09:39:46.699Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-07T09:39:46.739Z CNTRLR   [Node 057] The node is now asleep.
2021-12-07T09:40:50.922Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:44:05.677Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:44:06.111Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:48:13.785Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:49:46.801Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:50:46.690Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:50:47.108Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:50:47.475Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:53:13.714Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:54:56.645Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:57:56.486Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T09:57:57.119Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:00:56.535Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:01:56.590Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:02:43.755Z CNTRLR « [Node 012] received wakeup notification
2021-12-07T10:02:51.976Z CNTRLR « [Node 013] received wakeup notification
2021-12-07T10:02:51.977Z CNTRLR   [Node 013] The node is now awake.
2021-12-07T10:02:52.978Z CNTRLR » [Node 013] Sending node back to sleep...
2021-12-07T10:02:53.048Z CNTRLR   [Node 013] The node is now asleep.
2021-12-07T10:02:56.641Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:05:56.514Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:06:56.585Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:07:56.641Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:07:57.024Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:11:56.554Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:14:57.013Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:15:56.715Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:16:52.884Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-07T10:16:52.940Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-07T10:17:11.883Z CNTRLR   [Node 021] treating BasicCC::Set as a report
2021-12-07T10:17:56.431Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:17:56.689Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:19:09.813Z DRIVER   Dropping message with invalid payload
2021-12-07T10:19:10.907Z DRIVER   Dropping message with invalid payload
2021-12-07T10:21:56.427Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:22:56.880Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:24:46.910Z CNTRLR « [Node 031] received wakeup notification
2021-12-07T10:24:46.911Z CNTRLR   [Node 031] The node is now awake.
2021-12-07T10:24:47.913Z CNTRLR » [Node 031] Sending node back to sleep...
2021-12-07T10:24:47.960Z CNTRLR   [Node 031] The node is now asleep.
2021-12-07T10:28:33.219Z CNTRLR « [Node 039] received wakeup notification
2021-12-07T10:28:33.219Z CNTRLR   [Node 039] The node is now awake.
2021-12-07T10:28:34.220Z CNTRLR » [Node 039] Sending node back to sleep...
2021-12-07T10:28:34.317Z CNTRLR   [Node 039] The node is now asleep.
2021-12-07T10:28:52.120Z CNTRLR « [Node 032] received wakeup notification
2021-12-07T10:28:52.120Z CNTRLR   [Node 032] The node is now awake.
2021-12-07T10:28:53.120Z CNTRLR » [Node 032] Sending node back to sleep...
2021-12-07T10:28:53.176Z CNTRLR   [Node 032] The node is now asleep.
2021-12-07T10:29:56.469Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:29:56.774Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:30:56.690Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:32:56.557Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:34:56.620Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:34:57.041Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:35:56.658Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:36:56.513Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:39:56.613Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-12-07T10:40:07.060Z CNTRLR « [Node 057] received wakeup notification
2021-12-07T10:40:07.061Z CNTRLR   [Node 057] The node is now awake.
2021-12-07T10:40:08.062Z CNTRLR » [Node 057] Sending node back to sleep...
2021-12-07T10:40:08.139Z CNTRLR   [Node 057] The node is now asleep.

Hi, is there any other thing I can do to get rid if these disconnects?

EDIT: created an issue:

Maybe it’s something with the hypervisor you’re running on? I see you mentioning ESXi, what version? There are quite some issues with v7.0 Update 3x. As you’re running in a VM environment, can you double check the console to see any dmesg logging about USB (re)connection? If so, please also check the same on your host to see if maybe your hardware is starting to fail.

Otherwise I’m all out of ideas and I’ll continue to monitor the conversation/issue created for future references.

6.7. u3 I run (if it ain’t broken don’t fix… well it might be actually :-))

I can get the dmesg log via the ssh SSH & Web Terminal addon but cannot copy.paste it… tips?

via the ESXi host I can get it… but I do not wish to share publicly…

Just wondering if you see your Z-Wave USB device triggering the logs every X seconds. Don’t need to actually see the logs :slight_smile: Should you ever need to paste long texts you can use Pastebin. (Web service)

Hi Rick, not sure how I can see that in the logs. I do not now how to look that up in linux…

Some more info. I investigated the homeassitant host, the hypervisor host ans discovered some weird errors. I google them and saw some hits but no solution. And all on esxi 6.5 and 7. I have 6.7

Preventive rebooted the ESXi host which had been running for 364 days :-).

But still errors in homeassitant.

Below errors were in esxi before reboot. Now gone in esxi.

e[7m2021-12-06T11:16:42.685Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.685Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.686Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.686Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.693Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.693Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.694Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.694Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.694Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.694Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.694Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.695Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.696Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.696Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.696Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.699Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.700Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.701Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.701Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.701Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.701Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.701Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.702Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.702Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.702Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.702Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.705Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.706Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.706Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.706Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.706Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.706Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.707Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.708Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.708Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.708Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.708Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.709Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.709Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.709Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m
e[7m2021-12-06T11:16:42.710Z cpu3:2097577)WARNING: vmkusb: transfer error [18]: endpt = 0x82, nframes = 1, timeout = 0, interval = 0, max_packet_size = 32, max_frame_size = 32: Failuree[0m

I have this host (6.7u3) running for over 2 years now with usb passed trough all the time:

[[email protected]:~] lsusb
Bus 001 Device 006: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 001 Device 005: ID 8087:0aaa Intel Corp.
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 003: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 002: ID 1cf1:0030 Dresden Elektronik
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc. Root Hub

Never had issues… even with OZW Beta. Until now with ZwaveJs I see the disconnects…
I do see some topics about 6.5:
https://kb.vmware.com/s/article/2147650

https://floating.io/2017/02/openhab-a-z-stick-and-esxi-6-5/

But none of them clearly mention 6.7, only 6.5

I do not “dare” to execute the command esxcli system module set -m=vmkusb -e=FALSE on my 6.7 machine since I might get into worse troubles then.

Any advise?