Matter Woes with a Nanoleaf A19 | Home Assistant | Page 1

spice wren Aug 23, 2024, 1:17 AM

#

Logs:

#

... Oh, I can't attach files.

#

Okay, here's a snippet of an error I'm seeing. Unsure if related:

[32m2024-08-22 19:35:25.406[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.EM][0m [31mFailed to Send CHIP MessageCounter:28433952 on exchange 28577i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4[0m
[32m2024-08-22 19:35:28.935[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.SC][0m [31mCASESession timed out while waiting for a response from the peer. Current state was 4[0m
[32m2024-08-22 19:35:39.525[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.EM][0m [31mFailed to Send CHIP MessageCounter:28433953 on exchange 28578i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4[0m
[32m2024-08-22 19:35:42.209[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.SC][0m [31mCASESession timed out while waiting for a response from the peer. Current state was 4[0m
[32m2024-08-22 19:35:52.127[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.EM][0m [31mFailed to Send CHIP MessageCounter:28433954 on exchange 28579i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4[0m
[32m2024-08-22 19:35:55.483[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.SC][0m [31mCASESession timed out while waiting for a response from the peer. Current state was 4[0m
[32m2024-08-22 19:36:05.431[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.EM][0m [31mFailed to Send CHIP MessageCounter:28433955 on exchange 28580i with Node: <0000000000000000, 0> sendCount: 4 max retries: 4[0m
[32m2024-08-22 19:36:08.755[0m (Dummy-2) [1;30mCHIP_ERROR[0m [34m[chip.native.SC][0m ```

#

Looking at some of the other messages in this channel, I'm seeing some similarities.

#

Restarting the device fixes the issue temporarily, then it drops out again.

spice wren Aug 23, 2024, 2:46 AM

#

Could some of this be indicative of a border router out of range?

upper zephyr Aug 23, 2024, 3:10 AM

#

what firmware is the bulb on? Make sure to use the Nanoleaf app to update the firmware before adding the bulb to HA

spice wren Aug 23, 2024, 3:10 AM

#

Updated it after adding to HA

#

It is on latest now.

upper zephyr Aug 23, 2024, 3:10 AM

#

the errors you pasted look a lot like a known bug in an older firmware when multi-admin is enabled.

#

but shouldn't be happening any more with the current firmware

spice wren Aug 23, 2024, 3:11 AM

#

I can look into this tomorrow, appreciate the response.

#

Would you recommend a factory reset and recommission?

upper zephyr Aug 23, 2024, 3:13 AM

#

wouldn't hurt, but shouldn't be needed. could try doing a re-interview first. (that's located in the three dot menu in the top left box on the device page)

spice wren Aug 23, 2024, 3:14 AM

#

Just did.

#

Will monitor this.

#

I should note that this device is a fair bit away from where I have the Skyconnect located, which I thought is the culprit. I'm getting a set of Lines, which will hopefully help this out.

#

That I can probably just solve by adding more devices into the network to create a better mesh.

#

Would I get these errors if the device was out of range?

upper zephyr Aug 23, 2024, 3:17 AM

#

it's possible, especially if it only happens sometimes (which could be due to interference from other things like wifi or microwave ovens)

#

the lines act as a thread border router, but should also relay messages i think. I'm not sure whether/how to get them to join an existing thread network tho. It's possible that the Nanoleaf app might let you do that, if it can see your existing thread network.

spice wren Aug 23, 2024, 3:19 AM

#

It can.

#

I can view the Thread network the bulb is enrolled in.

upper zephyr Aug 23, 2024, 3:22 AM

#

note that a quirk of the networking setup if you're using skyconnect via the haos otbr add-on is that messages sent from ha to the thread network will always be sent via the skyconnect, and it'll rely on relaying messages over the thread network to reach out of range stuff. It won't use external thread border routers for outgoing messages.

#

(handling of multiple thread border routers from different vendors is hopefully something that will improve in future thread revisions)

spice wren Aug 23, 2024, 3:24 AM

#

That is, it won't use the new border router for sending out messages directly, but OTBR will start at the Skyconnect -> NL Border Router -> etc. ?

#

Or will it just not use the new border router

upper zephyr Aug 23, 2024, 3:29 AM

#

i think the NL border router will act as a routing device at the thread level, so skyconnect -> lines -> bulb should work.

#Matter Woes with a Nanoleaf A19