AlCalzone

Try re-interviewing to have the lifeline association set up automatically. Maybe that went wrong last time.

Please make a [driver log](https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs), loglevel `debug` and attach it here as a file (drag & drop). Please start the log before doing another re-interview and keep it running for...

Ok, so the interview of the thermostat (37) looks okay, the association is set up, but no messages are received after the interview. Did you do anything on the thermostat...

There are a couple of reports in the log after the interview though. * Node 34, temperature * Node 2, Binary sensor * Node 5, kWh, W, V, A *...

All I see in relation to Node 39 are pings after driver startup. No commands controlling it, no automatic reports of any kind. But there are a lot of serial...

Yes please. That doesn't seem to work as intended

There's one incoming report for Node 39 in there (power usage stayed the same at 0.8 W): ``` 2022-09-25T13:27:44.701Z CNTRLR [Node 039] [~] [Meter] value[66049]: 0.8 => 0.8 [Endpoint 1]...

There were also several multi sensor reports, I just focused on that one. Yep, either the device has a flaky connection and some reports get lost. Or it doesn't report...

It might be that OZW polled them regularly and hid the underlying problem. Without seeing logs I assume this is a connectivity issue. For troubleshooting I recommend these steps: -...

Please re-test with v10.0.4. This version is included in: zwave_js addon: 0.1.70 or zwavejs2mqtt: 7.1.0