Zigbee Devices Greyed Out - “This entity is no longer being provided by the mqtt integration”

DarkKnight · September 30, 2024, 11:47pm

I have read through several similar topics about this issue and have not been able to discover the cause. MQTT Explorer shows the MQTT feed looking normal from what I can tell.

I deleted the MQTT integration and readded it, only after rebooting Zigbee2MQTT did the devices show back up, but they were still ‘unavailable’. I have tried reconfiguring the integration with both localhost & the IP of the system. Both have the same result. I tried wiping away HA and reinstalling that. After that hassle, the same result.

Everything works fine through the Z2M UI. HA Logs show no errors related to Z2M. Z2M logs have only sensor messages and a few messages related to unplugged/disconnect devices.

What is going on here?

Edit: Similar Threads that I have reviewed:

github.com/home-assistant/core

entity is no longer being provided by the mqtt integration

opened 09:43PM - 06 Feb 24 UTC

closed 11:10AM - 07 Feb 24 UTC

StCyr

needs-more-information integration: mqtt

### The problem After a reboot of my HA installation, 1 of my MQTT devise has a…ll its entities "no longer being provided by the mqtt integration" ### What version of Home Assistant Core has the issue? core-2024.1.3 ### What was the last working version of Home Assistant Core? core-2024.1.3 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue mqtt, mosquito broker, ebusd ### Link to integration documentation on our website https://www.home-assistant.io/integrations/mqtt ### Diagnostics information (shortened to fit issue's maximal body size of 65536 chars) { "home_assistant": { "installation_type": "Home Assistant Supervised", "version": "2024.1.3", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.11.6", "docker": true, "arch": "x86_64", "timezone": "Europe/Brussels", "os_name": "Linux", "os_version": "6.1.0-17-amd64", "supervisor": "2024.01.1", "host_os": "Debian GNU/Linux 12 (bookworm)", "docker_version": "25.0.2", "chassis": "desktop", "run_as_root": true }, "custom_components": {}, "integration_manifest": { "domain": "mqtt", "name": "MQTT", "codeowners": [ "@emontnemery", "@jbouwh" ], "config_flow": true, "dependencies": [ "file_upload", "http" ], "documentation": "https://www.home-assistant.io/integrations/mqtt", "iot_class": "local_push", "quality_scale": "gold", "requirements": [ "paho-mqtt==1.6.1" ], "is_built_in": true }, "data": { "connected": true, "mqtt_config": { "broker": "core-mosquitto", "port": 1883, "username": "**REDACTED**", "password": "**REDACTED**", "discovery": true }, "device": { "id": "54da48d241f17b4cc094a922a1d63652", "name": "ebusd b7v", "name_by_user": "Thermostat Vaillant", "disabled": false, "disabled_by": null, "entities": [ { "device_class": null, "disabled_by": null, "disabled": false, "entity_category": null, "entity_id": "binary_sensor.thermostat_vaillant_adaptheatcurve_yesno", "icon": null, "original_device_class": null, "original_icon": null, "state": { "entity_id": "binary_sensor.thermostat_vaillant_adaptheatcurve_yesno", "state": "unavailable", "attributes": { "restored": true, "friendly_name": "AdaptHeatCurve yesno", "supported_features": 0 }, "last_changed": "2024-02-06T20:06:29.303846+00:00", "last_updated": "2024-02-06T20:06:29.303846+00:00" }, "unit_of_measurement": null }, { "device_class": null, "disabled_by": null, "disabled": false, "entity_category": null, "entity_id": "sensor.thermostat_vaillant_z1actualroomtempdesired_tempv", "icon": null, "original_device_class": "temperature", "original_icon": null, "state": { "entity_id": "sensor.thermostat_vaillant_z1actualroomtempdesired_tempv", "state": "unavailable", "attributes": { "restored": true, "state_class": "measurement", "device_class": "temperature", "friendly_name": "z1ActualRoomTempDesired tempv", "supported_features": 0, "unit_of_measurement": "\u00b0C" }, "last_changed": "2024-02-06T20:06:29.306560+00:00", "last_updated": "2024-02-06T20:06:29.306560+00:00" }, "unit_of_measurement": "\u00b0C" }, ] }, "mqtt_debug_info": { "entities": [], "triggers": [] } } } ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt I can find mqtt messages related to that deivce in the mosquito broker addon. Example: 2024-02-06 21:50:53: Received PUBLISH from ebusd_23.2_273 (d0, q0, r0, m0, 'ebusd/b7v/z1ActualRoomTempDesired', ... (30 bytes)) 2024-02-06 21:50:53: Sending PUBLISH to ebusd_23.2_273 (d0, q0, r0, m0, 'ebusd/b7v/z1ActualRoomTempDesired', ... (30 bytes)) 2024-02-06 22:07:23: Received PUBLISH from ebusd_23.2_273 (d0, q0, r0, m0, 'ebusd/b7v/z1ActualRoomTempDesired', ... (29 bytes)) 2024-02-06 22:07:23: Sending PUBLISH to ebusd_23.2_273 (d0, q0, r0, m0, 'ebusd/b7v/z1ActualRoomTempDesired', ... (29 bytes)) 2024-02-06 22:07:23: Sending PUBLISH to mqtt-analyzer-Xxe7vFSJ (d0, q0, r0, m0, 'ebusd/b7v/z1ActualRoomTempDesired', ... (29 bytes)) ``` ### Additional information Here's a screenshot of the _z1ActualRoomTempDesired_ entity's history: ![image](https://github.com/home-assistant/core/assets/8179031/26055612-4a89-4d63-a4b4-3f834fe10964) Its latest update really dates from the moment when I reboot my system: ![image](https://github.com/home-assistant/core/assets/8179031/10158f29-9f50-4f64-8992-85ab7e27e46a)

