Skip to content
Home Assistant TestFlight
Lighting

Nanoleaf

nanoleaf

Built inLocal push

The Nanoleaf integration allows you to control and monitor Nanoleaf Light Panels, Canvas, Shapes, Elements, and Lines.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
lightLight
buttonButton (as a switch)

2 reports below say how a device from this integration behaves in the Home app.

What people report

Core Nanoleaf covers panels over the local API; Essentials products are not in core and users are pointed to a custom component. Firmware 5.x broke effect parsing, fixed in the library.

  • Partly works3
  • Requested1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Nanoleaf Essentials Floor Lamp NL72K4Partly works LocalFirmware 5.2.57 caused effect exceptions and stale on/off state; library fix confirmed
Saved copy
The problem ### Description After upgrading a Nanoleaf Essentials Floor Lamp NL72K4 from firmware 4.x.x to 5.2.57, two regressions appeared in Home Assistant, partially via `aionanoleaf2`. The first issue affects effect response formats and causes exceptions in Home Assistant. The second causes the physical lamp and its Home Assistant entity to temporarily disagree after turning the lamp off. These issues did not occur with the previous 4.x.x firmware. ### Environment - Device: Nanoleaf Essentials Floor Lamp - Model: NL72K4 - Previous firmware: 4.x.x - Current firmware: 5.2.57 - …

Excerpt saved from GitHub on 2026-10-23.

Issue #184440 · 2026-10
Nanoleaf LinesPartly worksWorks in Home
Works via HomeKit while HA shows unavailable
Dropouts mitigated by firmware update and repairing
Saved copy
I was able to mitigate this issue for my Nanoleaf Lines by updating them: 1. Reset my lines and removed them from HA 2. Paired them directly to the Nanoleaf iOS app 3. Updated them from version `9.5.9` to `9.6.4` 4. Removed them from the app and Apple Home and performed another reset 5. Re-paired them to HA via the Nanoleaf integration It seems to have worked (for now, at least). I'm no longer seeing issues with dropped connections

Excerpt saved from GitHub on 2026-10-23.

Issue #118542 · 2024-05
Nanoleaf SkylightPartly worksWorks in Home
Controllable through HomeKit even when HA shows unavailable
Integration marks it unavailable repeatedly; HomeKit-bridged scenes unsupported
Saved copy
The problem I received a Nanoleaf Skylight last week. Since them HA integration has been a bit of hit and miss. Multiple times a day the light would become "unavailable" as reported by the Nanoleaf HA integration. Thing is: It isn't! I can still control the light through the app or even through HA itself over the Homekit integration (which unfortunately does not support the build-in scenes, so its not really a work around). I do think this is API-related somehome, because - while Homekit always works - when I start the smartphone app, I can see the light listed there also as "unavailable". …

Excerpt saved from GitHub on 2026-10-23.

Issue #118542 · 2024-05
Nanoleaf Essentials (Rope Lights NL72K6, Lightstrips, String Lights)Requested LocalCore support PR closed; custom component suggested for Essentials
Saved copy
Summary - Add support for Nanoleaf Essentials devices (Rope Lights NL72K6, Lightstrips, String Lights, etc.) - Enable effects/animations control via direct HTTP API for Essentials devices - Essentials devices use a different API than Panels for effects, so we bypass `aionanoleaf` library and make direct HTTP calls ## Details ### Supported Essentials Models | Model | Product | |-------|---------| | NL71K1/K2 | Holiday String Lights | | NL72K1/K3/K4/K6 | Indoor Lightstrips, Floor Lamp, Rope Lights | | NL73K1/K3 | Outdoor String Lights, Permanent Outdoor Lights | | NL75K1 | WiFi A19 Bulb | ### …

Excerpt saved from GitHub on 2026-10-23.

PR #160268 · 2026-01

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local push

Talks to the device on your network, and the device tells Home Assistant the moment something changes.

Found automatically over

  • HomeKit pairing
  • SSDP/UPnP
  • Bonjour (zeroconf)

Devices that also speak HomeKit

  • NL29
  • NL42
  • NL47
  • NL48
  • NL52
  • NL59
  • NL69
  • NL81

These can pair with Apple Home directly, without Home Assistant.

Details

Installs (analytics)6,461 (0.91%)
Added inHome Assistant 0.67
Set up in the UIYes
Maintainers@milanmeu, @joostlek, @loebi-ch, @JaspervRijbroek

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.