MQTT devices not working on Lovelace after HA update

I have two Schneider Electrics shutter controller connected to my Home Assistant with Zigbee that were working correctly until I updated the HA to the core-2022.2.6 version.
Now the control buttons to move the shutter are all grayed and the automations are not running anymore.
The devices and entities are still there, the only ‘strange’ thing is that the entities status says resotred with a red exclamation mark icon.
On the Zigbee2mqtt GUI both devices appears as before and can be operated from there.
In the past I had some similar problem that was solved removing and reinstalling the Zigbee2mqtt add-on, but in this case it is not working.

Thanks

Yeah “restored” is a bad name for this. It means they were there, now they aren’t. They are “restored” as in their config has been restored/loaded from the .storage registry after a restart but the devices aren’t available.

Are there any errors in your log?

Were there any breaking changes for this integration in the release?

Thanks Tom

There are two breaking changes for MQTT but relative to light switches and climate, they should not affect my devices.
The log contains few errors but they are about google assistant:

2022-02-15 11:03:22 ERROR (MainThread) [homeassistant.components.google_assistant.http] Request for https://homegraph.googleapis.com/v1/devices:reportStateAndNotification failed: 404

2022-02-15 11:43:48 ERROR (MainThread) [homeassistant.components.google_assistant.smart_home] Unexpected error

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/components/google_assistant/smart_home.py", line 57, in _process

result = await handler(hass, data, inputs[0].get("payload"))

File "/usr/src/homeassistant/homeassistant/components/google_assistant/smart_home.py", line 213, in handle_devices_execute

execute_results = await asyncio.wait_for(

File "/usr/local/lib/python3.9/asyncio/tasks.py", line 481, in wait_for

return fut.result()

File "/usr/src/homeassistant/homeassistant/components/google_assistant/smart_home.py", line 157, in _entity_execute

await entity.execute(data, execution)

File "/usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py", line 641, in execute

await trt.execute(command, data, params, challenge)

File "/usr/src/homeassistant/homeassistant/components/google_assistant/trait.py", line 1904, in execute

await self.hass.services.async_call(

File "/usr/src/homeassistant/homeassistant/core.py", line 1577, in async_call

raise ServiceNotFound(domain, service) from None

homeassistant.exceptions.ServiceNotFound: Unable to find service cover.close_cover

2022-02-15 11:43:48 ERROR (MainThread) [homeassistant.components.google_assistant.smart_home] Error handling message {'inputs': [{'context': {'locale_country': 'US', 'locale_language': 'en'}, 'intent': 'action.devices.EXECUTE', 'payload': {'commands': [{'devices': [{'id': 'cover.kitchen_shutter'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '008e8db1ad664e08c09c2ea6c2affa5d4d326942b395a977408114d1e9979e6f10036ed2155c38a57f8ba5ee9f3fdb2cb6579eb9', 'openPercent': 0}}]}]}}], 'requestId': '2310301423882392649'}: {'errorCode': 'unknownError'}

In zigbee2mqtt, what happens if you change the name of one of the shutter controllers and turn on the update home assistant toggle (you can change it back later, just a test)?

Does it update the name of the device in home assistant?

Does it fix the issue?

Either way, you can change the name back, remembering to turn on the toggle to update home assistant.

It does not have any effect. The name remains the old one in home asssitant and the issues is still there.

And it did not create a new device with the new name?

Sounds like there is something wrong with the discovery messages zigbee2mqtt is publishing to the broker. Maybe only for these devices. Try a different type of device.

No, it does not create a new device. I see the two with the old names.

Unfortunately I don’t have other zigbee devices to test

You could open an issue here:

Thanks for your help Tom.
I will open an issue there

1 Like