Entities Replaced with New Entities after Firmware Update via HASS #7006
Replies: 5 comments 1 reply
-
👋 Hey @barndawgie! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
I couldn't get a log of this happening, but Device Diagnostics are attached and you can see the new, "_2" entities that were created. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to delete the device in Home Assistant an force it to be recreated? |
Beta Was this translation helpful? Give feedback.
-
It looks like the old values reference endpoint 0 while the new ones reference endpoint 1. To know why, please make a driver log of a re-interview, loglevel |
Beta Was this translation helpful? Give feedback.
-
@AlCalzone - Thanks for getting back to me. Driver Log is attached. |
Beta Was this translation helpful? Give feedback.
-
Checklist
I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.
Describe the issue
What is happening?
I updated my Aeotec ZWave Plug via Home Assistant Update entity. When it came back up after successful upgrade, all existing entities were unavailable and new entities suffixed with “_2” had been created.
What did you expect to happen instead?
Existing entities should still have been active
Steps to reproduce the behavior:
Anything else we should know?
Software versions
Driver (node-zwave-js): 12.12.4
Z-Wave JS UI: 9.14.6
Home Assistant Z-Wave Integration: 2024.7.2
If you are using something non-standard, tell us here: ZWave-js-ui running in docker
Device information
Manufacturer: Aeotec
Model name: Smart Switch 7
Node ID: 009
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
No response
Beta Was this translation helpful? Give feedback.
All reactions