https://www.reddit.com/r/homeassistant/comments/14pws01/upgraded_ha_now_getting_entities_no_longer/

Tinkerer · October 4, 2024, 2:11pm

What version of HA?

What version of Z2M?

What changed recently? Did you change any settings in Z2M?

DarkKnight · October 7, 2024, 3:42pm

HA 2024.9.3
Z2M: 1.40.1

I asked HA to show a hidden entity (Current use in amps) from a Zigbee device that reports this info. Doing this caused the plug to show as unavailable. I tried to delete and readd the plug, but it would not show. I deleted the MQTT integration and readded it with the same localhost:1883 settings. Nothing showed up at all. Restarted MQTT, devices show up, but are now all unavailable. Nothing I have done at all has changed this state.

I did not make any changes to Z2M or to MQTT before encountering this problem. Afterwards, I did update the images for everything.

HA MQTT debug log has only the following:

2024-10-04 18:38:58.057 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:38:58.068 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:39:58.189 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:39:58.192 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:40:58.338 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:40:58.349 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:41:58.472 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:41:58.480 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:42:58.596 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:42:58.608 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:43:58.743 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:43:58.751 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23
2024-10-04 18:44:58.886 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: register write 23
2024-10-04 18:44:58.889 DEBUG (MainThread) [homeassistant.components.mqtt.client] localhost: unregister write 23

I have searched these messages and not found anything useful.

ddaniel · October 7, 2024, 3:54pm

Maybe you just didnt enable discovery in mqtt or you have mismatch topic in z2m and mqtt

DarkKnight · October 9, 2024, 11:10pm

It was working fine before, and I hadn’t changed anything. Regardless, what should the topic settings look like in Z2M & HA?

ddaniel · October 10, 2024, 7:56am

This is how it is on my side.
mqtt integration

and zigbee2mqtt

DarkKnight · October 10, 2024, 7:01pm

The only thing that was different was the MQTT protocol version. Mine was 4, I changed it to 5, restarted Z2M, and suddenly everything worked. Only, the problem isn’t the protocol version. 4 or 5 both work fine, but only works when I soft restart Z2M after changing that setting.

If I leave it at either 4 or 5 and restart everything, it’s starts up broken. If I restart Z2M using the UI, it’s still broken. If I change the protocol and restart Z2M with the button that comes up after making that change then wait a minute or two after Z2M starts, suddenly everything works.

What is going on?

Edit: After it was working, I tried again to add ‘current’ and the whole thing broke again. This setup is about as robust as tissuepaper. I again switched the protocol version and restarted Z2M, and it came back up.

ddaniel · October 11, 2024, 6:17am

You know how they say… don’t fix it if its not broken.

DarkKnight · October 14, 2024, 12:58am

I get it, but it needs manual intervention on reboot. That’s not what I would call fixed. Maybe I can have docker compose wait until HA is up and then start Z2M. I’ll have to play with it when I have some more time.