#Nanoleaf Essentials beta firmware updates

1 messages · Page 1 of 1 (latest)

vapid moss
#

Let’s discuss everything about Nanoleaf Essentials beta firmware updates in this thread. Thanks

sand shell
#

No update forcing ExecuteIfOff 🥲

ashen slate
#

Updated my A19 to 3.6.70. Still package drops while controlling the lamp and occasional package drop every now and then, but things seem to generally work fine 👍

obtuse mural
sand shell
obtuse mural
#

Unless I misread

sand shell
#

"This discrepancy is possibly due to the ExecuteIfOff Options field being set differently between us and Yeelight. That field is up to the vendor. The behaviour of ExecuteIfOff being set to 0 is that if a device receives Color Change -> Power, Color Change will simply not occur and then Power will be executed. Notably ExecuteIfOff is a default set by the vendor, but a Matter admin can provide a OptionsMask and OptionsOverride that can change this behaviour to optimize for the way in which the Matter admin sends commands. I don't think I've seen a single admin make use of these fields yet."

In this case nanoleaf is the vendor, no? Or is the vendor HA and I'm not understanding?

obtuse mural
#

Im not sure didn’t seem very clear

#

He said they haven’t seen a single admin make use of these fields yet so im assuming that means no?

nova vine
#

Awesome just updated.

#

Only issue I've been experiencing so far was that randomly turning light on in the middle of the night just one of five devices are doing it hopefully the 3.6.70 fixes that ( if NL is the cause of this).

sand shell
nova vine
#

I don't know what's going on at the packet level I'm sure there's other stuff going on but from a user perspective so far this has been really awesome

obtuse mural
tacit leaf
#

I finally got all of my bulbs updated. I'm still seeing timeout errors in the matter server logs on HA. I'm only seeing some schema errors which I don't remember seeing before.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/chip/clusters/Attribute.py", line 150, in init
raise KeyError(f"No Schema found for Attribute {Path}")
KeyError: 'No Schema found for Attribute 1/291175681/291110913'

#

The Bluetooth connection when controlling the bulbs seems to have a quicker response time though

sand shell
#

That's fine, it's related to a custom schema that the HA sdk doesn't understand

vapid moss
#

I updated 11 of my bulbs to the current beta firmware. That’s my current Nanoleaf setup:

5 GU10
6 A19 (E27)

Update procedure was without issues. It took one hour to update one bulb after the other.

I restarted my two AppleTV TBRs to start clean. This was one hour ago. I still see unavailable messages. But maybe my Thread network is still in the meshing process. I also have 35 EVE devices (22 Matter, 13 HomeKit over Thread).

I will give it some more time.

sand shell
#

That seems like an excessive amount of time to update

#

I only have 3 devices but it only took maybe 5 min

nova vine
#

Interesting one of my a19s just randomly turned on

#

This is the second device that's doing this

ashen slate
#

These deviecs have a default state right? So this is probably a device reset then? 🤔

vapid moss
#

Yes, I also recognized that 2 of my bulbs switched on randomly with the current beta firmware installed.

vapid moss
nova vine
#

Sorry not sure if you're comment was directed towards me do you think resetting the device might fix the randomly turning on issue?

vapid moss
nova vine
#

Updating a device for me takes up to 1 minute/device but I'm near the device when I'm doing it and using the nanoleaf app android phone

ashen slate
nova vine
#

OK I can try that, thanks

vapid moss
ashen slate
#

Actually probably a good thing to have them go on by default so you can confirm that the firmware still has issues 😅

vapid moss
nova vine
#

I have 3 A19 bulbs, and 2 LED strips. 7 border routers

vapid moss
vapid moss
sand shell
#

I've got 4 BRs

sand shell
ashen slate
#

There are also drops (sequence interrupts) in regular operation at times. But usually just 1. I guess a reset will be more than one.

sonic lichen
#

How do you find and install the beta firmware?

nova vine
sand shell
obtuse mural
obtuse mural
nova vine
#

Okay it seems I'm not an isolated case so I'm just going to post this observation in the nanoleaf beta forum I already did but for the new firmware

sand shell
#

With the lights turning on, does it turn on to a default state or to the previous state?

obtuse mural
nova vine
nova vine
obtuse mural
#

The main issues is mDNS errors

nova vine
obtuse mural
#

I restarted my router like 5 times and nothing fixed. Im like wtf? I restarted my switch and it started to fix some things

sand shell
obtuse mural
#

You know I have a bunch of mDNS errors that happened before I left my house for break and I for the life of me could not figure it out again. I suppose I should try to shut everything off so it can flush the system. BUT, I have been running the skyconnect on OTBR firmware. I have it tied to my apple home dataset and its perfecto!

#

So I have the system working on my apple home side via the apple border routers. There is mDNS errors in HA but I just fix that with the skyconnect and its working in HA

#

Don’t know why this janky setup but it works for me

#

You can manually flash/upload it via the Skyconnect website

nova vine
#

I have enabled power loss recovery on the lights so that'll solve the problem by putting a bandaid on it

#

😁

#

Unless it completely crashes and won't remember that setting

nova vine
obtuse mural
nova vine
#

Multipan?

obtuse mural
#

I am using just OTBR

#

SO no zigbee on that

nova vine
#

Okay then yeah you shouldn't have the same issues I was having where my Zha crashes and goes into a loop of initialization until I unplug the stick and plug it back in and that only works 80% of the time

#

So far with the new firmware I have not experienced it however it's still too early to tell victory as sometimes it can go in 8 or 9 days without crashing

obtuse mural
#

Yeah you have multipan. If you do not care for zigbee I would try the one I linked

vapid moss
sand shell
#

I'm running a skyconnect with thread only and not having the phantom flash bangs

#

But I'm also running way fewer devices atm

vapid moss
#

It’s really hard to remember all the different setups (Apple, Google, HA or a mix of them). Do we have possibility, where we can document such things, like a signature in an old fashion forum? 😃

sand shell
#

