A previously working sensor has a missing entity after changing it's name in z2m.

[Brucepbd]

The problem

I changed the name of a z2m motion sensor with illuminance from MS1 to MSL1. In z2m everything is working after the name change.

When I renamed the motion sensor with illuminance in z2m, I selected to update home assistant entity ID. Home assistant made the name change, but the illuminance sensor entity of the motion sensor (which is working fine in z2m) is missing from home assistant after the name change (see pictures).

I'm using home assistant green, I'm not sure what my system is or what the last working version of home assistant was. I installed the sensor in July or early August 2024 and the illuminance has always been working up until the name change today (12-25-24).

I checked the device properties in home assistant for entities not shown, and illuminance wasn't there (see picture). Before the name change I had 4 automations that relied on the illuminance value and had been working fine for months right up until the name change.

If home assistant has been using that entity for months, why has the name change from MS1 to MSL1 in z2m broken it? Why does home assistant recognize the other entities from this sensor but not the illuminance? Why did home assistant recognize and accept the illuminance entity from this sensor months ago during discovery but now it does not?

I checked another identical motion sensor with illuminance, and it installs/works flawlessly on z2m, but home assistant doesn't recognize the illuminance on that sensor either. The new sensor has no connections with automations or old names or devices ids - so it can't be that.

The debug info shows that z2m is sending home assistant illuminance data (see pictures).

I always update the core when there is an update, and z2m rarely has updates - so I am guessing that something is broken in the core discovery of home assistant or device registry. Since illuminance was working fine until the name change. Can you help?

What version of Home Assistant Core has the issue?

2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Zigbee2MQTT

Link to integration documentation on our website

https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html

Diagnostics information

System Information

version	core-2024.12.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.0
os_name	Linux
os_version	6.6.66-haos
arch	aarch64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.1
Stage	running
Available Repositories	1495
Downloaded Repositories	16

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.1
update_channel	stable
supervisor_version	supervisor-2024.12.0
agent_version	1.6.0
docker_version	27.2.0
disk_total	28.0 GB
disk_used	23.3 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	green
supervisor_api	ok
version_api	ok
installed_addons	Mosquitto broker (6.4.1), Advanced SSH & Web Terminal (19.0.0), Zigbee2MQTT (1.42.0-2), File editor (5.8.0), Get HACS (1.3.1), AppDaemon (0.16.7), Samba share (12.3.2), Grafana (10.2.2), InfluxDB (5.0.1), Studio Code Server (5.18.0), ESPHome Device Builder (2024.12.2), Home Assistant Google Drive Backup (0.112.1)

Dashboards

dashboards	7
resources	11
views	5
mode	storage

Recorder

oldest_recorder_run	December 14, 2024 at 4:51 AM
current_recorder_run	December 25, 2024 at 1:56 PM
estimated_db_size	1429.72 MiB
database_engine	sqlite
database_version	3.45.3

Sonoff

version	3.8.1 (ffa7e22)
cloud_online	0 / 2
local_online	2 / 2

Example YAML snippet

No response

Anything in the logs that might be useful for us?

There wasn't any error related to MSL1 in the logs

Additional information

Core
2024.12.5
Supervisor
2024.12.0
Operating System
14.1
Frontend
20241127.8