Saltar al contenido principal
👋 ¡Hola, fan de Nanoleaf, encantado de verte! ¿Necesitas enviar un ticket? ¡Haz clic aquí para contactarnos! 💚

How to identify device friendly name via UPnP/API call?

Comentarios

3 comentarios

  • Comentario oficial
    Nanoleaf CX Community Management
    Nanoleaf Community Team (Verified)

    The “user-friendly name” isn’t actually stored on or accessible from the device itself. Support for renaming was added to meet HomeKit certification requirements, but providing a way for users to change it depends on Apple’s interface, which is not currently available.

    As a result, the device name defaults to the unique identifier printed on the controller. This is intentional, as the device name is used to set the service instance name on mDNS. Allowing it to be freely changed could lead to naming conflicts between devices, which may cause connectivity or discovery issues.

    By keeping the controller’s predefined unique name, it ensures reliable mDNS operation. This may also explain why Apple has not enabled a user-facing option for renaming, despite requiring OEMs to support the capability.

  • iLikeAurora

    Hey there, I stumbled into the same issue: Users are used to name their devices - AND find their devices by their user-defined name. If you feel that there should be a unique name, make that a e.g. “uniqueName” field, and store the user defined name in the name field.

    Regarding mDNS discovery: Any app that would not use the device ID and instead use the device name for unique identification would be considered bad coding. 
    When you change behavior in this case, inform developers about it in advance. A properly developed app should not stumble about this in any way.

    0
  • David Kery

    I agree that having the user-configured friendly name available through the API would be very useful, especially for people managing multiple devices. It would make device identification much easier than relying on the factory name and MAC address. Hopefully Nanoleaf can expose this through the LocalAPI in a future update

    0

Iniciar sesión para dejar un comentario.