I'd define it by the majority of devices to have (so over half Google BR would be Google?) Not sure

sonic lichen
#

Does anyone else have trouble with the Nanoleaf app listing all their bulbs twice? I think it's once for the Home Assistant paired device and once when it was separately paired by the app, which the app seems to encourage you to do. This isn't really an HA issue at all, just curious if I'm the only one affected/annoyed by this.

vapid moss
# sand shell I'd define it by the majority of devices to have (so over half Google BR would b...

Yeah, but I have a fairly big (Matter/HomeKit over Thread) network with 46 devices. Sometimes I am unsure, if I have too many Thread devices for my two AppleTV Thread Border Routers. Even though I don’t believe so, who knows. I have 36 Nanoleaf Matter bulbs, most of them lying around. Today I tried to get 16 of them to work, but it was really unstable. So I reduced the bulbs to 11. After that Nanoleaf launched the new beta firmware. Now I have it installed, but it all takes time…

Where do need to differentiate? Thread Border Router or devices vendors/models that are in the mix. My EVE devices are stable, at least when no Nanoleaf bulbs are paired… 😂

vapid moss
sonic lichen
# vapid moss Where does the app list them twice? I do not have this issue. My bulbs are paire...

I've been through pair and reset cycles many times, and every time they end up appearing twice in the nanoleaf app when it's done. I always reset the bulb first (on/off x5), pair with HA, then pair with Nanoleaf. The most recent time I didn't pair one of the bulbs in the app, and that one is only displayed once. It seems to be the pairing with the app afterward that makes it get listed twice. It seems to have trouble de-duping the devices.

vapid moss
sonic lichen
# vapid moss I am unsure, if this behavior has something to do with Nanoleafs bulbs firmware....

I am using iOS. I have never paired with Apple Home, I was expecting the bulbs to come via my HomeKit Bridge integration. Actually from reading the Nanoleaf docs it sounded like I had to pick an ecosystem to pair to and it would only support one. I actually thought that the Matter spec required support for 5, but the docs seemed pretty clear that things wouldn't work trying to pair if the device was already paired to any controller.

When I pair in the HA app, the device shows up as a paired matter device in my iOS settings. I didn't do anything specific to make that happen, and don't know how to make it stop.

If I pair with the Nanoleaf app and then HA, the HA pairing will fail. This seems to be very dependable behavior.

That one bulb that I hadn't paired wit the app last time... i tried to change a scene on it, and it said it needed to be paired with the app to continue. I did that, and I immediately see two of the device. And their state isn't even the same.

#

And now I've lost the ability to control the bulb in HA. Awesome. Was not worth the experiment. Now I have to purge and re-pair it again. There's an hour of my life I'll never get back.

vapid moss
#

As already said, my 11 Nanoleaf bulbs are paired to Apple Home, Home Assistant and the Nanoleaf app. So, where do you find this docs?

Yes, it’s normal that you see the bulb in the iOS settings > general > Matter accessories. If you pair a Matter devices to two or more fabrics you can see the connected services there and delete them from one or more services their. Did you try to pair it to Apple Home first, then HA and then to the Nanoleaf app? If not try that.

  1. Delete your bulb from the iOS settings > general > Matter accessories
  2. Check, if it’s really deleted from all fabrics and from the Nanoleaf app, if not delete it there, too
  3. Factory reset your bulb (switching on/off 5 times until it flashes red)
  4. Pair to Apple Home
  5. Share with Home Assistant from Apple Home
  6. Pair to Nanoleaf app
sonic lichen
#

I think the doc I read was poorly worded and didn't really mean there could only be one ecosystem paired. I can't find the doc at the moment, but I just ran across it again last week when trying to figure out how to get my second app entries to go away. Their support content is... mediocre at best.

If adding apple home to the mix really fixes anything then I'd argue that is its own problem. What if I didn't actually want to use Apple Home for anything?

I do see in this page that it says to pair with the Nanoleaf app first rather than second. I've done that in the past though, and it didn't ever let me pair with HA at that point.

I will try repairing everything tonight in the order proposed. I'm tempted to pair the Nanoleaf app first though since it explicitly says to do that, but I'll try Apple Home first anyway. I'd just really like my bulbs to show up exactly once. I'd also like them to always work, but that's another issue I think.

sonic lichen
#

It seems that the bulb needs to be off for 30 seconds to re-enable pairing mode. Resetting the bulb doesn't seem to do it, you really have to power it down for 30 seconds. This might be one of the reasons these bulbs have been so excrutiating for me to configure in the past. I only discovered it because I found a new screen in the app stating this when I paired it with the nanoleaf app first. I can't get it to pair with Apple Home at all, though I tried before I discovered this 30 second thing.

#

I really hate these bulbs. I managed to pair it now with Nanoleaf and Apple, but can't get it to pair with HA. It just keeps failing to connect.

vapid moss
#

For me only the following pairing works:

Apple Home
Home Assistant
Nanoleaf App

Did you try that?

With this method it’s at least possible for me to pair it to to all 3 fabrics (The Nanoleaf app is not a fabric, it communicates with a proprietary protocol with the bulbs).

I also have problems to pair/share it from Apple Home with Home Assistant. It needs some tries. But this seems to be a common issue at the moment. Maybe it’s related to Home Assistant Matter (over Thread) and not directly related to Nanoleaf. We don’t know.

sonic lichen
#

I couldn't pair with Apple Home first at all. It just fails every time.

vapid moss
#

For me it seems to work for 3 hours without major instabilities with my 46 Thread devices. At least I don't see 'unavailable' logs in Home Assistant. That is already a big milestone. 😄

I have 3 GU10 bulbs in a not so much used room. One bulb switched 'on' by its own without me doing anything. So I switched it 'off' via Home Assistant. Shortly after that, it got unavailable.

