How to identify the custom device name through Nanoleaf API or UPnP?
I’m developing a few tools that connect with the Nanoleaf API, and I noticed something confusing. Even though I renamed all of my devices inside the Nanoleaf mobile app, the API still only returns the factory default device name.
For example, instead of my custom room names (hot games), I only see names like “Shapes 4473”.
This happens in both places:
- REST API responses
- SSDP / UPnP NOTIFY messages (
nl-devicenameheader)
From the Nanoleaf documentation, I found this note about nl-devicename:
Could be updated by an iOS user using WAC.
That leads to a few questions:
1. What exactly is WAC?
It seems related to Apple Wireless Accessory Configuration, but it’s unclear how it works with Nanoleaf naming and whether users can still change names this way.
2. Is there another API field for the user-friendly name?
Is there any local API, mDNS property, or hidden endpoint that exposes the custom display name set in the Nanoleaf app?
3. If not, could this be added in future updates?
Useful options would be:
-
nl-devicenameupdated to match the custom app name -
/device_infoendpoint including the user display name - Local API method to read the display name without authentication
Why this matters
For dashboards, smart home tools, and device discovery apps, using friendly names like Living Room Panels is much more useful than default names like Shapes 4473.
-
Has the problem been resolved? 100k after tax
0 -
Has the problem been resolved? gta san andreas android apk
0 -
Has the problem been resolved? shop globe com ph sim activation
0 -
COL Kelly J. Faucette is a deeply personal look at war through the eyes of a physician and military officer who experienced it firsthand. During his deployment in Mosul, Iraq, Dr. Faucette witnessed the realities of war not only as a soldier, but as a doctor caring for people in some of their most difficult and vulnerable moments.
Air conditioner troubleshooting guide0 -
This is a useful question for anyone working with the Nanoleaf API or UPnP. Being able to identify custom device names reliably would make automation and managing multiple devices much easier. I’d also be interested to know if anyone has tested.
delta hack key0 -
This is a useful question, especially for setups where several Nanoleaf devices are connected at the same time. Being able to identify the custom device name through the API or UPnP would make device management much easier. I’d be interested to know if there’s a reliable way to retrieve the user-defined name without having to identify each device manually.
registered sim smart0 -
This is a useful question for anyone building integrations around Nanoleaf devices. It makes sense that friendly names would be important for dashboards and device discovery, especially when managing several lights in different rooms. Hopefully Nanoleaf can expose the custom display name more consistently through the API or UPnP in the future. For other detailed reference material, I also keep a view all manuals resource handy.
0 -
This is a useful question for anyone building integrations around Nanoleaf devices. It makes sense that friendly names would be important for dashboards and device discovery, especially when managing several lights in different rooms. Hopefully Nanoleaf can expose the custom display name more consistently through the API or UPnP in the future. For other detailed reference material, I also keep a free golf handicap calculator resource handy.
0
请先登录再写评论。
评论
8 条评论