Software Beta for Nanoleaf Essentials Matter

[wild oracle]

to add further context, we currently represent all scenes to Apple Home. This update allows you to manage that more closely

[swift phoenix]

I haven’t installed the update or looked into it but I figured you would have the option to toggle a scene on in HA that is imported from Nanoleaf app?

[wild oracle]

Yup, so most of that is already possible, although theres no seamless “copy to ha” function. Let us know if theres something else missing

[swift phoenix]

Is that something you guys will add in the future? “Copy to HA function”

[wild oracle]

That feature in apple home is enabled by the homekit apis. Its been there since basically our first homekit products. I’m not aware of equivalent apis provided by ha

[swift phoenix]

Oh I see

I thought it was doing it through matter scenes?

Since now that is possible correct?

[wild oracle]

matter scenes is a matter specific feature that was added to Matter 1.3. I am not aware of any platforms that have adopted it. One potential advantage is you can trigger a scene without a matter hub in the middle.

Otherwise most scenes are hub driven (whether apple home hub, or home assistant)

[swift phoenix]

Maybe Nanoleaf can be the first 😉

[green frost]

Oh no no no. That's a path no vendor should ever go down.

[swift phoenix]

lol probably true

[green frost]

Nanoleaf products should work without having any third-party product involved.

[wild oracle]

This is not mutually exclusive. Matter scenes require some “admin” but otherwise allow more device to device interactions in the future. It will be interesting if/how platforms adopt it

[green frost]

I would expect Nanoleaf to provide that which is needed to work with other Nanoleaf products. Some people just want lights and don't care about home automation. I'm just one of those silly consumers that thinks the world is looking out for me. 🤣

[vital stump]

Random and super minor bug but switching away from the app stops the spinning wheel on the update screen, entertainingly screen recording starts it again. (iOS)

[ocean whale]

Anyone know if 3.6.196 is released officially? I’ve never signed up for the beta prog (didn’t even know it existed) but half my Essentials lights updated to this fw using the Home app recently, the other half are still on 3.1.173

[plain kettle]

Yeah it is

They can update via the DCL (aka using the matter OTA spec) so your home app and that can update it

[ocean whale]

Lol good, now just need to figure out how to update the rest

Updates wont show up in Home anymore and nanoleaf app just disappeared all my devices today 😂

Hopefully it autoresolves

[plain kettle]

Yeah ahahah, the new app update lost like 4 of my devices, it’s cooked

[ocean whale]

RIP. Thats why i try and never use the app!

Works seamless when I leave it to Home

[main matrix]

hmm, I wasn't under the impression 3.6.196 was released to prod (plugged in 6 other MoT Essentials lights last night, they can only see 3.6.173). That, and normally NL would update the public release notes (last entry is 3.6.173 ~3 months ago).

[plain kettle]

Ah wait @ocean whale are you in the beta for any other matter/thread product and were told to install a profile?

[ocean whale]

No, I’m a recent matter adopter

Last few weeks

Haven’t had time to look into any beta stuff

Maybe it’s a staggered rollout?

[main matrix]

well if you're not part of the beta, then in theory none of your lights should be beyond 3.6.173 in the firmware.

[plain kettle]

I’ll check the public DCL, see if it’s there

[ocean whale]

Very curious. Another thing: at the time, none of my lights were setup through the nanoleaf app. All happened through Apple Home

I just today re-setup all of them to see if I could update the rest, then they disappeared lol

[main matrix]

then Poshy's theory of updates via DCL may ring true, but can't say I've had that experience (could also be I don't use Apple at all 🤷 )

[plain kettle]

Yeah I’ll have a look when I get home from work

The DCL site is absolutely cancer to look around on mobile

[main matrix]

I've had a brief look at the DCL, but can't see anywhere specifically for updates 🤷

[ocean whale]

@plain kettle @main matrix looks like the updates on the dcl are semi random, and 3.6.196 is the newest. Wonder if it was an accidental addition since it’s not working in-app

[plain kettle]

Haha nice work! Yeah @wild oracle you wanna maybe dig into it

[ocean whale]

Now just wanna know why Home is only updating a few! 😂

[main matrix]

lmao, overlooked the drop down for the vendor info...

[green frost]

If he was, the NDA prohibits him from acknowledging so.

[plain kettle]

lmao not every company has a NDA set up for a beta program

not software beta thats for sure

eve dont, tuo dont, nanoleaf dont

[ocean whale]

Yeah, and if someone signed and was aware of an NDA, they wouldn’t be confused when a beta firmware was installed 😛 😉

[green frost]

This is the Nanoleaf Beta Essentials Matter channel. Please stay on topic. This is not a Home Assistant channel.

The other moderators will be removing off topic messages.

[safe ice]

I've upgraded my lightstrip and recessed lights to 3.6.196 and now none are reporting to HomeAssistant, nor can I readd them to HA or Google Home. The app sees the lights on the Thread network, so at least that seems to be working but the matter bit isn't. Do we need to factory reset each time we upgrade the firmware? My lights were working relatively well with .173, sad that .196 has broken it.

[wild oracle]

no, you shouldnt need to factory reset. the most obvious quick troubleshooting step you can take is to power cycle your border router(s). otherwise if you want to dig deeper, Flame browser for mac (or iOS) is very useful. if you know the device name and ID, you can find it like this:

in this example, A19 511 is a bulb in my home. Its connected to two Matter fabrics, so there are 3 entries (1x ltpdu and 2x matter)

[safe ice]

That was it! I rebooted my Nest Hub and it restarted working right away. Thanks for the quick help 🙂
Is there a tool for Windows to do the same as Flame Browser?

[wild oracle]

Not that I know. This may get you close. https://hobbyistsoftware.com/bonjourbrowser the advatage of flame is it aggregates things from the same host (although its terribly inefficient, at least on my m1 mac)

[plain kettle]

ive had pretty good luck with this

https://apps.apple.com/us/app/discovery-dns-sd-browser/id305441017

or for windows, this

https://support.apple.com/en-us/106380

it also installs the command line program DNS-SD which will let you query mdns stuff

[safe ice]

Thanks for the suggestions!

[undone spire]

I've also been given the 3.6.196 update for my 7 essentials lights and 9.6.2 update for the 4D . Became available to update today and not enrolled in the beta program.

[amber harbor]

Good luck! My four essential bulbs and single essential strip has been unresponsive in Apple Home since the update, even after two resets. Guess I will have to wait this one out.

[undone spire]

What are you using as the thread border router? Have you power cycled it?

[amber harbor]

I'm using an Apple TV 4k.
I did several troubleshooting steps, like restarts and resets, but now I can't even get the bulbs to join thread, let alone matter. I advise you to try one bulb first, and give it a week to see if it gives you any issues.

[amber harbor]

Hah. I just connected my apple tv to my router via ethernet instead of wifi, and suddenly I was able to add all my lights to both thread and matter.

[opal sparrow]

ah, that sounds like your wifi router might have been filtering out some of the required broadcast packets (for ipv6 router annoucements and mdns) that are needed for thread comissioning to work :/

[amber harbor]

My network configuration did not change and my bulbs were able to stay connected to thread longer using previous firmware versions, so it is the most likely culprit imho. 🤷‍♂️

[woven scaffold]

Since updating my HomePod mini and iPhone to the latest iOS18 Developer Beta, controlling my 4 Matter over Thread NL Down Lights（3.6.196） in Apple Home is no longer reliable, with popcorn effect and severe slowdown/stuttering when turning on/off.

[green frost]

Have you asked Apple what changes were made in that area. I have been dealing with this type of issue in Windows 11 Developer Beta and a few bugs have been found and others are caused because of intended changes.

[woven scaffold]

Apple won't reply to me 😦 I think NL's close communication with the Apple Home team will solve the problem more timely😭

Or wait until Apple's upcoming latest Matter Hub is launched, and then consider further docking and repair problems.

[tired cloak]

I still get these kind of errors:

My Setup is 5 GU10 Essentials Bulbs with up to date firmware (3.6.196) connected via Thread with a Homepod Mini (iOS 17.5). I imported the Thread Credentials of the Homepod to HomeAssistant. All bulbs are connected via Matter to AppleHome and HomeAssistant (Matter Server v6.3.1). While using the adaptive Lighting Option via HomeAssistant i get flashing lights from time to time on different bulbs. Most of the time its working fine. Can you help me?

[plain kettle]

This is a implmentation issue, iirc @opal sparrow has also been looking into this

[tired cloak]

implementation of what in what?^^

of the nanoleaf essentials to apple home? to HomeAssistant?

[plain kettle]

from what i remember, its an issue on how nanoleaf implemented one of the cluster attributes

im sure kepstin will know when he comes past 😅

[tired cloak]

ok, so something nanoleaf should fix in their firmware?

[plain kettle]

(i think from what i remember the last time this came up in the HA discor)

[opal sparrow]

I don't think I've ever seen flashing lights. I know people have reported flashing GU10 bulbs before, seems like there might be a hardware issue with some of them?

[opal sparrow]

I'd recommend opening a ticket with nanoleaf regarding the flashing bulbs

with my A19 bulbs, i've had no issues with home assistant's adaptive lighting at all, except for these known issues: * brightness transitions at low levels look like they have "steps", * transitions between color temp and rgb mode aren't supported.

[opal sparrow]

hmm, there is another issue - if transitions are running at the same time, it can cause a lot of thread traffic due to subscription updates which might cause some bulbs to drop from the network. That shouldn't cause flashing tho, i think? But regardless, you could try tweaking your adaptive lighting settings to set the transition duration to 0 and see if that helps.

[tired cloak]

i set the "skip_redundant_commands" box now and will see if it helps

[tired cloak]

Every 30 minutes I get these errors. Anything I can do?

2024-07-30 14:41:05.302 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 15:11:05.091 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 15:11:05.098 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 15:41:05.045 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 15:41:05.054 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 16:11:05.070 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query
2024-07-30 16:11:05.097 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to parse mDNS query

[void pulsar]

For flashing bulbs please open a ticket with us and mention that you talked to me on Discord @tired cloak

I will also raise this issue with Home Assistant's team to see if they have observed it.

[craggy plaza]

Do you have a flat network or do you use VLANs with some kind of mDNS repeater/reflector?

[opal sparrow]

i haven't heard of any mdns issues with apple thread border router hardware, fwiw :/

[tired cloak]

No, just a flat network, without vlans. Router is a AVM FritzBox

[craggy plaza]

Ok, so you do not use the guest network for some of your devices? Do you have any Fritz Repeaters in use or the FritzBox only?

[tired cloak]

no, i dont use guest network for any of the devices. I just have normal 2.5 and 5 Ghz Wifi. No Repeaters

[manic plover]

I wonder, is the Nanoleaf team working on a new firmware version? I invested in more border routers, but I keep having problems. After a reset (e.g. briefly cutting power from all lights), they all connect - and then slowly decay over time.

I also set up OTBR to debug, and switched from Google Home to Home Assistant.

The screenshot above should explain better what I mean. For 48 hours after reset the lights are continuously connected. Then the experience starts to be very choppy.

[green frost]

Nanoleaf is working on firmware for several products. With which products are you having issues? Please provide the NL## if possible.

[plain kettle]

U on the 2024.8 beta for HA?

[manic plover]

No, stable. Should I test the beta?

[plain kettle]

wont make much diffrence, just curious

[manic plover]

Right, silly me. All GU10.

[plain kettle]

how many BR's you got?

[manic plover]

2, tested with 3 as well.

[plain kettle]

what ones are they?

[manic plover]

SkyConnect + Nest Hub gen 2 + GL.iNet GL-S20.

[main matrix]

The S20 is probably your source of problems.

[plain kettle]

yeah....

[main matrix]

I have 2, and they've been disconnected for some time as they introduce instability

[manic plover]

That's the 3rd one I tested which is no longer on the network.

[main matrix]

I'm using 5x GH Gen 2s and stable as a rock

[plain kettle]

i mean, the product seems EOL from glnet, no updates to the underlying OTBR firmware in months

[manic plover]

The screenshot above is with SkyConnect + Nest Hub only.

[main matrix]

not necessarily; they go months between updates for other products

the S20 is also a fairly recent release to market, so I'd hope they wouldn't deprecate it so quickly..

[plain kettle]

cant it just be flashed with whatever BR fiwmare you want anways?

[manic plover]

The light I selected for the screenshot are right next to SkyConnect, in the same room.

But it's the same for all.

Also those right next to Nest Hub.

[main matrix]

the S20 and Skyconnect all use OTBR, so it's also possible that's playing a part. I have a Skyconnect but flashed for Zigbee duties only. The GHs are Matter controllers themselves, so... might be worth testing without the Skyconnect connected? (inb4 other peoples setup work with the SkyConnect, yes I am aware of this but no two setups perform the same)

