Software Beta for Nanoleaf Essentials Matter

[plain kettle]

The matter server is pretty mature now, so no reason no to

You can share the pairing code from apple home to home assistant

[fallen fulcrum]

I've been using Flame to watch the bulb broadcasts... it seems when you try to pair something repeatedly in a short time, there are multiple addresses broadcast by the same bulb. I've found that just waiting for a while lets the old broadcasts die off

[plain kettle]

Yeah, can take ~30 or so minutes

[fallen fulcrum]

I noticed when I have my matter bulbs turned off and I go into the 4D settings in the nanoleaf app, I can set them to live sync with the tv like the lines can. Then when I power them back on, the setting sticks and the syncing actually works for a while

[brazen canyon]

Ben mentioned there's issues with the essential and 4D and to not use it for now

[fallen fulcrum]

yeah i'm sure that's why its disabled. Just fun to screw around with

[spice harness]

Adding this to the backlog for us to test/investigate, lower priority than the incoming 1.2 stuff so we won't be looking at it immediately. Any videos or further details you can share would be appreciated to speed things up once we pick it up.

Check the oldest pinned message in this post for the instructions on beta enrolment for your devices (if you haven't done so already) 🙂

[brazen canyon]

I'll send a DM but I'm pretty sure it's a spec limitation as the behavior is the same in Google home

[spice harness]

It seemed that way when I last looked at it, will review again when I need a break from other things.

[fallen fulcrum]

I have, thanks!

How would you generate an auth token to communicate with your devices for testing?

[steel hemlock]

1.2 will be rolled out / available for all beta users world wide on Monday? 😍

[stark crystal]

I'm running Google Home (Nest Hub) with Home Assistant (Green + SkyConnect).

Each smart home platform has its benefits: Home Assistant has wide device support (including Zigbee), advanced automations and custom dashboards. Also it can work locally and has the best community in my opinion...

Google Home is easier to use and still has the better voice assistant (even if Home Assistant is making progress in that area too).

I thought it would be really cool having multiple Thread Border Routers in my home, I believed it would make my Thread network super-stable, wasn't that the point? In reality it seems to be the opposite.

This is my Thread network including two Shapes controllers. It's really cool when it works.

[craggy plaza]

By the way… Do we know which Matter version the different eco systems support? I have only Apple Thread Border Routers. But is Apple supporting Matter 1.2 with their latest OS (17.3)?

[plain kettle]

1.2 is the latest iirc?, but matter is backward compatible so it doesn’t really matter

[craggy plaza]

Yes, right, it’s backward compatible. But the latest Matter version on the server may also improve the situation in combination with the Nanoleaf Matter 1.2 bulbs. So, IMO it matters. 😉

[grand pilot]

Home assistant just updated the thread documentation on their site that mentions they don't recommend combining networks at the moment as it causes instability. I removed my sky connect and my lights haven't lost connection at all since.

[craggy plaza]

Yes, that’s true. For testing purposes I also added a SkyConnect to my Apple Thread network. After I lost some devices, not Nanoleaf only, EVE devices also got unavailable, I removed the stick, too. Now I am back to the typical situation. Every now and then I loose some Nanoleaf bulbs in Home Assistant. EVE devices are stable. 😉

Yes, I know EVE and Nanoleaf are not directly comparable. But I do not switch 10 bulbs at once. My automation is switching only two bulbs in parallel, waits a bit and then switches the next two bulbs and so on. That works a bit more reliable.

[brazen canyon]

I don't think that's a universal truth as apple seems to have the most problem

I run sky connect and no issues

[craggy plaza]

Apple is stable for me. Do you have any other Thread Border Router in your network? Sorry, if I already asked. I lost track with all the different setups. 😉

[brazen canyon]

Yeah I have Google, nanoleaf, skyconnect, and an espressif OTBR

[craggy plaza]

Ok, maybe it’s Apple in combination with the SkyConnect. Maybe TREL was the culprit. I used the SkyConnect with TREL, because my Apple Thread network already supports TREL. However, I do not use the SkyConnect at the moment. 😉

[brazen canyon]

I think that's the case

[craggy plaza]

Another question… Did anybody here get the Nanoleaf 1.2 firmware update?

[stark crystal]

What is TREL? I have a SkyConnect but can't find an option to toggle TREL.

[plain kettle]

It’s automatic on OTBR add-on version 2.4.4

You can see the mdns entry if you use a discovery tool

[craggy plaza]

Here is a good description of TREL:

https://github.com/orgs/openthread/discussions/8478#discussioncomment-4315812

[steel hemlock]

It will be released on Monday for the beta users. It is still Sunday. ☺️

[craggy plaza]

Yes, that's right. But there was an offer to volunteer testers to try out the new firmware over the weekend. Alpha tests, if you want to call it that. Some of us sent Ben the serial numbers for this. But well, if nobody has received this firmware yet, then either it couldn't be finalized yet or it didn't pass quality control. However, let's look forward to next week (Monday = tomorrow). 😉

[steel hemlock]

Sorry. You’re right. 👍🏻

[strong rune]

Hi @spice harness I’m trying to troubleshoot an issue I’m having with the Lightstrips (Matter version with firmware 3.5.41, HomeKit network with Apple TVs and HomePods running 17.3). When powered on, they will randomly turn off for about 1 second, then back on again. This tends to happen a few times per hour at random times. Is this a known issue that might be addressed by the beta firmware? I have Eve thread devices (only one with Matter), and many other HomeKit devices, and none of them do this. I keep seeing others describe an issue of lights randomly powering on but I’m not sure it the same cause/issue (when off, my lights stay off). I’ve been going back-and-forth with support for a couple of weeks, but after asking me to perform factory resets and asking me to restart my iPhone, they’re asking for photos and videos of my lights exhibiting the issue which isn’t inspiring confidence.

[steel hemlock]

Hi Tony,
I had the same issue with my light strips in almost the same scenario as yours. The current beta solved this issue for me. …but I agree: the question for videos is kind of frustrating. How should we capture a video of something that is happening random. The support can not help in my opinion. Because of that I simply signed up as a beta user and debug it myself.

[strong rune]

Thanks for sharing! Perhaps I'll give the beta firmware a go. As for the video, I had my iPhone setup on a tripod and managed to capture a video of the lights turning off/on within 15 minutes. I then trimmed the video to a few minutes to make it easier to share and mentioned that in my email (so I could tell them how long the lights were on before they powered themselves off), then they asked for the full video. Then they said they couldn't view the full video and asked for "photos of your Nanoleaf." I just don't understand what they expect to see that will help troubleshoot. Very frustrating.

[steel hemlock]

I had a smiliar experience with the support. Because of that, I am not longer talking to the support as long as the Nanoleaf products do not have a defect.

[brazen canyon]

That's the bulbs crashing, which was somewhat lessened in the beta firmware

[steel hemlock]

Good day everyone. Do we have already an information regarding the time for the new beta software release today?

[plain kettle]

It’s only 4am in Toronto at the moment 🙈

[steel hemlock]

😄 Maybe I forgot the timezone. Greetings from Germany. 😉

[verbal drift]

Greetings from UK

[upbeat mica]

Greetings from Norway. Eagerly awaiting new beta lol

[craggy plaza]

Greetings from Germany 😃

[brazen canyon]

Usually it's been in the late afternoon/early evening in the US, so like 10-12 hours from now

[dapper acorn]

Greetings from Vermont! 🍁

[upbeat mica]

Wish to travel to Vermont one day. It looks beautiful.

[dapper acorn]

We would be more than happy to welcome you! Fall and winter are our best seasons for tourists, summer is best for “GREEN” and winter for skiing :)

Don’t come in spring tho lol

[spice harness]

Good morning/afternoon/evening - thank you to those of you who sent serials to me, even though I know you didn't get an update over the weekend. Unfortunately we ran into some more issues on the candidate 1.2 build in several of our setups late Friday evening (regressions even from the 1.1 builds) so I decided to hold off on pushing that to the small subset of testers. I've got an alternate 1.2 build that I'm going to push to the small group now that I'd like to check performance on before deciding if we make that available to the broader beta group. Stay tuned, thank you for your patience.

[spice harness]

Oh and a sidenote with respect to timezones, most of the Nanoleaf folks that you'll interact with in the Discord are based in Toronto, Canada 🙂 (Eastern)

[upbeat mica]

The whole year sounds amazing, haha. I've been many times to the US but never New England. It's on my bucket list though.

[scenic grove]

New England is wonderful. I'm in the Boston area suburbs myself.

[dapper acorn]

Boston is great, I’ve always loved driving down (granted the highways are crazy compared to vermonts tiny I89 lol)

[steel hemlock]

Is there a known issue in the current beta regarding the following: some GU10 are not turning on/off, stay in a very low dimmed status, are not controllable but are not marked as “offline” in neither the Nanoleaf app or the home app.

[upbeat mica]

Welcome to the club buddy

[stark crystal]

I'm experiencing significant stability improvements since upgrading my Home Assistant SkyConnect multiprotocol firmware to version 2.4.4. It's still not perfect and I'm waiting like everyone for Nanoleaf to release the fixed Matter 1.2 firmware, but still better than before. I just wanted to share for any other Home Assistant SkyConnect users.

[plain kettle]

Multi protocol is by far not recommended; but the OTBR add-on has gotten a 2.4.5 release with some nice fixes and a bump to the version

[stark crystal]

I'm happy to test multiprotocol in my home, it's cool when it works... I hadn't realized 2.4.5 was released!

[lyric panther]

Gave it another try. I reset the bulb, the added it to the nanoleaf app, which worked okay. Then I tried connecting to my HomeKit network and it continues to fail at that. Really bummed about this because my experience with the non-Matter bulbs is still good.

[scenic grove]

So true! We have family in Rutland, VT. Always love the drive out there from here.

[dapper acorn]

That’s awesome! It’s so cool to hear/interact with fellow New Englanders online :)

[scenic grove]

Be careful what you wish for! We are “wicked extra” people sometimes

[dapper acorn]

Yes you are lol. And pardon my French, but you are a flatlander as well

[scenic grove]

Haha

[feral steeple]

My multiprotocal has been pretty stable on this when i switched back from just thread to Multi. Reduced the nanoleaf's to only 16 lights on the network and its been mostly stable with some drops here and there. But im scared to add the other 14 nanoleaf's cause it seemed to be hell when they were on. So hopefully we get a good new firmware soon!

[stark crystal]

Consider yourself lucky if your Thread network is stable. I only have six bulbs (and one Aqara P2 sensor), yet have constant issues. Whether it's the bulbs, Home Assistant or the Nest Hub, my Thread network is never stable for too long.

At least Nanoleaf and Home Assistant are making efforts to fix everything. Google on the other hand fired hundreds of engineers (hopefully not the ones working on Thread).

[steel hemlock]

Now I am even more frustrated that the new release wasn't released on Monday!! (...even tough I understand the reason for it).

[deep notch]

I really hope the update will get released today 😊

[eternal hill]

How does your network setup look like? Sounds like its not only the Nanoleaf bulbs causing trouble for you. Also the Nest Hub is stable.

Also thread + matter uses more data than zigbee, so just because something "works" with zigbee, doesn't mean that it will work with thread and matter.

[eternal hill]

i would not get my hopes up 😦

[stark crystal]

@eternal hill I sent my Thread network topography above. Nest Hub might be stable on its own but not together with Home Assistant. It's better with the current SkyConnect multiprotocol firmware but still crashes sometimes.

[eternal hill]

What happens if you remove the sky connect from your thread network?

Are you sure you need that many border router for this few bulbs?

When you run a border router on the same device as home assistant, right now all traffic into the network is routed through the sky connect.

The answers still take the most effective path, but maybe the sky connect just has a really bad connection into the network?

Another thing I have problems with are bulbs in a lamp kind of like this https://www.lampemesteren.com/joffrey-4-ceiling-lamp-l80-nickel-lindby.aspx
I think it’s acting a bit like a faraday cage

[brazen canyon]

I've got two nest hubs, skyconnect, nanoleaf BR, and another OTBR and don't have any stability problems so I wonder if there isn't something else going on

[eternal hill]

One of the problems might be that he's running multiprotocol.

[stark crystal]

As far as I can tell these are my Thread instability issues:

1. Nanoleaf bulbs (waiting for Matter 1.2 firmware).
2. Buggy Silicon Labs Multiprotocol firmware (slightly improved with the current version).
3. Combined multi-vendor Thread network (the updated Home Assistant Thread documentation recommends against this).

These issues combine into my Thread network crashing often.

Now that I know what the issues are I am willing to put up with them, I am patiently waiting for Silicon Labs, Nanoleaf and Home Assistant teams to push fixed firmwares.

Sometimes factory resetting my Nest Hub fixes the Thread network. I don't know what causes that

[tranquil pollen]

The Home Assistant team recently did a live stream on Matter and recommended removing the multi protocol firmware from SkyConnect and just running it with the OTBR add on for Thread only. There’s instructions on the SkyConnect website.

[grand pilot]

To add to this, they also say combining apple or Google Networks with the skyconnect is known to cause stability issues.

Since I removed mine none of my thread devices have gone offline yet. Now I just have two nest hubs and nest WiFi pro for border routers for now.

[eternal hill]

What does fixing mean?

[eternal hill]

Im having a somewhat stable network with 13 nanoleaf bulbs, 2 google nest hubs an apple homepod mini + an "skyconnect" (some thread rcp running on an wireless gecko)

[plain kettle]

Yeah, you can’t really “fix” a network by just removing a device and re-adding it

[eternal hill]

That really depends

If removing an otbr makes the thread network choosing another route out of the network for a while that does not go through a problematic device, it could totally "fix" it.

[stark crystal]

In detail, the issues with my Thread network started a month ago. Before that, everything was stable, then I started having issues. My best estimation is that something was causing the Thread network to crash (I don't know whether it's the bulbs, the Nest Hub or SkyConnect).

Factory resetting the Nest Hub solved the issue, but then the Thread network would crash again every couple of days. Eventually I got tired of constantly factory resetting the Nest Hub. I found out that if I wait long enough eventually the Thread network recovers by itself (this can sometimes take hours).

Now with the current SkyConnect firmware (2.4.4) these crashes happen much less often. It was particularly bad with the previous firmware.

[eternal hill]

But does crashing mean that all devices die? And are they just connected to home assistant or also to google home? Maybe its your srp server thats acting up for whatever reason.

[stark crystal]

I don't know what SRP is. Crashed Thread server means ALL Thread devices in my network were unavailable (not just Nanoleaf). Occasionally they worked via only one of the platforms (Google Home or Home Assistant), but usually both would stop working at the same time. Nanoleaf app always works (via Bluetooth fallback).

Anyway I'm not going to troubleshoot it further. Right now it's working fine and will improve with Matter 1.2

[eternal hill]

Not the crashing of your network.

[stark crystal]

Home Assistant is aware of these issues and working on them. Seems like 2024 is "Year of Matter" for Home Assistant.

[frozen crystal]

I have now had 4 GU10 bulbs seemingly die. They respond fine on the network but no longer illuminate. Has anybody else suffered these early-life failures? I’m not looking forward to picking this up with support 🙄

[plain kettle]

@spice harness…. Might wanna help out here

[frozen crystal]

Shhhh… I don’t want to distract him from far more important jobs 🤣

[plain kettle]

Well, he did say he would personally help out on any issues. So if it turns out to be bricked, no doubt you will ship back + get new ones

He would no doubt roll back your firmware first tho, to confirm

[lyric panther]

Is it possible to remove our matter bulbs from the beta?

[void pulsar]

@lyric panther it might not be the best idea to revert a FW haha
We can try though 😛

Just to give you all an update

• If your devices do get bricked like @plain kettle mentioned --> We will issue a replacement
• For the next bigger update. We are very close but we found issues in which our devices were bricked. So hopefully in the coming days we will push out an update to this group with a lot of the issues fixed ( fingers crossed 😄 )

