home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.51k stars 30.71k forks source link

Nanoleaf requires frequent reconfiguration which always fails #87690

Closed axiomatic-mk closed 1 year ago

axiomatic-mk commented 1 year ago

The problem

Since a few months ago Nanoleaf integration prompts for a reconfiguration, which always fails - following the instruction to press and hold the power button to get the LEDs blinking still produces the error 'Nanoleaf is not allowing new tokens, follow the instructions above.' despite the LEDs blinking as expected.

This behaviour is more and more frequent over time.

What version of Home Assistant Core has the issue?

2023.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nanoleaf

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nanoleaf

Diagnostics information

No diagnostics available from integration.

Example YAML snippet

Not applicable.

Anything in the logs that might be useful for us?

Despite enabling debug logging this integration does not provide any log entries.

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @milanmeu, mind taking a look at this issue as it has been labeled with an integration (nanoleaf) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `nanoleaf` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign nanoleaf` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


nanoleaf documentation nanoleaf source (message by IssueLinks)

Trurl101 commented 1 year ago

I have probably the same problem. I have three Nanoleaf shape integrations. All of them worked fine. Suddenly one needed a "reconfigure" in Home Assistant. I hold the power button for 5 seconds and LEDs start flashing but Home Assistant can not connect: "Nanoleaf is not allowing new tokens, follow the instructions above."

I reset the Nanoleaf device but it still does not work. All three devices work fine in the Nanoleaf app (and Google Assistant). The other two shape devices continue to work in HA.

magicbenny commented 1 year ago

this also happens to me relatively often. the quick and dirty solution is to remove the respective Nanoleaf Device, restart HA and then HA discovers a new device which can be newly configured. not the best solution but it is a work around to get them back into HA.

Ladonize commented 1 year ago

This issue happend to me as well yesterday. One Nanoleaf suddenly required reconfig (after 6 months with no problems) but I had no problem reaching and controlling the device trough Nanoleafs own mobile and desktop app. It seems to be an integration issue. @magicbenny your solution worked, thanks!

Cavorter commented 1 year ago

I have a fairly recent install and one of my Nanoleaf installs (Lines) started exhibiting this exact behavior this morning as well. Works fine with the Nanoleaf apps and a couple of custom solutions that have been in operation a lot longer.

Trurl101 commented 1 year ago

this also happens to me relatively often. the quick and dirty solution is to remove the respective Nanoleaf Device, restart HA and then HA discovers a new device which can be newly configured. not the best solution but it is a work around to get them back into HA.

I can confirm that deleting the device in HA and reconfig it works.

Cavorter commented 1 year ago

I can confirm that deleting the device in HA and reconfig it works.

Yes, but apparently I have to do that at least two times a day now if I want those light panels to be usable in HA. I didn't see an obvious way to automate that yet. :-)

tkdrob commented 1 year ago

I only use the triangles and these work fine. What models are all of you using?

Cavorter commented 1 year ago

I only use the triangles and these work fine. What models are all of you using?

I have three installations: 1 Panels (the old triangles), 1 Shapes (Hexagons and new Triangles), 1 Lines (60 degree). It's kind of interesting that there were two days that I had to remove and re-add the Lines a total of 5 times, but now it's been stable again since.

tkdrob commented 1 year ago

I may have seen this too but can't remember. I would have blamed my Wi-Fi and network setup first. Maybe some time I will take out my squares.

axiomatic-mk commented 1 year ago

Some additional details from my side - I have two Nanoleaf light instances that are both affected by this issue, with varying frequency:

Both started acting up more or less at the same time, and the issue has existed since Core 2022.11 I think.

magicbenny commented 1 year ago

It was calm for a few days. Installed 2023.3.0 yesterday, everything was fine so far. then there was a Nanoleaf Firmware Update available 7.1.3 -> 7.1.4 and I had to reconfigure again. maybe this helps.

jparchem commented 1 year ago

Same here. The firmware update from 7.1.3 -> 7.1.4 happened for me as well. Afterwards, HA said that my lights needed to be reconfigured. Only for me, I had to delete and re-add for them to work again. Going thru the reconfiguration steps did not work.

tazmad commented 1 year ago

I have two shapes and one canvas, one of the shapes dropped out and wouldn't let me reconfigure, the other shapes and canvas has stayed working with no issues throughout. I got myself into a mess by accidentally disabling the entity rather tan deleting it and re-adding, currently working on sorting that out.

Schonhoffer commented 1 year ago

Same problem:

GBurchel commented 1 year ago

Same problem here with my 4 shape and 1 canvas setups

Schonhoffer commented 1 year ago

Here's what my core.config_entries has. Two of the control panels have the same IP, all three have generally the same token, although for some reason one is slightly varied in the first and last digit, but otherwise the same.

To be clear, the three obfuscated portions of the screenshot are the same string.

2023-04-01 15_20_54-core config_entries - home-assistant - Visual Studio Code

KC-inDomus commented 1 year ago

Same here. Quite annoing. The only solution is removing the integration and redoind the process in full - loosing, btw, every kind of customization you may have applied.

GBurchel commented 1 year ago

Same here. Quiet annoing. The only solution is removing the integration and redoind the process in full - loosing, btw, every kind of customization you may have applied.

My solution is to create a helper for each nanoleaf and use the helper in the automations, then when it falls over u just have to replace the nanoleaf in the helper

tazmad commented 1 year ago

@GBurchel

My solution is to create a helper for each nanoleaf and use the helper in the automations, then when it falls over u just have to replace the nanoleaf in the helper

Any chance you can provide more info on how exactly you’ve done this as it sounds like the best work-around for now, thanks in advance for any help!

bcink commented 1 year ago

Still not resolved after several months :(

codahq commented 1 year ago

There's no work because there's nobody assigned. Does this integration have a maintainer? @milanmeu any help on how to get some progress on this?

nickpdawson commented 1 year ago

Same issue on all my Nanoleaf products.

Merlin5005 commented 1 year ago

Had the issue today on my Nanoleaf Shapes, while to more sets of lines worked perfectly. Fixed it with a backup from some days ago.

Cleanbands-Dev commented 1 year ago

Similar issues for me with canvas. Can't figure out how to remove integration however. No delete option, only option is to reconnect, which fails.

image

tazmad commented 1 year ago

@Cleanbands-Dev,

if I am reading this right you’re having trouble removing and then reading your canvas. Go to the nanoleaf integration and delete the canvas from there. You’ll then be able to re-add it.

HTH

kmanan commented 1 year ago

Did we solve this? My Shapes keep disconnecting and then when I to reconfigure, I keep getting this error: Press and hold the power button on your Nanoleaf for 5 seconds until the button LEDs start flashing, then click SUBMIT within 30 seconds.

Nanoleaf is not allowing new tokens, follow the instructions above.

nickpdawson commented 1 year ago

as of today I'm still have the same error @kmanan

GBurchel commented 1 year ago

@GBurchel

My solution is to create a helper for each nanoleaf and use the helper in the automations, then when it falls over u just have to replace the nanoleaf in the helper

Any chance you can provide more info on how exactly you’ve done this as it sounds like the best work-around for now, thanks in advance for any help!

My work around is Settings, devices& services, helpers Create helper Group Light group- name this what u want to call your nanoleaf and add the entity of the nanoleaf

Now use this helper in all automations, dashboards ect.

When the nanoleaf falls over delete it and then reinstall it, then go to the helper for that nanoleaf and change the entity under group options.

Your nanoleaf will then be working again whith out the hassle of changing all your automations ect

Schonhoffer commented 1 year ago

Reporting in that my panels continue to disconnect regularly. /bump

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

brimmasch commented 1 year ago

it's pretty silly to mark an issue with 31 comments with many unique individuals watching and subscribed. like... really silly. there is clearly an issue and nothing the reporters can do. the system is meant to de-incentivize spam. so... what do we have to do here?

kmanan commented 1 year ago

Agreed. Not big enough of a problem so auto close it... that's one way to address issues.

NvL-WEAP commented 1 year ago

Same issue here! I have 3 nanoleaf setup's. One of them always loses connection with the API. Trough the nanoleaf app everything works fine.

Trying to add the device again leads to a Nanoleaf is not allowing new tokens, follow the instructions above.

Re-adding helps for a short time.

This issue shouldn't be closed, due more people are facing this issue.