[plain kettle]

@manic plover what fuchsia version are you google hubs?

[manic plover]

18.20240225.3.63

[plain kettle]

hmm yeah ok, thats the latest

[green frost]

I have nine of the GU10 on an Amazon Echo Dot 5th Gen and 6th Gen eero and they work fine.
However, the new firmware coming out has a few improvements that may solve your issues.

[manic plover]

I tested that as well. Also with more Nest Hubs. I also tested SkyConnect alone.

[main matrix]

probably an obvious question, but you're on a flat network? no vlans/etc?

[plain kettle]

they are all on the same thread network yeah?

[manic plover]

I know it can work well, there was some ancient version of Nanoleaf firmware where my entire setup worked well for a week or two.

[main matrix]

yeah, the NL firmwares have been a bit up and down

[manic plover]

Nothing like that. One network.

[manic plover]

Yes.

[manic plover]

I've seen someone mention NL working on auto updates over Matter, do you know if new firmwares are going to be distributed this way? Just checking 'cause I need a full day to update all via Bluetooth 😅

[green frost]

It should be automatically available.

[plain kettle]

yes, they can update via the DCL now

using TestNET or the offical DCL

*i wouldnt use TestNET certificates on your nanoleaf devices (enabled through the matter-server config), rather stick to their beta program

but its there

i was updating all my devices through a hardware beta using the DCL, so it does work

[manic plover]

Yeah, I try to test and provide feedback whenever I can, but it's already very time consuming. I'll stick to Beta.

Do we know when the new firmware might come out?

[plain kettle]

[green frost]

I will chat with Homer and try to get you some help. I don't use Apple products so I'm no help there. My experience with Android and Amazon has been that it just works. But I still prefer Wi-Fi but I see the light at the end of the tunnel with Matter. I'm just not a fan of Thread.

I will enquire as to an ETA on the firmware.

[manic plover]

Yeah, I have Wiz at another location for years (Wi-Fi) and well... That's my measure of rock solid 🙂 Just that the colors on those are so washed out, I don't even use them at all. NL is much better.

[green frost]

I hear rumors of new products coming that might be fun to have. I wish they would hurry.

[craggy plaza]

Hi, I have 60 MoT devices and 23 (13 A19, 10 GU10) of them are from Nanoleaf. Not a single disconnect here. So, it’s maybe your Thread network. Which Thread channel are you using? Maybe it interferes with your 2.4GHz WiFi or your ZigBee network, if you have one. All these technologies use and share the same 2.4GHz frequency band and so can interfere with each other. Do you use ZigBee? If so, which channel? Which 2.4GHz WiFi channels are in use?

[plain kettle]

yeah, you can see in the Thread intergration on HA what channel they are sitting on

[manic plover]

Channel 26.

APs are fixed to either 1 or 6.

[green frost]

Channels 1 and 6 are 2.4 gHz and channel 26 is 5 gHz.

[wraith bear]

Hey guys, when was the last beta firmware pushed out?

[plain kettle]

It’s been months

[wraith bear]

Any significant improvement in the last one?

[craggy plaza]

What? Channel 26 is 2.4GHz, too. ZigBee and Thread use a different channel naming scheme in the 2.4 GHz band than WiFi. Here is a good description for WiFi and ZigBee coexistence:

https://www.metageek.com/training/resources/zigbee-wifi-coexistence/

@manic plover Seems to be an ideal configuration. You do not use WiFi channel 11. But I am unsure about Thread channel 26. Never heard that anybody used this channel. Apple‘s Thread channel default is 25. Do you live maybe in an apartment, where you have a lot of neighbor WiFis?

[green frost]

Thank you. I wasn't aware that ZigBee had channels that high. I appreciate you linking that page.

[manic plover]

No, it's a single family building. No neighbors nearby, I have no other Wi-Fi signals anywhere at my home, besides my own Wi-Fi.

Also, I'm not sure how to explain that for nearly 48 hours it's been working fine. It's not that I turned my Wi-Fi off 🙂

I can also try channel 25, why not 🙂

[main matrix]

I find when that happens, mDNS decided to start "playing nice".. would be curious to see whether your mDNS records on your network disappear if the lights stop working again.

If you're on Windows, zeroconfServiceBrowser is a good one to use (do your own research, obviously). https://www.tobias-erichsen.de/software/zeroconfservicebrowser.html

Android and Apple have their own variants to do the same job.

[manic plover]

Well, so I changed the channel to 25 this morning. It's been 10 hours since, so I decided to take a look at the uptime. To my surprise, everything is back online since yesterday evening... (before changing the channel). I can't explain it.

[craggy plaza]

Ok, great! But let’s wait some days. 😉 By the way… I planned to change the Thread channel from 25 to 26, because of less interference with WiFi 2.4GHz channel 11. But seemingly I should better stay away from this decision. 😃 Please, keep us updated.

[craggy plaza]

What did you have to do to change the channel? Was it the update of the channel in the OTBR settings only or did you have to reset and readd all Thread devices?

[swift phoenix]

Someone make this make sense please

[wraith bear]

Is this a new feature in home assistant? Seeing uptimes like this?

[manic plover]

Just in the OTBR.

[opal sparrow]

That's just the history view with the light entity selected. In this case it's showing times when the lights are on vs off vs unavailable.

[feral steeple]

If it helps, since the latest beta a couple months ago, my 30~ GU10 nanoleaf bulbs have had a great uptime with HA.
The only problem I have is a delay to turn them on if too many signals are sent. I.e. walking through the hallway and living room to the kitchen wants to turn 26 bulbs on. And it takes about 3-5 seconds till the kitchen turns on.
I would say the connection issues have all been resolved since that update though

[swift phoenix]

Can share what that looks like in the frontend of HA. I just wanna see how yours reacts compared to my setup.

[feral steeple]

Here is a bunch of them for this week if it helps. Selected them individually and got fed up after selecting that many haha

[feral steeple]

And not sure what you are using, but early days with the nanoleaf issues I split thread and zigbee off from skyconnect into 2 separate USB's. SO skyconnect does thread and another one does zigbee. That did help with stability. Not sure how far that has come in the last 3 months though. But was a nightmare at the start of the year when running the multi one on skyconnect

[swift phoenix]

Can you show how it looks like from my video i posted

[feral steeple]

From your video it seems you are showing switching it and not responding? Hopefully this video helps. https://productivuspte-my.sharepoint.com/:v:/g/personal/leon_productivus_co/Ea0QK8zomypLpDP-uNKwpocBtrq7BYa4sEJIHA20V1lF-Q?e=lwgvsB

[rare aspen]

Hello team, any ETA for Essentials Bulbs firmware with awaited 4D Sync+ compatibility ?

[woven scaffold]

A question: Does the Nanoleaf Matter Essential series support Adaptive Lighting on the Apple Home Matter platform because it runs HomeKit and Matter over Thread dual protocols at the same time?

[opal sparrow]

current essentials lights do not run homekit over thread. they do matter and a nanoleaf proprietary protocol only.

and i'm pretty sure apple isn't using the proprietary protocol, so I bet they're using the normal matter interface (which does provide everything needed)

[feral steeple]

Anyone have an issue in the nanoleaf app with Matter? All matter ones show up with "a critical update is required before connecting your device via matter" and I cannot link it via nanoleaf to home assistant.
Its weird. THere is no update for the app, and no update for the bulbs all 3.6.196

[opal sparrow]

that's really weird. that firmware should be new enough that you won't have any issues with matter, so i'd say just go ahead and connect to HA.

[plain kettle]

Were you apart of any hardware beta that included the lights?

[feral steeple]

Nope

[feral steeple]

They have all previously been fine, and connected directly with HA, but i could usually add it via the NL app

[swift phoenix]

Any ETA on next beta firmware devs?

[daring marsh]

Yes, same issue here

[void pulsar]

can you send me a screenshot?

[void pulsar]

3.6.196 is the latest FW that we have pushed out. We don't have a date for a new beta firmware just yet

[rare aspen]

Do you plan a beta FW to make essentials compatible with 4D sync+ ?

[feral steeple]

Im guessing there was an app update as now its showing connect as it normally would 😄

[green frost]

If there was, you will see the version number in the top right corner on the desktop and at the bottom of the More page for the phone application.

[dark junco]

Is anyone able to update firmware to 3.6.196 on A19 (from 3.5.41) without having to factory reset and re-commission?

On android, latest app version (10.8.6). The app detects the devices and shows Bluetooth connectivity, no thread. Offers to start the update, then gets stuck on processing at 0% before eventually failing:

Update Error We're having trouble with the Bluetooth connection to Nanoleaf A19 ....
Keep it nearby during the update. If issues persist, try powering off the device for a moment before powering it back on.

No logs, nothing to help troubleshoot. Thread network shows correctly in the app, HA skyconnect. Surely it's meant to work, or is everyone resigned to resetting every device every firmware release?

[plain kettle]

are you near the devices when you go to update them?

iirc, the update is done over bluetooth

[dark junco]

Can't hold the phone closer, right next to them. Signal strength makes no difference unfortunately.

[plain kettle]

does it show 3 green bars on the bluetooth connection?

[dark junco]

Yep.

Oh how I wish for some logs

[woven scaffold]

I found several versions of the firmware stored by Nanoleaf on the DCL Main Net. They seem to be a little newer than the latest 3.6.196 version? If the answer is yes, I will consider using HA for OTA pulls.

My mistake. It turns out that the latest 198340 is the latest 3.6.196 firmware.

[craggy plaza]

How do you know? Can you calculate this somehow?

[woven scaffold]

This

[swift phoenix]

Will nanoleaf bulbs be updating to Thread 1.4?

[plain kettle]

bit early to say, but no doubt they will eventally

[rare aspen]

Will Bulbs eventually be updated to sync with 4D screen mirroring ?

[undone spire]

There's a good chance we will find that out in less than a hours time.

[rare aspen]

Should anything be announced soon ?

[undone spire]

In 30 minutes they are hosting a live launch event

[green frost]

The 2024 Keynote from IFA. It will be interesting.

[undone spire]

Nope no updates unfortunately

[rare aspen]

Thx for the followup

[opal sparrow]

Note that updating the nanoleaf bulbs to thread 1.4 wouldn't really do much - the interesting thing would be to get nanoleaf devices with integrated thread border routers updated to thread 1.4.

[manic plover]

The release notes for 1.4 mention "maintenance updates aimed at improving overall network performance and reliability", and also better troubleshooting tools.

I really wish to see that happen, at this point I just learned to live with my lights having their own crazy teenager life ❤️

I even checked Silicon Labs SDK, but they mention 1.3 only 🙂

[plain kettle]

I mean yeah, it’s cool to have more troubleshooting/debugging info, but the company needs to expose that information to the user, which Nanoleaf isn’t known for

[manic plover]

I guess the company is focused on a direct to the consumer market, where it might be less of a requirement. That's a shame, for installers it still feels like it's not an option to use Nanoleaf.

[wraith bear]

Hang in there buddy, I believe matter and nanoleaf will come around one day

I paused my facility project for 1 year at least, I dont know where nanoleaf and the market will be at with matter over thread, but I keep logging into discord every now and then to see the progress and read news articles on potential products etcc

[manic plover]

I have a construction company which also does smart home, so I'm always on the lookout for best products for my clients. Plus it's a hobby. But I always test on myself first to keep quality high. Keeps my reputation intact 🙂 I just really wish I could start offering Nanoleaf.

[woven scaffold]

https://www.silabs.com/developers/software-development-kit-release-notes

[plain kettle]

i would expect it to hit openthread based BR's devices pretty quickly if its recived well and comes out of "beta"

[manic plover]

Nice!

[main matrix]

For those looking for more info on Thread 1.4: https://threadgroup.org/Portals/0/Documents/Thread_1.4_Features_White_Paper_September_2024.pdf

[rocky quail]

Anyone else having issues with Google Home (GH) losing thread/matter connection with the A19 Essentials? Came back from a trip Sept 2nd and I have not been able to get my 9 bulbs to connect to or work with google home since. I resorted to deleting them all and reseting before adding them to back in the android app. fw 3.6.196 and android app 10.9.0 (427) In the past the app prompted me to connect bulbs to matter in the settings area of the bulbs. It does not ask this anymore. Google Nest Hub Max firmware 20.20240530.3.236 Google Nest Wifi version 14150.882.9 Any troubleshooting ideas or recomendations?

[green frost]

@void pulsar @mystic light Did you submit a ticket on thisd?

[rocky quail]

I just submitted a ticket now. In the past I had periods of time where it may have just been laggy google servers and was curious if there are others having issues too.

[green frost]

What is the ticket number?