[lyric panther]

I'm just kind of tired of my bulb not working with homekit.

[steel hemlock]

I totally agree. Neither the official release nor the current beta works stable, unfortunately. It is such a big effort for every customer, far more effort for those of them debugging and trying to fix the issues on their own. Lost time with an expensive customer (friendly) product that we won’t get back… 😢
But, it is not the fault of the devs and because of that this is the wrong place to complain about it. Let‘s wait for the next software update. ☺️

[feral steeple]

Thats great, do we need to do anything to get in for the update, or it will just be available to people who have signed up for the beta stuff?

[midnight solstice]

Hi all, new member here. Been working on stabilizing my Essentials Matter bulbs for a few months, didn't realize there was a Discord server and Beta program that I could participate in until this week.

I have 7 bulbs (mix of A19 and BR30) using the latest GA firmware (3.5.41) that are paired with HomeKit. They are also paired to Home Assistant via the Matter Server Add-on. I don't have a simple network situation, 3 VLANs, which complicates things quite a bit, but I think I've worked out the network kinks for the most part.

When the bulbs work, they work great. Based on discussion in here, I'm clearly not alone in having the bulbs sporadically change to an unreachable/unavailable state. In my Matter Server logs, I see messages like below:

2024-01-31 08:35:45 core-matter-server chip.DMG[126] ERROR Subscription Liveness timeout with SubscriptionID = 0x92d6613d, Peer = 01:0000000000000003
2024-01-31 08:35:45 core-matter-server matter_server.server.device_controller.[node 3][126] INFO Previous subscription failed with Error: 50, re-subscribing in 0 ms...
2024-01-31 08:36:01 core-matter-server root[126] INFO Re-subscription succeeded!
2024-01-31 08:36:01 core-matter-server matter_server.server.device_controller.[node 3][126] INFO Re-Subscription succeeded

Anyway, I signed up for Beta updates, and I am prepared to help test and debug. Is it a good idea to go ahead and update to 3.6.94, or should I wait for the release being discussed above?

[plain kettle]

These logs are more HA specific and not really helpful to Nanoleaf as a whole. And the idea of Vlans is not at all compatible with matter/thread

[midnight solstice]

Here is History from Home Assistant from the last day or so; you can see the lines and gaps where the bulbs go unavailable.

[midnight solstice]

Yes, I solved that by putting HA on the same VLAN as the bulbs and other devices. Is has multiple interfaces.

[midnight solstice]

Sorry for my ignorance, is there somewhere that I can get logs specific to Nanoleaf? I haven't seen anything like that. HA is the only place I've been able to get any visibility into what is actually going on.

[plain kettle]

Most likely not, sillabs would have their own internal debugging tools, but just telling them what we see visually/somewhat debugging from the HA logs can be sorta helpful

But the HA logs were more or less designed for the team to debug it themselves as to if it’s a server issue, or device issue

[brazen canyon]

Youd need to identify the node and correlate that to the specific bulb and check which firmware it has. I suspect that the node id listed there corresponds to the GA firmware, which is prone to crashing and forgetting it's subscription, hence the error in the logs

[humble whale]

Is there any software or tools that a software developer from outside of Nanoleaf could use to diagnose Matter-over-Thread device problems? HA logs provide very little insight.

[brazen canyon]

No NL won't provide their internal debugging tools but HA and basic networking tools should be more than enough to triage some problems. That said, it seems the current issues are clear on NL end and they are just working to resolve them. There's nothing we can do to reconcile SDK and library compatibility

[boreal surge]

Hi everyone—new to Discord, I'll be starting to help our product teams scale up and systematize our beta initiatives in the near future. Our goal is to really deepen our technical engagement with the community of folks like you and continually improve. I just wanted to say thank you for your contributions and look forward to chatting 😃

[frozen crystal]

This is a genuinely exciting development. Thank you

[plain kettle]

Huh wow, impressive to see. Good improvement lads

[steel hemlock]

Do you already have news on the software progress, too? 😉

[civic elbow]

This is very welcome, thanks for the update 😊

[verbal drift]

Welcome and thanks for the info

[void pulsar]

Just to add what @brazen canyon already mentioned. We are not able to provide a dev tools that gives more logging than the open source tools that are already there.

No reason for that except for our debugging we have special development boards that we use and the production hardware does not have the capabilities ( at least not easily configurable )

[midnight solstice]

Thanks @void pulsar; understood. My other question remains; is it a good idea to go ahead and update to 3.6.94, or should I wait for the release that was being discussed? I don’t mind bleeding edge, but I’d rather avoid bricking any of my lights if there is a known issue. 🙂

[upbeat mica]

Will there be a new beta this week?

[feral steeple]

If you want to wait, wait, but 3.6.94 is a lot more stable than the production firmware

[void pulsar]

@midnight solstice 3.6.94 should not brick your device

@upbeat mica Yes we want to do a beta this week. However we also wanted to do a beta FW last week 😄 but we ran into some critical issues. So I don't have a firm date not because we are trying to "hide" the date but we want to make sure it passes our internal test cases before shipping it to you all.

[upbeat mica]

Not in my experience

[rare aspen]

same here

[eternal hill]

Have you actually found the real reason why the bulbs are crashing sometimes? Its good that it has improved, shouldn’t the problem that actually is causing it be fixed instead of reduced? Or are there just multiple causes?

[wild oracle]

nothing super pre-packaged. if you're familiar with routes, netstat helps. Discovery (https://apps.apple.com/ca/app/discovery-dns-sd-browser/id305441017) is super useful

[wild oracle]

HA, as you mentioned. Apple has profiles you can install as Home Network Diagnostics https://developer.apple.com/bug-reporting/profiles-and-logs/?name=home

note these logs are not "specific to nanoleaf" but would have information relating to your Matter connected Nanoleaf devices that can help with diagnostics

[eternal hill]

set it to debug logging.

[boreal surge]

hah! 🙂 Let me get my bearings a little bit. Improving communication with folks who are trying out prototype hw and sw is something I'm keen on. And, I'm always open-ears when it comes to suggestions on how to improve. The space that I'll be occupying with our product teams is kind of an insights researcher / analyst / scrum master / community manager rolled into one.

[wild oracle]

3.6.126 has been released. It uses Matter 1.1, where we've found things to be more stable broadly. It should also have fixes for lights turning on unexpectedly and flashing unexpectedly. Keep us posted on what you're seeing.

[shell vigil]

Started downloading will check my 40 Nanoleaf essentials how they’ll work 😂 fingers crossed if I will divorce or stay married … these lights are causing issues in my marriage

[steel hemlock]

Roll out is in progress!

[craggy plaza]

I am using alpha version 3.6.115. Should I expect issues, when downgrading the bulbs from Matter 1.2 to 1.1?

[wild oracle]

nope. for any users who had persistent unreachable on .115, this should resolve if they havent already reset

[craggy plaza]

I have resetted them after the update to .115 because of that. So I shouldn’t need to reset them again?

[wild oracle]

correct, they should continue

[shell vigil]

Nathan, if the lights are flickering and the wrong color is chosen despite all of them are grouped, one of them has wrong color turning on especially white color would that be a firmewear or a hardware issue ?

[deep notch]

