Matter entities attached to wrong devices

[jagged sequoia]

At about 4:30am this morning a lot (but not all) of my matter devices went haywire.
I first noticed when my dashboard had several rooms temperature sensors as unavailable.
Many entities were duplicated with _2 added. The origonal version marked as no longer provided and the new version operating.
But the weird ones are door/window switch devices that have temperature and humidity entities attached to them.

The questions are:

1. how do I reassign the entities to the correct devices
2. how can I not lose two years of data on the entites that are now unavallable.

[jagged sequoia]

In the last couple of days i've tinkered and researched.
Restoring a backup from a few days ago fixes the problem, but it just comes back again.

The only good news is that I found a forum post stating that I can just delete the old "no longer being provided by the matter integration" entities and rename the _2 ones back to the original name.

The bigger problem is with the entities that have taken on the name of the device they attached themselves to.
sensor.front_security_humidity is a functional humidity entity attached to the front security door switch device. I have no way of knowing what that sensor is and where it came from.

oh, and I just found a new one.
binary_sensor.front_door has renamed itself to
binary_sensor.front_door_door

As a fun side note, binary_sensor.front_security_door refuses to take on the friendly name I set. It just wants to be Door and nothing else.

As enormous as the job would be, i'm wondering if it is going to be easier to just yank out the matter integration and start again.

[bright blaze]

@winter bough i thought unique ids were unique for the device?

[winter bough]

Could it be related to a Tapo bridge update that changed the identifiers for bridged devices?
Otherwise, I don't see why it would have changed for no reason.

[winter bough]

Identifiers are provided by devices or bridges. We have no control over this behavior if they are changed during an update.

[bright blaze]

Yea that's what I expected, hence I thought this was weird

[bright blaze]

Is this something we can detect and migrate? Or is this very niche?

[winter bough]

There is already an open issue for this, but no solution.

[winter bough]

I couldn't find it. It's worth creating a new issue.

[jagged sequoia]

possible, but the combination seems random.

[jagged sequoia]

On the Tapo integration?

[winter bough]

Matter integration

[winter bough]

Please attach diagnostic file: https://www.home-assistant.io/blog/2024/02/07/release-20242/#matter-diagnostics-and-actions

The problem is that we would need the diagnostic file before and after to compare.
As it stands, I don't really see how to do it without that.

[jagged sequoia]

Is this the right place? @winter bough @bright blaze

forgive my noobness. github is a tangled mess of I-don't-know-what-i'm-doing.

[bright blaze]

yes!

[jagged sequoia]

https://github.com/home-assistant/core/issues/162519

[jagged sequoia]

Started to attempt a repair, one device at a time.

can't delete the device so I tried disable/enable

The only thing in the system logs is an error from a template that used that sensor, and this

Source: helpers/entity.py:1145
First occurred: 5:28:30 PM (2 occurrences)
Last logged: 5:28:30 PM

Entity sensor.james_temperature_humidity_sensor_temperature_2 is incorrectly being triggered for updates while it is disabled. This is a bug in the matter integration
Entity sensor.outside_temperature_and_humidity_humidity is incorrectly being triggered for updates while it is disabled. This is a bug in the matter integration```