8:42:05 PM - I rebooted all my Thread Border Routers (2 hardwired Apple TV 4K 3rd Gen)
8:43:55 PM - Home Assistant found the bulb via mDNS
8:49:34 PM - the bulb turned 'on' on its own
11:54:11 PM - I reconized that the bulb is on and switched it 'off' by the Home Assistant app
11:57:46 PM - the bulb 'became unavailable'
11:58:26 PM - Home Assistant found the bulb via mDNS

Here is a screenshot: https://imgur.com/a/u8WfW04

sand shell
vapid moss
#

When I go to 'Log" in the Matter server addon. I see a lot of 'ERROR Timeout waiting for mDNS resolution.' for the bulbs I have paired to Home Assistant, but not on current at the moment. The log at this place starts at 2023-12-19 00:01:14.

Where do I find the logs for the day?

#

Another thing that I rcognized today in my logfiles:

2023-12-19 00:08:44 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
2023-12-19 00:08:58 core-matter-server chip.DIS[210] ERROR OperationalSessionSetup[1:000000000000002E]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout

000000000000002E is a Nanoleaf data corpse of an incomplete pairing/sharing procedure from Apple Home to Home Assistant. I saw the message that the device is added to HA, but after that I got a message that it couldn't be paired to Home Assistant (I don't know the exact wording. I need to work more with the logs, now where Nanoleaf wants to solve their firmware issues.

How can I remove this node entry from my devices, when I don't see it in the Matter integration?

sand shell
#

That's the extent of the logs sadly lol

vapid moss
# sand shell That's the extent of the logs sadly lol

It seems to be possible to change that behavior for the system logs using the parameter 'max_entries': https://www.home-assistant.io/integrations/system_log/

This is not exactly what I need. I need log files for at least one day, better 2 or 3 days and only for the Matter server, not the complete system. I am not looking at the log the whole day and at the moment I am not willing to unpair the bulbs that fill my logs with mDNS resolution timeouts. It was a hassle to get these bulbs paired to HA. 😉

@ashen slate Any idea how to accomplish this? Marcel seems to be on vacation already. 🙂

sand shell
#

@vapid moss so what's your total number of bulbs running on the beta?

ashen slate
#

FWIW, Marcel is still around, he was traveling today 😅

sand shell
#

Wish I knew about the logs thing earlier

#

Sometimes it's so hard to catch stuff in the matter logs

ashen slate
#

Yeah we want to bring this also the frontend. There is also a continous mode (-f for follow)

vapid moss
# sand shell <@1005545243824885782> so what's your total number of bulbs running on the beta?

First try with 3.6.54 was with 8 bulbs. It looked promising. After 24 hours no disconnects at all. So I it paired 8 bulbs more, but that ended in a disaster. All Thread devices (round about 50) were in a constant re-meshing procedure. Shutting down all TBRs for some minutes didn’t help to solve this.

So I decided to decrease the number of bulbs from 16 to 11 today. Directly after I exchanged the bulbs, the new firmware 3.6.70 was released. I didn’t test it again with the old firmware and updated all bulbs. Now it seems to be stable with 11 bulbs.

sand shell
vapid moss
sand shell
vapid moss
vapid moss
vapid moss
#

I just happened to see that apparently one of the bulbs I disconnected from current today is not up to date, but still on firmware 3.2.0 according to the Nanoleaf app:

https://imgur.com/a/P3WCUEP

Maybe the firmware version doesn't match reality, because I'm sure I updated all the bulbs before I paired them with Apple Home and HA. But that might describe the constant re-meshing when I had 16 bulbs connected. I will check that tomorrow in the evening. Now I want to see that it works at least 24hours without major issues.

nova vine
#

Anybody catch this automatic random light turning on in the logs? It sounds like the firmware is crashing and just restarting

sand shell
ashen slate
#

I run into it as well, the lamp was on in the morning

#

Nothing really in the logs 😢

vapid moss
# ashen slate The logs are stored in systemd-journald on the OS side. The `ha host logs` gaine...

Thanks for this command. It works perfectly fine. I had another light going on:

https://imgur.com/a/HPWC1La

and IMO there is nothing relevant in the log for that time slot:

Dec 19 11:48:48 homeassistant addon_core_matter_server[414]: 2023-12-19 12:48:48 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
Dec 19 11:49:02 homeassistant addon_core_matter_server[414]: 2023-12-19 12:49:02 core-matter-server chip.DIS[210] ERROR OperationalSessionSetup[1:0000000000000040]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
Dec 19 11:49:02 homeassistant addon_core_matter_server[414]: 2023-12-19 12:49:02 core-matter-server matter_server.server.device_controller[210] WARNING Unable to subscribe to Node 64 as it is unavailable, will retry later in the background.
Dec 19 11:49:33 homeassistant addon_core_matter_server[414]: 2023-12-19 12:49:33 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
Dec 19 11:49:47 homeassistant addon_core_matter_server[414]: 2023-12-19 12:49:47 core-matter-server chip.DIS[210] ERROR OperationalSessionSetup[1:000000000000004E]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
Dec 19 11:50:18 homeassistant addon_core_matter_server[414]: 2023-12-19 12:50:18 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.

The following fabric ids (is that theright name?) are bulbs that I removed from current:

0000000000000041
0000000000000040
000000000000004E
000000000000004C

So, these mDNS issues are expected.

But what is with this?

WARNING Unable to subscribe to Node 64 as it is unavailable, will retry later in the background.

How can I determine, which of my devices is Node 64?

#

Is normal that syslog is 1 hour behind? Does it have something to with the timezone I am living in?

I am from Germany. That is UTC+1

Here is the syslog block from one hour later, but it's nearly the same result In this case Node 46.