I've done the update, right now, it's already better, all my bulbs are back on HomeAssistant (before I had 3 bulbs that didn't wanted to re-register even with a reboot)

[upbeat mica]

Firmware. I got the same problem.

[plain kettle]

you also on the HA beta for Core and the beta matter server?

[shell vigil]

I hope, for a group I choose white or blue , it appear pink or cold white , apart from some of them flickering

[upbeat mica]

Just go into the individual bulbs and go back and forth on the colors, eventually it'll display it correctly.

[deep notch]

Nope, HA and Matter are not in beta, I currently have 2024.1.5 for HA and 5.0.4 for Matter

[shell vigil]

Yes it does , that’s what I usually do. It has been like that through all the beta. It’s good to have some fun on the way 😂

[plain kettle]

is anyone running the new fw with the (beta) HA core 2024.2.0 b1 and matter server beta?

[deep notch]

It's not too instable and if I have something more instable than now, it would be really hard with my girlfriend 😅

[upbeat mica]

Yeah, lol. This beta seem better, currently. Only two of my bulbs flicker and stuff now. Hopefully they'll fix it all eventually.

[shell vigil]

Hahaha we have same issues with partners, I have the divorce papers ready because of NL

[shell vigil]

I have noticed once they got better and less flickering on one the beta application in test flight after installing it. I still had beta firmeware installed

[brazen canyon]

I'm having a hell of a time updating

[shell vigil]

What do you mean ? Do you have issues ?

Mine some of them have errors , I move to the next one. Sometime the app crashes and I reopen it, I go back to the one that had errors and it update again

[brazen canyon]

Yeah unreachable in the app

[shell vigil]

Yeah I noticed they went unreachable after I reached half of them, I think it broke the thread network ,

[haughty grove]

Updated 10 minutes ago and already had my first spontaneous bulb turn on

[frozen crystal]

It would be super to have an “update next” queue for firmware updates. I can leave my phone in one place and comfortably reach 20-30 bulbs over Bluetooth. It’s a pain to have to keep going back to manually fire off another three

[brazen canyon]

What are your secrets? I can't connect to 3 when I'm touching them 😭

[shell vigil]

100%

[scenic grove]

@wild oracle I have 2 bulbs that are not updating and i'll DM you the details. I suspect they need a little push and i think i know why. I'll give you the details in a DM.

[shell vigil]

Is anyone having difficulties with the firmeware ? Some of my bulbs or not responding in Apple home app

[brazen canyon]

The vast majority of mine are unreachable in HA and in the NL app

There might be a lot of remeshing going on with devices going down for the update so I'm not ready to throw the firmware out yet

[brazen canyon]

Seems mine have settled down now

[craggy plaza]

Are you using the beta Nanoleaf iOS app? I also recognized that nearly all bulbs lost their Thread connection with 10.4.0, when I upgrade my bulbs to 3.6.115. So, I downgraded from the TestFlight app (10.4.0) to the latest GA App from Apple AppStore (10.3.0) and all was good. But I did not upgrade all my bulbs to the latest alpha. I want to wait a bit.

[craggy plaza]

So the question is whether a re-mesh procedure is normal if you update many thread routers at the same time and they are not available for a short moment during the update.

[brazen canyon]

I think so

[craggy plaza]

You are a Google/Android user… 😃

[brazen canyon]

The real test is can the nanoleaf bulb limit be breached

If things look good tomorrow I will try

[craggy plaza]

The question is if the crashes are solved, if the proactive case resubscription works and the lights stop switching on by themselves. 😉

[brazen canyon]

Yes but I'd also like to use more than the 12 bulbs I have deployed too

[craggy plaza]

Yeah, when they solved the crashes, the ’limit‘ is hopefully gone.

[dull dagger]

Surprise FW update now 3.6.126

Fingers crossed

[lime willow]

Damn. My two light strips were actually pretty stable in the last beta (minus lots of trouble initially commissioning them.) Upgraded them both to 3.1.126 this afternoon and now one of them went unresponsive. Boo

[dull dagger]

One of my light strips is being a bit stubborn. I deleted it from HA but now I cannot add it back. It add no problem to the NL app, but when I try to add to HA immediately after a device reset, it goes to the part where it creates HA credentials the light flashes on and off, but then says error that I have to be on the same network. But I am...any tips/tricks to get it back in HA? I even tried transferring it from the NL app to HA... but still no success.

[lime willow]

Power loss recovery settings still don’t stick with this firmware either 😦

[dull dagger]

Yes I am

[steel hemlock]

First feedback from my side regarding the newest beta firmware:

The update itself was done successful without any issues.
All automations are still working and all the devices are responding.
The flickering still appears, but not that often and not on that many devices.
The behavior, that bulbs are turned on in the wrong color, does still exist, unfortunately. The same bulbs (even after resetting them) are turning on in a cold white or pink, sometimes blue. Even though this color is not set in the turn-on automation. When the same automation for these bulbs is triggered a second time, the color is set right.

Edit: It seems that the flickering is always happening on the same bulbs.

[steel hemlock]

To be honest: 3.6.94 bricked on of my bulbs, at least. The one bulb was not reacting to anything in HomeKit nor Nanoleaf. A reset didn't change anything. Couldn't even pair it anymore after resetting. Had to switch it with one of my backup bulbs.

[shell vigil]

Same , 3 bulbs as well turned on at night above my head

[verbal drift]

So I am on the non-beta app and see the update, tried to apply to a couple of lamps and boom, now they have gone offline saying no response in Apple Home and just a grey broken connection icon. So all my matter lamps are showing offline, I have about 10 lamps. Thats nuts as I only tried a couple and all matter NL lamps are offline and just checked my two Matter plugs are showing offline.

So does this mean something caused the matter over thread to break something. By the way this is even before they got the update.

Do I need the NL beta app from Testflight?

[rare aspen]

Just installed 3.6.126 FW -> makes the Bulb (matter only) fully reachable from HomeKit and Nanoleaf app. Works perfectly fine so far.

[brazen canyon]

Did the devices ever come back for you? I had a similar experience but it was just my network remeshing and everything resolved after about an hour

[verbal drift]

rebooting the devices sorted it

[brazen canyon]

I've not had the problems the others have described (yet). Single admin HA setup. No random light turning on last night and no weird/unexpected colors. I'm going to add some additional bulbs today to see if the stability has really improved

[swift phoenix]

Think it might be bricked. My GF had a HomeKit version bulb that when you reset it, the color was different. When you tried to set it to green it would turn yellow.

[verbal drift]

So after updating to .126 lamps are dropping between offline, bluetooth and back to thread. Is this by design or will they settle down.

[upbeat mica]

Pretty much the same experience here

[verbal drift]

Right now, I would say this .126 is not good at all. Happy to be proven wrong but...still bouncing through the various stages of offline, BT and thread and back again.

[dull dagger]

So far .126 has been good for me. 7 hrs no disconnects, but I cannot seem to add back a device to HA anymore. Had adding devices changed since prebeta?

[brazen canyon]

For me it settled down. Updating brings the node down (router) so routes are updated

[brazen canyon]

I added two this morning without issue

[dull dagger]

Can you tell me how? Thanks

[brazen canyon]

I updated them in the NL app, removed them from NL app, put them in pairing mode via power cycling, then added them in HA using add matter device

[verbal drift]

mine have been cycling through the various offline, BT, Thread modes.

[brazen canyon]

I don't use the NL app except to update so I can't speak to that. I've seen the same thing in the NL app even when other apps report things as stable so I've kinda written that off as unreliable

[verbal drift]

yeah I get that, but the fact the devices are dropping off Apple Home suggests a bigger issue than just the NL app.

[brazen canyon]

Ah okay. I only run home assistant so can only comment on that

[carmine skiff]

I have to strips on fw 3.5.41 and 3 bulbs that were on 3.6.96. All 5 I had provised using iOS on Google home, as Google Home on android was failing on "Generating Matter Credentials" step. This has been working for ~3 weeks. Then without any change ( that I know of. Google Nest Hub fw upgrade??), 2 of the 3 bulbs stopped responding, even in the nanoleaf app. I factory reset the 3 bulbs and upgraded to 3.6.126. But to no avail. I cannot add the bulbs to google home on either Android("Generating Matter Credentials) or iOS("Unable to add accessory"). Can anybody help?

[magic tartan]

same problem here, cannot add them to Goggle home via my Iphone

[craggy plaza]

Did you reset the bulbs to factory defaults? You only have a short period of time to commission the bulbs to your favorite ecosystem after the reset. I I not use Google, only Apple Home and Home Assistant. And I didn’t find the time until now to update them from the alpha firmware to latest beta firmware.

[dull dagger]

Thanks I think I just have to keep trying. This device happens to be also the furthest away from the thread border router so that could be part of the issue

And it's the LED strip not the a19. I find the A19 is much easier to deal with

[magic tartan]

ja reseted them, the message pairing failed pops up

bit i use pairing code, QR wont get scanned on my Iphone

[brazen canyon]

I'm on Android/ Google so maybe iOS specific?

[magic tartan]

adding them to NL app works fine, only GH and HA

[carmine skiff]

Yes, multiple times. And rebooted my google nest home

[magic tartan]

tested it with android, didnt work. GH and HA

[craggy plaza]

At First I always pair a new Nanoleaf Matter bulb to my Apple Home by scanning the QR code. When that was successful, I use the sharing code from Apple Home to pair the device with Home Assistant. In the last step I pair the device with the Nanoleaf app.

If the device should get a new firmware in the first step, I pair it to the Nanoleaf app, update it to the latest firmware, delete it from the Nanoleaf app, factory reset it, and start over with pairing to Apple Home, to Home Assistant, to Nanoleaf app.

I also use an iPhone to pair my devices. But I never paired a device to Google Home via iOS. Does this work with other devices or is it a general issue?

[magic tartan]

it worked with other devices finde, dont have any router from apple

i guess its a problem with new firmware, i tested it with on bulb an firmware 3.5.41 and it woked instant (direct add to HA with ios)

[carmine skiff]

So for fw 3.6.196, provisiong doesn't work but 3.5.41 does?

[magic tartan]

fw 3.6.196?

i am on 3.6.126 with the A19 bulbs

[magic tartan]

for paring it, the fw 3.5.41 has problems with staying online bit thats known

[carmine skiff]

Sorry , yes 126

Ok, So the beta helps the thread connections issues, but introduces matter pairing issues?

[magic tartan]

yes tested it 3 more times and i am not able to connect it to HA or GH on fw 126, with IOS

i also test it 2x with android, didnt work

[magic tartan]

on android it fails on "Network connection is checked"

[carmine skiff]

Ok, Thanks for the feedback. I will leave my 2 working essential strip as is. I have put back my Sengled Zigbee bulbs in the mean time. I'll give them time to work on the firmware

[magic tartan]

good idea, i reseted all 5 and now i am not able to add them back in🙂

[brazen canyon]

I've still got the phantom light turn on issue

[verbal drift]

ok after a good 4 hours the lamps look stable, lets see how this progresses.

[spice harness]

For anybody still seeing lights turning on spontaneously, can you confirm what model it is? (A19/A60, GU10, BR30, lightstrip, recessed downlight)

[shell vigil]

Both

A19 and gu 10

In my case, yesterday night I had A19 next to my bed turning on in my face and one gu10 turning on above my head

One in the kitchen gu10 and another in the living room

In total 4

Never had the light strip turning on

[dull dagger]

not sure if this helps NL, bud these are the logs when I try to add/transfer to HA via the NL app
http://pastie.org/p/1CdU0lxST219AKw12LwujI

[brazen canyon]

A19 only for me so far. (I own a19 br30 and strips)

I think it's possibly related to the NL app. As on the previous .96 FW other people reported the problem but I didn't have it but I also did not have bulbs in the NL app. As of now I have some, including ones that spontaneously turned on

@shell vigil do you have your bulbs in the NL app?

[shell vigil]

Yes I have the Nanoleaf app and the HomeKit

[brazen canyon]

I'm going to try to remove my bulbs from the NL app this afternoon and see if the issue persists

[shell vigil]

But always to remember I have 35 nanaoleaf devices mostly gu10

So my thread network is very unstable because of that and always causing issues on all formeware so far

And for the time being I still don’t have big hopes that it will ever be fixed , I might need to switch to different smart home devices and platforms that are more reliable

[brazen canyon]

Yes but if thread instability was causing the lights to come on, I wouldn't have the issue since I only have about 12 atm

[shell vigil]

No not the thread itself rather than the NL Thread configuration

[brazen canyon]

? I don't understand

[lyric panther]

I updated the bulb firmware 3.6.126 and still can't add it to Home.

[upbeat mica]

Some of my GU10s will spontaneously dim.

[shell vigil]

Me too

😂

[haughty grove]

GU10

[feral steeple]

I updated half of mine to test and see what happens 🙂

[eternal hill]

Gu10

[eternal hill]

https://tenor.com/view/wongwingchun58-gif-15613675

When do we get the nanoleaf essentials ben edition?

[spice harness]

It's quite funny you say this because for quite a while, my place has been the golden sample where things magically work even when they fail in other environments 😄 This has unfortunately not been the case during the 3.6 rollercoaster but I am back to stable here with 3.6.126...

And noted, looks like GU10 majority from the small sample size + some A19.

[lyric panther]

Is there anything else I could/should try to get the bulb into Home?

[lime willow]

Yeah my Lightstrip that dropped off Thread after the firmware upgrade still hasn't recovered. I tried power cycling last night too.

Anything specific to try/test before I just factory reset it?

[dull dagger]

so, people are talking about possibly bricked devices, if the devices is bricked would it be completly non-functional, or just flakey? I'm having lots trouble with one of my essentials light strip. It seems to add to the nanoleaf app, but I cannot add it to Google or HA

[wild oracle]

flickering is never expected. If you have good steps, a video would be great. send to @boreal surge . I believe @shell vigil saw similar.

[wild oracle]

if all devices go unreachable in Apple Home, its possible something may have also broken with the Border Router. Easiest way to check is power cycle the border router(s). We've been tracking a number of issues on various types.

[wild oracle]

design should be stable on Thread, BLE as a fallback option.

[brazen canyon]

Okay I'm also adding in to the reports of unpairable devices. I was able to pair 2 BR30 this morning, but I can't add anymore a19 s in any configuration (Google home, home assistant, or shared from NL app)

Prayers to the machine god not helping either

[dull dagger]

yes, that is what im talking about BUT there is a bug in the HA app that prevents this right now...but not with Google

so it should add to google

but it simply does not for me

[brazen canyon]

Same issue

I can't add to GH either

[dull dagger]

im the same too, must be FW related...I also updated the NL app (android) there was a Jan 30 update, but that did not help

But it concerning as the device does not seem to play well with even the app.

How close does it have to be to a thread border router? This one is about 25 ft away

[brazen canyon]

Same behavior on my a19 which is in direct line of sight of a BR

But my paired bulbs are quite stable

[dull dagger]

good to know we're expercing the same.

[brazen canyon]

Maybe I just got lucky earlier

[dull dagger]

My other concern this is how am I even going to update this device now

[brazen canyon]

@dull dagger also getting the discovery failed message

When trying to pair

[shell vigil]

@wild oracle @boreal surge there you go, these are grouped bulbs

The last turn on didn’t turn on

And sometimes It changes color even if I selected different color

[dull dagger]

if you were having a party, it would actually be a good effect 🙂

[shell vigil]

Now because I played with them a lot they became unreachable 😂😂

[shell vigil]

Yeah especially that I have few in each group making this 😂

[modest pumice]

I want to join the softlock/brick party

I've got a pile of GU10 bulbs in a track that haven't been able to get a stable thread network going. I moved the TBR (elements) into the same room and disconnected all but a couple bulbs, but still no dice

Tried on stable firmware, then 3.6.94 and now 3.6.126, with no further success

Removed all the bulbs from the app to see if I could start over, and the first one being added back in can't find the thread network, but doesn't fall back to BLE either, so is just totally unresponsive

[dull dagger]

this is what im experiencing...which has me concerned if I can even update it anymore

[brazen canyon]

Okay lights turning on not related to having bulbs in the app

[boreal surge]

Thanks Ed. I've seen this in GU10s also. @spice harness will log in Jira.

[boreal surge]

@shell vigil forgive me if I missed this detail above—you're using iOS or Android? And, when you experience the flickering was the device connected to the Thread network or had it fallen back to BTLE ?

[feral steeple]

Not sure if its related to the new firmware or not, but since updating it (and accidentally resent a bulb) I cannot add it to Google home again. It just sits generating matter credentials for ages then errors.

[frozen crystal]

“You’ve set up your light in another app. Complete the setup to access all features.” A large amount of my lights seem to have suddenly lost all of their settings in the Nanoleaf app (bulb groups, ability to set Scenes…). I didn’t provoke it by doing anything strange. Anybody else had this? iOS, Apple Home

[swift phoenix]

A19 here turned on randomly still

[frozen crystal]

GU10. (My other bulbs are all HomeKit)

[brazen heart]

A19 here, 6 bulbs in all, HomeKit. Still randomly turning on.

[alpine ore]

This is a bloody nightmare. I’ve reset all 21 of my GU10 bulbs, paired and connected to the Nanoleaf app (without renaming or connecting to Matter, as Nanoleaf’s pairing procedure doesn’t allow me to identify them, and Matter pairing failed initially so I just skipped it for subsequent bulbs), and now they’re all unreachable in the Nanoleaf app so I can’t even connect them to Matter! Furthermore, they appear to be reachable only for about 10 seconds after a power cycle — which is obviously not long enough to pair with Matter.

@void pulsar @boreal surge @spice harness sorry for the ping, but any help with the above would be greatly appreciated. More info about my setup (but not specific to this issue) can be found in ticket 10770. Again, all devices have been reset and now I fear having to go through the process of resetting them all — again!

The attached video in my reply below demonstrates the issues I’m facing. I turned my lights (a group of 4) on at the switch about 2 seconds before opening the Nanoleaf app, then didn’t touch it again.

[eternal hill]

My bulbs have started transforming into light strips

[eternal hill]

I’m at a point where I have almost memorised some of my setup codes 😂

[blazing meadow]

Same as what others are reporting, 3.6.126 NL67 + reset => Bluetooth through the app is OK but I can't add the bulb to either GH or SmartThings with Matter.

[swift phoenix]

RIP 🪦

[brazen canyon]

I have a literal print out spreadsheet posted to the wall of my office

[scenic grove]

Looks like all my matter bulbs dropped off the thread network and never came back after I rebooted my WiFi network tonight to test

[strong rune]

I took the plunge and 3.6.94 seemed to fix my issue (and didn’t create new ones). I’ve since moved to 3.6.126 and the lights haven’t crashed while I’ve been present anyways. I know there’s still bugs for some, but they must be on the right track.

[brazen canyon]

Yeah stability for paired bulbs seems a lot better to me. Problem is I can't pair bulbs on 126

[scenic grove]

Seems like when the home hubs can’t internet things get very weird. Powercycling my bulbs doesn’t seem to be letting them hop back on at the moment will wait to see what settled

[tranquil pollen]

My down lights are still having the spontaneous power cycle but the new beta firmware hasn’t shown up for them yet. A19 seem good so far.

[eternal hill]

They can’t crash a thread network if they never join it in the first place

https://tenor.com/view/tkt-smart-gif-20642718

[alpine ore]

It took 3 hours, but I finally got them all connected and updated to 3.6.126 and that seems to have helped a lot… with the Nanoleaf app, but now some are simply not responding to Apple Home (via Matter) — always ‘no response’ no matter what! I didn’t have this issue before the reset…

[shell vigil]

iOS, it does that when I change color and turn on and off. It is connected to thread

I just select the scene in Apple home or just chenage the colors or brightness

[shell vigil]

Try to turn off your electricity completely wait 5 min and turn back on

[steel hemlock]

@wild oracle @spice harness will be hard to force this behavior and capture it. It seems for me, at last, that I can not reproduce it when I manual trigger the automations. But I will try it tomorrow. @shell vigil did a good capture that shows my behavior. How have you been enable to reproduce it manually?

[alpine ore]

My dearest Nanoleaf, WTF is this UX?

Watch me struggle to connect my 4 GU10s in my bedroom to Matter — feat. Nanoleaf app crashes, Matter errors, unreliable/unreachable connectivity, and more!

Note: every time I terminate Nanoleaf.app, I turn my lights off at the switch for a few seconds.

Even after 20 mins of screen recording (which follows over an hour of similar attempts), it doesn’t work. Not happy 😐.

[quiet sky]

I have the same issues but then with Android and Home Assistant. It is just not possible to add the essentials to Home Assistant via Matter. Always connectivity issues!

[alpine ore]

I even have a day % bar widget on my home screen so that I can obtain a greater sense of how much of my life is being wasted by this product.

And the worst part is that there’s no way to enter a dev mode and obtain detailed logging or patch the app (without a jailbreak) or bulb firmware myself to try and fix it, even if I’m technically capable of doing so. Ngl, right to repair should extend to all dependant source code IMO, but I guess that breaks capitalism, right? 😅

[brazen canyon]

The NL app is fairly unreliable in my experience. I try to avoid it except for updating bulbs. My recommendation is always to just add bulbs directly to whatever platform you're using (but it seems not even that is working now)

Also note that that bulb isn't connected to thread so that's part of the problem also

[magic tartan]

How can i go back to an older fw? Cause i would add them to HA and then update again so thex are more reliable

[brazen canyon]

You can't unless the NL people do some manual stuff

FWIW @wild oracle @boreal surge

Pairing from reset directly to matter controller: discovery failure
Sharing from NL app (pairing to matter hub): case exchange error

[wind finch]

Strange, I have absolutely zero issues connecting the bulbs via Matter to Apple Home, bulbs are always reliable and responsive as well.
My only problem is then trying to add them to an additional Matter controller, like HomeAssistant (or I even tried Google Home) it just keeps failing.

[swift phoenix]

Woke up today and one of my bulbs are randomly on.

[dapper acorn]

I’ve been away from home, but about once a day to once every two days somebody at home tells be a random light it on, ranging from my 4D, to my matter bulbs, and I’m guessing my shapes will do it next.

[ornate obsidian]

Yeah, unfortunately 126 seems to be the worst I have had so far - had trouble updating a few of the bulbs, reset one of them just to see - it then updated, but now can't get it back even onto the Apple thread network

i'm looking forward to trying out the Matter 1.2 builds....

[rare aspen]

my A19 matter only bulb is working continuously stable with .126

[manic plover]

I updated all of my devices today. Posting my learnings as it might help someone and can serve as feedback for the team.

1. I have to disable my border router before updating. It's impossible to update over Thread, I need to use Bluetooth (updates over Thread hang at "processing" and eventually fail). Bulbs which are connected to Thread don't seem to be able to connect to my phone over Bluetooth, or maybe the update process defaults to Thread. After disabling my Thread border router, I can connect over Bluetooth and update.

2. It seems that the app can only connect to 10-20 devices at a time. To update all lights I need to turn off all circuit breakers, then turn them on one by one (1 breaker = 1 room ~ 6-12 devices). Then I can connect to the lights in that room and update.

3. Connectivity status in the app (icons on the list of devices) shows incorrect statuses - I have devices with a Bluetooth icon next to them, which are disconnected (update button is grayed out and the "identify" option throws an error that the device is disconnected).

4. It seems that the device state/connectivity doesn't refresh. When I force-stop the app and clean the cache, on the next launch it immediately finds more devices. Sometimes I need to clear the storage as well.

5. A queueing mechanism for updates + auto-retry would be tremendously useful. The limit of 3 devices doesn't work with the number of devices I have.

6. Version 126 seems less stable than 94 I've been using before. On 94 lights were disconnecting after executing a command, if I was not expecting any commands, all would eventually connect. On 126 they connect and disconnect spontaneously. In addition, 126 seems to have some meshing problems, or maybe it's an effect of overall instability - lights which are further away from the border router don't connect at all.

[feral steeple]

Guess i wont be getting the 2 lights that reset themselves back onto GH or HA anytime soon 😦

[manic plover]

Small update: after a few hours most of the bulbs connected.

Two rooms are entirely offline (all bulbs in two rooms), in the remaining rooms all are connected. That's different than with 94, maybe some devices will be elected as mesh extenders and these two rooms will also connect (I wish!).

I tried turning all the lights off for the night and it worked, all connected lights turned off. I haven't seen everything work with previous firmware versions.

Once they turned off, some went offline, but less than on 94. They also reconnected quicker.

So I might have been wrong in saying that this version is a regression, it just needs quite some time (6-8h?) to get going.

[alpine ore]

Tried adding via Apple Home and the setup codes, but to no avail. Still getting the same Matter pairing failure — just this time without all the Nanoleaf.app bugs.

[frozen crystal]

Ah well, I’m glad it’s not just me. I guess tomorrow I’ll be doing other DIY rather than finishing setting up lights then 🙄🤦‍♂️

[alpine ore]

At least I can update the lights via the Nanoleaf app, but dear lord I need some technical assistance from Nanoleaf here because I’m truly at my wits end.

[brazen canyon]

It's the weekend so you won't hear back until monday

[alpine ore]

Yeah 😐 although I have a support ticket which has been open since December and I still haven’t heard back, despite providing 10 minutes of YouTube videos explaining everything they could possibly need.

I would argue that they make it particularly difficult for themselves by not providing any logging mechanism. That’s literally the first thing we do when we build a new product — and we keep it in production so that users can help us debug issues… yet it’s missing here, in what is undoubtedly the buggiest product I have ever experienced in my 21 years on this planet.

[brazen canyon]

There are logging and debugging mechanisms, they just aren't in the NL app.

#1184371187464290344 message

[plain kettle]

and it should be kept that way

[alpine ore]

Ahh that’s useful, thanks! This should be documented somewhere… I really had to dig around to find this thread in the first place!

[plain kettle]

not really, its not meant to be used by most people

and if you know about it, you know about it and what its meant to be used for

and throwing out just a spam of what you see in the mdns discovery app can cause more harm than someone giving targeted feedback

[craggy plaza]

Ok, here is my feedback.

Firmware 3.6.115 (alpha, Matter 1.2):

After the update from 3.6.94 beta to this alpha version all bulbs got unavailable in Apple Home and Home Assistant. I had to factory reset all of them to get them back to life.

My pairing procedure worked without unexpected issues:

1. pair to Apple Home
2. pair to Home Assistant
3. pair to Nanoleaf app
   Seldom it didn’t want to pair to Home Assistant. But I found out that works really well, to do step 1 and 2 very quickly one after the other.

I had 14 bulbs paired to Apple Home and Home Assistant. They felt really snappy, no late reactions when switching on/off a group of 2 or 3 bulbs.

But every day I lost some bulbs in Home Assistant and they didn’t get available even after waiting one day. I suspect that the proactive case resubscription didn’t work after a bulb crash. These bulbs always worked as expected in Apple Home, while unavailable in Home Assistant. This issue was always solvable by removing the respective bulb from current for 10 seconds. 5 minutes later it was available for Apple Home and Home Assistant. So in this case the proactive case resubscription was seemingly working fine.

Seldom I had bulbs available in Home Assistant, while unavailable in Apple Home. Never before I had it that way around. This issue was not solvable by removing it from current. It got solved by itself after some hours.

At last I removed 3 bulbs to get back to the magical limit of 11 bulbs, but the issues remained. .

————————

Firmware 3.6.126

So I decided to upgrade my 11 bulbs to the latest beta.

Update procedure was fine for 10 bulbs. It was not possible to update the 1 remaining bulb. I force closed the Nanoleaf app and removed it from current, but it didn’t help. I had to reset it to factory defaults, pair it to Apple Home > Home Assistant > Nanoleaf app. After that the firmware update worked as expected.

Another bulb was unavailable in Apple Home and Home Assistant, while it worked in the Nanoleaf app. Removing it from current didn’t help. I decided to reset it to factory defaults. After that I ran into the issue some of you also had. It was not possible to pair it to Apple Home anymore. But it’s possible to pair it to the Nanoleaf app. So we can update the bulb to the next firmware and it’s not bricked. I have some more bulbs in the beta program, that are not paired at the moment. So I took one of them, paired to Apple Home > Home Assistant > Nanoleaf app and updated it to the currently available beta firmware without issues.

At the moment all bulbs are available in Apple Home and Home Assistant

———————

EDIT: One day later I had several unavailable bulbs in Home Assistant. Always solvable by removing the respective bulbs from current. So, proactive case resubscription is not working after a bulb crash or whatever makes it unavailable. Some bulbs also switched on by themselves over the day.

[brazen canyon]

Did you manage to pair a bulb after reset that was on .126? Seems a lot of us having that issue

[eternal hill]

How are people supposed to log the issues? Solder an usb to ttl cable to the bulbs and plug it into their pc?

[craggy plaza]

Yes, I ran into that issue with one bulb. I couldn’t pair it to Apple Home anymore. This bulb lies on my desk now and waits for the next firmware update. It can be paired to the Nanoleaf app, but not to Apple Home or Home Assistant.

[plain kettle]

so bluetooth still works, but not thread

rightio

[craggy plaza]

I am unsure. Nanoleaf App says it’s paired to my Thread network. The commissioning process of Matter uses Bluetooth. 😃

[eternal hill]

just to exchange the initial thread credentials

[plain kettle]

yeah, but the nanoleaf app communicates over their propriety ble connection, hence the fact it works when your close to them

[eternal hill]

They also still publish mdns entries over thread

[plain kettle]

huh right

[eternal hill]

But after restarting my apple home 2 days ago, they haven't come online again 😦

[craggy plaza]

Yes, I know that, but you said that thread doesn’t work. Nanoleaf app says it’s successfully paired to my Thread network in the commissiong process and I see the Thread logo.

[plain kettle]

thats super strange

i guess it technically is?

but doesnt mean its working 😆

[craggy plaza]

Who knows…

[eternal hill]

I had them connected to apple home on the newest firmware

[craggy plaza]

I didn’t check that for that bulb…

[craggy plaza]

Ok, that’s hard. So it can happen to all of us. When we have to restart our Apple Home, all bulbs don’t come back. I had that with the alpha firmware. But it was possible to reset and re-pair them.

[eternal hill]

At least for me

Maybe try it yourself

😄

You could be lucky

[craggy plaza]

And what do you do now? Did you have some other bulbs lying around?

[eternal hill]

I have a shelly in all my outlets

[brazen canyon]

I suspect this busted in this FW. I was able at one point to commission BR30 over IP, but now I get various discovery errors

[eternal hill]

yeah me too

But the alternative is waiting a few days every "release" for them to completely test every firmware

Or magically add logging to a crashing chip. Maybe they can use IPoAC for that 🙃

[plain kettle]

what?!? are you telling me a closed source company wont give away ways to log and possible root into their devices?!?!?

[brazen canyon]

Yeah they mentioned the prod bulbs don't even have some of the debugging tools

So it's not even an option

[plain kettle]

which is normal honestly

[craggy plaza]

The great thing is, that my Nanoleafs do not disturb/crash my complete Thread network anymore. My 37 EVE devices (24 Matter over Thread, 13 HomeKit over Thread) are working absolutely stable.

[main matrix]

now that you've said that out loud... 🙃

[plain kettle]

no doubt nanoleaf have a few MG24 dev kits around the place for debugging

i could imagine a world where nanoleaf use nordic chips, instead of sillabs 😪

[eternal hill]

its the main chip crashing. Its really hard to "log" that.

[plain kettle]

yeah i understand that, i was more being sarcastic. as no doubt the dev kits have a way of doing it

but you would never expect anything like that in modern day products

[eternal hill]

Even when you have access to the pcb and software it can be a struggle to actually log everything.

And when you have logging enabled it actually can change some timings.

Or a debugger connected to a board

[craggy plaza]

@eternal hill Why did you have to restart your Apple Home?

In the past I often did that to get all Nanoleaf bulbs and EVE devices back to life.

2 weeks ago I exchanged some of my Sonos speakers to HomePods. Now I have 7 Apple Thread Border Routers in my house (2 hardwired AppleTV 4K 3rd Gen, 4 HomePod Mini and one HomePod v2). Sadly Sonos doesn’t have Thread Radios in their speakers and sadly Apple has no Subwoofers and soundbars. One of my Apple TVs is always the active Apple Home Hub. It works really great. Read a lot of Horror stories on Reddit about HomePods as the Home Hub. Until now I can not acknowledge this.

[eternal hill]

My HA otbr stopped working 😦 So tried to restart my apple home to test if it works, but later found out that my HA otbr was in a different thread network for some reason.

So it was completely unrealated.

[craggy plaza]

I have to say that I like the HomePods and the integration to Apple Music. It works much better than Alexa with Apple Music. Now we have to speak to Siri instead of Alexa. Siri is not much better, it’s different… 🤣

[eternal hill]

Often its also the 0.5% of people that have problems you see writing online, not the 99.5% where it works

[craggy plaza]

Ufff….

I also have Shellys for all my HomePods and AppleTVs for the case I have to reboot my complete Apple Home. I do not want to run through the house to unplug/replug them. And I recognized that I can’t do this with EVE plugs. When you remove all your Thread Border Routers from current, you can’t control EVE Thread devices anymore. So I needed something that works reliable with over WiFi…

[eternal hill]

Your main fuse 😂

But it should hopefully not be nessecary anymore in a few months

[craggy plaza]

Yeah the main fuse. How do I tell that my wife? 🤣 IMO she kills me, when I start playing with the main fuse.

You called my house a poor man’s castle. Sadly I do not have fuses for every room or every outlet. My father-in-law built the power cabling here 40 years ago. 4 rooms are connected to one fuse. So this fuse has the same purpose like a main fuse. 😂

The Shellys are perfectly fine for this job…

[eternal hill]

Maybe trigger it then, then you need to go there to turn it back on 😄

[alpine ore]

I don’t see how documenting this for advanced users somewhere on Nanoleaf’s site would cause any issues!

[alpine ore]

They could’ve potentially enabled local logging in the bulbs + offloading via Bluetooth, or even with the current hardware, logging between the Nanoleaf app and the bulbs — heartbeat logs alone would help with figuring out where the fault is.

[eternal hill]

So the bulbs would constantly write to their internal flash?

Have you ever done anything with embedded products?

A heartbeat is not gonna debug this.

[alpine ore]

Doesn’t mean it shouldn’t be the standard! Who owns the device I purchased? Me or Nanoleaf? 😉

[alpine ore]

Not sure how big it is, but the last ~1,000 lines before a fault surely wouldn’t be too difficult. Or is the embedded processor not fast enough to be doing that?

[alpine ore]

Yeah, not commercially though. Just as a side project.

[alpine ore]

How so? For connectivity issues, I would’ve thought that a heartbeat (continual logging of the connection state) would help!

I’m always interested to learn more, if I’ve made a mistake or am unaware of something :)

[eternal hill]

You either need to put that into the limited amount of ram of your product or wear out your flash in no time.

And most of the internal libaries don't have any logs.

Unless you have a debugger connected there is rarely much to see in the logs

[alpine ore]

why can’t everyone just implement logging, it’s not difficult and is a good code practice.

[eternal hill]

in embedded products?

[alpine ore]

Yeah! It could be a runtime flag enabled temporarily or based on certain event triggers.

Maybe someone just needs to build a logging library for embedded products with built-in solutions like that.

(And then people need to use it.)

[alpine ore]

What’s the difference between embedded flash and the flash I have in my phone (aside from the obvious capacity and speed differences)? Are these chips not as durable?

It’s not like the GU10s are a budget option, and a couple extra quid for more longevity and better technical support would be worth it IMO.

[brazen canyon]

The chip in the bulb has like 1.5 MB flash so logging would eat an insane number of write calls. All memory/storage has a limited number of writes including your phone

NL has dev boards with embedded debuggers to help track issues

So they have a variety of test setups

[plain kettle]

Seems like someone here has never worked around or with limited hardware in SOC’s before 🙈

[steel hemlock]

Unfortunately, since yesterday we are facing the behavior that lights are turning on themself and are unreachable.
My wife is turning crazy because of this. As a customer, we are troubleshooting Nanoleaf devices since several months now. This should not be a task for the customer.
I am starting to consider a return of all devices including a refund (fyi). I know the devs are working on it, but especially my wife cannot handle this any longer.

The Nanoleaf support cannot help at all. The tickets are getting answered after several weeks with "default" replies. Within two days of now reply from my side, the tickets are getting closed.
As a customer, you do not get the attention you should in my opinion.

Any advice from the devs? ❤️ Getting a little bit frustrated.

[brazen canyon]

Look, I'm not associated with NL at all and I'm not going to defend the state of the hardware, but what more do you want them to do? They've added more staff to organize the beta program here and it's clearly an issue upstream with firmware from the chip manufacturer. You can scroll up and see the current state of things ( @craggy plaza has a nice write up here #1184371187464290344 message including experience with the 1.2 build).

If I were you, I'd set a deadline for myself (If things aren't resolved in X firmware updates or Y weeks I'm going to return them). I don't think they can provide you a date when it's going to be fixed because they are relying on the chip manufacturer to some extent to resolve the issue

[steel hemlock]

As stated in my comment: I asked for an advice, if they have one. Not more, not less.

In addition: I have already set a deadline for myself. But the fact that the normal support is not useful in these cases, it will take a lot of time to ask and argue for a refund. This means even with a deadline, you will need to spend a lot more time discussing this step with the support.

[brazen canyon]

They're gonna tell you they're close and it should be fixed soon

Just being real

I'm not confident in that myself

[steel hemlock]

Yes, this could be answer. But from a technical point of view, this answer can't be true. If you look at the past (beta) firmware releases, I can not see a big improvement. Scrolling and reading through the experiences with the releases in this forum, on Reddit and my own experience kind of prove this.

Maybe the switch to the 1.2 build will change a lot. I hope for it.

[brazen canyon]

As I mentioned there was feedback about 1.2 here #1184371187464290344 message and it doesn't seem like it was a massive improvement either

[verbal drift]

Since the initial hiccup seem things to be much more stable

[rare aspen]

hello team, was just wondering when we would get a beta FW that would enable Sync+ with Essentials ?

[plain kettle]

lets just get bulbs working at all first 🙃

[eternal hill]

at least he's willing to learn 🙂

[eternal hill]

It's not and scales badly

A companies use millions to save a few cents on making software work on the smallest chip possible.

[alpine ore]

Damn, really? How does it scale badly?

[eternal hill]

Because you increase the cost pr product for some "debugging" functionallity that might not be used later on.

[alpine ore]

I guess. But in this case, it was obviously a premature launch, so it would’ve made sense to launch an open beta with better debugging capabilities to start with, IMO. From a consumer perspective, it sure beats purchasing a device which is expected to work, then finding out it doesn’t.

[eternal hill]

i really don't think it was the plan to release a product that is working as badly as it is right now.

[humble whale]

Well, you don't see car manufacturers using this as an excuse: "it's not our fault the wheels fall off, it's just the wheel manufacturer. We've added more staff to work around the issue." It was Nanoleaf's responsibility to find a reliable chip before selling their product. The chip manufacturer's failures do not justify @steel hemlock's support experience, either.

[alpine ore]

Perhaps, but clearly they could’ve benefitted from another round of testing :P

[brazen canyon]

I mean Boeing just did that lol

[plain kettle]

to be fair, nanoleaf couldnt of expected 1.2 to be much more taxing than when they initally released the bulbs on the very lightweight 1.0 spec

i have slight empathy for them, but im glad to see a more open beta approach to their products

[civic elbow]

Since the update three of my lights have randomly turned on. Here is where I am. Someone from Nanoleaf needs to tell me where and how I get a refund for these bulbs. I purchased them off Amazon. Do I need to contact Amazon or do I need to contact Nanoleaf directly

[plain kettle]

what country you from?

[civic elbow]

Uk

[plain kettle]

amazon

[civic elbow]

Thank you

[plain kettle]

uk has decent consumer protection, so if you detail all your issues with amazon, they should offer a refund w/ return of the product

[civic elbow]

Perfect, thank you

[frozen crystal]

This does not bode well for Nanoleaf if we are all returning the product…

Perhaps there’s some form of incentive to be considered for active participation in the beta. Otherwise this may not play out too well, and non-beta consumers even less likely to have their issues tested at scale

I have just disconnected the GU10s in my less-used rooms as, despite them at last joining the mesh with the new beta, network response was unusable in the rooms I did care about. Shame… I thought we had had a real breakthrough!

[craggy plaza]

One day later: I had several unavailable bulbs in Home Assistant. Always solvable by removing the respective bulbs from current. So, proactive case resubscription is not working after a bulb crash or whatever makes it unavailable. Some bulbs also switched on by themselves over the day. I reduced from 11 to 9 bulbs. Too many bulbs got unavailable in that short period of time.

[stark crystal]

Wasn't this the same issue that the HomeKit Essentials line had? It was expected to be upgraded to Matter, but turned out to be too underpowered for that. Hence the new Essentials Matter line.

[frozen crystal]

Argh, I hope not. I still say that my HomeKit essentials are the most bullet proof devices in my home. I had evangelised Nanoleaf to many as a result. And now this… 🤦‍♂️🤦‍♂️

[stark crystal]

Your HomeKit bulbs are fine, they are just never going to get upgraded to Matter.

[frozen crystal]

I know. Amen to that. Matter brings only unnecessary computational complexity for our Apple-only network and we absolutely love Adaptive Lighting

Let’s hope that one day I’ll feel similarly enthusiastic about the Matter bulbs 🙄

[brazen canyon]

So there's no adaptive lighting through homekit on the matter ones?

[frozen crystal]

Nope. @spice harness gave a super explanation somewhere above. I’ll look for it later. It sounded promising that it shouldn’t be too far away in the spec once controller and device vendors have agreed the colour change profiles

I hope he wasn’t just placating me 🤣

[brazen canyon]

Ah I just assumed it was something apple implemented on their own

[frozen crystal]

Yeah but I guess as they don’t own the standard for how the target bulb needs to respond, that needs to be agreed, specified and implemented in Matter

[eternal hill]

That’s not Nanoleaf fault though. In the beginning of the development of matter it was supposed to be able to run on less powerful chips. Also the spec just says that some more capabilities are needed (like acl entries), but this does not mean that they are used.

[brazen canyon]

Well I just say that because home assistant has adaptive lighting that's bulb agnostic so I was curious especially since I don't have homekit

[worthy grove]

Since updating to 3.6.126 one of three bulbs turned on by itself today. Power Loss Recovery switched off by itself on all three of them over the weekend. Yesterday two bulbs flickered intermittently when switched on or off, but that fixed itself after some time. I’ve never seen flickering on any bulb before. Finally, it’s not possible to share any of the bulbs with 3.6.126 from Apple Home to a new matter controller.

I only have 3 GU10’s active in one room at the moment and I will return my other 12 GU10’s and 1 E27. I‘m now waiting for almost three months for a working firmware and I've reached the end of my patience. Don‘t get me wrong but for me this product is in early access state and should have never been released to the broad masses. Like others I‘ve spend hours testing an unfinished product but paid for a product that should simply just work. Never seen such problems with my other Matter over Thread devices from Eve and Aqara. Beside the firmware problems it took me three weeks and two tries to get an answer to my return request.

[feral steeple]

@spice harness What is the process with a dodgy bulb? (Considering support never responds) One of my bulbs is completely checking in and responds to commands, but zero light is coming out of it at all. On a software side it looks like its fine, but the light is just dead.

[plain kettle]

what fw version?

[feral steeple]

It was one I had not updated to the new FW yet (so still .94) , and after the problem occurred I updated it to the new firmware and it is still doing the same thing 😦

[midnight solstice]

I took the plunge and updated to 3.6.126. The biggest change for me is the same as @craggy plaza reported, I cannot keep the bulbs alive in Home Assistant anymore. For me it hasn't been so simple as turning off power for 10 second power cycle... it has been much more finicky than that. Of my 2 A19 and 5 BR30's, only 1 BR30 is available in HA. At one point I had all but 1 BR30 responding.

[wild oracle]

for those seeing bulbs turning on randomly, 126 closed a number of places we thought it could have occurred from. obviously havent caught them all. we have at least one working theory that centers around voltage fluctuations coincident events. If you have observations that back that, or alternative coincident events you suspect may speak to what else occurs around it (e.g. Home Assistant logs, or for the bold, sysdiagnose logs) that would be helpful. We have yet to catch it on debug devices (yes, they have wires soldered). We've experimented with logs over bluetooth - the tricky bit is the heisenberg effect. Most critical issues around connectivity often have timing related dependencies. If you're blasting logs over wireless, it tends to disrupt those flows

[swift phoenix]

The lights bulb turning on seems to happen more consistently in this build then it did in the previous build number. However it seems to only be occurring with 1 bulb at a time. I have 10 A19 in my apartment

I shut off my lights and go to bed. When I wake up 1 bulb is usually turned on

[brazen canyon]

I also see it happen at night and in some cases, to one of two bulbs in the same light kit. If it was a voltage fluctuation I'd expect it to be both bulbs since they are wired in parallel.

Also since we see this happen frequently at night (myself and others) when grid and house load is the lowest, so you'd expect voltage fluctuations at the lowest then

As far as logs in HA we don't see anything since no commands are being sent from HA. We would have to set debug level logging and filter by node which would take time and I suspect we wouldn't see anything anyways (again no commands originating from HA)

[craggy plaza]

The light just came on above me. I then checked the state in Home Assistant. That bulb is still available, but another bulb in the same room went to unavailable about 15 minutes earlier.

[brazen canyon]

I think someone in here has Shelly's in the circuit with the bulbs which would provide some info

[craggy plaza]

@eternal hill has Shellys in the circuit, if I understood this right:

#1184371187464290344 message

[brazen canyon]

Ive also seen the turn on behavior while the bulb is already turned on

[plain kettle]

it just resets to a default colour?

[brazen canyon]

No it goes to full brightness

I have two bulbs that I use as a night light at like 10% brightness and when they have the event occur, they end up at 100%

But if the event happens to bulbs that are off, they go to their previous brightness they were at before being turned off

[worthy grove]

All of my three GU10‘s are installed in the same ceiling lamp and only one turned on by itself.

[plain kettle]

huh right. interesting

[eternal hill]

Yes, i have Shellies in front of all my devices.

I can collect some data for you.

[brazen canyon]

Seems pretty easy if you have the bulbs come on, just check the voltage at the time

[craggy plaza]

Was that bulb available in Home Assistant, when it happened. Any other bulb got unavailable, while it happened?

[brazen canyon]

No they're always available, before, during, and after

[worthy grove]

Can you turn the bulb off right after it turned on by itself?

[brazen canyon]

My guess is it's related to the PLR behavior as people have said it's screwy in the app

[brazen canyon]

I can

[craggy plaza]

I do not use the app, only for updates.

[brazen canyon]

Yes but if the PLR behavior is being reported in strange ways in the app, could indicate it's not working correctly on device, regardless if you use the app or not

[craggy plaza]

Ok, but what about the other bulbs? Is there any bulb unavailable, when a bulb switches on by itself?

[brazen canyon]

Nope

[craggy plaza]

Hm…

[brazen canyon]

This update has been stable connectivity wise, no unavailable bulbs (but pairing is broken and ofc the flashbang exists)

[swift phoenix]

Yeah when my bulb turns on it has never been “unavailable/unresponsive”

Just have to shut it off via command

[worthy grove]

From what I‘ve seen all my other devices were also available then one of my bulbs turned on by itself.

[craggy plaza]

Are your bulbs paired to Google Home and Home Adsistant or HA only?

[eternal hill]

But tbh im not living in Germany the US or any other country with a 3rd world power net.

So I would be surprised if that would actually cause it

[craggy plaza]

Then it was probably just a coincidence in my case.

[worthy grove]

Think so 😉

[brazen canyon]

HA only

[worthy grove]

My bulbs are connected to Apple Home and HA and connection itself seems stable in general.

[craggy plaza]

Ok, that’s a difference. All my Matter over Thread devices are paired to Apple Home and Home Assistant.

[craggy plaza]

How many Nanoleaf bulbs and other Thread devices do you have?

[worthy grove]

At the moment only 3x GU10. But I have 6 BR‘s, 6x Eve Energy, 9x Eve Motion Blinds & 6x Aqara P2 Contact Sensors… all stable.

[craggy plaza]

Ok, so you need more Nanoleaf bulbs to recognize the issue. The more bulbs, the more likely you will see the issue. We have something like a consensus that it gets worse with more than 11 bulbs. At the moment I have 9 bulbs connected to current and 37 EVE (Matter/HomeKit over Thread) devices. But an hour ago one of my bulbs got unavailable.

[worthy grove]

I know. 😉 But after two tries of connecting all of my Nanoleaf bulbs (15x GU10, 1x E27) and non working lights, I switched back most bulbs to Hue. Wife approved…

[wild oracle]

you’re speaking with respect to random turn ons?

[craggy plaza]

Yes, Philips Hue is my fallback, too. 😃

[craggy plaza]

No, to get unavailable bulbs in Home Assistant. Sorry, if that was not clear.

[wild oracle]

I figured it was one or the other

[craggy plaza]

I already wrote it somewhere above. I updated one bulb after the other. While updating bulbs sometimes another bulb switched on. So my assumption is, that if one bulb gets unavailable or crashes, another bulb switches on (maybe it also kind of crashes).

[craggy plaza]

My next test would be to have my bulbs paired to one fabric (Home Assistant) only. But as long as we can‘t pair the bulbs to whatever fabric, I can’t reset them. Because then I can’t use them anymore…

IMO you need to get the crashes solved. Then maybe bulbs stop switching on by themselves. But it’s only an assumption. Maybe they stop crashing, when they are paired to one fabric only.

[brazen canyon]

Feel like the voltage theory could be tested in a lab bench setting

🫠

[plain kettle]

sheesh

yeah, surely you guys (nanoleaf) are in a better position to test the voltage theory than any of us are?

[worthy grove]

My GU10 turned on itself at 15:41:12. I don‘t think it’s related to voltage.

[plain kettle]

🤔

[swift phoenix]

Im sorry devs but I just cannot fathom how you guys are not able to reproduce the symptoms were having here?

Can you guys just use some of the production bulbs and pop them in your home and wake up the next day and see if it happens?

Obviously my frustration is coming out here but it just seriously puzzles me?

[brazen canyon]

I think the issue is that they can't reproduce it on the dev boards with the debugger

[feral steeple]

Here is a good example of 1 randomly turning on

[steel hemlock]

Since two days, the next GU10 on 3.6.126 has become unresponsible. In the Nanoleaf app it is switching between bluetooth and disconnect, in Apple Home und Nanoleaf it is not responding to commands nor automations. With a power cycle it is possible to turn the light on but not via smart home. The GU10 is sometimes responding in the Nanoleaf app, because of a stable bluetooth connection. I do not know why it switched to bluetooth, when the GU10 is paired via Matter.
The second GU10 next to that one (in the same bathroom light), is now often flickering when turning on/off.

The missing availability leads to non-functional automations.

[rare quail]

Lights are turning on by itself. And when you turn them off they’re dimming slowly until they’re off on version 3.6.126

[frozen crystal]

Meanwhile I now have 4 GU10 lights which I cannot even connect to even under Bluetooth. Two of them are stuck on .94 (I can’t update the firmware, obviously) whereas the other two are on .126 and only started this behaviour last night

Any advice? It seems weird that both radios on the bulbs are dead. Power cycling doesn’t help

Perhaps the only option is to reset… urgh 🙄🤦‍♂️

[craggy plaza]

Some of us (me included) recognized that it’s not possible to pair the bulbs after a reset, when they are on 3.6.126. 😉

[frozen crystal]

Yeah, I know. That’s the other reason why I’m not bothering. I guess I could relocate some paired bulbs from another room but this is fast becoming a ridiculous waste of my time

I have a room of 9 waiting to be added. I can’t pair them and even if I could the extra Matter overhead would wreck the rest of the network. Rock and hard place…

[alpine ore]

Lmao now mine are turning on by themselves too. Roughly a third of them every night!

All while being 'unreachable' in the Nanoleaf app, so I can't even turn them off again.

[plain kettle]

you have to go near the bulbs

it connects over bluetooth

[alpine ore]

I'm as near as can be without levitating

I guess I'll just use the switch for now

[plain kettle]

might have to yeah

[alpine ore]

They respond for about 10 seconds after being powered on

[steel hemlock]

The "unreachable" thing is kind of annoying. You should not reset them, because you will not be able to pair them afterwards. Tried it two times.
You cannot turn them on/off, because they are unreachable in the Home app, where the automations are configured.
More or less, half of the bulbs are non-functional.

[dull dagger]

Hi. So been 4 days, on. 126 and I can report more of the same: disconnects, random on, and unable to pair/trasnfer/commission to other platforms outside nano leaf. Thanks for your continued support.

[feral steeple]

Hopefully we get a new update soon to fix some of these things 😦

[boreal surge]

I concur with your sentiment, thank you. I began spinning up a separate site last week for centralizing useful information for testers (such as this), as well as to provide an interface for submitting bug reports and logs (where possible—as mentioned in the threads, embedded logging over a wireless connection isn't feasible, but there are cases where Android and iOS logging can be useful if the root cause of the problem exists in those apps). This site will be partly public, with some content visible only for logged in users. As someone else mentioned in the thread, having certain debug processes active without targeted guidance is counterproductive, and could obscure problems in some edge cases. Very much appreciate your input over the weekend.

[alpine ore]

Thanks for your response!

Did you see the 20-minute screen recording? (#1184371187464290344 message)

You needn't watch the whole thing — skimming through it should suffice — but I'm still having the same issues today, so confirmation that you're on it would put my mind at ease a little :).

[boreal surge]

Yup, I understand the frustration and it's warranted (I've installed devices in my own home and experience some of the issues mentioned here). As @brazen canyon noted, reproducing with a connected debugger is what points us in the right direction for really damning issues (this reproduction has been elusive). Observation in our own homes is of limited use, but trust me... we're eating our own kibble 🙂

[rocky quail]

Similar experience as reported by others. Bulbs turn themselves on seemingly randomly. Was unable to get them to pair with google home. firmware version 3.6.126 hardware version 4.0.8 model nl67 a19 essentials

[boreal surge]

Of course. Thank you for the link back to the video, I did see it and plan to skim it at 2x over lunch (we're in Canada / eastern time, UTC-5).

I'm still getting my feet wet here (transferring in from another team entirely), but am very committed to continuous improvement. We're discussing feedback from this channel (and others) in daily standups with technical teams. It might seem a bit radio-silence from us, but behind the scenes everything is being ingested and worked through. Continued feedback is very helpful.

[craggy plaza]

Tonight I had one bulb unavailable in Home Assistant. 9 hours later it came back by itself. But there is another bulb that is 18hours unavailable now. So it doesn’t always come back on its own.

The proactive case resubscription doesn’t work after a bulb crash or whatever happens when a bulb goes unavailable in Home Assistant.

[steel hemlock]

The GU10, that is not any longer connected via Matter and only sometimes reacting via Bluetooth in the Nanoleaf app, is the one that is turning itself on.
The second one was exchanged by myself with a new GU10 and updated to the current beta. It is acting normal so far.
Could it be that the betas (maybe even the stable official software) are producing some kind of hardware issue? Maybe some kind of overheating and “melting”?
A normal software issue (regarding the unreachability) should be solved with a restart. But a restart doesn’t solve it.

[stark crystal]

Just to understand, do the bulbs which turn themselves on have the Power Loss Recovery setting on or off?

[steel hemlock]

For all my GU10’s the power loss recovery is set to off. I did not configure anything (except the firmware update) in the Nanoleaf app.

And, just monitored during a quite session in the bathroom: the GU10‘s are producing some kind of whirring/buzz, when turned on.
I am not at home tomorrow, but I will check if all GU10‘s are doing this.

Can anyone else confirm this?

[dull dagger]

My Daugter: Why is the closet light on?
My Wife: I don't know why the closest light is on.
Me: I'm testing beta firmware for Nanoleaf
This conversation actually happend. 🙂

[steel hemlock]

😂😂 same here. Glad I’m not alone with these kind of conversations.
Our neighbors already asked use what we are doing in the bathroom cause the light color is changing that often.

[alpine ore]

every time I try to turn power loss recovery on, it turns off again by itself it's only stayed on for the devices I can't connect to Matter

wait a minute

hmm

coincidence or nah?

[brazen canyon]

I've seen people say PLT has problems

[alpine ore]

@boreal surge I've installed the home network, thread, etc. profiles to HomePod Mini and iOS. How can I grab the logs for this light which is the only one which has decided to be completely unavailable 100% of the time to both Nanoleaf.app + Matter (even after power cycling, while others will work for about 10 seconds via Nanoleaf.app and tend to be more stable with Matter)?

[plain kettle]

what border routers have you got?

just a single homepod mini?

and does the thread network (if you can see) start with "Home"

[alpine ore]

2 HomePod minis, one in my bedroom and one in the living room

[alpine ore]

wdym?

that?

[shell vigil]

Nanoleaf has antitheft system , this is to ensure someone is at home, the bulbs turn on by themselves which pushes away the thieves and they think someone is at home when you’re away or sleeping

[plain kettle]

yeah, thats all alright

thats just a nice gui for all the mdns stuff

[frozen crystal]

Hah, that’s why I originally bought a couple of HomeKit A19s many years ago. Now look at the mess it’s gotten me into 🤣

[shell vigil]

They got you protection and non sleepy nights

[frozen crystal]

Similar things with Apple Home, it seems. I have 5 bulbs which will not rejoin the Thread network. One of them is reachable by Bluetooth, at least. The other 4 just stay unreachable by any means, even if I leave them on permanently

[shell vigil]

Btw I recommend changing the light color to dark blue and dim the lights to 1%

When doing this , if any bulb turn on at night

It will turn on to the last setting which will be dark blue dimmed 1%

This doesn’t bother much and will not wake you up

[plain kettle]

so when it turns on randomly, it retains its last status?

[shell vigil]

Yes

[plain kettle]

strange

[shell vigil]

I have power lost recovery on

Of course if it didn’t disappear by itself as it does usually

No actually I lost all my power loss recovery

These are all off

They still have this blue color

All my bulbs are off through Apple home but some of them still on in the app… they might take some time to appear as off

I turn them all off now haven’t done that before maybe this will help not turning on

[midnight solstice]

My daily update; I haven’t noticed any lights going on/off randomly, which is discussed a lot here. My main gripe is that 6/7 devices are still unavailable in HA (which is where all my automations point); I still see the occasional bulb go unavailable in HomeKit.

The same bulbs are also paired on SmartThings, which I am planning to retire. I removed HA automations from referencing ST entities several weeks back, replaced them with HA matter entities. To my dismay, all 7 of the bulbs have been rock solid in terms of stability on ST. (Even when they show unavailable everywhere else. 🤯)

[craggy plaza]

Only to be sure that we mean the same things:

1. When I remove a bulb from current it always resubscribed to Apple Home and Home Assistant with the currently available 3.6.126 firmware.
2. When one of my bulbs crashed, remeshed or whatever made them unavailable, it always came back to Apple Home, but not to Home Assistant. So the resubscription doesn’t work in this scenario. Why does it come back to Apple Home and not Home Assistant? Apple has a better way to get unavailable devices back. Home Assistant uses the default SDK method, which really shouldn’t be a problem, if the bulb resubscribes proactively.
3. It’s not possible to re-pair Nanoleaf Essentials to a Matter fabric after a factory reset at the moment.
4. You shouldn’t reboot/restart your Matter Hubs at the moment. The result is that your bulbs are unavailable and you can‘t repair them (3.). So you loose all your bulbs until the next firmware update.

[main matrix]

I'm finding the opposite behaviour with the beta firmware; my Google Hubs (4x) all need to be rebooted at least once a day as the HA Matter integration can no longer communicate with the lights for whatever reason.

I'm now also finding that trying to add any GU10s with the 3.6.126 firmware into the HA Matter integration is causing a complete hard crash of the addon. I don't experience the same behaviour on the A19s I have, but I also don't have any spare GU10s to test that are not on this newer firmware, so it's hard to determine where exactly it breaks and who to report it to.

[feral steeple]

No, seems to be totally random. I dont have that setting on any of my bulbs (unless they turned it on themselves?) But I have a different light tonight that has turned itself on randomly

My 16 bulbs hav ebeen pretty stable and connected. 8 on the new firmware 8 on the previous beta (accidentally reset 2 and cannot join them to the network so not gambling with updating the other 8 till we can rejoin the devices again)

Top ones on .96. Bottom on new firmware

[brazen canyon]

I think an important point here that NL needs to investigate is that there's been 0 reports of this occuring on the LED strips or BR30? Seems it's only a19 and GU10?

I've got both BR30 and strips on the latest FW and haven't had any of these issues, only with the a19 (no GU10 here)

[dull dagger]

Unfortunately not I have 2 led strips, and they experiencing all the issues everyone is experiencing.

[wind finch]

Yes my Power Loss Recovery settings are always lost as well. I keep turning it on, but after a few days (maybe also after a firmware update?) the setting is off again.

[frozen crystal]

I tried power cycling two of the bulbs which aren’t even responding to Bluetooth. Nothing changed. Annoying.

Presumably I’ll have to reset and pair them again, once that functionality is fixed

[shell vigil]

Turn them off,

Turn off Bluetooth on your phone

Quit your NL app

Turn them on

Open the NL app and turn on Bluetooth

Try that they might be able to connect

This was happening to me@I tried this it worked

And if it didn’t work I turned off all the electricity in my appartment off waited 5 min and back on

[brazen canyon]

Including the random power on?

[verbal drift]

So, I left my office GU10's at 75% when I asked Siri to turn them off last night, came in this morning asked Siri to put office lights on and they were all at 26% I asked Siri to set to 75% and so far they are all ok.

Just thought I would share this weird behaviour.

[boreal surge]

Thanks for sending the video. There are Jira tickets open with our technical team for issues resulting in similar behaviour, I've added more information to them based on this. Very helpful.

[alpine ore]

let me know about this if you can! I want to provide logs :)

[dull dagger]

Actually come to think of it only my a19s are doing the random power on on 126

[brazen canyon]

Yes so seems GU10 and a19 are the only ones with the random power on?

@boreal surge seems that the random power on is only observed in the a19 and GU10, but not in the strip or BR30, so that might help narrow things down on your end

[craggy plaza]

I have A19 and GU10 only, both power on randomly.

[brazen canyon]

Yea but seems it's only those. My strips and BR30 don't

[craggy plaza]

Yes, I understood that. I just wanted to confirm the suspicion. 😉

[boreal surge]

Discussing with our embedded team 🙂

My suspicion is that the origin of the flaky behaviour is somewhere in the Matter SDK, the SiLabs chip application layer, or the overlap between them. If so, that would mean it's unlikely we could collect useful logs from your device (this is the paradigm that @brazen canyon described earlier - forgive me if I've misattributed the message).

[boreal surge]

Thank you ! Very helpful clue. I've shared this with our team working on it.

[frozen crystal]

No luck, sadly. I’ve just disconnected the two bulbs which are stuck powered on. I don’t want to power down the Matter controller as other users report that causing even more issues with this firmware 🤦‍♂️

[boreal surge]

Open question for the group here, would you find it useful if there was a summary of known issues on our side related to 3.6x accessible to you on a web UI somewhere? What I was thinking was that could reduce some ambiguity in conversation around challenges you run into and streamline communication with technical teams on our side. To borrow from Adequate Spectre's note above, example : "Seems that the random power on is only observed in the a19 and GU10, but not in the strip or BR30, so that might help narrow things down on your end -- I think this relates to CHIP-1234" (where CHIP-1234 is our Jira ticket for a known issue that's open). Throw a thumbs up if you like it, and/or reply back with thoughts.

[craggy plaza]

We need something like GitHub, where we can file our issues and work on them together with you. But your offer is good as a starting point. 😃

[blazing meadow]

Another useful tool would be a "test matrix" of situations you'd like to see tested on various releases, and users could report OK/NOK on it.

[boreal surge]

Yup, I concur with you on that front. I'm evaluating a few options for that that might be viable in the near term. Jira's servicedesk module is one of the options I'm going to look at. Centercode is another.

[boreal surge]

Yes, most certainly agree with you. We'll work towards building more structured test cases and response methods. Thanks!

[dapper acorn]

That would be very helpful. And could you also include number of lights before it becomes unstable?

[brazen canyon]

Platform also needs a way to associate a setup with users. Either in a profile or in a submission template

[lime willow]

Can confirm I’ve never observed my Lightstrips turn on randomly. I don’t have any other NL lights to compare with though.

[boreal surge]

Yup, I think in this kind of a system which I'm envisioning there would also be written guidance about known limitations relevant to the test cases and certain network environments, OS/tech stacks, etc.

[boreal surge]

Yeah I've been thinking about this topic. An open question for me on this approach is... what's the fine line between us collecting and holding information about you folks and your devices versus the need to preserve privacy and protection of personal information. My personal philosophy is that we should anonymize data which we hold as much as possible and avoid collecting data which relates to PII as much as possible (in Europe/UK, information which can be used to identify someone through enrichment with other data can also be considered PII and has to be protected as such... in some cases, this can mean that device and network IDs could be considered protected even if they can't by themselves be connected to "John Smith of 123 Main Street, New York").

But, how do you folks feel? Would you be comfortable if we stored information about your network environment, devices, and setups in order to increase convenience for you while participating in a beta? Are there any information 'red lines' that you'd be uncomfortable with?

[plain kettle]

i mean, network information sure and maybe some personal identifier you are issued when you "sign up" to the beta that links say people here (and on the forums or whatever) to a certain nanoleaf account where all that information would be available.

eg; i have an issue, can just log it somewhere and say i have had this happen, acc identifier xyz and then you guys could look into it

[brazen canyon]

I mean just saying things like # of BRs, what they are, how many devices, etc isn't really PII

[tranquil pollen]

The Downlight an are having random power ons but the latest beta firmware isn’t available for them.

[plain kettle]

PII is a tough one to skirt past tho

[boreal surge]

Yup, true. I'm thinking more broadly about detailed device, network, user hashes in our/another app, etc. It may very well be unimportant (I've been known to overcomplicate things sometimes), but some folks are very sensitive about PII (as they should be). And, out of respect for you folks, I wanted to ask the questions and consider your voice in the conversation.

[plain kettle]

its a tough mix up between you getting actual valuable data and/or just more "reports" in diffrent setups configs

[craggy plaza]

I am fine with having a profile, where I document my setup:

• ecosystem(s)
• border routers (brand, model, quantity)
• devices (brand, model, quantity, matter over wifi/thread)
• network equipment (brand, model, quantity)

[brazen canyon]

Instead of ecosystem, I'd list matter controllers instead

[high atlas]

poshy___ has been warned

Reason: Bad word usage

[plain kettle]

honestly the OTBR add-on (basically the thread web interface) is a good gateway into diagnostics about a thread network, i wonder if it would be worth adding the web gui into your dedicated lineup of BR's (like the shapes etc etc) if you are in the beta, would be no doubt a ton more helpful to get a dump of that rather than just "reports" from people

(https://openthread.io/guides/border-router/web-gui)

[feral steeple]

And also putting some info about what we should do with dead/stuffed bulbs, I still dont have a response on my one that just does nto produce light anymore but is still responding as normal

[boreal surge]

DM'd you 🙂

[main matrix]

I'm under the impression you should already have some of this information in relation to what devices users have, as we need to sign up using the Nanoleaf Developer Portal and opt in for our devices to be eligible for the beta. In that sense, we could provide the email address we used to sign into the platform and you can collate the devices used, along with their respective serial numbers etc. in the event the issue may be attributed to a particular batch of lights (as an example).

[boreal surge]

Thanks for the suggestion!

[plain kettle]

All good!

you guys are already running the otbr behind the scenes, so can be much hassle to integrate it directly into the web UI you have by a little button or something if the serial of the device is in the beta, would expand the diagnostics capabilities as you can capture a wider variety of people who may not be tech savvy, but have a large range of your products

[craggy plaza]

Ok, but this UI is not known to work reliably. In large environments, it can even do harm instead of good because of the simultaneous status queries to the thread network. I have used this in the past and then deactivated it again. Also, I never saw all my Thread devices in the topology. Some devices were always missing.

[shell vigil]

Seems it’s the first day where the lights are not connecting anymore it has been since today morning, I tried what I usually do with no chance

[craggy plaza]

And what do you usually do? Did you reboot your Matter controller?

[shell vigil]

I usually turn off the electricity of my appartment for 5 min

Did it twice didn’t work today the first time@

And now@did it the third time and the accessories got disconnected from Apple home and they asked me to set up them again int he NL app

They are connected to thread

And I just had a fight with my wife because of them

I am looking for another company meanwhile, sorry guys … but my appartment is run in full on these lights with 35 and I have another 40 in another appartment@

[craggy plaza]

That’s the issue. With the current beta, you shouldn’t reboot your Matter controller. Otherwise you loose all your bulbs. You should also not reset them to factory defaults. You can’t re-pair them.

[shell vigil]

It was working in this beta

But suddenly@it switched from home pod to Apple home and got disconnected and not connect again

😩😩

[frozen crystal]

I really hope that there’s a quick fix for this beta, then. Talk about walking a tightrope…

One momentary power loss incident or software update to my AppleTV and…

In fact, I’ll turn off auto software updates on all of my home hubs until there’s a fix

[craggy plaza]

@spice harness We need a new beta firmware. Maybe give us a firmware rolled back to 3.6.94. some of lost some or all their bulbs and can’t repair them. Thanks

[craggy plaza]

Yes, that’s the current situation.

[frozen crystal]

I also seem to be losing more and more bulbs to the no connectivity, not even Bluetooth, bug

It’s a rate of about 1 per day at the moment

[wild oracle]

thanks all for your patience. 3.6.134 is released

here's a summary of fixed issues:

1. Reset on 126 cannnot be resetup (fix coming)
2. Random turn on (we havent definitively caught this on debug, but have a reasonable hunch, test incoming with new version)
   --Note this test will make it more difficult to turn on A19s if they are soft-off. You'll need to make sure the capacitor fully discharges (cut power for ~5s). This is what we call the "partner test" which will fail as part of our test.

Issues being tracked:
3. Issue where BLE stops working but Thread remains (unless you know what to look for, its possible you've never noticed)
--need to zero in on reproducible steps or otherwise see if this still exists when we can commit to a reliable 1.2 build
4. Issue where both Thread and BLE stops working
--similar to point 3 regarding steps and Matter 1.2. what we really need to answer is whether the prevalence of this is higher in 1.1 (any 3.6 build) vs. 1.0 (3.5 and lower)
5. Flickering EU GU10s - in progress

trying our best to battle the multiple fronts and get you a build at least for 1 and maybe 2 today

[frozen crystal]

Thank you. That’s helpful. My one data point for 4: I never had the issue until two bulbs with 3.6.94, coincidentally (?) configured as a pair. Now with 3.6.126 it seems to be affecting 5 bulbs at least

[shell vigil]

I agree I would downgrade to even lower .79 which was for thread at least building@up if got disconnected

[shell vigil]

Flickering and wrong colors are not that huge issue

I believe it would great if the thread network doesn’t disconnect and the lights doesn’t turn on. These 2 are crucial for home@fucntioning

[wild oracle]

despite the large differences in numbers, there are few changes between 94 and 126. so its unclear why there was such a discrepancy in experience. its possible it was just (un)luck of the draw.

[shell vigil]

Can’t figure out; at least the thread network was connecting and bulbs are reachable

This is the current situation they are not willing to connect

[wild oracle]

resolving issue 1 may also relate to that.

[brazen canyon]

What's "soft off" here?

[wild oracle]

turned off from Matter or our App

as opposed to cutting power from a switch

the natural inclination for many (especially partners) is still to gravitate to the switch. so if they flick the switch (actually cutting power) and flick it back (resuming) we normally turn on. we suspect that that function became too sensitive in some evironments due to other underlying changes. if we're right we'll have to dig deeper to optimize that to avoid the random triggers especially while sleeping

if we're wrong, we're still searching for a light in the dark (pardon the pun)

[plain kettle]

while yes thats true, its honestly better than nothing, and its really only meant to be used for testing/debugging purposes in the first place. (which is the point of the beta)

google and co have seem to recently made some strives on improving the gui/backend in the more recent releases, but then again i have no idea what patch of the OTBR run on nanoleafs gear

[brazen canyon]

Curious if/how power loss recovery factors into this since it's an option in the app and seems buggy for some

[craggy plaza]

Yes, I made some PLR tests with 3.6.79 and maybe with 3.6.94. Everytime the option was enabled, I got unavailable bulbs in Home Assistant over the day. With the option disabled I had bulbs switching on randomly, but no unavailable bulbs. So, I disabled the setting.

[craggy plaza]

Ok, didn’t know, that there were some changes. Good to know. Thanks

[brazen canyon]

I wonder if it's some corrupted state log it tries to read on power up that causes it to crash

[wild oracle]

interesting. see if thats still the case in next build. that seems highly unexpected.

[craggy plaza]

I definitely did this test twice. Did we have another 3.6.x beta before 3.6.79? I can’t remember for sure. But I definitely wrote/described my findings after those tests in this channel. 😃

[wild oracle]

we continue to make changes that could either fix it or invalidate it

[craggy plaza]

@wild oracle I really appreciate the proactive communication from you Nanoleaf guys. But I do not understand the different roles of you. Ben is a Product Manager in my understanding. What is your role? What are the roles of Faisal and Paul? Is Faisal a Product Manager, too? Which products are Ben and Faisal responsible for?

[wild oracle]

Ben and Faisal are PMs on my team. Paul is going to be more active in beta program management moving forward.

ben will be in the mix, but less so this month. his last day is end of feb.

[spice harness]

🫡

[plain kettle]

sheesh dude

[craggy plaza]

What do you mean? Sorry, I am not a native English speaker. But sheesh dude means Scheißkerl in German. My statement was in no way meant badly. What’s wrong with it? I am going to delete it.

[eternal hill]

Nothing was wrong with it

[plain kettle]

nah its all good, just could be interpreted from as a bit weird for nathen

didnt mean to offend ya, we say that all the time in australia 😅

[craggy plaza]

Too late. I deleted my post. 😉

[high atlas]

ownedbygravity has been warned

Reason: Bad word usage

[plain kettle]

the bots pretty strict 🤣

[eternal hill]

They should not take it as hard either

[shell vigil]

Poshy are you always online ? 😂

[craggy plaza]

But the bot only seems to understand English. At least the bot didn’t recognize the German translation of sheesh dude.

[plain kettle]

discord works wonders on the 2nd monitor 😉

[wild oracle]

#1184371187464290344 3.6.134 is out. notes updated here: #1184371187464290344 message

[plain kettle]

Just to confirm, is this for all the beta users, or only the “alpha” ones (the ones that gave their S/N over to Ben a while ago

[iron trench]

Anyone update to the new 3.6.134 yet? Notice any improvements or new issues?

[peak mesa]

hey sir, when we can expect an update for the downlights? they are still at .79 and are bugged as hell

[plain kettle]

It’s only been a few minutes cobba, maybe give it a day or so until we get some substantial feedback/testing

[iron trench]

It’s been 3 hours and I know some of these peeps work fast! 😅

[bitter compass]

Ok so first question....

I've updated the first bulb to the new firmware, and now nanoleaf shows this as the firmware version....

[craggy plaza]

It looks good here on a GU10.

[plain kettle]

Other people are also experiencing the same, seems like an overflow of some sort

[bitter compass]

On the plus side, this light has been unavailable in home assistant since a day after the last firmware update, and has immediately popped up online in home assistant, so that's progress

[blazing meadow]

Indeed. Even with the latest update for the Android app, the version was fine upon flashing then got displayed as 3.6.-122 afterwards too.

[bitter compass]

Ah yes a second bulb I just watched as it showed the correct firmware briefly after update while it was only on Bluetooth and then changed to the weird -minus firmware when it connected to Thread

[blazing meadow]

I can't access the updated bulbs's advanced parameters anymore in the Android app, it returns to the main menu.

[bitter compass]

Ok so, another issue though - can't actually load settings for bulbs that have been updated. It crashes the app

I can still load settings for bulbs I haven't updated yet. So I suspect it's related to this firmware version display glitch

[plain kettle]

Sheesh, that’s pretty bad hey

[bitter compass]

Nanoleaf can likely fix that with an app update though, without needing a new firmware

For what it's worth Home Assistant is correctly reporting 3.6.134 and so is Google Home

[blazing meadow]

Trying to add a resetted/updated bulb to GH directly still fails at the "creating Matter identifiers" stage.

Ok, it worked after turning the power off, waiting a bit, then powering it on again.

Maybe the updating procedure should add "in case of trouble, power cycle your device".

[bitter compass]

it probably needs the power cycle to open the comissioning window

[dull dagger]

Going to settings on the device using the nanoleaf app crashes the nanoleaf app Android

[bitter compass]

but only for updated bulbs, you can still load the settings for bulbs you haven't updated

[blazing meadow]

…also added the bulb back to SmartThings through GHome. Control works fine from there too.

[bitter compass]

@boreal surge @wild oracle @void pulsar just in case you miss the information - the nanoleaf app crashes if you try to access the settings of any bulb that is running the new firmware (which is being reported as a 3.6.-122). The app still happily loads settings of any bulb that has not been updated. (Android)

[feral steeple]

Mine goes to -122 on bluetooth then back to .134 when on thread. I Lie, seems to have gone back to -122 on thread now, and I cannot add them to anything cause the app crashes when going to the settings as others advised. will try resetting one and see if i can add it then.

Also after updating 3 bulbs, it has knocked most of my nanoleaf's off HA and they stopped checking in. will give it some time to settle.

[dull dagger]

Does commissioning it directly in home assistant work now?

[feral steeple]

The one i just tried failed, but that could be a HA thing, i resorted to doing them all via google home as it seemed to be the most consistent way i have gotten them into HA.
But ill reset this other one and see if it goes straight in to HA

[dull dagger]

Okay good idea I will add it to Google first and then transfer to home assistant. I know there is a bug in home assistant right now for this but I thought it was a resolved but who knows

[high atlas]

shadoxity has been warned

Reason: Bad word usage

[feral steeple]

Weird, dont even know what word I said that was not allowed lol.

Its supposed to be fixed, but its been inconsistent for me still. sometimes something adds, other times it doesnt. Doing it via google and killing the HA app each time has been consistent for me though

[dull dagger]

Lol

[feral steeple]

FYI it failed going straight to HA.

[dull dagger]

All right thanks for saving me 20 minutes of my life. I will reset the device and add it directly to Google home and then transfer it to ha and NL hopefully that works

[feral steeple]

Actually, it said something went wrong, but it did actually add it to HA and its controlling it fine

[eternal hill]

For me commissioning was working perfectly

Better than with any other firmware version

Both Apple home and HA

[feral steeple]

It might be thread going all over the place with some of the bulbs updating and restarting that was impacting me

[scenic grove]

I was able to get the bulbs all updated (6 of them) and back into Home (yay) step in the right direction so far 🙂

[eternal hill]

That’s the trick, make sure the bulbs stop working completely, then everyone his happy that they at least can control them sometimes 😂

[brazen canyon]

Worked fine for me

I have so many problems with the updates in app

It's terrible in android (always not just this FW)

[feral steeple]

FYI still inconsistent going direct to HA, so would stick to google first. (may be thread settling down after updating 20~ bulbs though)

[dull dagger]

Awesome finally got the device back into HA. Did a couple of things I moved one of my TBRs within 10 feet of the device and it worked.

This particular device is the farthest from my TBRs about 35 feet

[dull dagger]

Just had my first auto on A19.

But, it's staying connected

[frozen crystal]

What’s going on here?

Firstly, what do I now have a “Setup” button next to a load of bulbs? (But not all)

[blazing meadow]

My updated A19 still becaame unreachable from GHome a few hours after the update (so, same as before), but it's still reachable through SmartThings so I guess Samsung has a more aggressive method of keeping the connection up.

[frozen crystal]

Secondly, why is this particular bulb listed twice? 🤣 it’s the only one in the house like that

[steel hemlock]

FYI: In my case, the update from 3.6.126 to 3.6.134 is failing on many devices continuously. Will continue trying.

[main matrix]

Can also confirm the weird firmware number on GU10s and A19s. Not to be that guy, but the Betas do go through a QC process before releasing to the testers, surely?

Ironically, after updating in the nanoleaf app, pairing to GH then sharing to HA, the Matter integration does identify the GU10 as 3.6.134. But as others have said, trying to load the settings on newly updated lights on 3.6.134 does crash the Nanoleaf app when trying to load settings.

The silver lining is being able to add it back into HA, so I'll take it.

[plain kettle]

We love a good integer overflow 🙈

[main matrix]

Next up, we have NaN!

[steel hemlock]

Should the Matter pairing work again after the update to 3.6.134?

[main matrix]

It has for me on two GU10s I've updated.

Process I took (which shouldn't be any different to normal):

1. Update to 3.6.134 in Nanoleaf app
2. Reset the light
3. Pair with Google Home via Pairing Code (interestingly scanning the QR code immediately errors for 'something went wrong')
4. Share to Home Assistant

It took a lot less time to pair for me as well (usually each light took upwards of 2 minutes to pair. These took no more than 15 seconds).

[covert marsh]

hurray with 3.6.134 i can add the NL67/A19 back to HA. It only worked directly without the nanoleaf app, in the nanoleaf app the bulb would not connect over thread and therefore the button to connect to matter does not appear.

I only tested 1 out of 7 so far.

[blazing meadow]

Let's hope the risk of a worldwide"Wives Against Nanoleaf" collective has been lowered enough thanks to this update.

[steel hemlock]

I will give it a try. Thanks for the feedback.

[main matrix]

I've added my last 2 GU10s using this method successfully so hopefully it's not just me.

[steel hemlock]

You are right. The pairing in Google Home and/or Apple Home does work again with 3.6.134
And, as you mentioned, the pairing took less time.

[main matrix]

https://tenor.com/view/sacha-baron-cohen-great-success-yay-gif-4185058

[bitter compass]

Light strip had fallen off HA overnight. Power cycle brought it back online.

Hall light which is in the next room between 2 border routers (1 in the living room and the light strip and an onvis socket) and the kitchen which has an onvis socket. So it should be fine on thread, and the nanoleaf app says it is on thread. But it doesn't show up in Google or Home Assistant

it's an A19

[brazen canyon]

Same issue, #1184371187464290344 message

[steel hemlock]

I just had to try several times. Now, all GU10 and light stripes are updated.

[brazen canyon]

Yeah it's possible, but difficult

I've got about 6 more a19 to update today as I gave up last night

[stable drift]

When I try to pair it to GH after deleting it just gets stuck at "checking network connectivity.."

Do I need to pair it to the nanoleaf app first?

Oh hang on, it worked now but I had to use the pairing code not the QR code, weird.

[bitter compass]

you probably need to reboot the Google Home. One of the issues with how matter works is that it relies completely on mDNS, and mDNS records get cached for a period of time. So if you try to pair a device and it fails, then there can be a stale mDNS record lying around for up to 6-8 hours. Rebooting the Google Home will clear it's mDNS cache

[stable drift]

Sorry to have made you type all that out haha

[bitter compass]

A few people have reported that further up the thread

[stable drift]

But thanks!!!

I'll remember that for in the future.

I have no doubts I'll need to do this again

[brazen canyon]

I'm not sure that's true as that was resolved in HA and I'm not sure it's an issue in GH

[stable drift]

What does HA refer to?

[covert marsh]

Home Assistant

[main matrix]

yeah QR code is broken for me as well

[bitter compass]

The HA issue was caused by it only picking the first mDNS entry it found. We don't know exactly how GH does it - because we don't have access to the source. But purely anecdotally I can definitely state that anytime I have had issues with thread devices misbehaving, rebooting both my Google Hubs have resolved the issue.

(and yes I have to reboot both, only rebooting one doesn't fix anything)

[stable drift]

Ah yeah just scrolled up a bit and found your post! Sorry to double post folks

[bitter compass]

no not at all - it's better for multiple people to confirm the issue, then we know it's not a weird edge case for just one person

[stable drift]

Ok awesome

Is there a reason to use Home assistant over just GH/Alexa/Nanoleaf app?

[bitter compass]

Some of us already have an established Home Automation system that has various complex automations, so that's what we prefer to use. For example I know there is basic circadian lighting in the Nanoleaf app, but I have lights that are Zigbee not just Matter - so I'd rather use my own Circadian lighting algorithm which controls Wifi, Zigbee, ZWave and Matter lights - rather than have my matter lights doing something different to the rest of the lights

[stable drift]

Ahhhh I see

[bitter compass]

I also have automations that control the brightness level of the lights in my house, based on the actual measured daylight level outside

So for example, if it suddenly clouds over wuth heavy clouds (like maybe tommorrow when the UK snow comes) - then the lights will come on automatically inside, and gradually get brighter as it gets duller outside

[eternal hill]

Proper QC would probably take days. So no, but this is also a "beta".

Or maybe more an alpha 😄

[brazen canyon]

There's a lot more insight into what's going on as well -- in HA you can see the logs of the matter server and thread border router, in commercial ecosystems... Not so much

[stable drift]

Woah

[stable drift]

Ok that sounds helpful! Thanks

[feral steeple]

Turning on/off the actual power of lights seems to screw the thread network now. All lights disconnected and have different getting reconnected after one room got turned on at the switch.
Actually, seems it crashed my thread network for some reason. ill see if it happens again.

[covert marsh]

Anyone having issues accessing the settings of the bulbs in the nanoleaf app? I always get a error message on the first try and crash at the second 😅

[feral steeple]

After the update you cannot access device settings in the nanoleaf app

[dull dagger]

Overnight, had one A19 light turn on randomly, twice and lights also disappeared from HA.

[feral steeple]

Dont know if its from teh update, but my HA thread router is constantly crashing and rebooting now. Only change has been the nanoleaf firmware updates

[bitter compass]

sigh......

and yes - it's offline in Google too, this isn't just HA

[stable drift]

Yeah this update has completely borked everything for me

[feral steeple]

Yea mine are being really crappy since the update 😦 The bulbs I left on .96 seem to be connected and happy, the new fw ones are going unavailable and/or crashing my thread border router.

[stable drift]

Can't even control the lights from the app when it's not connected to any other smart home services

Or even via Bluetooth

[feral steeple]

Is there a way we can downgrade them back to .126? Now i could add them back, 126 seemed to keep connected.

[main matrix]

Seems I may be an outlier here, but upgraded the 20 A19s and 4 GU10s I have to the new firmware. HA seems content and all lights are currently accessible and have been since the update. No issues thus far (couple of lights didn't want to update straight away, but force closing the app and reopening seemed to help). All with 4x GHubs in the mix.

Early to tell but this firmware seems to have worked out the best for me (short of Nanoleaf borking up the firmware versioning in their app and rendering all settings useless).

[boreal surge]

Thanks, this looks like a new issue which I'll ticket. Which version of the Android app are you running, and on what device brand / version? (ex : Samsung Galaxy)

[brazen canyon]

Same experience here regarding stability. This has been the best yet with 0 drops and I've even added more bulbs than my previous stability threshold.

Can't comment on the spontaneous light on yet

[feral steeple]

Turn some lights off and on at the power and let me know if it stays stable after that

BTW if anyone is using powercalc on HA to estimate power consumption, I have made a model for the Nanoleaf GU10's. Extract to /config/powercalc-custom-models and they will discover the bulbs to set up for power monitoring

[brazen canyon]

I turned off 4/15 and they came back and didn't give me grief

How many BRs you have? Could be the bulbs are routing a lot of traffic for you

[blazing meadow]

Galaxy S22Ultra, Android 14, Nanoleaf 10.4.0.

[brazen canyon]

@boreal surge earlier @eternal hill pointed out it's likely an int8 overflow

For the app crash

[feral steeple]

Just the 1 currently

[bitter compass]

@boreal surge Pixel 8 Pro, Android 14. App ver 10.3.2

[brazen canyon]

Yeah you've got a ton of bulbs for one BR, likely the bulbs are routing traffic and crashing (hasn't been stable on any version yet)

[feral steeple]

Thread/matter seems like it will be pretty average if you need multiple BR's to handle lights for 2 rooms and a hallway 😦 Maybe I should get that google hub v2

However they were stable until i did this recent fw update

[eternal hill]

Thats just the version number, idk if that actaully would crash the app. But yeah, for me ios works flawless and i don't have an overflow in the ios version

[brazen canyon]

Well the limit is 511 devices per BR, it's more that the signal won't fill your whole house. So unless those bulbs are all relatively close to the BR signal will be poor and bulbs will have to relay

But the relay action is buggy as hell in this FW

[feral steeple]

2 bed apartment, all the lights are less than 10m away.
Will prob bite the bullet and get a hub v2 (sadly have an old v1 google hub) for the future anyway

[wild oracle]

thanks for reporting. looks like a casting bug in android. we'll push a fix asap. i dont think it should be a problem besides UI and confusion (not nothing of course)

[bitter compass]

Well it also means you can't delete devices, access the power loss recovery setting or set the thread network. So it's slightly more than just confusion 😉

[wild oracle]

deleting devices at least should be accessible from 3 dot menu on "My Devices". changing Thread networks is only intended for some corner cases where devices can get orphaned (but understandable that its become a troubleshooting step if you have multiples and are seeing thread issues). noted re PLR.

[bitter compass]

More importantly - it's also where the "connect to matter" button lives, that "normal" users are expected to use, most people probably aren't aware that you can just add it to matter without going through that flow

[stable drift]

Kind of got it working again had to fully reset the lights, then add it to smart link and then add it to Alexa

Google home still shows them as offline once connected, and the nanoleaf app doesn't seem to work with the lights at all

[bitter compass]

did you remove them from Google Home though after you fully reset them?

[brazen canyon]

I can confirm I have the crash bug but was able to delete devices this way

[stable drift]

Yeah I unlinked all the Google home matter connection

I think it's partly because the thread border router I'm using, nest hubs, don't give you a way to split ssids which is annoying

[bitter compass]

I've turned the OTBR off in HA for now, and the LED strip has come back online, after about 20 minutes. Still no sign of the hall light coming back yet though - and that got power cycled this morning to see if I could get it back to life

[stable drift]

But I can't seem to find a border router that just has a 2.4ghz connection

HA green doesn't seem to be fully up & running for use as a thread border router unless I misunderstood the post

[bitter compass]

Green needs the Sky Connect adding to make it a Border Router

[stable drift]

Is that software or like a usb stick thing

[bitter compass]

USB stick

[stable drift]

Ahhh ok that makes sense

[bitter compass]

https://www.home-assistant.io/skyconnect/

[stable drift]

That could potentially help with my issues

[plain kettle]

External radio

[stable drift]

Cos I think the 5ghz is mucking things up

[plain kettle]

Don’t have to use a skyconnect, most of nordics chips work

[stable drift]

Just wish they'd let you split the SSIDs on the nest hub

[bitter compass]

thread runs on 2.4GHz so it will have much less inteference from 5GHz WiFi than 2.4GHz WiFi

[plain kettle]

Why do nest hubs even have a ssid when it’s connected to wifi

It’s weird

[stable drift]

I could just be making it up TBF and Google home is just on one till there's an update

I wanted a seperate network for my smart home devices

[plain kettle]

There hasn’t been a google nest update since the start of December lol

So I doubt that

[stable drift]

I meant Google home, the app

[bitter compass]

All Google Chromecast-y related stuff broadcasts an SSID when there is no internet connection - as a way to set it up / factory reset it.

[stable drift]

Oh sorry I mean the nest WiFi router, I'm using it as border router

[plain kettle]

Oh right

Right

Gotcha now

[bitter compass]

If you don't have 2.4GHz WiFi stuff, you could just turn that band off, so you are only broadcasting 5GHz stuff?

[stable drift]

And I don't know if the mixed band SSID is causing problems

[plain kettle]

Is there a setting somewhere called band steering?

That normally doesn’t play the nicest with some IOT devices

[bitter compass]

it shouldn't be. The vast majority of us have 2.4GHz and 5GHz (and even 6GHz) all broadcast as the same SSID

[stable drift]

It claims it's doing it all """""intelligently"""" so the options are limited for what you can change

Yeah it's lame

But I needed a border router and the information about it at the time was pretty hard to decipher

[plain kettle]

Yikes

[stable drift]

The idea of Matter/Thread is great but execution so far is a bit messy

[plain kettle]

It’s not too bad if you get deep into it, but the thing is most companies don’t give ya much options in terms of debugging

[stable drift]

Hoping 1.2 alleviates some issues too with multi-controllers

But then there seems to be little pressure on manufacturers to release these updates promptly so who knows

Google/Amazon/Apple etc

I'm still waiting on IKEA to drop matter support smh

Requiring a hub just for a smart blind smh

[brazen canyon]

I use separate SSIDs because exactly the scenario of IoT misbehaving

[brazen canyon]

Depends how adventurous you are, espressif has a SoC that's fairly easy to use for $10

[ornate obsidian]

Got my 8 or so current bulbs updatd to 134 last night and this morning. I did have one bulb turn on overnight (the one in my master bedroom so that was fun) - I did not apparently have power loss recovery on for that bulb. Had one bulb that refused to update from an older version (.94 maybe?), so I reset it and its fine now. I've been seeing sporadic non-responsive devices but it could be the mix of all the firmwares (got my last bulb updated 20 minutes ago). Home Assistant was performing more like it did before the betas, with stuff randomly dropping off as well. But I'm hoping maybe the thread network is settling down, and I'll see improved performance between HomeKit and Home Assistant now

[bitter compass]

For the people running Home Assistant - are you on the stable matter server or the beta matter server? (I'm stable, because beta just will not work for me, it never resolves ANY of my matter devcies, even the WiFi ones)

[frozen crystal]

What’s your stability threshold? I am keen for the Nanoleaf team to track this metric across our feedback

[eternal hill]

There is no one fits it all value there.

[brazen canyon]

Was 9 but now I'm up to 15. Might add another 3 from a box I have later this week

[frozen crystal]

Yes, it will be one of those impossible things to determine, given likely radio proximity to the nearest border router too.

[iron trench]

Updated bulbs to 3.6.134. Reset all bulbs and deleted bulbs from GH, HK, and NL. I couldn’t get them paired starting with HK, but they did pair with NL. After waiting about 30 minutes, I was able to connect them to HK with QR Code. After that, my bulbs in NL app show to “Setup” again. I go through the process but it says it can’t find bulb. It was doing this in the prior update but after a minute the “Setup” would go away. Now NL only shows the border routers on thread network despite my devices showing them connected to Thread. (Even after hours of letting everything settle). Bulbs are working in HK decently. Should I reset bulbs pair everything again?

[feral steeple]

Im on the stable matter. New beta just got released 30mins ago though if anyone is using the latest beta and wants to restart their matter server

[lyric panther]

I updated my A19 bulb to 3.6.134 using the Nanoleaf Test Flight build (10.4.0 (586)). Connecting to HomeKit from within the app is still failing, however, I was able to pair from the Home app (iPadOS 17.3). But after pairing, the bulb shows as non-responsive in the Home app. I am able to interact with the bulb from the Nanoleaf app.

[brazen canyon]

Tried beta, had lots of issues. Got stuck trying to interview an unreachable node

[haughty grove]

Not much improvement on my side. After update, only 5 out of 6 bulbs joined the thread network. Now, 10 hours later, only 2 are still connected to thread

[wind finch]

Are the updates done via Bluetooth or thread? I find that I need to go walk up to the device while it updates, otherwise it fails.

Anyway, I updated 3x lightstrips (NL68), 3x GU10’s (NL54) and 2x E27’s (NL67)to 3.6.134.

After this I was able to add the lightstrips and E27’s to HomeAssistant via Matter in 1 try all working perfectly! 👌🏼 This is the first time it’s gone so smoothly!

The GU10’s (all of them) are giving me some issues though doing the same, they all seem to time out even though they are right next to the other lights and seem to be controllable just fine….

[brazen canyon]

Bluetooth. AFAIK no updates over thread only, but there is OTA in matter. However I don't think any manufacturer has implemented it

[plain kettle]

Only eve has

And that currently only works through Apple home

As they are the only ones who have actually got it functioning

[eternal hill]

Ble

[eternal hill]

How are you checking that?

[feral steeple]

My bulbs that are still on .94 are being way more stable than teh .134 ones. Top here is .94, bottom is .134

[haughty grove]

Validating in both Google Home and Home Assistant. If available there, it means they're on thread

[shell vigil]

@spice harness @wild oracle the flickering persist , I believe it’s a hardware issue, I only have certain bulb from the 35 are flickering constantly. As for stability the connection of thread is much more stable now. One bulb failed to work in Apple home and was working only from NL App, I deleted it from Apple home and added it again through NL app and it works now@

[wind finch]

Well, my devices worked fine and were on Thread via Apple Home, but wouldn’t connect to HomeAssistant. So I’m not convinced that just because they are no longer responding in HomeAssistant that it means that Thread is not working.

If you want to check if they’re on the thread network, you can rather use the network option in the Nanoleaf app / Eve app, or some mDNS browser like Flame or Discovery.

[shell vigil]

No sorry I get back on what I said. Once I choose the scenes especially with more than 6 bulbs it breaks the whole@network@

[stark crystal]

Are Flame and Discovery iOS apps?

[plain kettle]

yes

[wind finch]

Yes

https://apps.apple.com/app/id325206381

https://apps.apple.com/app/id305441017

[plain kettle]

i have found that discovery is the better one of the two

[stark crystal]

Is there any equivalent for Android?

[wind finch]

I don’t have an Android, but this looks similar

https://play.google.com/store/apps/details?id=com.mdns_discovery.app

[stark crystal]

Thanks, I'm trying this one and WiFiman

[plain kettle]

wifiman doesnt do anything

you want to capture Mdns packets

[brazen canyon]

Not totally true as you can see the advertised mDNS services for devices on your network, but it will only apply to your BRs in that case

The new HA matter update has some good debugging tools

[plain kettle]

huh, then the ios app and android app must be diffrent

[stark crystal]

Yeah WiFiman feels useful, it also helped me know what to search in mDNS Discovery.

In mDNS Discovery, meshcop._udp finds all Thread Border Routers in the network. matter._tcp finds the IPv6 addresses for all the Matter devices in the network (although it doesn't say show the device name).

[steel hemlock]

If I remember your video correct, then the flickering appears only when turning on/off the lights or changing the color. Correct?

[shell vigil]

Mainly , but not when I have colors rather when it’s switching to white colors

[steel hemlock]

Are you using US bulbs or EU bulbs?

[shell vigil]

EU

[steel hemlock]

Maybe that is an important info for @wild oracle and @spice harness. If they do not know this already.
Is anyone else with US bulbs facing flickering?

[wind finch]

_itdpu._udp for the Nanoleaf things

[brazen canyon]

Not exactly. That's the advertisement for their proprietary protocol

So yes it will show nanoleaf things but not other matter devices

[wind finch]

Yes

[stark crystal]

It doesn't find anything for me. I have _nanoleafms._tcp and _nanoleafapi._tcp for the Wi-Fi devices. Anyway it doesn't really matter (no pun intended).

[main matrix]

Looks like a couple of blips overnight; one of the newly added A19s (that failed to pair before) has gone unresponsive in HA, and one of the GU10s I have on automation to turn off at sunrise and on at sunset has malfunctioned (GH and HA thinks it is off, the light is still on and powered and won't respond to commands). Won't be able to turn it off until later tonight but will see if it recovers on its own during the day.

[wild oracle]

we've already concluded its EU only, but if anyone on NA sees it please let us know.

#1184371187464290344 we identified another case in 134 that could lead to random turn ons. expect another release tonight to address that. still working through step function improvements to get to 1.2

[feral steeple]

any eta for the next fw update? 134 has made mine worse, pretty much only my bulbs still on .94 that are consistently connected.

[brazen canyon]

In contrast mine are great. I think once some internal reporting about setups are available that might help a lot

[dull dagger]

Anyone know what the max distance to a TBR should be? One of my furthest devices seems to stay disconnected all the time, except the FW before .79, that was working quite well except the random turns on...has the power/range somehow been diminished since the FW before .79?

This would be the firmware around Christmas holidays time

[feral steeple]

I wonder if its anything to do with the mix of firmwares. wonder if i update them all if it will go stable, just scared to and have most things not working again haha.

Is there any way to downgrade a firmware?

[brazen canyon]

No. Honestly you can just un pair some of them and use them with dumb switches then update all the others

[brazen canyon]

Ah now is the time of unreachable devices for me 🙂

[bitter compass]

So oddly - my hall light which has been unreachable on matter (both Home Assistant and Google Home) - suddenly jumped to life when I updated Home Assistant to tonights release (2024.2.0)

For the people looking for the Google Play app that is quick and east to use for mDNS - I use one called Service Browser

[main matrix]

Mine still seem to be holding.

[brazen canyon]

Most of mine have come back now.

I only have one offensive bulb that it seems is constantly crashing. Just going to leave it off in hopes the new fw resolves whatever's happening there

[stark crystal]

Is it the voltage difference or are there different EU models?

[midnight solstice]

Oh, new features for Matter debugging in Home Assistant 2024.2.0? I guess I have to take a break from work to get that updated... 🙂

[wild oracle]

EU has different models due to voltage difference. hard to put a universal PSU in such a small package

3.6.136 - Beta Release Notes

1. Fixed issue in 3.6.134 that could lead to random turn ons.
   --Note this test will make it more difficult to turn on A19s if they are soft-off. You'll need to make sure the capacitor fully discharges (cut power for ~5s). This is what we call the "partner test" which will fail as part of our test.
2. Fixed an issue where PLR is set to ON after a factory reset

Issues being tracked:
3. Issue where BLE stops working but Thread remains (unless you know what to look for, its possible you've never noticed)
--need to zero in on reproducible steps or otherwise see if this still exists when we can commit to a reliable 1.2 build
4. Issue where both Thread and BLE stops working
--similar to point 3 regarding steps and Matter 1.2. what we really need to answer is whether the prevalence of this is higher in 1.1 (any 3.6 build) vs. 1.0 (3.5 and lower)
5. Flickering EU GU10s - in progress
#1184371187464290344

[feral steeple]

Nice one. Think im just going to bite the bullet and get all mine up to this version and see what happens. hopefully cant be any worse that what they are currently doing 😛

[brazen canyon]

Haven't been able to update a single device yet 😵‍💫

[feral steeple]

neither, falls on all the ones it has shown for