Nanoleaf host won't save

  • Build: HEAD detached at 2.0.0-alpha.10.1


    I'm able to discover and identify my Shapes set, and the host and token seem to be working, but when I save the host information is lost.


    Not sure if this might be related to having multiple Nanoleaf sets on my network? Could be that the SSDP Discovery Service is getting confused by the other sets?


    Also seeing these error intermittently when try to save or turn on output:

    [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'nanoleaf' signals error: ' Open error. UDP Socket not initialised!'


    Code
    2021-10-05T08:31:10.177Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:148:get()) GET: [http://:16021/api/v1/sEW4TXvovYhmBy0K330zXMnQ2MfOqx35/]
    2021-10-05T08:31:10.178Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:237:getResponse()) Reply.httpStatusCode [0]
    2021-10-05T08:31:10.178Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'nanoleaf' signals error: 'Getting device details failed with error: 'Host  not found''

    But it seems like these are just related to the missing host name?


    Is this a bug, or am I doing something wrong here?

    • Offizieller Beitrag

    2021-10-05T08:43:38.696Z [hyperiond SSDPDISCOVER] (DEBUG) (SSDPDiscover.cpp:294:discoverServices()) [2] service record(s) found 2021-10-05T08:43:38.697Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1428:handleLedDeviceCommand()) response: [{"devices":[{"cache-control":"no-cache=\"Ext\", max-age = 60","id":"http://:16021","ip":"","location":"http://:16021","other":{"ext":"","nl-deviceid":"CF:8A:E4:90:74:CE","nl-devicename":"Shapes E76F","s":"uuid:e91115d9-6634-471a-8b03-0a7715fbee0e"},"port":16021,"server":"","st":"nanoleaf:nl42","usn":"uuid:e91115d9-6634-471a-8b03-0a7715fbee0e"},{"cache-control":"no-cache=\"Ext\", max-age = 60","id":"http://:16021","ip":"","location":"http://:16021","other":{"ext":"","nl-deviceid":"62:E1:C7:7A:30:97","nl-devicename":"Shapes 2ADB","s":"uuid:c0b1d9b0-b603-4507-be8f-611e027f1a8f"},"port":16021,"server":"","st":"nanoleaf:nl42","usn":"uuid:c0b1d9b0-b603-4507-be8f-611e027f1a8f"}],"discoveryMethod":"ssdp","ledDeviceType":"nanoleaf"}]

    I would need to check what happens during discovery.
    The response does not include the IP-Address and I would need to investigate why.

    To get it working, you can select "Custom Device" and configure the device's IP-Address manually until we figure out more...

  • Same issue occurs when I use "Custom"


  • Could've sworn I had tried it both ways, but that seemed to have gotten it mostly working.


    I am getting an issue deploying a custom LEDs tho. When I connect it it complains:

    "The hardware LED count (17) is greater than LEDs configured via layout (16),

    1 LED will stay black if you continue"


    I can either override or continue, it doesn't seem to matter much. If I override, it pushes a layout with the correct number of LEDs but the wrong positions. If I continue, it pushes the stored layout with the correct positions, but missing one LED.


    If I then go to the LED Layout tab and paste my corrected layout into the box, it complains:

    "The hardware LED count (1) is less than LEDs configured via layout (17).

    The number of LEDs configured in the layout must not exceed the available LEDs"


    And it won't save the configuration for the next load. Also it still isn't saving the IP address in the UI.


    • Offizieller Beitrag

    jackthias Let us sort one thing after each other. I need to see how the Shapes respond to the ssdp discovery. Strange is that the responses do not contain an IP-address, but that might be to the fact that the message looks different.


    Would you mind

    a) download the attached python script (ssdp.py.txt) and rename it to ssdp.py

    b) upload ssdp.py to the server where Hyperion is executed

    b) run the script in the directory where the script resides

    python ssdp.py

    c) Share the output with me

    • Offizieller Beitrag

    2. Would you mind to put the following into your browser url field and press return

    http://192.168.1.126:16021/api/v1/sEW4TXvovYhmBy0K330zXMnQ2MfOqx35

    Share the output

    I assume that the device with IP=192.168.1.126 is the one that you have the LED-Number/Layout problem with?

  • For what it's worth, I have managed to deploy the correct layout, although I'm unsure what exactly did it. I am still getting some wonkiness (same issues mentioned above: hostname isn't saving, complains there's only 1 LED, etc) when I try to change the configuration tho, so I wouldn't mind continuing to debug this, so that I'm able to make changes if I need to.


    I've attached both responses.

    • Offizieller Beitrag

    Thank you.
    Would you mind checking the ssdp-esp.txt file again, please?
    It contains the Nanoleaf data and not the ssdp output from the script.
    You can also post the file via a private conversation, if you like.

    • Offizieller Beitrag

    That the host information is not available after discovery is a Nanoleaf issue which you see as an effect in Hyperion.


    See the feedback by Nanoleaf:


    „Hi @Lordgrey

    This is a known issue and will be resolved soon. Thanks for reporting it. I will let you know once its ready for release. There is an internal ticket for this already and we are working on it.

    Apologies for the inconvenience caused.

    Regards“


    I will forward when they come back.

    Until then, please provide the hostname/IP-Address manually using the custom configuration possibility.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!