Shelly passwords have to be re-entered in HA

KruseLuds commented 2 weeks ago

The problem

I have 43 or so shelly devices. Randomly once per week or so I am asked to re-enter the password for one or more of them. They all have unique 30 digit passwords. I was ablet to get somediagnostic information and will get more with your guidance if needed. In the past it has been relays but in this instance it was three Shelly Plugs needing the password to be re-entered.

What version of Home Assistant Core has the issue?

core-2024.9.1

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

Shelly

Link to integration documentation on our website

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

Diagnostics information

MBR CNL Bedside Outlet config_entry-shelly-91e42ee2974f71f6bcfe7cdead2e8c3c.json Den Outlet by Front config_entry-shelly-628584ac83975930a9bbd8b5557221f0.json Bedroom 3 shelly fan outlet config_entry-shelly-01J6N0FHN0PQPBSCZEQH8CQFET.json

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

No response

Additional information

For the above three sensors I re-entered the password and the authentication issue went away. I then downloaded the diagnostic files as above, and when I then turned off the debug logging it tried to save the log but this popped up in the corner of my chrome browser:

When I click on the "keep" button nothing happens. Then closing and reopening the browser made that message go away but the log is nowhere to be found. I tried looking in the trash bin (Windows 11) and there was nothing there. Digging into the browser download history I was able to see this but there is no way to retrieve the file which unfortunately is now long gone:

Using the three buttons to get that menu and selecting the option to try to re-download the file fails.

How do I get that file, and do you still need it? I have turned on the debug logging to try to catch the issue again but I won't be able to keep the resulting log file without some guidance... How do I resolve that (if needed)?

(I have turned the debug logging back on to try to capture a log again if needed for when it next happens)

Also below is my HA setup:

System Information

version	core-2024.9.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.46-haos
arch	aarch64
timezone	America/New_York
config_dir	/config

Home Assistant Community Store

AccuWeather

can_reach_server | ok -- | -- remaining_requests | 29

Home Assistant Cloud

Home Assistant Supervisor

Dashboards

Recorder

home-assistant[bot] commented 2 weeks ago

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `shelly` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign shelly` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

shelly documentation shelly source _{^{(message by IssueLinks)}}

KruseLuds commented 2 weeks ago

It happened again with a different device and I have the log file but do not know how to get it to you. It goes along with the below diagnostic file, for my Kitchen Shelly +1 Relay that required reauthentication this morning (I was able to use a different browser to download the log file):

config_entry-shelly-d736fef589ec5de55e2e2749ce4ed01c.json

The log file is 19.17 GB - and that is just from one day of debug logs, sheesh. I compressed it into a .zip file which is itself 1.07 GB, still far above the 25MB limit for uploads here. How do I get the file to you? Can I email it? Can you give me an FTP location?

Please help, this is happening to me every day.

KruseLuds commented 2 weeks ago

From above -

"The log file is 19.17 GB - and that is just from one day of debug logs, sheesh. I compressed it into a .zip file which is itself 1.07 GB, still far above the 25MB limit for uploads here. How do I get the file to you? Can I email it? Can you give me an FTP location?"

Please advise

chemelli74 commented 2 weeks ago

How do I get the file to you? Can I email it? Can you give me an FTP location?"

Please advise

I would use one of the numerous free file sharing service

KruseLuds commented 2 weeks ago

OK the 1.07. GB (.zip) file is here in it's own folder in dropbox and shared - please reply that you can or cannot retrieve it, thank you:

https://www.dropbox.com/scl/fo/rdeiia7i6r1f3guhge95a/AJNNSKS8JBuMrhe8mKJkrx8?rlkey=do9m10j1q28fa8hp3bifltm9m&st=2ibovs1m&dl=0

thecode commented 2 weeks ago

I successfully downloaded the file, will look at it tomorrow

KruseLuds commented 2 weeks ago

@thecode thank you

KruseLuds commented 1 week ago

@thecode any update?

thecode commented 1 week ago

The log shows that the device reports invalid authentication after already passing the authentication phase. This can happen if you change the password during runtime (which I am 100% sure you didn't), so for now I have no clue why the authentication is breaking. I have left few devices with authentication enabled but could not reproduce the issue. We will discuss it internally and report back.

KruseLuds commented 1 week ago

Thank you, you may need to leave some devices up and running for a while I guess. FYI my passwords are all 30 digits is that makes any difference

From: Shay Levy @.> Sent: Sunday, September 22, 2024 3:39 AM To: home-assistant/core @.> Cc: KruseLuds @.>; Author @.> Subject: Re: [home-assistant/core] Shelly passwords have to be re-entered in HA (Issue #125672)

The log shows that the device reports invalid authentication after already passing the authentication phase. This can happen if you change the password during runtime (which I am 100% sure you didn't), so for now I have no clue why the authentication is breaking. I have left few devices with authentication enabled but could not reproduce the issue. We will discuss it internally and report back.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/125672#issuecomment-2365787473 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXBJ5MIH4ZDUAQXEVMOWXK3ZXZX2HAVCNFSM6AAAAABN62JFPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVG44DONBXGM . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXBJ5MK4HY6KP4WILSMVFG3ZXZX2HA5CNFSM6AAAAABN62JFPWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUNAMGVC.gif Message ID: @. @.> >

home-assistant / core