AlCalzone

Please make a [driver log](https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs), loglevel `debug` of a re-interview and what isn't working and attach (drag&drop) it here as a file.

For reference for my later investigation: ``` 2022-09-12T14:00:08.451Z SERIAL « 0x010b0004003c052603646402ee (13 bytes) 2022-09-12T14:00:08.452Z SERIAL » [ACK] (0x06) 2022-09-12T14:00:08.453Z CNTRLR [Node 060] [~] [Multilevel Switch] duration: {"value":2,"unit":"s [Endpoint 0] econds"}...

FWIW, one of the latest driver versions makes sure not to "forget" which keys a device has. This was solved suboptimally before.

This looks suspiciously like the other issue you commented in, at least to some degree. Node 9 has 27 timeouts during the interview alone. I don't know if you tried...

I did change the default report timeout from 10000 ms to 1000 ms a while ago, to be in line with what the specs recommend. So far the only devices...

@doug-hoffman that was fixed today in https://github.com/zwave-js/node-zwave-js/pull/5015, version 10.0.4 (HA addon 0.1.70, z2m 7.1.0)

Please share a driver log of the interview attempt

> Not sure which one of these things specifically solved my issues The USB extension definitely played a big part in this

yeah, I think the real number is whatever your machine can handle 🙈

If anyone plans on helping out with this file, please read https://zwave-js.github.io/node-zwave-js/#/config-files/using-telemetry-data first.