#No firmware update found for Nanoleaf Essentials

1 messages · Page 1 of 1 (latest)

fading hull
#

Hi, thanks for all the active help I see around HA and Matter. I wish other project would be so active.

I just setup HA and commissioned my first device.
The device works just fine with Matter over Thread. But firmware updates are not found.

Matter reports the FW as 3.5.10, but that version is almost two years (!) old and there are 5 newer ones available: https://helpdesk.nanoleaf.me/en-US/nanoleaf-essentials-(matter-over-thread)-release-notes-255125#3510
From what I've read, they are supposed to increase Matter reliability a lot.

When I search for a firmware update through Matter Python Server's UI, it says there is no update: "No update available. No update available for this node".
When I enable debug logging (Matter server log level: verbose, Matter SDK log level: detail), I see the following.

Check for updates.
Software version 198340 not applicable.
Software version 197910 not applicable.
Software version 197888 not applicable.
No new update found.
I attached the full logs with the productive DCL and testDCL. They report the same versions, though.

Apparently, according to Matter Server, there are firmware updates for this device, but they are "not applicable". Does that mean they are seen as older than the current one?
I am not sure how to interpret these version numbers. They look way different than the format Nanoleaf and Matter show (x.x.xx vs xxxxxx)

Continuing in the first comment due to character restriction.

📎 testDCL.log 📎 prodDCL.log
Nanoleaf Essentials (Matter over Thread) Release Notes

3.6.196
June 10, 2024

What’s Changed:

#

I currently run the following.

HA core 2025.1.4
HA OS 14.2
HA SV 2024.12.3
Matter server 7.0.0
OpenThread Border Router 2.13.0
SkyConnect stick (that is now apparently called ZBT(?))
Thread-only firmware
The device below is the only device in HA and the Thread network.

Device

A19/A60 (67)
by Nanoleaf
Firmware: 3.5.10
Hardware: 4.1.8

The device can be found on https://webui.dcl.csa-iot.org/models by searching for Nanoleaf Indoor Lights.

The docs of Matter server state that Matter OTA FW updates should be possible with Nanoleaf: https://www.home-assistant.io/integrations/matter/#matter-ota-device-updates

Currently, Eve and Nanoleaf are using the DCL to provide updates.
@narrow jackal, who seems to be very active here and on Github, also confirmed this: #1289680614148014265 message
Only a very limited amount of devices actually support OTA updates with Matter. At time of writing only Third Reality, Nanoleaf, Eve and Innovelli that I'm aware of

Am I missing something?
Is Nanoleaf not updating the DCL as they should?
Is there another way to update the FW? Nanoleaf's app refuses to run on my phone.
Should I open a issue on GitHub?

Home Assistant
Matter (BETA)

Instructions on how to integrate Matter with Home Assistant.

narrow jackal
#

Unfortunately if the fw update is too old, it cant be updated using DCL. So you need to update it once using the Nanoleaf app after which the matter updates start working

fading hull
#

Hmm, OK, thanks a lot for the swift reply!
How sure are you that that will be the issue? Two years is a long time with a novelty protocol ofc, I understand that.
Can you tell me how to interpret the version names matter_server.server.device_controller is reporting?
I don't see any reference to a number looking even similar to 198340, 197910 or 197888 on the DCL or the device info or the entities page in HA. There are also only two entries for Nanoleaf Indoor Lights on https://webui.dcl.csa-iot.org/models. How come Matter Servers finds three?

narrow jackal
fading hull
#

Well, that is not true. The Software Version on the site is in that format. I just did not realize because they are numerically WAY lower than the ones Matter Server finds: 66816 and 131079.
They seem to map to Nanoleaf's version strings 1.5.0 and 2.0.7. These are older than the change log by Nanoleaf goes...
Again, where is Matter Server getting these 19xxxx version from?

fading hull
#

I also just noticed that the OTA URL on DCL is not populated for this device. Is it required? I see that Eve Energy, for example, has the link to the .bin there.

fading hull
oak dawn
#

It's likely that database only contains information as it was initially submitted and not any changes afterwards. And considering OTA over Matter was added in a firmware update you'd otherwise receive through the Nanoleaf app over Bluetooth...

coral parcel
#

there's actually an issue with the firmware that nanoleaf put on the DCL. they added the 3.6.196 (198340) firmware, which includes the matter stability fixes... and it has the OTA download link populated... but they set the "min applicable software version" (i.e. what version you need the bulb to be upgraded to before you can upgrade to this firmware) to 198317 - and there is no firmware on the DCL older than 3.6.196 which is at least 198317

#

so it's there, but according to the metadata they added, it can't be installed.

#

anyways, update nanoleaf bulbs over bluetooth with the phone app, it's the only supported way to do it :(

#

you should expect to get firmware 4.1.3 if you upgrade an NL67 bulb right now.

ember crescent
#

I had to use the Nanoleaf app to update my Nanoleaf A19 bulbs.

oak dawn
#

Dawg I'm gonna be real the correct solution is to get a refund

#

I've told this story before but i once put two bulbs in a roommate's light fixture, they stopped connecting to the thread network after a day and one of the bulbs would not factory reset after performing the on/off dance. Just complete garbage

fading hull
# coral parcel anyways, update nanoleaf bulbs over bluetooth with the phone app, it's the only ...

I tried it, but

  • the app refuses to install through the Play Store on my Android phone. It says it is not compatible with my phone.
  • the app refuses to launch when I install it from APK manually. It says it is not compatible with my phone.
  • on the iPhone of my GF, I can't connect to the bulbs because it requires Apple Home, but I hesitated to bloat her phone with that stuff so far.

I assume the issue with my Android phone is that I am running a custom ROM (Lineage OS 14), and Nanoleaf is actively blocking custom ROMs.

coral parcel
#

Nanoleaf requires your device to pass play integrity checks for no reason

fading hull
#

I just got a few Matter Eve Energy's and I see that they have the OtaSoftwareUpdateRequestor Cluster on Endpoint 0. The Nanoleaf bulb does not have such an attribute. Perhaps that is the issue? It does not say that it can do OTA?

fading hull
#

Can anyone tell me how I can check what Matter version a given device is using at the moment? I don't see that on the device info page in HA and the Matter server's UI is quite cryptic...

narrow jackal
narrow jackal
coral parcel
#

there's some assumptions you can make from the device - e.g. if it implements a cluster or cluster version added in a specific matter spec, it must be using that spec version or later. but the matter spec version certified against and the matter sdk version used are both separate things.

#

(honestly, one of the biggest benefits of a matter device getting "upgraded" to a newer matter version is actually that it's getting a newer matter sdk with bugfixes, not necessarily anything related to spec changes)

jolly violet
#

FWIW its worth, I was able to get the NanoLeaf App (Android) to pair ( showed connected via bluetooth) to an already operational Matter/Thread Essentials A19 and the App was able to upgrade the bulb from 3.5.10 to 3.6.196, and right after that to 4.1.3. HA Matter/Thread kept right on working no problem and also sees the bulb's updated version. And to finish, the DCL's latest is 3.6.196