AlCalzone
AlCalzone
> So, how could any HA automation depend on it ? I thought it does indirectly through the entity names? > Those entities should be renamed, if possible. This requires...
> Some routes are pretty odd, and clearly NOT the best route. That's unfortunately a result of the Z-Wave routing algorithm being suboptimal. I'm looking into optimizing this for the...
Additionally, do you have some documentation for that proprietary protocol? I wonder what else is in there.
We should avoid using transformers for this, as it isn't clear how the future for those will be. Probably just pass the enum name as a string, with some ESLint...
Still happening
I think the node names should be stored separately for each home ID. Or you could use the properties from the node instance to have the driver handle it?
In any case, nodes belonging to a different home ID are very likely not the same devices. Especially if the Node ID also changed.
@robertsLando I still think we should tackle this. It is extremely confusing that devices get some unrelated names just because they have the same node id another device previously had
A [driver log](https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs) of the addon startup on loglevel `debug` would be good. Please attach it here as a file (drag & drop into the text field).
Uhhh. How was it working before the update then? This means you didn't have secure communication before either, which seems weird for communication with an alarm panel.