AlCalzone
AlCalzone
I was trying to find a correlation between the error you quoted from the HA logs: > zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts....
> even after downgrading to 0.10.0 these errors persist., they just dont break the system It looks like the Z-Wave JS driver doesn't retry these failed commands on v15/0.11 as...
> OpenThread Border Router add-on using the zbt-1 That has nothing to do with Z-Wave.
https://github.com/zwave-js/zwave-js/releases/tag/v15.1.0 should fix this, but the addon still needs an update.
> I havent been able to 'reproduce' actively or find a specific reason in the log, but it is quite impactful. Best make a new issue in the zwave-js repo,...
Since this is tagged "Awaiting more feedback", I'll just link to https://github.com/microsoft/TypeScript/issues/36194 as a potential use case.
The problem here is that the device does not support reporting its range, so this info isn't known to Z-Wave JS or HA. The default range HA uses for this...
> I could be wrong, but it doesn't look like ZMNKID reports its range either It does. It supports Thermostat Setpoint CC V3, which adds the functionality to advertise the...
I'll review it soon. Lots of stuff on my plate right now.
Strictly validating a setpoint using an **assumed range** due to lack of known capabilities does not seem right. The Z-Wave integration at least will need an escape hatch to fulfill...