1/2 unreachable via network then unable to pair again

Started by raybies


2-3 weeks my normal schedule for 2 instances of Canvas started at different times.
Additionally I noted that my Stream Deck was unable to control the Canvases.
Alexa and the App where able to control the Canvases.
DHCP server (opnSense box) showed status as off-line, they're in the same VLAN as ALL my other IoT devices (62) which work flawlessly.

With 1 unit I tried a soft reset, I could pair via the app, but no change from above.
Tried hard reset.
After 3 days and MANY hours I have been able to pair the Canvas and Andriod App.

Please adivse.

Josh N

Hello @raybies,

Thanks for bringing this up, I apologize for the inconvenience this has caused you. I would be happy to help look into this for you - could you confirm the following:

  • Was it working well before?
  • Did this start happening after an update?
  • Are your Nanoleaf Canvas on the latest Firmware?
  • Is your App version and device OS version up to date?

If you have any questions, please let me know.

Kind regards,


@"Josh N." I had a similar issue.
It boils down to the fact, that the Nanoleaf Canvas updated to FW 6.2.1 automatically and without myself even been asked for.
During that update Nanoleaf changed its MAC address itself. That triggered that the router assigned a new IP Adress (and not using the fixed assigned one).
I was similar puzzled that my setup did not work from one day to another.

It took me a while figuring out that a FW update caused all this; plus it brought additional bugs in on top, e.g. that ssdp does not provide an IP Adress.

Not something I was very happy about…


I have 4 devices 1 iOS and 3 Android.
I was able to connect the after MANY hours by:
1.- Joining the Canvas WiFi AP directly then it found the device and added it to App.
2.- Then I was able to update the WiFi settings from Canvas2575 to my network via the App. This option should be there from the start.

It's still invisible on my network to other devices. The MAC address didn't change.

@Nanoleaf please make available a WebUI to configure the Canvas/Shape/Aurora directly without messing around for days trying to get the App to do it. Maybe look at Tasmota for the correct way to do this.

Aliakbar Eski


Which app did you use to pair with the controller? iOS or Android?

Further, when you updated the wifi settings, did the panels on the Canvas flash green. That is a confirmatory flash that the device has joined the WiFi network. At which point your DHCP server should provide it with an IP address which you should be able to ping.

What do you mean by indivisible to other devices? Are you talking about mDNS discovery? Does it now show up under mDNS? On iOS and Android you can download apps from the App Store / Play Store that can help show you if the device is available on the network. It will also show you the IP address so you cause that to ping the device. I can link you to the apps if you want.

If all of the above works, your app should be able to connect as well, on both iOS or Android.

Also would you be able to let me know the Firmware of your Canvas controller?

I am determined to help you resolve this. @"Josh N." and I will work together with you and we will have this resolved.

Aliakbar Eski


I used Android App to pair.
I seem to remember a green flash and also blue, but this is just by memory. I don't want to delete the Device and try again because I seriously spent many hours trying before.
I didn't write "indivisible" I wrote "invisible". I have home automation devices and they couldn't see the Canvases.
I use IPs instead of DNS, and my OpnSense box was assigning an IP but then reporting the Canvases as being offline. Not sure where to find the IP in the Android App, but I know the IP from DHCP server.

Both of my Canvas:
FW 6.2.1

DHCP: - 02:55:da:04:25:** - fireplaceCanvas - static - offline - 00:55:da:54:25:** - officeCanvas - static - online (just now)

Pinging with 32 bytes of data:
Reply from Destination host unreachable.

Pinging with 32 bytes of data:
Reply from bytes=32 time=4ms TTL=64
Previously neither would return PING, and were not "visible" on the network from home assistant or OpenHAB or StreamDeck, but the Android App could still control them.

Just now returned all PINGS, so I assume will also be visible to the above automation sw.

Both still controllable from Android App.

My WiFi is AP only.
Both same VLAN.
Both same AP.
No firewall rules.

The reality is that both Canvases started to malfunction by themselves and schedule start times broke.
When I tried readding them I was unable to until I connected to their Wifi AP directly and then updated the WiFi through the App but not readding them… this method doesn't even seem to be documented.

Currently 1 is working ( as expected while the other is 1/2 working from a communications perspective.

Aliakbar Eski

Hey @raybies

A green flash is good. That means the controller has associated with the wifi network. Don't reset your working system right now. So long you have some memory of a green flash, we are good.

Sorry about the typo, I did mean to ask what you mean by invisible. I am assuming "see" the devices basically means if the HA devices can ping the device.

If the android app can control the devices, it means its able to figure out the IP address of the device. The app controls your device on the local network not over the internet. You can check this by simply turning off WiFi on your phone and you will see the app lose connection with the device.
The app uses mDNS to discover the IP address of the device. Its possible the controller did not receive an IPv4 address at all and the app is working over IPv6.
I am not sure what the logic for your DHCP server is to assign IP address, particularly if you are working with static IPs. Maybe you did not configure the IP address for the Canvas 0425.
Actually, on a hunch, try configuring it with this MAC address: 00:55:da:04:25

I am not sure what happened with the pairing process on the app. I have never experienced that before.

the schedule start times breaking is another issue, although, can you verify they are still broken on the Canvas that's now connected to the network and can be pinged?

Hope this helps
Aliakbar Eski