[rocky quail]

78121

[void pulsar]

@rocky quail I will take over this ticket internally and get back to you

[swift phoenix]

I have another product although I cannot say who or where it’s from due to NDA. But…. Man it’s much more responsive and polished than the essential bulbs. I really believe this is all down to firmware. If they can figure it out then I am positive the nanoleaf team can make these bulbs more polished as well.

[plain kettle]

Yeah, i also have other MG24 based products, and no issue. guess the duel stack takes its toll

[swift phoenix]

I mean its enough to make me want to switch as soon as this device is released. Unless nanoleaf can somehow pull it together.

[dark junco]

Ooo gimme, looking forward to more options

[craggy plaza]

Which chipset is used by Nanoleafs Essentials line, EFR32MG21 or EFR32MG24? What are the differences?

[feral steeple]

Its really sad they stopped working on the firmware after they got it to just stable... They should have gotten it at least 1 step more before stopping

@void pulsar Can you help with my ticket? Its been months and I cannot get some faulty bulbs replaced. - 64274
can I get my ticket escalated? I am getting nowhere and am currently short 11 bulbs that are failed. I get no response for weeks then just get a "we are still waiting for a response from our team".
I would have thought my faulty bulbs that are only 8 months old would get replaced under warranty a bit quicker than this. Its pretty clear it seems to be a bad hardware batch. I have not had any of the already replaced bulbs die like these have yet

[green frost]

What firmware are you referring to that has stopped work on?

What bulbs do you have and how do you know they are defective?

[swift phoenix]

Idk if you guys saw this but they are now trying to sell matter over wifi bulbs. Does not seem like a good sign for the essentials thread version.

[green frost]

I don't know if you saw this but those bulbs are going into Walmart stores. Walmart thinks that Matter/Thread is too complicated for most customers; Walmart is correct.

[feral steeple]

GU10 firmware. After all our testing got to a stable thing, no more updates or work. When its stable but not really polished.

I know my bulbs are faulty because they start going to only a dim brightness and when going to a colour like candlelight it goes red. OR the light has just completely gone off, nothing, HA shows it turning on and off, NL app shows it turning on and off, and no light out of it.
This also happened to a few of them already which have been replaced. It seems to be a faulty batch, as all the ones that have failed with these similar symptoms seem to be from the same initial order of 26 I got, the 10 that have already been replaced from these same problems have not had the issue re-occur.

[craggy plaza]

@feral steeple Which firmware do/did you use on your defective bulbs?

[feral steeple]

3.6.196, what is this 3.8? I dont seem to get an option for that :S? Bulbs are enabled for beta too but show 3.6.196 as the lastest firmware.
Had some failed bulbs before 3.6.196 as well and we tried to see if it was something that could be resolved with the firmware, but it didnt. Seems to be a hardware fault.

[green frost]

The firmware development for the GU10 has not been stopped. It is currently being refined and will be updated when the Sense + switch is released.

[opal sparrow]

