Shelly passwords have to be re-entered in HA

[KruseLuds]

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

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.1
Stage	running
Available Repositories	1466
Downloaded Repositories	29

AccuWeather

can_reach_server	ok
remaining_requests	29

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 13.1
update_channel	stable
supervisor_version	supervisor-2024.08.0
agent_version	1.6.0
docker_version	26.1.4
disk_total	491.4 GB
disk_used	27.5 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	kvm
board	generic-aarch64
supervisor_api	ok
version_api	ok
installed_addons	Matter Server (6.4.2), AdGuard Home (5.1.1), Log Viewer (0.17.0), Home Assistant Google Drive Backup (0.112.1), File editor (5.8.0), Core DNS Override (0.1.1), Cloudflared (5.1.19), Mosquitto broker (6.4.1), Ring-MQTT with Video Streaming (5.7.1), RPC Shutdown (2.5), Studio Code Server (5.15.0), DbStats (0.5.8), Advanced SSH & Web Terminal (18.0.0)

Dashboards

dashboards	10
resources	20
views	44
mode	storage

Recorder

oldest_recorder_run	August 11, 2024 at 1:29 PM
current_recorder_run	September 9, 2024 at 8:52 AM
estimated_db_size	3533.50 MiB
database_engine	sqlite
database_version	3.45.3