Dec 19 12:48:50 homeassistant addon_core_matter_server[414]: 2023-12-19 13:48:50 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
Dec 19 12:49:04 homeassistant addon_core_matter_server[414]: 2023-12-19 13:49:04 core-matter-server chip.DIS[210] ERROR OperationalSessionSetup[1:000000000000002E]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
Dec 19 12:49:04 homeassistant addon_core_matter_server[414]: 2023-12-19 13:49:04 core-matter-server matter_server.server.device_controller[210] WARNING Unable to interview Node 46, will retry later in the background.
Dec 19 12:49:35 homeassistant addon_core_matter_server[414]: 2023-12-19 13:49:35 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
Dec 19 12:49:49 homeassistant addon_core_matter_server[414]: 2023-12-19 13:49:49 core-matter-server chip.DIS[210] ERROR OperationalSessionSetup[1:0000000000000041]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
Dec 19 12:50:20 homeassistant addon_core_matter_server[414]: 2023-12-19 13:50:20 core-matter-server chip.DIS[210] ERROR Timeout waiting for mDNS resolution.
#

Is there a way to disable the bulbs that are currently removed from power to stop that mDNS timeout logging?

nova vine
ashen slate
#

(note that you'll have to convert hex to decimal)

vapid moss
#

While looking through my logs and checking the fabric ids, I recognized that there is one fabric device id, that I do not see as a device in the Matter intergration web interface:

2023-12-18 16:33:13 core-matter-server chip.DIS[287] ERROR OperationalSessionSetup[1:000000000000002E]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2023-12-18 16:33:13 core-matter-server matter_server.server.device_controller[287] WARNING Unable to interview Node 46, will retry later in the background.

What can I do to remove this device from the Matter device database?

Some of my pairing Nanoleaf bulbs went wrong. I saw the message on iOS that its added to Home Assistant, but immediately after that got a message, that the bulb could be paired. So it's definitely a data corps.

ashen slate
#

Decimal 64 is 0x40 in hex, so the one lookup timeout then leads to the subscribtion issue.

ashen slate
nova vine
#

Oh no lol

vapid moss
sand shell
#

FWIW I've still not had the nanoleaf late night flashbang yet, but I'm going to try to add more bulbs today. I've got about 7 that I've left offline

vapid moss
#

With 'late night flashbang' you mean a bulb switching 'on' late at night? You are crazy! You installed these bulbs in your sleeping room? 😉

#

And by the way... My setup works stable so far, no unavailable messages and no re-meshing. That's definitely my personal Nanoleaf record. 😄 But I'm still a bit unsure when I'll start putting more bulbs back into operation.

#

I have 25 left offline... I am also crazy... 😄

ashen slate
# vapid moss OK, great. So my Nanoleaf data corps node id 46 is 2E in HEX. The two log lines ...

For me, sometimes devices reappeared after restarting the Core. But if Core restart doesn't show that device, and you are sure that 0x2e/46 is really not a node which is known/shown by Core, then it might be a stale node only known to the Server. I've discussed that just recently with Marcel, we'll introduce a way to cleanup them eventually.

For now the only way to clean those is to manually delete them from the server side storage (which is PITA).

sand shell
vapid moss
# ashen slate For me, sometimes devices reappeared after restarting the Core. But if Core rest...

Ok, thanks for the explanation.

I also saw that happen in the past, that bulbs failed to pair, came up after a HAOS reboot.

I already rebooted my HAOS yesterday, after doing all the Nanoleaf firmware updates to have a clean environment. I am unsure, if this really helps, but when diagnosing mDNS via an mDNS browser, I recognized that there are some entries for devices, that do not exist, because they failed to pair. There is definitely an issue with Apple Thread Border Routers. These entries never go away, unless you remove all your Apple Thread Border Routers from current at the same time (Maybe rebooting one after the other works, too. Never analyzed that.). Only that way, you can clean your mDNS service.

Good to know that you and Marcel already discussed that. Should I open a Github issue? Thanks again

vapid moss
vapid moss
ashen slate
vapid moss
sand shell
#

For those of you with the problems with the flash bang lights, I'm able to trigger the behavior by simply force closing the nanoleaf app, then opening it.

Wait a few seconds and see if your bulbs crash

If not force close and open again. Usually doing this 2-3 times max will trigger a bulb to crash for me

#

edit: you don't need to even wait. open (wait till you see dashboard), force close, open -- bulbs always crash when I do that

vapid moss
vapid moss
#

When I woke up today, I had 4 unavailable devices in Apple Home and Home Assistant:

  • 2 Nanoleaf Essentials (A19 E27)
  • 2 EVE Thermos

The first bulb came back after removing from current. But the second bulb did not. So I removed the batteries from my EVE Thermos. Both EVE Thermos also came back immediately. After that I removed the bulb from current again. This time it worked. I think that bulb was in the Thread Router (Mesh Extender) role and the EVE Thermos were connected to it.

So I had a stable uptime of 1day and 6hours with my 11 Nanoleaf bulbs.

Yesterday evening I enabled the Power Loss Recovery (PLR) setting for all my bulbs. Now I am unsure, if there is a dependency (at least when it happens on its own, not by force closing the Nanoleaf app):

  • PLR disabled: state change after bulb crash to ’on‘
  • PLR enabled: state change after bulb crash to ’unavailable‘

What do think about it?

sand shell
#

Yes force closing the NL app isn't the actual problem but it's related to the root problem of the bulbs still crashing. The purpose of mentioning the app triggering the crash is so that NL can hopefully gather some info by triggering the problem on demand

vapid moss
#

The next bulb became unavailable 1 hour ago. Removing from current worked, the current beta firmware is not ready for production…

sand shell
#

Yeah it seems if they go down and they are on 3.6.70, then if you cut and restore power, then on the next checkin from the matter server they reconnect

#

Which is an improvement over the current firmware where they never reconnect 🙂

vapid moss
#

Yes, true words, but still not ready for production. I do not have any real light switch. The bulb are always on current. My living room lamp is surrounded by a closed shade. 😂

sand shell
#

Yeah fair enough. I ordered some switches that are always powered and just have a smart bulb mode and I'm really worried about using them

vapid moss
#

@sand shell Can you have a look the log from a bulb that was unavailable today in the morning, please?

https://pastebin.com/R8vAN6bN

We are talking about the following device:

0000000000000049 > node id 73

The mDNS timeouts you see in the log are from Nanoleaf devices, that I removed from current recently to get my Thread network more stable. So don't be surprised. 😉

Do you see anything special? Thanks

vapid moss
sand shell
vapid moss
sand shell
#

What you're seeing in the logs is the server trying to reestablish connection but it can't

vapid moss
#

OK, I only wanted to be sure that I understood it right. Thanks 😉

sand shell
#

3.6.79 is out

ashen slate
#

The pace of their updates is impressive, I must admit 💪

subtle blaze
#

Only time will tell how reliable it is 🙃

vast copper
#

updating now 20 bulbs to new version, we will see xD

vast copper
#

anyone tried already? i will be stuck updating the next 2 hours 😛

vapid moss
#

My 11 bulbs are updated. Procedure was without issues, no remeshing, no instabilities. At the moment everything works fine.

subtle blaze
#

Don’t jinx it 😝

vapid moss
#

Yes, I know it’s to early to say anything about reliability. 😃

sand shell
#

.79 decimated my mesh and knocked all my bulbs offline

#

Did remesh and come back pretty quick though

vast copper
#

Sat Dec 23 00:16:46 2023 daemon.info dnsmasq-dhcp[5109]: DHCPACK(br-lan) 192.168.1.234 c0:95:6d:53:14:b5 Wohnzimmer-2
Sat Dec 23 00:17:04 2023 daemon.info dnsmasq-dhcp[5109]: DHCPREQUEST(br-lan) 192.168.1.234 c0:95:6d:53:14:b5
Sat Dec 23 00:17:04 2023 daemon.info dnsmasq-dhcp[5109]: DHCPACK(br-lan) 192.168.1.234 c0:95:6d:53:14:b5 Wohnzimmer-2

#

i get that one every some seconds on my router, thats my homepod. its normal?

#

f**k off, its still so inconsistent.. it really fucks me up...

#

i can see in homeassistant how my bulb switches are going grey and come back go grey and so on..

#

havent had thats problem befor in installed the matter downlights

vapid moss
#

My Thread network was re-meshing the whole night and still does it.

Not only the updated Nanoleafs, all EVE devices become unavailable and get back to its latest state, some devices do this every minute, some every 10 minutes, it varies. In Apple Home it doesn’t look as dramatic as Home Assistant, but I also see devices coming online and going offline.

I already did the following:

  • rebooted my 2 Thread Border Routers > 1,5 hours later it was still re-meshing
  • removed my 2 Thread Border Routers from current > 1 hour later it was still re-meshing
  • reduced my Nanoleaf bulbs from 11 to 9 > it doesn’t stabilize the situation

I think the next step is to remove more or all of the bulbs from my Thread network and download/analyze the Matter logfile.

sand shell
#

Mine seems to be a bit more settled

#

Looks like it was more on the thread end than the matter end

# 
otbr-agent[183]: [ERR ]-MDNS----: Failed to register service Nanoleaf A19 33D-7E3A._ltpdu._udp: Name Conflict
rose fox
#

So I also have matter wifi devices going on and off line now

#

That were previously stable

subtle blaze
#

Logs?

ashen slate
rose fox
#

As well as the Eve and Nanoleaf devices

#

@subtle blaze will send here shortly

subtle blaze
#

Okie

sand shell
#

Yeah I actually just found that repo for the first time this morning. It was something that Marcel has suspected led to the device crashing -- running two protocols

rose fox
# rose fox That were previously stable

Ok I take it back. I have two Matter Wifi devices that aren't responding, but they are consistently not responding in Home Assistant (for 48 hours) - so nothing to do with teh other issues

#

My situation sounds a lot like @vapid moss

sand shell
rose fox
#

No i am saying that's a separate issue - the main issue is the Nanoleaf and Eve Thread devices constantly coming on and off line

#

They are staying off-line which has happened once before - and I had to reset the two bulbs and add them back

#

trying to paste in my logs as a file

subtle blaze
#

What Nanoleaf device? Any wifi ones?

#

Like the shapes etc

rose fox
#

Currently have 2 Nanoleaf A19 Matter devices (more I removed from before when we were consistently having issues). I'm on the beta firmware for Nanoleaf

#

.79 or whatever the release was yesterday

#

although this started a few days ago i think

#

2023-12-23 09:43:26 core-matter-server root[215] INFO Re-subscription succeeded!
2023-12-23 09:43:26 core-matter-server matter_server.server.device_controller.[node 55][215] INFO Re-Subscription succeeded
2023-12-23 09:43:26 core-matter-server root[215] INFO Re-subscription succeeded!
2023-12-23 09:43:26 core-matter-server matter_server.server.device_controller.[node 46][215] INFO Re-Subscription succeeded
2023-12-23 09:43:27 core-matter-server chip.DMG[215] ERROR Subscription Liveness timeout with SubscriptionID = 0x5da6d649, Peer = 01:0000000000000033
2023-12-23 09:43:27 core-matter-server matter_server.server.device_controller.[node 51][215] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2023-12-23 09:43:27 core-matter-server chip.DMG[215] ERROR Subscription Liveness timeout with SubscriptionID = 0x889f892b, Peer = 01:000000000000002D
2023-12-23 09:43:27 core-matter-server matter_server.server.device_controller.[node 45][215] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2023-12-23 09:43:28 core-matter-server root[215] INFO Re-subscription succeeded!
2023-12-23 09:43:28 core-matter-server matter_server.server.device_controller.[node 57][215] INFO Re-Subscription succeeded

#

just a whole lot of that - along with the schema errors that don't matter

sand shell
#

What sort of BRs do you have?

rose fox
#

About 12 or so AppleTVs and HomePods

#

Was stable on the first version of the Nanoleaf beta firmware for the first time

#

Then sometime over the last few days became unstable

sand shell
#

Okay just collecting some information so we can post it in the beta discord

rose fox
#

Oh yeah I could post there too

#

Been following the threads

#

And thanks

subtle blaze
sand shell
subtle blaze
#

Cheers

sand shell
#

I added commissioned a few more bulbs on the .79 firmware and had a really difficult time

#

I have 15 deployed now to see if it's actually as stable as NL claims

vapid moss
# rose fox As well as the Eve and Nanoleaf devices

Since when are you in that situation that your devices are going on and offline?

I still see it, even though all Nanoleaf bulbs are removed. In the morning I did the following in hope it gets better:

  1. removed more bulbs (I had 6 of my 11 on current)
  2. rebooted my TBRs
  3. 1 hour later, the same situation, everything is re-meshing
  4. removed all Nanoleafs from current
  5. rebooted my complete house (switched the main fuse on and off) Maybe a bit overkill, but I didn’t have much time, was not at home the whole day. 😃
  6. all devices connected to my TBRs and are absolutely stable in Apple Home
  7. startet Home Assistant (this is round about 8 hours ago), everything goes on and offline. Never was in such a situation.

The issue seems not to be related to the Nanoleaf beta firmware, because I do not have any bulbs connected, everything is freshly restarted and all devices are rockstable in Apple Home. Only Home Assistant got crazy. I am unsure, when I find the time to download the log files.

Any idea without logs?

rose fox
#

Ok I was suspecting the same thing - I think it’s been a few days for me - I run the dev version of both HA yellow for HAOS and HA itself

#

So maybe it’s something there

vapid moss
#

I run all the general available versions.

#

I saw something similar some weeks ago, when I was on vacation and updated the Matter server from 4.x to 5.x to get the EVE energy monitoring. All EVE Energies went crazy by going on and offline. I decided to reboot my HAOS and after the reboot it was not solved. But it automagically solved over night. Maybe it has something to with it.

#

The last days with some Nanoleafs connected I recognized that my EVE Energies nowadays are always the last devices that are available after a reboot. While all battery powered EVE Thread and Nanoleaf devices were already available, the EVE Energies needed it’s time to get available.

sand shell
#

I had to remove all my bulbs from the nanoleaf app to get any stability

#

Even then a few bulbs I had to reset multiple times

vapid moss
#

Ok, I am starting slowly to add my Nanoleafs back to my Thread network, now where my general issue with the help of @frozen fiber is solved. I used Matter beta addon and didn’t recognize it…

I added 4 bulbs for now. Merry Christmas!

vapid moss
#

I am back in the game.

I have 11 bulbs active in my Thread network now. I didn’t need any special rituals. The only thing I did was giving current to my bulbs.

Now, I am going to wait until Christmas is over before playing with more bulbs… 🤪

nova vine
#

Noticing elevated cpu usage with matter today

#

About 15 to 20 %

#

Not sure if it's related to NL beta

vapid moss
#

Hi, neraly 24 hours of HA uptime later, I brought 3 more bulbs to current. The bulbs were already paired. All bulbs are working as expected in Apple Home, but only one bulb came back to Home Assistant. Here is the log for the 3 bulbs:

  • bulb 1: fabric node id 000000000000003F (hex) node id 63 (decimal)
  • bulb 2: fabric node id 0000000000000040 (hex) node id 64 (decimal)
  • bulb 3: fabric node id 0000000000000041 (hex) node id 65 (decimal)

Only the first bulb (node id 63) came back to HA automatically.

Here is the log time frame for this 3 bulbs:

https://pastebin.com/jpNZW8NX

My understanding is that the bulbs should report its availability automatically.

  1. Am I right?
  2. What is this feature called?
  3. Is this a firmware bug?

I know that Home Assistant uses the SDK poll variant and that there is something better planned for the future.

What do you think about it?

sonic lichen
#

I've got two bulbs that I haven't been able to pair to either Apple Home or HA since updating to 3.6.79. They pair with the app instantly. I've reset them countless times, disconnected from power for a few hours to let them calm down (in case, you know, smart bulbs get angry at you...), nothing seems to work. Sometimes it says it can't connect to them, other times it says it's already paired to a fabric. I've tried Home first, HA first, app first, no combo seems to allow them to pair with a matter fabric.

vapid moss
sonic lichen
vapid moss
sonic lichen
# vapid moss Did you reboot all your Thread Border Routers and your HOAS?

I have restarted HAOS, but not the BRs. I can try that later today. Several of the bulbs seem to be working find with a thread connection, so it didn't occur to me to restart the entire network. I wish there were better Thread network diagnostic tools available. I can tell bascally nothing about what's going on. It's hard to even find the on-mesh IPs of the devices.

vapid moss
#

I came back from a christmas party, went into the kitchen. switched the light on, 2 of 2 bulbs were on (as expected). Left the kitchen switched the bulbs off, one of them switched off with a 2-5 seconds delay. I looked at Home Assistant and then it already became unavailable.

I have 11 Nanoleaf bulbs and 35 EVE devices in my Thread network, only the one bulb became unavailable after 2 days. I removed it from current. It took 1 hour and 15 minutes to come back online. It worked fine in Apple Home the whole time.

fabric node id 0000000000000042 (hex) node id 66 (decimal)

  • 7:47:32 PM > became unavailable
  • 9:02:46 PM > turned off (it came back)

Here is the HA Matter Log for the respective time frame. https://pastebin.com/3jY8DcWa

vapid moss
#

How many TBRs do you have and which models exactly?

sonic lichen
vapid moss
#

Ok, do not know anything about Eeros. So you do not own an Apple Home Hub?

sonic lichen
#

No, and no Google gear either

#

I do have an Apple TV 4k 2nd generation. Does that count as a Home Hub? If so then I guess I do have one. I was able to pair a single bulb to that and also to HA. Just one.

sand shell
vapid moss
vapid moss
#

I had to pair the bulbs 3 to 5 times before it was successful.

sonic lichen
# vapid moss How often did you try it?

I've tried pairing things to the Apple Home several times over the past week. Two of the bulbs I've been focusing on though can't seem to pair with anything and are intermittently reporting they are already paired to a fabric even after just resetting them. I suppose I could try resetting my office bulb again to see if I can pair it with home. That's been the second most cooperative of the bulbs.

sonic lichen
vapid moss
#

There is a method to clean your Thread network and all your mDNS entries. You have to shutdown all your TBRs for some minutes, until Apple Home app tells you that there is no Hub connected.

I don’t know the exact wording in English. I use my Apple Home App in German.

Did you try something like that?

sand shell
#

It seems the problem is within the matter controller

sonic lichen
#

I probably haven't shut them down for long enough. They're all my wifi routers, so my entire house would be without any network while I do it. My family would be... unhappy with me. Maybe I can do it late tonight.

vapid moss
sand shell
#

By looking at devices with open matter ports

vapid moss
#

Offtopic: Can you please check with the Flame app, if you find the ‘_trel._udp.‘ on your Eeros? I am really interested in that.

sand shell
#

If you have a nanoleaf BR you can also look for _ltpdu._udp

vapid moss
#

@sonic lichen How many Thread networks do you have? Is your Apple Thread network using the credentials generated by Eero?

#

Read the posts around that post.

#

When you want to have one Thread network of Eeros and Apple TBRs you need to reset your Apple Home Hubs to factory defaults, delete the Apple Thread credentials from the Keychain, write your Eero credentials to the Keychain and setup your Apple Home Hubs /TBRs again. Then Apple should use your Eero Thread credentials.

sonic lichen
#

Hmm. I hadn't thought about the fact that I might have another thread network via the Apple stuff. Let me investigate that.

vapid moss
#

Yes, AppleTV 4K 2nd Gen definitely has its own Thread radio.

sonic lichen
#

The mDNS tool is showing a ton of changes with the defined hosts. One device in particular is intermittently displaying its name as a bunch of 0's.

vapid moss
#

A Matter device gets a Matter fabric node ID for every fabric. If you use Apple Home and Home Assistant every device has 3 Matter fabric node IDs. Apple gives you 2 IDs, one for Apple Home and one for general. You do not necessarily need to pair your device to Apple Home, so you need the general ID. At least this is my understanding. 😃

vapid moss
#

Alternatively you can disable your Eero Thread network for testing purposes. After that you may have to reset your already paired devices to factory defaults. They maybe won’t work anymore, because they are paired to your Eero Thread network with your Eero Thread credentials and so do not work in your Apple Thread network.

sonic lichen
#

Using Flame, the host list on the left is reconfiguring every few seconds. It looks like something lis misreporting itself and constantly updating? Also looks like it's confusing three different devices in this set.

#

Disabling my Eero network doesn't seem like a good plan. My house is too big, the bulbs are not anywhere near the Apple TVs.

vapid moss
#

Ok, that’s definitely not normal. When I open the Flame app, everything is static. At least nothing changes constantly.

vapid moss
sonic lichen
#

I've unplugges all of my Nanoleaf devices and a Meros wifi/matter plug, that's all of my matter devices. The Flame mDNS hosts is still hopping around.

#

Let me give it a few mins to see if something TTLs away

vapid moss
#

It’s late here in Germany. Do you have any mDNS reflectors active?

sonic lichen
#

Probably no? At least I haven't done anything intentional with mDNS here.

vapid moss
#

You need to shutdown your Apple Home Hub (and maybe your Eeros) to get rid of the mDNS entries.

#

Again, please try to disable the Thread radios of your Eeros for testing purposes. You can enable them later.

#

IMO this whole Eeros thing is offtopic in this Thread. Please, create your own Thread and tag me. 😉

sonic lichen
#

Eero thread network has been disabled. I'm still seeing the host list jumping around, but it seems to be just one entry moving now where before it was a few of them.

vapid moss
sand shell
#

I'm actually doing some more reading and I think that the nanoleaf app just uses the old API from when they were homekit only and just ignores the matter socket

#

Since the NL shapes are described as border routers not matter controllers that would make sense

vapid moss
#

Did anybody here try to enable the Power Loss Recovery? I set it up for my 11 bulbs 3 times now, but the Nanoleaf app or the bulbs forget the setting. Does this work for you?

sand shell
#

Opening the app is asking for trouble on my setup so I haven't tried it

nova vine
nova vine
#

Is it me or is .79 really bad firmware? My devices don't connect to the thread Network even according to the nanoleaf app

#

Some of them have been disconnected for 7 days and the only reason why they connected is because I unplugged them and plug them back in

obtuse mural
#

Not happy with it

vapid moss
# nova vine Is it me or is .79 really bad firmware? My devices don't connect to the thread N...

My 11 Nanoleaf bulbs and my 36 EVE devices are stable. I disabled Power Loss Recovery and strictly did not touch the Nanoleaf app since one week. 3 lights switched on by itself, but all devices are still available. Sometimes when I switch the lights on or off via Home Assistant automations they do not react on the first try. But it works on the second attempt. I think that’s the moment, where the bulb crashed and it took some time to restart and get available again.

I still do not trust this Nanoleaf beta firmware, but my bulbs do not crash my complete Thread network. Until these issues are solved, I am not going to install more bulbs.

vapid moss
# obtuse mural I cannot share them to HA now. They fail every time. They are somewhat stable in...

When I had PLR enabled, some of my bulbs became unavailable in Home Assistant only and they didn’t come back without removing them from current, even after hours of waiting. But they always worked in Apple Home, even though they were unavailable in Home Assistant.

I have 16 bulbs paired to Apple Home and Home Assistant. Only 11 of them are on power at the moment, because I had big issues with 3.9.70 and all 16 bulbs on power. Maybe the issue is solved with 3.9.79, but currently I do not have the time to test again. I am afraid to make my complete Thread network unstable again. That’s not a lot of fun, with this big Thread network. 😉

So, I didn’t need to pair new bulbs to Home Assistant. I am waiting for the HA update tomorrow. There should some good fixes. I already tested the 5.1.3 Matter beta server and had issues. But that will not necessarily mean, that it doesn’t work. I was in a short analyze with Marcel. I still saw the following issue with 5.1.3:

INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...

Marcel said, that this issue should be solved with Matter 5.1.3 beta server. He was unsure, if my code was clean. So I rolled back to 5.0.3 and it’s as already said stable.

#

I am running HAOS as a Debian KVM. One week ago I gave my VM two more virtual CPUs. Before my HAOS had only two vCPUs, now it has four vCPUs. Maybe that’s related.

vast copper
#

how i force the matter-server to update? beta is enabled and auto-update is on. its still on 5.01

#

ah sorry matter addon 5.0.1 is pyton matter 5.0.3

subtle blaze
#

You have to check the logs

#

It won’t update in the UI

#

The beta should say downloading 5.1.3 (is the beta iirc)

vast copper
#

not for me im at 5.0.1 pyton 5.0.3

subtle blaze
#

In the logs?

#

So, it says nothing about 5.1.3 in the logs after maybe a minute?

sand shell
#

Yea you should be able to see the pip install in the logs

vapid moss
sand shell
#

I don't actually have the problems you guys do on the beta

vapid moss
sand shell
#

I can't add the led strip anymore

#

I know someone else mentioned having that problem

vapid moss
#

My 11 bulbs and my 36 EVE devices are still working as expected, but one bulb switched on over night. I force closed the Nanoleaf app after the latest update. Maybe that’s the reason.

sand shell
#

The bulb that turned on is on .94?

vast copper
#

why i have to repair all my bulbs to nanoleaf again...

#

there is no update fpr the downlights right?

vapid moss
subtle blaze
vast copper
vapid moss
vast copper
#

ok

#

my nano downlights do not have the beta update .94 they are still .79 without updateinfo

vast copper
#

i still have one bulb which is unable to pair to HA. i resetted the bulb many times, also restarted borders and run the latest beta. just this single one wont pair to HA, can pair it to apple every time.

#

i think its just broken i will order a new one....

ashen slate
#

You use the Apple BR in both cases?

vapid moss
vapid moss
obtuse mural
#

My new setup has been to directly pair the Nanoleaf to my Skyconnect OTBR and have everything else paired with apples thread network. This is nice since the Nanoleaf will not effect the stability of my Apple products.

#

However, I have had trouble with pairing them directly to the skyconnect. Some cases I had to reboot my HA and then Was able to pair 1 or 2 of them before running into the troubling error pairing message

#

I finally got them all paired up though

#

Also if they failed at pairing initially, then you would have to reset the bulb again. You cannot just try clicking pair again as it would not say “setting up”

vapid moss
# obtuse mural Also if they failed at pairing initially, then you would have to reset the bulb ...

If I can’t pair a Matter device (Nanoleaf bulb), I usually do the following:

  • delete the bulb in the Nanoleaf app (this typically deletes it also from Apple Home)
  • check if it’s really deleted from Apple Home (if not, delete it manually)
  • delete it from Home Assistant
  • delete it from iOS settings > matter accessories
  • reset the bulb to factory defaults (switch it 5 times on/off, until it flashes red)
  • remove it from current, wait some seconds, bring it back on current
  • pair it with Apple Home
  • pair it with Home Assistant by the code from Apple Home
  • pair it to the Nanoleaf app

If it didn’t work, I started the procedure again.

#

With the unpairable bulb I tried it again and again. It’s always the same. It’s not possible to pair it with Home Assistant anymore. I definitely had some unsuccessful pairings with Home Assistant, where I saw the popup that its added, but the device was not in the ui. And now I have this ghost. So I have the assumption that there is a relationship. But I am not sure about this idea.

vapid moss
obtuse mural
#

Yeah

vapid moss
vapid moss
obtuse mural
#

Yep I think so too

#

I just port it back in with HomeKit bridge integration

#

I think I just got the self turn on issue happen

sand shell
vapid moss
#

Yeah, one of my bulbs turned on tonight, too.

obtuse mural
ashen slate
vapid moss
vast copper
#

i still have blubs which are not paring with HA. tried everything recommended above...

#

its 2 of 4 nano downlights, before it was just 1 of them but after i reset them all 4 i have now 2 which i cant pair..

#

there is no .94 beta for them atm, tought that maybe helps

sand shell
#

Probably related to issues that got fixed in .94 -- I know for a fact the strips had problems

#

Might have to wait until it's released to down lights

ashen slate
vast copper
#

there is another method i can try?? maybe that helps preying

ashen slate
#

There is also Android (and there are some improvements pending). Not very familliar with iOS

sand shell
#

Well nanoleaf announced new essentials products but didn't announce new bulbs so they must be confident they can get them under control

vapid moss
#

Nanoleaf is hitting the ground with debugging Thread/Matter issues. They are very confident, that it’s a firmware issue and not an issue of underpowered hardware. They are close before a reliable firmware and are determined to make their Matter Essentials a reliable Full Thread Device (FTD).

So, we have to be patient. I hope that this will soon come true and really won't take much longer. 😃

Here are the respective sources for my comment written in the Nanoleaf discord by a Nanoleaf representative:

we are hitting the ground running with debugging the Thread/Matter issues that have been plaguing us.
Source: #1184371187464290344 message

We're quite confident that we're close to a jump forward in reliability and I'm happy to have all of you providing such great feedback 🙂
Source: #1184371187464290344 message

Yes, very confident.
Source: #1184371187464290344 message

We're determined to be a reliable FTD.
Source: #1184371187464290344 message

vapid moss
sand shell
vapid moss
#

Ok, thanks for sharing the link. Hm… I am not really interested in new products until they get their existing lineup reliable.

That means you can group them with your indoor lights and automate them with schedules via the Matter app

How does this work when Matter doesn’t support group scenes? 🙃

sand shell
#

Matter does support group scenes

#

It's not implemented in HA IIRC and obviously NL hasn't either

vapid moss
#

Ok, I didn’t know that. Thanks for the enlightenment