yeah, your gu10 issues sound (mostly) like hardware problems :(, tho the one 3.8 bulb that won't pair could be software.

[opal sparrow]

the 3.7 and 3.8 firmware versions are from a private beta, so you won't get them unless you're in that beta.

[rare aspen]

I think the main issue with Thread is that is requires a hub.

[rare aspen]

are there distinct private and public beta programs ?

[plain kettle]

yes

[rare aspen]

didn't know that. Does FW 3.8 for Bulbs include Sync+ compatibilty ?

(in that case, it would be interesting)

[green frost]

Those in the Beta program are prohibited to speak about the Beta. In fact, those I'm the Beta are under NDA to not even acknowledge they are part of the Beta program.

[rare aspen]

Beta is just like the Fight Club 😀

[green frost]

In some respects, yes. Just that no one gets the crap beat out of them.

[rare aspen]

I have one matter essential Bulb in the Beta program, but didn't get 3.8 FW. How should I apply to be part of that beta ?

[plain kettle]

You can’t, it’s closed

Most of the hardware betas have associated software betas that allow the features to work

[rare aspen]

so I won't get the 3.8 beta until it's made available in the beta program ?

[plain kettle]

Basically

[rare aspen]

OK.I'll wait, then. Thx for clarifying.

[woven scaffold]

3.8.4

[plain kettle]

Interesting, seems to be coming over the testNet DCL

Seems odd, as the hardware beta I was is locked it to 3.8.0

[green frost]

'Ang 'bout, You stated, "I have one matter essential Bulb in the Beta program..."

Were you or not part of a test group that would have been updated to v3.8 firmware?

[rare aspen]

Nope

I only received 3.6.196 when it was still beta

[plain kettle]

@woven scaffold 🔥

seems like its on all matter/thread devices

[woven scaffold]

Nice🚀

[plain kettle]

seems weird i dont have that update prompt in home assistant

seeing as i have testnet DCL usage on

[swift phoenix]

Im not seeing any update in the nanoleaf app?

[opal sparrow]

nanoleaf app is a separate update channel which can show different firmware versions (and also has the stuff for per-device opt in to specific firmware betas) - and this is the "testnet" dcl, so it's not firmware updates that they expect to have automatically applied by third-party matter controllers (yet)

[green frost]

Just because it can be seen does not mean the servers will actually serve the file.

[opal sparrow]

If you open up the details on the testnet dcl and click the link, the servers do indeed serve the file.

(well, you have to copy/paste the link, they didn't actually make it clickable on the dcl ui)

[green frost]

Nanoleaf needs to fix that.

[plain kettle]

Nanoleaf don’t need to fix the that, that’s the CSA’s job

Or anyone who wants to fix it, iirc the testNet website source is on GitHub

[opal sparrow]

i mean, it's not really intended for you to download the firmware in the browser - there's not really much you can do with it (except attempt to reverse-engineer it, i guess)

other tools, like matter controllers checking for updates, interact with the dcl programattically.

[zealous wave]

Does anyone know if the update includes exposing scenes via matter protocol? I would like to have the ability to set them in HA.

[plain kettle]

not sure, im a bit hesatent to update, seeing as they arnt pushing it out via "conventional" means like nanoleaf normally does, and also no official word on it, seems like more of an alpha bulid of it

[void pulsar]

@everyone The latest production firmware is 3.6.196

3.7.x and 3.8.x are beta firmwares

If you unintentionally got 3.8.x and are facing issues please send me a DM. The 3.8.x is supposed to be part of a private beta that we are running which is prone to have more issues than our public beta but we have made progress on that as well internally.

[plain kettle]

just to confirm, going down from the 3.8 fw wont stop the hardware beta products from working?

aka the product from the lw000x betas?

[opal sparrow]

Depends on the beta I bet - you're probably better asking in the beta specific forums

I don't think it's possible to downgrade fw version on matter devices anyways?

[void pulsar]

Going down will stop hardware beta products from working @plain kettle

and for certain FW I won't be able to degrade either

[plain kettle]

hmm yeah, thats what i was thinking,

might just be worth waiting for the final firmware for when the product hits the public, ive personally been having no issues with my devices on the 3.8 fw

[magic tartan]

i'am nor reciving any beta update, i enrolled ti for my devices a few day ago.

and the Testflight Nanoleaf App Crash everytime

[bitter compass]

I enrolled a new nanoleaf essentials strip in July and it's never received the 3.8.x update that the existing bulbs and light strip all have.

[magic tartan]

Yeah same here but i enrolled some devices in may i think and still ni 3.8 or 3.7

[swift phoenix]

I’m enrolled in beta and don’t see any updates? Am I missing something?

[opal sparrow]

There is currently no public beta firmware for essentials thread devices, you'll get the same 3.6.196 firmware regardless of whether you're opted into public beta or not.

[woven scaffold]

Only one of my 4 Matter Down Lights received the 3.8.4 FW update, the other 3 are still at 3.6.196

3.8.4 FW exists in Test net DCL, I don't know why my other 3 Down Lights can't detect the new firmware update

[craggy plaza]

Did you update the bulb via OTA or via the Nanoleaf app?

[plain kettle]

its strange, my homekit caught onto the testnet DCL changes, but not home assistant (with the testnetdcl toggle on)

[woven scaffold]

Via Apple Home App use Matter OTA

[craggy plaza]

Did you configure your Apple Home for testnet DCL?

[plain kettle]

yes, you can do that

[woven scaffold]

Ward's HA Test DCL also cannot detect 3.8.4. I suspect there is something wrong with HA itself. Apple Home APP's Matter OTA (Test Net DCL) is all normal.

[plain kettle]

yeah, thats what im thinking. wonder if its worth seeing if the HA devs know

[woven scaffold]

Currently only this bug exists

[woven scaffold]

Yes

[craggy plaza]

IMO Nanoleaf doesn’t want us to install this firmware until they make it available in the Nanoleaf app via public beta.

[opal sparrow]

keep in mind that you cannot downgrade the firmware if you run into issues

[rare aspen]

you'll have to wait until the issues are fixed by the next FW

[main matrix]

as far as I know, HA Devs usually shy away from anything testnet DCL as they run the risk of bricking devices.

[plain kettle]

yeah, which is fair in all honestly, just seems odd none of my devices (eve and nanoleaf) arnt getting testnet updates on HA, but they are on apple home. ah well

[main matrix]

at least that is the case with the Aqara P2 sensors. Couldn't imagine that it'd be different based on vendor.

you can supposedly force a testnet DCL file to update by adding the .json into a particular folder, but YMMV on whether you have a working device after the fact.

[plain kettle]

haha yeah, im not that ballsy

thats what i think "use testnet DCL does", doesnt actually poll it for updates, rather just allows you to "inject" custom json for devs

[main matrix]

yeah, makes sense

[feral steeple]

@void pulsar Any chance you might be able to get me some progress on my ticket that has been going for months? 64274. Im currently about 10 GU10 bulbs down from the 36 i bought. Been trying to get the other faulty ones replaced so I can get all my bulbs back in the roof! Getting no where with support and its very annoying. Seems to largely have been a faulty hardware batch I originally received.

[green frost]

Please enter the ticket details here #1259294662796120174

There is a pinned message explaining the details.

[manic plover]

Interesting discovery: I've been struggling a lot with connectivity. Recently I decided to play with adding more border routers. I bought a cheap one, GL.iNet GL-S20. Check out what happened when I connected it INSTEAD of my Nest Hub (the total number of border routers remained the same). I need to run more tests (re-add Nest Hub, do it a few times) to have more certainty. But at a first glance, it seems that the Nest Hub could have been causing some of the issues.

(blank spaces on the timeline - disconnected)

[plain kettle]

The fuchsia version on the google hub starts in 20?

[main matrix]

I have the opposite experience. Adding a GL.iNet S20 to my network (I have 2) caused instability within the first 5 minutes. Had done a bunch of testing with/without the hubs, and it didn't work very well for me, but YMMV.

I also have an S200 (same architecture as the S20), same experiences too.

[manic plover]

20.20240530.3.236

[manic plover]

I've seen similar opinions online, I was very hesitant to buy it, but with all the issues I had I decided to give it a shot. It was not stable immediately, I had to let the network rebuild, it took a few hours. But since then - you can see on the screenshot, rock solid. Haven't experienced such stability since Nanoleaf released these bulbs.

[main matrix]

yeah was also the same (I bought mine just after they announced them being on the market). I have 5x GHs and for the most part are now stable (the hubs do freak out once a week and drop off the Thread network, not sure why, but I've scripted to reboot the GHs in HA if more than X amount of lights go offline), so it's a workaround but works for me.

in my case though it's not just Nanoleaf lights going offline (Eve, Meross and Aqara devices* do too). Probably an underlying cause, but 🤷‍♂️ - will look at that when people complain enough.

[manic plover]

Here's another room:

I'm about to receive MotionBlinds over Thread for testing, I'm curious about the stability of those in my environment. From what I can read online, it seems generally stable, similar to Eve.

[plain kettle]

Most of eve’s stuff is, and if you have any issues, one of the main hardware devs is in the HA server

[craggy plaza]

I have 1 EVE MotionsBlinds since more than a year. Absolutely rock stable. But my Thread network is overall very stable. I have 62 MoT devices (23 Nanoleaf bulbs, 39 EVE devices). Only when I upgrade the firmware of my network hardware (router, switches, APs) it sometimes gets a bit crazy. I think it’s because TREL gets a problem, when the infrastructure is not available for some minutes.

[manic plover]

I would love to see Unifi release APs with Thread border routers, and have first-party support for routing all the Thread IP traffic 😄

[main matrix]

ha, glad to see Unifi actually working with Matter... I ended up migrating to an alternate vendor entirely (Omada) due to the constant mDNS issues.

[craggy plaza]

Which mDNS problems are you talking about exactly? I do not have Unifi related mDNS problems with my Thread network. All my Matter related devices are in the same VLAN. That’s all you need to get it stable.
I have 7 Apple Thread Border Routers (2 hardwired AppleTV 4K 3rd Gen, 4 HomePod Minis and 1 HomePod v2) for my 62 MoT devices. I am really waiting for Smart Light and Dimmer switches with a normal form factor to exchange my existing ZigBee dimmer switches.

[craggy plaza]

Oh, hell yeah… I already bought the new U7 APs, but that would be a great addition. 😃

[main matrix]

MDNS traffic not passing for one. Regardless of settings, spent more than a month troubleshooting. Matter devs kept saying it was my problem and not theres, even though there was a multitude of users reporting the same problems. Found a blog post mirroring the same problems I was experiencing and the same hoops I jumped through, swapped to Omada, problems disappeared immediately.

[craggy plaza]

Ok, interesting. What makes my setup different? 😅

[opal sparrow]

yeah, matter over thread networking is rather tricky. anything talking to a thread device needs two things: needs to be able to resolve mDNS queries (answered by one of the thread border routers) to find the device's ipv6 address, and needs to be able to route IPv6 to the thread network's subnet (advertised by the thread border router via IPv6 RA).

in theory things can be made to work across vlans/subnets, but you need to have a correctly operating mDNS relay and your inter-subnet router needs to know about the thread subnet and where to route packets to reach it.

[opal sparrow]

the thread folks seem to recommend that thread border routers support DHCPv6-PD (prefix delegation), which in a properly set up network will add the delegated prefix to the routing table, but the TBR I use doesn't support that :/

[woven scaffold]

I think the Nanoleaf Matter over Thread Essential series needs to rewrite the firmware, because their experience and performance in Apple Home are too bad.

I have removed several of my downlights. They are really terrible.

😭😭😭

[craggy plaza]

How can I check that?

[craggy plaza]

How many Nanoleaf bulbs do you have in total and which model?

[woven scaffold]

4，Essential Down Light (Matter over Thread)

Even if I upgraded to the internal beta version of 3.8.4, I didn't feel any experience improvement.

[opal sparrow]

Hmm... usually diagnostics or logs for the router/dhcp server will include information about which devices have dhcp leases and which subnets are delegated.

Yeah, i'm pretty sure that firmware was for a feature or product beta, and wouldn't help you any with stability. (Might even be worse than the stable 3.7.x firmware)

[woven scaffold]

I can only wait for the Aqara Matter over Thread lighting series to conduct a comparative test to see how Aqara will do.

[opal sparrow]

if you're in an apple home environment... the home assistant folks have seen a bunch of stability issues recently when the thread networks had multiple apple border routers. if you have more than one, consider temporarily removing some to see if it improves things.

[woven scaffold]

I only have one TBR (HomePod mini) at home, and there are no other ecological TBRs running at home. I will try to exclude some factors that affect stability.

[craggy plaza]

I have 7 Apple TBRs and since the update to Apple OS 18.0 it works flawless.

[craggy plaza]

3.8.4 was maybe not the best decision. This version was never released via the Nanoleaf app.

[craggy plaza]

Ok… How many Thread devices do you have in total and what’s the distance between them and your HomePod Mini?

Have you investigated possible channel interference? Which WiFi 2.4GHz channel(s) are you using? Do you use ZigBee? If yes, which channel is used?

[rare aspen]

I personaly a better NL devices wifi connectivity after moving from HomePod Mini to Apple TV 4K as Thread border router.

[plain kettle]

wifi connectivity wouldn't really be effected by what thread BR you are using (as big of a change where it is noticeable)

[frozen crystal]

One of my GU10s running 3.6.196 occasionally strobes for a few seconds before settling again. Is this a known bug?

[green frost]

Not that I know of. Please submit a ticket at https://nanoleaf.me

[frozen crystal]

Shall do. I now realise that it has been an issue with this one bulb since it was installed in January. It has recently become more frequent. It is not firmware dependent and I have tried resetting. Good thing none of us are epileptic!

[royal moss]

Hi all, just got my first Nanoleaf essential bulbs NL67 for testing. I'm using HA 2024.10.3 and skyconnect matter radio and got everything working after few tries (I'm using the open border router and matter server addons on HA to make this all work). Was bit surprised that I didn't get any firmware update notification so I started poking around. Here's what I've found:

• My NL67 bulbs are of firmware version 3.2.0 and HW version 4.1.8.
• By manually trying to start the update from Matter server webui, the ui states that no updates are available. Looking at the debug logs the server seems to righly go through the main DCL's catalog for the device (vid: 4442 pid: 67 type: 269) but determines that all available versions 198340, 197910 and 197888 are not applicable without any further info.
• I haven't enabled the test DCL yet, but according to past announcements here it seems that 3.6.196 (197888) should be of general availability.
• I haven't yet downloaded the matter spec to try to understand how the min applicable software version etc work, but if the current firmware version 197120 of my bulbs needs to be equal or larger of the firmware 197888's MinApplicableSoftwareVersion = 198317, then that might be the problem...?

Ideas, anyone?

EDIT: After digging through the python-matter-server code the HA matter server addon is based on, found that the firmware 197888 is indeed blocked by the MinApplicableSoftwareVersion (See https://github.com/home-assistant-libs/python-matter-server/blob/078f48037a9bfd270a32f7539bd8b94dd50cfbc3/matter_server/server/ota/dcl.py#L68-L75). Anybody from Nanoleaf have time to weigh in on this or should I make a proper support ticket?

[rare aspen]

Unless HomePod mini wifi connectivity is unstable. Ethernet connectivity of the Apple TV is more reliable.

[plain kettle]

i would reccomend trying to update via the app, not the DCL

the version is blocked due to some previous issues with it and the DCL iirc, so its reccomended to just update via the app to the latest GA

[royal moss]

I haven't even installed the app. Is there a way to install the updates through the app without it messing up the ha's thread network?

[plain kettle]

yeah, the updates are delivered via bluetooth

so it wont mess with the existing thread credentials at all

[royal moss]

Great! I'll try that then.

[plain kettle]

👍 lemme know how you go, if you have any issues, you can ask in the HA discord server

as nabu casa can raise DCL issues (internally through the CSA) with nanoleaf, more chance of a actual fix than asking here

[barren sky]

I have the exact same issue, contacted nanoleaf support and they sent out a free replacement

[royal moss]

Managed to update the firmware for all the bulbs through the app. Thanks for the help! And yes I might actually take the time to post about this to nabu casa. Kind of a blow to the whole DCL system if the upgradable firmware is blocked like that. There's a zero chance a non-technical person would ever figure that out.

[plain kettle]

Oh for sure, eve’s devices exclusively update via the DCL, while Nanoleaf is kinda in the grey area of both DCL support and also having their own updating mechanism

[plain kettle]

You should be be able to do it here https://discord.com/channels/330944238910963714/1284966617670881350

Make a forum post and marcel will no doubt respond in the next few days (I think it’s still the weekend in the NL)

[frozen crystal]

Thank you. My experience of obtaining replacements from support does not make me look forward to this!

[green frost]

If it becomes an issue, please let me know.

[frozen crystal]

Thank you, I appreciate it

[barren sky]

That’s odd, never had an issue with replacement myself, I just try what they tell me to do and then I send a video showing the issue and then they said it might be a hardware issue and they just sent me a new one, thought the issue doesn’t happen if the bulb is already 100% at the temperature lights so I can still use it for that, just no scenes

[verbal drift]

Question: I have a GU10 thats still connected to the network but is no longer lighting up, is this likely to be a failure of components and what is the best way to get it replaced?

[marble cloud]

I had two of those gu10 still connected via thread but no longer lighting up. I emailed the support, had to record of a video and they replaced both of them.

[zealous wave]

I've had the same thing for two days now ;/

[tiny gale]

Is that a test-net firmware?

[plain kettle]

it would be

[woven scaffold]

Niceeee🚀

[woven scaffold]

https://csa-iot.org/newsroom/matter-1-4-enables-more-capable-smart-homes/

[plain kettle]

Very cool, wonder if Eve will move straight to 1.4 now, and not worry about 1.3 seeing as it’s not out of beta yet

[stark crystal]

Still no Scene support with Matter 1.4?

[green frost]

Are you asking or just stating a fact?

[plain kettle]

apparently it does i think

lemme look it up

@stark crystal

seems like it does, but i would expect it to be 6+ months untill we actually see some product adopt it. but i know home assistant is working on 1.4 now with an ETA of soon

[stark crystal]

Thanks for finding this, Scene support wasn't mentioned in the article above.

[woven scaffold]

A question:

If I have updated to the TestNet beta firmware 4.0.10, will it affect my update to the MainNet 4.1.0 firmware?

[plain kettle]

i dont think so? it seems to be diffrent

i would update to 4.1

[plain kettle]

is it on the "Main" DCL? i would just update via the nanoleaf app

[woven scaffold]

I haven't detected the 4.1.0 MainNet firmware on Apple Home yet, maybe I should check from the Nanoleaf app

[plain kettle]

it should appear

[woven scaffold]

The 4.1.0 firmware has not yet appeared, maybe I can wait a little longer

[plain kettle]

hmm strange

[main matrix]

lol, tried to check my lights for an update in the NL app, disrupted 30% of the mesh (Eve, Nanoleaf and Aqara devices all stopped responding). Killed the app, all devices came back to normal. Guess I won't be updating anytime soon 🙃

[woven scaffold]

@plain kettle You are right, the 4.1.0 firmware is not stored in MainNet, it only appears in the Nanoleaf APP. What I want to know is: if the 4.1.0 official version firmware in the Nanoleaf APP is the same as the 4.0.10 in the TestNet? If the features are the same, then I don’t have to worry about them.

[plain kettle]

im not sure how diffrent it is. would be intresting to know why 4.0.1 is on testnet? maybe its a typo?

[woven scaffold]

@wild oracle Hi, Nathan, can you explain this?

[main matrix]

curious; entering the OTA URL for 4.1.0 on the DCL does pull down a .matter file, so... it appears to be uploaded but hidden?

[woven scaffold]

I can even download it😂

[main matrix]

except it seems to be different to the one I grabbed (mine was r8)

not sure if there is any functional difference but 🤷‍♂️

[woven scaffold]

This is the firmware of DownLight（NL65）

[main matrix]

ahh, that's the difference. I grabbed NL67 (A19)

[woven scaffold]

Matter over WiFI?

[main matrix]

no, MoT

[woven scaffold]

OK

This NL67（A19）

[plain kettle]

@main matrix you may be pegged by this https://discord.com/channels/837773208027529287/1303718998529146892

everyone else is stuck on that version, i dont think its the same issue cyber has

[main matrix]

to be honest, didn't even know that thread was a thing 🤷‍♂️

[plain kettle]

haha yeah, its pretty hidden

[main matrix]

my lights are still on 3.8, as that works... couldn't be bothered breaking them again just to spend 900 hours resetting them up

they're also not showing 4.0.10 as an option to update to

so, idk

[plain kettle]

i think home assistant does check for testNET dcl versions properly, even with the toggle

i see it on my apple home (with the testnet cert), but never on HA

[main matrix]

does HA have the ability to update NL lights via DCL? never seen that appear

and the NL app(s) are god awful

[plain kettle]

it supports updates, but im not sure if its also updates via the testnet?

[main matrix]

yeah I have that toggled as well

there is also an "unsupported" way to update matter devices, but requires a JSON and an OTA with particular attributes. I haven't come across either for NL.

and the .matter files seem to be encrypted

[plain kettle]

i think there is a way to get the info from the DCL, but i wouldnt wanna risk bricking soemthing

[main matrix]

I have a couple of lights to burn, so...

[opal sparrow]

it's possible that it won't show up as available on the main DCL until the matter certification is done

HA can update nanoleaf devices via matter, but there's some issues with how the nanoleaf firmware is published on the DCL (incorrect "min" version on at least one firmware) which means you might not actually see it.

iirc they published one of the firmware versions with metadata set such that the upgrade is only available for devices which are already running that firmware version.

the way the version numbers are set up, 3.6.196 isn't available for people who are running any previous stable version, since the "min applicable version" 198317 is greater than the "software version" of the previous release, 197910. It might be available for people who were running previous 3.6 beta firmware versions tho.

the download links in the dcl just go to an s3 bucket owned by nanoleaf, so it's entirely possible that they've uploaded new firmware there already while they're still going through the processes of certification and publishing to the dcl :)

i hope they get that right on the next one they do; the "out of the box" experience for people who get old stock bulbs and add them to HA is pretty poor atm, since they don't get the firmware with the matter stability and multi-admin bug fixes.

[humble whale]

Looks like they have been completely focused on Litewave development, for the past half a year. I wonder if they are still committed to improving their Matter implementation.

[craggy plaza]

Watch the following video:

https://www.youtube.com/live/BXdiQjwVCkM?si=XIRnrrU9N1U9oG1S

The part from 18:40 to 19:30 maybe interesting for you. 😉

[green frost]

Not completely. Yes, Nanoleaf is fully committed to Matter and that Thread crap. I am not a fan of Thread but it's here and we are stuck with it. I honestly hope it improves and has a solid implementation. @plain kettle and I have had heated exchanges about Thread. I dislike Thread but I honestly hope that Poshy is correct.

[plain kettle]

Haha yep, we have had our arguments, but we can both agree it needs to mature in an open environment like with matter

[green frost]

Did I mention i dislike Thread. Yeah, I'd rather eat dirt.

[humble whale]

Aqara's T2 smart bulbs will be Matter over Thread. We'll see if they do better than Nanoleaf. I'm pretty happy with their Matter over Thread door sensor, so far.

[green frost]

Consider that Aqara is coming late to the party and has the benefit of the others before, it better be flawless. However, Thread still has s lot of issues to overcome.

[swift phoenix]

I tested the litweave tech with the sense+ and man all lights came on instantly. It made me really upset that matter over thread cannot achieve the same yet. Like the lights are capable of doing that, why cant we just have that happen with matter.

Barely any popcorn effect or anything

[green frost]

Matter dose not support 100% of all features of 100% of all products. Also, Thread is involved and has its own issues.

[opal sparrow]

yeah, the lack of matter controller support for groups (which are actually kinda neat internally, they work using ipv6 multicast to send commands to multiple devices at the same time across both thread and wifi) holds things back a fair bit here :(

that's been a "coming soon" feature in home assistant for quite a while now.

other than that, the main problem i have with matter/thread is some spec issues that make the protocol very talkative when devices are reporting changes, especially when transitions are involved. (nanoleaf has partially worked around this by reducing its reporting interval for some transition updates)

the rest is down to quality of individual device implementations :(

[opal sparrow]

getting matter scene support going would also be nice in combination with groups to reduce command traffic, if you want to quickly switch a bunch of lights to a preset scene where they're all different color/brightness...

(scenes were added in matter 1.3)

[craggy plaza]

Maybe this gets prioritized, when Home Assistant is certified as a Matter fabric.

[craggy plaza]

By the way… Do we already know which Matter library/version is used by the Nanoleaf Essentials? Is it still 1.2 or is it 1.3?

[stark crystal]

It doesn't seem that Nanoleaf is fully committed to Thread (for better or worse). They are still launching plenty of Wi-Fi products. They even launched a new Essentials light model that uses Matter over Wi-Fi.

Personally my Essentials Matter lights have been working well with Thread in recent months. I've had issues in the past with the early firmwares, but that's in the past.

Matter and Thread still need to mature with support for things like Scenes and Matter Binding.

[humble whale]

The Essentials bulb was for Walmart. They talk about it in that video @craggy plaza linked, above.

[green frost]

Nanoleaf is not a one-trick pony. The company, like most, is run on a departmental team model. Each team has projects based on the strengths of that team.

SOFTWARE:
The Matter protocol is mostly established. Easy to implement.
The Wi-Fi protocol is as solid as it gets. Nothing to see here.
The Thread protocol is a nightmare. It is changing almost daily and is not east to understand.

HARDWARE:
The hardware teams are easy. They build a physical device and design the internals to operate within transmission and power requirements. The have to continue introducing new products OR they don't get a paycheck.

The above statements are based on information gained from companies, that I believe were created similar to Nanoleaf. Otherwise, I'm making this up as I go, based on knowledge from days past. In other words, like a doctor, I'm making a best guess based on previous examples.

[stark crystal]

I also saw it on Amazon. And yeah I saw the stream, I understand Nanoleaf wants to continue offering both Wi-Fi and Thread products.

[proven path]

Have you had bad experiences with Thread / Thread devices? I admit that my experience is limited to very specific companies’ products and specific SKUs, but at least with those specific products (one of which is the Essentials Matter + Thread bulbs), and using AppleTVs as hubs, there have been zero issues and fantastic responsiveness.

[green frost]

The Wi-Fi devices just work and I prefer Wi-Fi over Thread. I wish there were a way to skip Thread and just use IPv6 over Wi-Fi.

I understand why IPv6 is need and I also understand why the Thread Border Routers are a big part of the issue. TBR software coders should learn from the early trials and tribulations of BGP.

[proven path]

I suspect the biggest issue with Thread Border Routers is that people don’t realize they need one (despite all the documentation about it). And the come home with things and can’t add them without buying something else.

[undone spire]

That and not power cycling the thread border router when there's connectivity issues.

[opal sparrow]

The other problem that we see on the home assistant side is enthusiasts with complex network setups, where it's difficult to get the correct network routing and mDNS resolution working.

Much easier to set in a typical household network with a single wifi router.

[humble whale]

Wifi loses its ease of use case as soon as you ask for privacy and security, though.

[green frost]

That's an issue with marketing but brings up a good point. Why is there no stand alone TBR that is:

1. Easy to install
2. Inexpensive
3. Built and developed by actual experts in building routers.

[proven path]

Probably needs to be priced at no more than $99 USD - ideally $50 or less

Also, should never need to be manually power-cycled

[green frost]

Name three devices that do not need to be manually power-cycled.

[opal sparrow]

a bunch of the google nest wifi routers have thread routing built-in, but those aren't cheap :/

[green frost]

I ditched all the Google products for Amazon. But... I don't want a TBR that is dependent on an Internet connection.

My entire system is Internet Independent.

[frozen crystal]

I’ll send you a DM with the details. Thank you

[manic plover]

Is it just me, or is someone else experiencing an issue where the app does not display updates to v4 for some devices?

[plain kettle]

I do as well, currently have a ticket open for it, 96543

it sucks as i cant pair my sense + to it

[manic plover]

I have 27 devices with this issue 🙂

Successfully updated ~40 though.

[plain kettle]

i see your in lw0004, which i think is the issue, they havent pulled some devices out of the fixed firmware channel

i said that in the ticket, but the support agent isnt too helpful and im not sure if its being referred to the right people

if i dont hear back by the end of the week imma post it in #1259294662796120174 and see if @green frost can do anything about it going to the right people, as i feel there is more people than just us with this issue that dont know

[manic plover]

Not sure if it's related. I have both devices which were in lw0004 which I updated to 4.1.0 and which are stuck at 4.0.0, and I have devices which were not a part of it, which I updated to 4.1.0 and which are stuck at 3.6.196, ans some stuck at 3.7.21 🤣

[plain kettle]

sheeeesh

[manic plover]

I wonder if they haven't pulled this update for some reason.

[plain kettle]

its possible? unfortunately the easy contact most of the hardware beta/software beta programs had for fixing issue isnt at the company any longer

[manic plover]

I have a device which lost connectivity to the world (both Bluetooth and Thread) after the update. Doesn't respond to power on/off. Didn't do a reset yet, no time 🙂

[plain kettle]

yeah thats roughhhhh

[craggy plaza]

My 26 Nanoleaf bulbs are all on 4.1.0 and work as expected. I also had two bulbs that updated seemingly fine, but the version stayed on the old version. So, I updated these two bulbs again and the right version was shown in the Nanoleaf app.

[plain kettle]

Thing is, im not getting any prompts to update on the offical app

[craggy plaza]

Ok, after the update I still saw the update button. After another update everything was fine.

[frozen crystal]

Weird. That’s the one bug I haven’t experienced and I have 69 GU10s IIRC

I do think that there were some early batch defects though. Apologies if this has been discussed already.

Two died after a few minutes or their first power cycle

Six in total (I think so far) have the flickering and random hue changing issue

Two others occasionally refuse to turn off fully. They just become super-dim white. One of these had the flickering thing too.

A number of others turn on super-dim after power cycling, until given a specific brightness level to adjust to (this doesn’t bother me so much, but I’d be glad to offer them for investigation if helpful)

[plain kettle]

@manic plover

[manic plover]

Thanks, so they pulled the update.

[craggy plaza]

Interesting news. All my bulbs were updated in a 3 week period. I didn't want to update all the bulbs at once and destroy my lighting system all at once. 😃

[frozen crystal]

Most wise

[opal sparrow]

if they're holding back the 4.1.0 update that probably means there's gonna be a lot of dissatisfied sense+ customers who can't use it to control their lights, because they can't update the lights to a supported firmware release :(

so it must have been a pretty bad issue…

I haven't had any problems with my devices on 4.1.0 tho.

[plain kettle]

Yeah, and I’m surprised there isn’t more complaints on reddit etc about it. You’d think it would be a priority to fix, and it wouldn’t have held the update for over a month now

[tardy badger]

hello is there anywhere a docs for the beta api ? I think its not the same as the one I found in the nanoleaf dev website

[swift phoenix]

Difference in 4.1.0 vs 4.1.3?

[plain kettle]

Not sure, and I don’t there will be a way to test seeing as 4.x has been pulled

[green frost]

Reddit is for those that like to complain.
Discord is for those that like solutions.

[plain kettle]

Well, i got an open ticket with this issue (96543) if you wanna push for some answers behind the scene

[opal sparrow]

At some point i should try changing the thread channel again, and see if that issue has been fixed... In an earlier firmware version, changing the thread channel would break the connection between the bulbs and the remotes, presumably because since the remotes weren't participating in the thread network, they got left behind on the old channel.

right now the issue i have with the 4.1.0 firmware is that "pause" is broken (trying to pause sense+ doesn't seem to do anything; lights still work automatically, and going out and back into the control group in the app it shows the state as "on" again)

in particular, pausing motion sensing via long press on buttons on the switch isn't working for me.

[plain kettle]

Oh for sure, I mean. Just a shame they launched this product, which required firmware 4.1 or higher on all the bulbs, and they have pulled all the firmware version required to allow it to work

[opal sparrow]

oh, hah, i said that and then just tested it again and now pausing works for me

oh, no, it didn't, nvm. somehow the lights got unpaused without user input

[swift phoenix]

I’m trying to give
Lights to GF and moving on to another brand

[plain kettle]

Yeah, the lack of transparency around the firmware issues is rather concerning

[split forum]

I have 12 GU10 bulbs and strangely only one got 4.1.3. All the others got 3.6.196.

All my E27 bulbs got 4.1.3 straight away. Very strange.

[opal sparrow]

They didn't publish release notes for 4.1.3 even https://helpdesk.nanoleaf.me/en-US/nanoleaf-essentials-(matter-over-thread)-release-notes-255125

[main matrix]

I can't upgrade any of mine past 4.0 :/. All were on beta though so guessing that has something to do with it. Most are on 3.8 and short of an all GH reboot once a week, work fine.

[opal sparrow]

all my beta devices got 4.1.0 without me having to do anything special (other than switch to the non-beta app), but it looks like they've done a general halt of the firmware rollout, so... :/

[main matrix]

Yeah, something is borked with mine. The beta app shows only some can go to 3.8.6, some 4.0 but none 4.1.x. I feel like it's more hassle than it's worth to try and get them in line.

[swift phoenix]

My beta bulbs are on 4.1.0 and do not see the 4.1.3 update. However new devices I recently bought from firmware below 4.1.0 allow me to upgrade to 4.1.3

Seems they might be the same update just that 4.1.3 is the the release channel version or something

[craggy plaza]

Same…

[craggy plaza]

Did you try it with the general available Nanoleaf app? That was the key for me to get firmware 4.1.3.

[plain kettle]

that doesn’t work either. @main matrix seems to be in the same boat as me with it all

I have a ticket open, but haven’t had a response in a week now lol

[craggy plaza]

Oh… I recognized, that I was wrong. I got firmware 4.1.0 with Nanoleaf GA app. With the Nanoleaf beta app, the latest available firmware was 3.6.196. But round about one week ago, I paired a spare GU10 with the Nanoleaf GA app. It got firmware 4.1.3. So all my bulbs are on 4.1.0, except this one GU10. Sorry, for the wrong information.

[plain kettle]

Ahhh all good

[main matrix]

I might look at "repairing" the lights into the Nanoleaf GA app at some point, unfortunately when that happens the Thread network gets disrupted and half of the Matter devices in HA become unresponsive for a period of time. Not sure whether that is by design, but it's an annoyance I like to try and avoid.

[opal sparrow]

Yeah, I think it's intentional that when you add a device in the Nanoleaf app it reprovisions the thread credentials.

But you will need to switch apps at some point, it doesn't seem like the beta app will continue to get updates (until they start a new beta, I guess)

[plain kettle]

Yeah, seems like they have just left that behind, guess Paul also managed that, as it was quite well ran (beta app updates came out before the GA)

Now it just seems like they are pushing everything to GA

[main matrix]

ah, the classic "UAT is Prod" approach.

and just like that; deleted one light (that was not reachable through the NL GA app) and I've lost 22 MoT devices (NL, Eve and Aqara).

[plain kettle]

[main matrix]

we'll see how long it takes for the network to go stable again, but usually it's about half an hour

HA logs are just littered with "timeouts"

[plain kettle]

Well, this is what I got back

Seems like a generic copy/paste. I never asked about the thread/homekit only bulbs

Maybe this means that the 4.1.x will be releasing the same time? I guess we can only hope

[main matrix]

Can't say I'm surprised at the response (the tickets I've raised in the past have taken 2 weeks to respond only to be told to "turn the light off and on again"). If you throw anything at support that deviates from a "standard" problem, the response is usually of no use.

[plain kettle]

Yeah, @green frost have you had any updates behind the scenes of what is going on,

Not being able to use my sense+ coz the firmware on the sense+ is 4.1 and the lights are on 4.0, it’s ridiculous

[main matrix]

I ended up putting mine back in its packaging, as the battery died within 3 weeks (and is a non standard battery - replacement was $10 for what is essentially a thicker button battery).

[high atlas]

poshy163 has been warned

Reason: Bad word usage

[main matrix]

bot go brrr

[plain kettle]

Ffs

Basically it’s stupid it’s been 2 months and no resolution/ETA, going to ditch it for a relay if it’s not fixed by new years, enough is enough

[main matrix]

I still can't update any of my lights beyond 3.8 as the app thinks no update exists beyond that. 🤷‍♂️

That said they're working, so cbf.

[barren sky]

That's very odd because my beta of it works flawlessly with sense+ so maybe If you do sign up for the beta it should work fine.

[plain kettle]

what firmware version are they on?

[barren sky]

The one they pulled maybe 4.1.0 I think I'm not home to check

[split forum]

I now have 20 gu10 bulbs in 4 rooms and the network is very unstable. some real ones are very often unavailable or respond slowly.

In addition, some lights are on 3.6.196 and the rest on 4.1.3

[craggy plaza]

Do you have many neighboring WiFis? Maybe it’s 2.4GHz interference.

Which ecosystem(s) are you using?

How many Thread Border Routers do you have? Which brand/model?

Any other Thread devices? Are the working as expected?

How many WiFi Access Points do you have? Which 2.4GHz channel(s) did you configure?

Any ZigBee technology in use? Which ZigBee channel is configured? Do you have any ZigBee Hubs?

Which Thread channel do you use?

Thread, ZigBee and 2.4GHz WiFi share the same frequency band.

[split forum]

Homeassistant

Eve Thermostat and Aqara und Eve Sensors for Windows

3 Appletv 4K and Sonnos Stick as Thread Borden Router

3APs with Omada System Channel 1,6,11

Zigbee Channel 15 und Hue Bridge Channel 20

Thread channel i dont know i can See this

why are the lights in the living room not routers?

[craggy plaza]

Wifi channel 11 slightly interferes with the sidelobes of Thread channel 25.

https://www.metageek.com/training/resources/zigbee-wifi-coexistence/

Apple uses Thread channel 25. You can see it in the Home Assistant App.

[craggy plaza]

Your ZigBee channels do not overlap with your Thread channel.

Try to not use the Sonoff stick. Some time ago I tested the radio of HA Yellow. But I lost some Thread devices after some time. When I started to use my Apple Thread Border Routers with HA only, instead of also using the integrated radio, everything got stable.

I have 69 Matter over Thread devices (43 EVE devices, 26 Nanoleaf devices.

I also reduced the Thread traffic by not pairing all devices to Apple Home and Home Assistant. My Nanoleaf bulbs are paired to Home Assistant only, while my EVE devices are paired to Apple Home and Home Assistant. Multi-Admin seems not to be ready for prime time with this many Thread devices.

My EVE devices are paired to both ecosystems, because I do not want to miss the sensor statistics in the EVE app. My wife has the EVE app in daily use.

Besides one of the HA devs said, that there is an issue with Apple TBRs. When you use them with HA exclusively, the Matter OTA update feature of HA doesn’t work. But I want to be able to update my EVE devices. Nanoleaf has its own proprietary protocol for updates via the Nanoleaf app. So I do not necessarily need the OTA feature for Nanoleaf.

How many HomeKit/Matter over Thread devices do you have overall?

[craggy plaza]

Thread devices decide by themselves, in which role the act. Nothing you can change. Read this:

https://openthread.io/guides/thread-primer/node-roles-and-types?hl=de

[plain kettle]

https://www.reddit.com/r/Nanoleaf/comments/1hksaq0/nanoleaf_essentials_matter_over_thread_bulbs_413/

mannnn, so people are saying 4.1.3 is out, yet nothing....

half the people in the thread cant upgrade, something is really wrong with this company

[craggy plaza]

I am one of them. 😅 I don't see the update either.

[plain kettle]

unreal, i really do wonder if we are still tied to the beta firmware

like, there is 0 way for us to manually unenrol our own devices from lw0004, and there seems to be nothing support can do

[craggy plaza]

Yeah, I asked this myself, too.

[plain kettle]

GW doesnt seem to have much of a response either about it all

[craggy plaza]

Hm… However… Merry Christmas. 🎄🎁😉

[plain kettle]

haha you too, even tho in australia we celebrate it on the 25th 🤣

thats only well, 15 mins out for me haha

[barren sky]

Non matter essentials devices have an update too that's 3.0.1. any ideas what it brings?

[plain kettle]

I assume that includes support for the sense+ stuff

[humble whale]

I've never used the beta firmware and I don't see 4.1.3.

[craggy plaza]

This is how it looks here. There is one GU10 bulb with the name ’Badezimmer Spot’ with firmware 4.1.3. This one bulb was not part of the private beta. All other bulbs are on firmware 4.1.0.

[plain kettle]

Crazy, yeah. I’ve still got 0 updates

God, might have to return these, and get some new ones just so I get new serial numbers which are not tied to a beta

[craggy plaza]

Are your bulbs on firmware 4.1.0 or 3.6.196?

[plain kettle]

4.0.0

[craggy plaza]

Oh, 4.0.0 is still behind 4.1.0.

[plain kettle]

I’m not even joking, i can’t even use the sense+ coz they are on different firmware versions

and im not sure how @green frost went with finding out what is going on, i know its holidays but this has been almost 2 months now, its crazy

[craggy plaza]

By the way… I removed my Sense Control, because I had some unnormal behavior in my Thread network. After some days it got unreliable, which I normally do not have. Typically it’s rock solid.

I also lost the sign for Thread connectivity 2 days after I paired my Sense Control to the Nanoleaf app, Apple Home and Home Assistant. But the bulbs were working as expected in Apple Home and Home Assistant. So, the Thread connectivity was still there. After I removed the Sense Control and re-added all bulbs to the Nanoleaf app, the Thread connectivity sign came back. After another start of the Nanoleaf app, all Thread symbols got away again. But then came back slowly within one day.

Now everything works as expected again.

[craggy plaza]

Ufff… It happened again. All Thread connectivity symbols are gone. But all devices are reachable for Home Assistant via Thread and work as expected. Even the Thread Network monitor in the Nanoleaf app works as fine and shows all bulbs as connected. Look at the screen recording.

At the moment I think it’s a glitch in the Nanoleaf app. No Sense Control connected. What do you think about it?

[green frost]

Okay. Forget the symbol. Can you control the products?

[craggy plaza]

No, not via the Nanoleaf app, except the bulbs that are reachable via Bluetooth from my iPhone. But all bulbs are connected and work fine via Matter (over Thread) in Home Assistant.

[opal sparrow]

@craggy plaza from the symptoms, i'd guess that your phone isn't receiving either the mDNS replies or IPv6 router announcements from your thread border router. There's some mdns diagnostic apps available for iphone (i forget the name of the often-recommended one right now) which would be a good first thing to check

what's your network layout look like? any vlans or guest wifi?

[manic plover]

I just need to vent for a minute... I have 3 different versions installed now across all my devices. Can't seem to update no matter what I do. No information from Nanoleaf whatsoever. No news on updates via Thread either. No news on new firmware versions and what's actually being worked on. No information on why they pulled some versions. Just no information 🫤

[split forum]

I have the same problem and I hardly have any contact with the bulbs on my Android devices. They are always offline. My iPad is fine normally.

I also had constant problems with the reliability of the lights in Home Assistant and a lot of mDNS entries in the Matter server.

I deleted all VLANs in my Omada system 3 days ago and since then everything has been running much better in Home Assistant.

Unfortunately, there is little information on how to properly set up the entire WiFi system so that everything works correctly.

[opal sparrow]

yeah, in the home assistant community there's a bunch of people who know what's going on, but not really a whole lot written down outside of individual support posts.

matter is designed to "just work" on typical simple household networks where you have one wifi router, possibly provided by your isp, bridging wifi and ethernet into a single network.

because it relies on protocols that use non-routable local broadcast - specifically, mDNS and IPv6 router announcements.

your matter controller and whatever device you're using for provisioning (typically a phone) have to both be able to resolve mDNS from your thread border router and from wifi matter devices, and also receive ipv6 router announcements from the thread border router.

in theory, thread border routers could support DHCP prefix delegation to get their routable IPv6 prefix, which should integrate into more enterprise-like networks - but very few if any do right now, and that still doesn't solve the mDNS problem. Cross-subnet mDNS repeaters are notoriously troublesome; Unifi's in particular is known to cause issues with matter.

[split forum]

Well, at the moment the bulbs are running very well and the Matter server is almost error-free. But the Nanoleaf app is almost useless. Sometimes I have a connection on my Android devices, but most of the time a few are offline or only connected via Bluetooth. But a lot of people in the Google store have this problem and I think there is also a problem with the Android app.

[opal sparrow]

hmm. not something i've run into personally. using network diagnostic tools on your phone to verify the mdns and ipv6 routing is working should always be the first step there.

it's unfortunate that sense+ makes the app mandatory, since there's no way outside of the app to do anything like enable/disable motion sensing

my understanding is that in order to toggle that, the app has to be able to talk to all of the lights in the control group

[split forum]

well I don't care about the switch, I have the Hue switches and have all automations via HA

[craggy plaza]

Hi guys, I'm currently on winter holiday for one week.

[craggy plaza]

There was not network or firmware update change the last month. There are two apps for iOS (Discovery and Flame). I saw all my devices with both of these mDNS browsers.

[craggy plaza]

I have VLANs. But all relevant devices (iPhones, Macs, Apple Home Hubs/TBRs, Home Assistant) are in the same main VLAN. It worked for some month without any issue. Out of a sudden this started to happen.

[craggy plaza]

Don’t get me wrong. I typically do not have any issue. My 26 Nnaoleaf bulbs are rock solid since we have firmware 3.6.196. so it’s round about half a year without any issue nearly zero issues.

[shell vigil]

Hello everyone, I need to get back to firmwear 3.6.196 who can help me do that ? The last firmware is breaking all my matter network

@spice harness @green frost @boreal surge

[split forum]

Firmware 4.1.3 works just as well, the network crash is caused by using the Nanaoloeaf app, at least that's how it is for me.

I updated all bulbs and removed them from the app because I only use Home Assistant and since then they've worked almost flawlessly.

[manic plover]

I think Thread E27 are discountinued... #general message.

If Nanoleaf is dropping Thread, then... there might never be a good, stable firmware.

[zealous wave]

my thread bulbs work very well. I use a border router from home assistant, which has currently updated to matter 1.4. and I'm waiting for nanoleaf to release a version supporting scenes.

[plain kettle]

atleast you guys can still get firmware updates 🥲

im still on 4.0

[zealous wave]

Have you tried resetting the bulbs?

https://youtu.be/CPad4fDq2iA Factory reset

[plain kettle]

Yes

[zealous wave]

😪

[manic plover]

I'm not getting firmware updates either. My bulbs are currently at 3 or 4 different versions...

[plain kettle]

its stupid, and support isnt helpful at all

[green frost]

Nanoleaf is not dropping Thread. Where did you get that idea?

[plain kettle]

yeah, i dont think they are dropping thread at all, just got some sorta issue with firmware being offered to some devices

[green frost]

Please submit a support ticket on your firmware and I will escalate it immediately. It is poor support that you can't get bulbs to update.

[plain kettle]

already did, 96543

pain hahaha, and other people within lw0004 seem to be having the same issue

cheers for whatever you can manage to do

annoying having the switch on 4.1, and the bulbs on 4.0 and unable to pair

[green frost]

Good information. I can guess at the issue and it does concern lw0004. Maybe @void pulsar can help by clearing all that data from the system,

[plain kettle]

yeah for sure, hopefully resolved soon, will be better than having to return the current bulbs and replacing them to get new S/N

[manic plover]

E27 with Thread are 75-80% off and completely out of stock. As a customer I perceive it as clearance sale/end of life sale.

Same with B22.

I was also a part of LW0004, but not only the devices which were a part of it are affected - I have 50+ devices which were not a part of it and I can't update any of them (the app doesn't see any available updates). Ticket number 111180. Thanks for posting some answers on the thread, I actually feel better knowing that someone from NL is still alive 😅

[green frost]

I suspect that Nanoleaf is making changes to the hardware (this is my guess and I have no proff of this) and firmware. There are no GU10 bulbs in the U.S. and I'm waiting to order 12. I'm in the same situation as many users here.

[opal sparrow]

It sounds to me more like boxing day / end of year sales, tbh. I suspect they sell products quite a bit faster during the holiday season than otherwise, so it might just take a little while before things come back in stock :/

there's definitely some more work being done on the firmware, but I wish there was more transparency on communication so we could know why a lot of devices aren't getting updates.

[void pulsar]

can you message me your email account?

I can take a look as to why you cannot update

[void pulsar]

could you also send me a DM?

FYI

People that are stuck in 4.1.0 instead of 4.1.3 --> This is expected. We did not roll out 4.1.3 to 4.1.0 customers because of a few technical reasons.

The next FW that we will roll out will merge both FW.
However there are no significant differences between the FW

[craggy plaza]

Any information about a release date/period/month/week? Thanks

[void pulsar]

I think it should be around February/March

but don't quote me on this --> Not official

[errant spindle]

And what about 4.1.0 or 4.1.3 for downlights? My Sense+ is for no use any longer 😦

[void pulsar]

@errant spindle which FW are you stuck at?

[errant spindle]

4.0.0 🥲

[woven scaffold]

I stuck in TestNet 4.0.10😬(NL65 Down Light)

[plain kettle]

Can’t upgrade via the Nanoleaf app?

Guess you are stuck on an old firmware as well

[main matrix]

I have also raised a request for my firmware issues (all of my lights are either stuck on 3.6.196 or 3.8.0. None of them can see 4.1.3). Ticket number 111862.

[woven scaffold]

Yes, the Nanoleaf APP cannot detect any new firmware higher than 4.0.10

[green frost]

It can but most firmware updates have been put on hold as the issues are bring worked on to provide a stable release.

[rare aspen]

Is there a plan to extend 4D Sync+ to Essentials in the upcoming iOS beta release of the NL app ?

I read in reddit it was included in the Android beta release of the app

[void pulsar]

it is coming soon @rare aspen

I think in a day or two we will go to prod

the beta release has that already

[rare aspen]

Is that to say there will be a new iOS prod app release ? We are still running 11.1.0.

[void pulsar]

We released 11.2.0 just today

It should be available soon

[plain kettle]

It’s out on iOS

[rare aspen]

Yes ! Just updated ! Let’ s test it now. !! 👍

[rare aspen]

Hello just tested 11.2.0 but even though I've added the Essentials LightStrip and 2 bulbs to be Synced+, nothing happens when I activate 4D. Only Lines are mirroring TV content.

I rebooted the Lightstrip, the bulbs and my iphone with no more luck.

did I miss something ?

[rare aspen]

I eventually made it work ! I had to reinstall 4D controller, one of my bulbs, it took hours, but in the end, it's working like a charm ! GG Nanoleaf !

Synced+ 4D with Lines and Lightstrip.

So immersive !

[main matrix]

so after 10 days of waiting for a response, it's clear whomever is doing Nanoleaf support for tickets do not know how to break away from a scripted response, nor do they read what was provided in the initial support request. @green frost @void pulsar any chance of helping out with this one, please?

[void pulsar]

Message me your serial number

I can take a look

[main matrix]

there's more than 20...

but sure, give me a few minutes

[void pulsar]

Just give me 2-3

I can look up the rest

I am on my way home so my response will be slower

[main matrix]

no problem, thanks

[wary iris]

What exactly did you do to get it to work?

[rare aspen]

I had to reset and resintall the 4D controller entirely, restart my router, restart my Apple TV. And wait until the mesh network is rebuilt. Took some time, so now I won't touch anything 🙂

[wary iris]

I’ll just wait for a fix hopefully it’s soon lol i know it’s not just me having these issues it seems to be basically everyone so hopefully they’ll get it sorted

[barren sky]

Mine doesn’t work either, it’s shown as supported but just doesn’t work so I’ll wait for a fix as well rather than restart everything since it’s a hassle

Also with the sync+ it makes it so slow, when I disabled sync+ the 4D is significantly faster

[rare aspen]

enabling sync+ for Matter over Thread devices makes the whole slower, yes.

I think it would be fine for devices with Matter over Wi-fi.

[rare aspen]

Will the Multicolor Floor Lamp be able to Sync+ with 4D controller ?

looks awesome

[void pulsar]

yes @rare aspen

[void pulsar]

Is it only with Thread devices that it is slow? or even other devices Sync+ is slow

[void pulsar]

It needs your bulb to be on Thread

Can you confirm what FW version you are running and what is your Thread Border router?

[void pulsar]

basically all Nanoleaf products work with 4D now ( with the exception of Sense+ Wireless Switch )

[rare aspen]

Excellent News !

[barren sky]

Everything, I have string lights, HD lightstrip and lines and if I enable anything other than the 4D lights it becomes slow

Might be trying to sync everything but it's too noticeable

[wary iris]

The thread router is my Nanoleaf lines and the version 4.1.0

[wary iris]

I asked Nanoleaf support and got a reply rather quickly, here’s what he said

At the moment, Essentials will work with Sync+ with an upcoming firmware update, but it will also need to be connected via Thread. Unfortunately, we do not have an ETA for when this update will be released yet.

In the meantime, we’ve recently released a new firmware version (4.1.3) for the bulbs

I haven’t seen this firmware show up at all. Nor do I know if this is the firmware that makes it work with sync+ or not. It’s kinda confusing when it says in an app update that it’s working now, but then it doesn’t work, then this guy says it will work in the future and then he says they have an update, which is an update I haven’t gotten 🙃 kinda confused… is it out or not? Lmao

[opal sparrow]

if your essentials bulbs have 4.1.0 then you won't receive the 4.1.3 update (there doesn't appear to be any user-noticable differences between the two). The sync+ firmware is a future version, not yet released.

... i think?

or maybe the support person was misinformed there, i'm not sure

either way, bulbs on version 4.1.0 are up to date and will not receive 4.1.3, but will receive future updates.

[wary iris]

Then why say in the update patch notes that essentials are now supported in sync + that’s so weird. Eh whatever. Guess it’s back to waiting again 🙃

[opal sparrow]

yeah, i honestly don't know the status of sync+, it's not something i use

but from what i've heard, if it's in 4.1.3 it should also be in 4.1.0

[plain kettle]

4.1.3 seems to be even worse than I first through, tons of the down lights seem to go into an unresponsive state for some weird reason, uncontrollable via the app, via light wave (aka the sense+ and obv via thread/matter)

[stark crystal]

4.1.0 has been stable for me for the past few months. All the Essentials Matter bulbs are stable and stay connected to both Home Assistant and Google Home. Also works with my Sense+ switch. I still don't know why 4.1.0 was pulled and replaced with 4.1.3 (which I didn't get).

[stark crystal]

Really glad to see this! Just waiting for Sense+ support now.

[wary iris]

I’ve never even heard of 4.1.3 till now lol I’ve never gotten the update notification and in the last couple I reset my bulb a couple of times to see if I could get sync to work and that didn’t cause the update to push so i dont really know anymore lol but I’m hearing even that update sync doesn’t work so i dont really care lol

[opal sparrow]

since it doesn't seem like they changed much between 4.1.0 and 4.1.3, i wonder if the difference between the two is in the OTA update process rather than the bulb's functionality.

[green frost]

There are bug fixes and tweeks but nothing major from what I can deduce.

[green frost]

Here is the first mention of 4.1.3 from December 5th.

#essentials message

[plain kettle]

Not sure if anyone is having the same, but there is some serious commissioning issues (to matter) on 4.1.3, dispite being within the thread network, and routing traffic, its unable to connect them to external ecosystems (aka during the commisioning phase, its unable to add to apple home, and its showing connected via BLE on the app and cannot still pair)

and also there is many times where you just cannot connect to it even via the app, its odd

[opal sparrow]

that indicates mDNS / SRP issues normally.

if you use an mdns diagnostic tool, are the _ltpdu._udp entries being found for all of your devices?

what are you using as thread border routers?

oh, that's neat. the _ltpdu._udp service data includes the firmware version in it. makes that easy to check remotely.

[green frost]

There are definitely issues that need to be resolved and I wonder if some are in the border router.

[plain kettle]

It’s super odd, it was rock solid on 4.0 and now it’s super flakey

[green frost]

I wonder if having border routers acting on the same network anf same devicex might cause issues. I used only one border router and had few issues.

[plain kettle]

Hmm, slept on it overnight after adding them back into the nanoleaf app, appears now they are showing as "on the thread network" (despite the fact they always were) and i can now share them to other ecosystems via matter, odd

[green frost]

It could be a combination of bugs in the applications and firmware. I wish there was a bugfree border router that all vendors would sign off on that it is good. Then we would have a standard device to test with.

Clearly, Nanoleaf has a lot more work to do.

[main matrix]

might be OTBR regression @plain kettle? I think we both had issues with OTBR being in the mix with Apple/GH (which is why I've left my OTBRs out of the mix and just went GH).

[plain kettle]

yeah iirc thats possible, just sucks that everything else is rock stable, just the 4 downlights. if it breaks again might try to remove the home assistant OTBR's and that seemed to fix it in the earlier betas

[slow wedge]

Am I just experiencing an issue on my side but my A19 Downlight version, is experiencing weird glitches and delays? I have the down lights which is just the A19 but they are on version 4.1.3 instead of 4.1.0 unlike my other A19 bulbs. And the bulbs work fine. Not the Downlight though?..

[tiny gale]

Dumb question: is there a way to restore unresponsive essentials (4.0.1) without resetting them? The power lost status still works but they won’t go online after a power outage.

My essentials just died randomly on each power outage 🥲 some may survive some my not

[humble whale]

Rebooting Home Assistant always works for me. Though, I'm on 4.1.0. Nanoleaf essentials always become unresponsive in HA after a blackout, but are still visible from the Nanoleaf Android app.

[opal sparrow]

Oh, this is weird. my lights on 4.1.0 are showing an available update to 4.1.3 now

I don't know if I should do it or not :)

[plain kettle]

Maybe it’s some sorta RC2?

[opal sparrow]

it's only showing up for my lights tho, not my switches

[plain kettle]

I don’t think the switch even has 4.1.3?

[opal sparrow]

ah, well, i wouldn't know :)

[plain kettle]

I could be wrong hahah, I just never got offered it even after handing over all my serial numbers and getting a pathway from 4.0.0 to 4.1.3

[opal sparrow]

been running all 4.1.0 on my system for a while, and the main issue i have is that pausing sense+ doesn't work properly - it seems to unpause itself without any apparent reason after a while, and i've had it turn on my lights in the middle of the night waking me up.

annoying enough that i usually leave sense+ disabled

and then i use my old zigbee remote rather than the sense+ for manual controls, since it has better ergonomics - and since it goes through home assistant, so lights turn on at the correct color/brightness instead of turning on at last used brightness and getting switched to the current adaptive brightness setting afterwards.

honestly i'm really considering getting separate motion sensors and ditching the sense+... I was really hoping that the sense+ would work as matter presence sensors so i could integrate them better.

[plain kettle]

I haven’t kicked a fuss yet coz I have a eve motion doing that, I only use the on and off button if I wanna override what the motion sensor is controlling

I can see how it’s annoying with only relying on the app and it’s stuff

[opal sparrow]

i picked up an aqara t2 motion/light sensor to use in my entryway/hall and it works well, integrates nicely with HA and my routines. i have it switch between low/high brightness during the day and off/low brightness at night, with times managed by my phone alarm settings.

like, i just wanted the sense+ to be that plus a bunch of buttons that i could use via matter. i don't want any of their proprietary direct light control nonsense :(

[plain kettle]

They must of internally cut back their ambitions post CES release, maybe some key team members left or realised how challenging it would be?

There is no reason all the buttons couldn’t eventually be exposed via matter

[opal sparrow]

matter specs even provide guidance on how to make buttons that can be used both to control devices directly (via matter bindings, but the logic would be similar for lightwave) and also make the buttons simultaneously produce events that can be consumed by a matter controller.

[plain kettle]

It’s a shame they had to use the light wave stuff, if they didn’t and conformed to strict matter/thread they could almost make any light be controlled via the switch

[opal sparrow]

yeah - the problem with that is there is literally no matter controller on the market right now which can set up matter bindings

(that i know of)

not really any spec compliant way to do that via their app, since they can't see or talk to matter devices on a fabric controlled by a different matter controller.

... so they decided to back-channel it, but you think they could at least have back-channeled it over thread rather than run a second protocol on the same radios

now the bulbs have to be mesh members and relay messages for two separate meshes at the same time, which i can't imagine helps people who are already dealing with mesh stability issues on just thread

i will admit that at the time development on the device started, matter over thread wasn't in very good shape for low power sleepy devices.

[tiny gale]

Thx, but I think my essentials are dead. They won’t light up and reset anymore 🥲 Nanoleaf dev asked me to send them back

[opal sparrow]

anyways, put the 4.1.3 firmware on my lights, guess i'll check whether the sense+ pausing works better now

[rocky quail]

I saw 4.1.3 being available now to my A19 bulbs but not the BR30's. My bulbs were already on 4.1.0. Testing it on a few and seeing how it goes.

[opal sparrow]

Ah, I think I figured out what's going on with pause. It looks like sense+ unpauses when the bulbs receive commands from matter.

Which makes pause useless to me, since I want pause sense+ in order to temporarily give matter exclusive control over the bulbs

Specifically, I want to pause it when going to bed, and then have matter controlled fade out / nightlight. Problem is that when I do the fadeout via matter that renewables sense+ - and the after the fadeout my lights turn back on if there's motion.

(obviously it would be better if I didn't have to manually pause sense+ - i.e. if it could be controlled via matter or other API or better if I could use the motion sensor from matter)

[dull dagger]

Anybody else's lights just turning on randomly since 4.13?

[plain kettle]

Not that I know of, you got auto power recovery on in either home assistant (via matter) or in the Nanoleaf app?

[dull dagger]

Oh okay. I suspect it's related to the sense+ switch. I was troubleshooting another problem and playing with the wiring and I think perhaps it didn't delete the wiring because I was getting some messages then my lights were not synced now I suspect there's some ghost wiring to these bulbs that are turning on from the sense+ even though they are not connected at least from the app guess I'll have to do some factory resetting but this is not a good bug

[rare aspen]

Not here. Everyrhing is fine with 4.1.3

[dull dagger]

thanks, they were not randomly turning on, actually, they were turning on with the Sense+. What had happened was I wired these light to the Sense+ and then unwired them. But for some reason, they did not unwire, despite the control group saying they were unwired. I even deleted the control group, but that did not work. A factory reset of the lights seems to have solved the issue.

there was a message in the app saying the lights were not synced in the control group so i pressed synced now, but still the ghost wires were there and the they were still controlling the lights despite it not being in the control group.

its possible there was a temporary communication issue to the bulbs when they were removed supposed to be removed from the control group, but it didn't happen so it remained connected to the Sense+

[rare quail]

Trying to update from 4.1.0 to 4.1.3. All the lights are failing to update. Gets to 15-20% then revers back to 10%. After 2-3 times shows an error. Tried to power cycle everything including my router. Same thing.

[woven scaffold]

There is no official description. Has 4.1.3 FW been put back?

[icy elk]

Same here, after all lights was turned of for an hour (did electrial in the apartment I could upgrade some, and some still refused

[opal sparrow]

it seems like 4.1.3 has been release for people running 4.1.0 yeah. The updates did succeed on all of my devices.

[craggy plaza]

Yeah, I also updated 25 devices from 4.1.0 to 4.1.3. Update procedure was without issues.

[frozen crystal]

Any insight on when Apple Home might include a Matter version which supports device groups (1.4…?)? Nanoleaf firmware 4.1.3 works flawlessly on my whole house of devices, but it’s so tedious that this basic feature is still lacking from Apple Home

[frozen crystal]

Also, when I say “Siri turn on the light”, why do my HomeKit essentials bulbs remember the last brightness setting but my Matter GU10s not? They come on very dimly. Even more strangely, most do this but not all…?! 🤷‍♂️

[opal sparrow]

matter has supported group addressing of devices from the start (it's built on top of ipv6 multicast), as as far as i know it should work with nanoleaf's products.

it's all on the developers of matter controllers to actually support that feature.

(as far as i know, there are no matter controllers which do)

[verbal drift]

So I have a dead GU10 (second one) I know support will want me to send videos of the lamp not working but the pain of going through poor support is not something I want to do. Plus the lamp is dead, it flickered when power on in the morning. After a power cycle at the main switch its now lost the will to live....Anyone of the admins help me get it sorted?

[plain kettle]

Ask in #1259294662796120174, not here

[verbal drift]

got it

[little flame]

hi, what is the latest beta firmware and when did it come out, because i am on 3.02 stable and it doesnt want to find it

[frigid saddle]

To be clear, this thread is about the newer Matter over thread essentials. The 3.02 firmware is for the Homekit over thread essentials and that was only publicly released in the last few weeks to the best of my knowledge. 4.13 nanoleaf Matter public firmware or other Beta Matter firmware can not be installed in the Homekit over thread essentials.

[little flame]

Oh okey

[manic plover]

Hi, I was wondering how it's going, since it's April now 🙂

[frozen crystal]

I have started experiencing GU10s resetting themselves. I have to delete them from the Nanoleaf app and re-add them, including the Matter association to Apple Home. This has happened three times now… (out of approximately 70 bulbs). Anybody else?

[frozen crystal]

I am now experiencing bulbs deleting themself from Apple Home. This has happened with a GU10 and two screw bulbs. Very concerning! Some sort of corruption issue between Nanoleaf app and Apple Home? Anybody else?

[tired cloak]

Hi everyone, my GU10 are working kind of ok-ish but some of them, when I want to turn them on or off they flicker during the transition in different colors/color temperatures. Is this behavior known and are there any suggested solutions? I am using a Sonoff E on channel 15 and a homepod mini as border routers. Firmware is current 4.1.3. I saw that some of them are connected via Bluetooth instead of Thread

[frozen crystal]

I had that issue with a few of them. Some did this from new, others developed it over time. I was told by Nanoleaf that there’s a faulty batch. The ones where it was a severe issue were replaced by support (eventually!)

[frozen crystal]

I have this random turn-on issue too. It only affects lights which are in a Control Group for Sense+. I have tried resetting devices and deleting the group. I noticed it with 4.1.3 but I cannot confirm whether the issue existed with earlier firmware versions too

[tired cloak]

I already replaced nearly all of them by support. I guess from different batches but I don’t know. Any other hints? Are yours working flawlessly now?

[green frost]

Are you guys having issues with the beta applications or product hardware?

[frozen crystal]

Not really. See above. The random turn-on issue is annoying as that was one of the very first issues this group helped Nanoleaf to eradicate. It took a concerted effort. Now it seems to be back with their proprietary connection to Sense+.

A couple show signs that they might develop the flickering colour issue too. I wonder if it’s related to being in situations where they’re frequently being turned on for short times

[frozen crystal]

Historically, both. There are no public software betas at the moment that I am aware of.

My current issues are with production hardware and software. I really hope that device groups in Matter 1.4 will solve my most frustrating issues associated with my large deployment

[tired cloak]

To be honest I tried several different beta and non-beta firmwares but no big change. When I want to turn the lights on/off and they try to fade in/out they flicker. Also within transitions when i try to change color/temperature/brightness. once they have settled in, it looks ok.

But recently I noticed that some of them loose their Thread connection.

As all of them have already been exchanged by the support team I thought this has to be a software issue

[green frost]

It could be a firmware issue with the particular hardware.

[tired cloak]

@green frost do you have any suggestions?

They all report a hardware version 1.1.7

Is there any suggested Channel to use for Thread?

[plain kettle]

No, whatever is less congested

You can check if you are running the google OTBR software the channel density/utilisation

[wide slate]

Yeah all mine keep losing their thread connection, and I have to fsctory reset them and re-set them up again. Its got to be firmware. Not great, only had them since Feb, and ive had to set all of them up about 3 times each periodically now, all at different times

[manic plover]

Is there any news on the new firmware release? Last time we've been given guidance that it will arrive in March or April.

[green frost]

Firmware for which product?

[manic plover]

Thread GU10, E27.

[frozen crystal]

Has anybody experienced an issue where a bulb will reset its pairings and so it needs to be added back to the Nanoleaf and Apple ecosystems (in my case)? This has happened with 4 of my house-load of GU10s

[wide slate]

yes

I have a support ticket open, but they just blamed my thread border router, even though its not that

happened to 5 of my bulbs so far, Apple Home, Thread, E27 and B22 fit

[frozen crystal]

Goodo. I’m not going insane then… I have however become mad with Nanoleaf because of this latest in the long line of shoddy firmware features 😡

[wide slate]

yeah im not impressed either

[frozen crystal]

@green frost do you have visibility of this issue, please? I have a whole house of these things… this does not bode well. Is there a fix in sight? Even a beta to test?

[green frost]

I don't but I will bring this to the attention of those who own the company.

[green frost]

@void pulsar

[frozen crystal]

Thank you very much. Given how unreliable and disruptive it usually is to add Nanoleaf devices back to a large Thread network, this is an urgent issue if this is likely to happen more and more

[green frost]

I think the issue is with a large network. Mine is rather small and I have no issues.

[plain kettle]

i wouldnt be suprised if it couldnt handle the high routing load from bigger networks

[frozen crystal]

With the bulbs dropping off? My failure rate is currently about 5% so statistical probability may be on your side

[frozen crystal]

That is certainly an issue which causes many problems. In this instance it’s why it takes so long to re-add as I have to give the mesh (plenty of) time to stabilise and then hope that I can complete the process before doing so knocks things over again. It’s a real pain.

[plain kettle]

unfortunately, without additional tools (like running the OTBR server independently) its hard to tell how much traffic is actually going through it or the mesh topology

[frozen crystal]

Yep. I’m literally shooting in the dark

[frozen crystal]

Were you able to add the affected bulbs back to Matter/Thread? I’m struggling and I’m trying to work out why

[wide slate]

Mines small and I have issues, but I want to double the size soon

[wide slate]

Yeah, with a factory reset of the bulb, and deleting from the nanoleaf app

[frozen crystal]

Do you have any strong channel 11 wifi networks nearby? I deliberately kept mine on 1 and 6. New neighbours have moved in. I wonder if that’s coincidence. Need to investigate… their AP is only advertising 20MHz though and I don’t see any clients on that channel, so… 🤷‍♂️ https://embeddedcomputing.com/application/networking-5g/visualization-orchestration-management/driving-wi-fi-zigbee-and-thread-coexistence-in-the-2-4-ghz-band-part-1-unmanaged-coexistence

[wide slate]

hmmm possibly

both issues have been in rooms with wifi access points

not channel 11 tho

infact not a channel 11 in sight on environment scan

[wide slate]

well ive set the controllers to exclude channel 11 here now

and deployed 9 extra bulbs to the network

so time will tell

[frozen crystal]

I had no more issues for nearly 2 months but last night 4 more bulbs reset their pairings. This simultaneous timing surely cannot be a coincidence. Have you made any progress with this issue please?

[void pulsar]

@mystic light can you please advice here

[mystic light]

talk to you on DM

[wide slate]

I had 7 last night reset their pairings

[plain kettle]

yeah, i occasionally have them reset their pairings after being powered off (cold) for a long period of time

[wide slate]

really really really annoying me now

lol

[plain kettle]

no firmware update in what? almost a year now?

odd indeed lol

[wide slate]

yep, feels abandoned

[main matrix]

Replaced all mine with Aqara T2s and haven't looked back (bonus is the T2s have both a zigbee and thread radio).

Got sick of all the problems with the Nanoleaf lights.

[upbeat mica]

Same

[undone spire]

Dead company walking

[frigid saddle]

Maybe not the company but their thread efforts (or lack of them) are a dead end for a while now.

Just seems they never developed a reliable Thread based firmware. Understand early adopter issues, but other companies like the T2 above have been to put out better thread firmware in a much short amount of time.

[covert marsh]

It is really sad that there is no further development of the matter essestial bulbs. These are the only one that i tried and have no coil whine... aqara failed and hue to, which is painful for the price that hue takes.

[opal sparrow]

The last word on the subject is fairly recent, from November: #essentials message

So… there is further development of the matter essential bulbs ongoing. With any luck they might have something for us to test early in the new year.

[heavy oak]

Any update on when we might see the next firmware from 4.1.3?

[void pulsar]

Still under development
The next FW should have Thread 1.4 support.