Nanoleaf Canvas product stopped working with 2025.3.4

[Fatalmose]

The problem

After updating HA to core 2025.3.4 the Nanoleaf Canvas panels stopped working.
Configuration error.

Log.

home-assistant_nanoleaf_2025-03-22T09-02-14.331Z.log

What version of Home Assistant Core has the issue?

2025.3.4

What was the last working version of Home Assistant Core?

2025.3.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nanoleaf

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[Fatalmose]

Enregistreur: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:537
intégration: Home Assistant WebSocket API (documentation, problèmes)
S'est produit pour la première fois: 09:58:34 (8 occurrences)
Dernier enregistrement: 10:15:17

[281472251588336] Error handling message: Unknown error (unknown_error) Jean Sacré from 192.168.1.38 (Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.2) Mobile/HomeAssistant, like Safari)
[281471967588944] Error handling message: Unknown error (unknown_error) Jean Sacré from 192.168.1.38 (Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.2) Mobile/HomeAssistant, like Safari)
[281471831868032] Error handling message: Unknown error (unknown_error) Jean Sacré from 192.168.1.38 (Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.2) Mobile/HomeAssistant, like Safari)
[281471636861376] Error handling message: Unknown error (unknown_error) Jean Sacré from 192.168.1.38 (Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.2) Mobile/HomeAssistant, like Safari)
[281471621654864] Error handling message: Unknown error (unknown_error) Jean Sacré from 192.168.1.38 (Mozilla/5.0 (iPhone; CPU iPhone OS 18_3_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Home Assistant/2025.2 (io.robbie.HomeAssistant; build:2025.1178; iOS 18.3.2) Mobile/HomeAssistant, like Safari)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 28, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 537, in handle_manifest_list
raise int_or_exc
homeassistant.loader.IntegrationNotFound: Integration 'google_home' not found.

[joostlek]

How do you control your nanoleafs?

[Fatalmose]

I use the Nanoleaf HA integration. I have the lightpanels and 4D strip working. Only the Canvas panels stopped working giving a configuration error. Le sam. 22 mars 2025 à 10:18, Joost Lekkerkerker ***@***.***> a écrit :

…

How do you control your nanoleafs? — Reply to this email directly, view it on GitHub <#141101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGEH4FVBOR444HT5SSMVEID2VUTHLAVCNFSM6AAAAABZRVPXACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGE3DCMZYGU> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: joostlek]*joostlek* left a comment (home-assistant/core#141101) <#141101 (comment)> How do you control your nanoleafs? — Reply to this email directly, view it on GitHub <#141101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGEH4FVBOR444HT5SSMVEID2VUTHLAVCNFSM6AAAAABZRVPXACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGE3DCMZYGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Fatalmose]

I just notices that the canvas panels went offline.
This is really à coïncidence…
Just hapend after update to 2025.3.4.
So I will close down the ticket…