AlCalzone

> zwave-js: 8.0.5 Ok I thought you might be on an old one. Can you share a driver log (loglevel debug) which shows the effect that all values end up...

> if I should try excluding and reincluding the device first? No, unless you changed a parameter which changes the capabilities of the device, this is not necessary.

Something is not right there. First, I don't see any log that the re-interview was started - just that all config paramters get queried. Second, the device doesn't respond to...

> Sorry, didn't realise that you needed a re-interview... Sorry, I got confused for a second here. I probably don't... However none of your logs include the situation you described...

No, that came from telemetry where we had >10 users. That device didn't have any auto-discoverable info that helps here. The manufacturer is **Good Way Technology Co., Ltd.**, at least...

Didn't find anything on the Z-Wave Alliance Website either

Looks good, I'd remove the `"reset": "n/a"` though. Can you post this as a pullrequest?

Please make a [driver log](https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs), loglevel `debug` and attach it here as a file. The logfile should highlight the interaction that isn't working as expected.

Wrong log. 

Ok, that is the interview. Do you also have a log of this? > The logfile should highlight the interaction that isn't working as expected.