Closed xrsprint closed 2 years ago
confirmed. with 2022.7.6 Shelly Gen1 work again. So Microsoft was not guilty?
They are. There is a workaround added here. Sadly other integrations are also affected.
Had similar issue here as well, although initially not all Shelly devices were broken. Probably because I don't them all constantly. After restarting HA I got a lot of "Timeout during device setup" from all Gen1 devices as well including the Shelly Plug S and Shelly Button. I ended up in this thread and removed the KB which now fixed the issue.
I'll checkout the patch 2022.7.6 later when I have some more time, but I wanted to compliment the contributors and mostly @skoog84 @thecode for the find and fix!
I can confirm that the integration works again as expected. Thank you so much for fixing the problem so swiftly!
It's not working for me on 2022.7.7.
No Shelly devices are available or discoverable.
Very useful thread, thanks. Same issue here, after patching my Hyper-V server and rebooting it, my Shelly 1L stopped being recognized. As I didn't want to uninstall the security patch, I decided to fully uninstall the Shelly integration and switched over to using MQTT (which I was already using for other devices) instead of the integration. Not sure what I would be missing by doing so but so far, all good.
The problem
Hi there
This morning i had to reboot my PC for updated which is running hypervisor and HA on a VM, once restarted i noticed all of my Generation 1 shelly devices unavailable (i have about 30 of them), all Generation 2 devices were still online, after rebooting a number of times, i then rebooted all shelly devices with no luck, then rebooted everything from Switches, Wifi, Gateway, VM Host, and still no luck
i first verified all of my gen 1 devices are running the current firmware of 20220209-094317/v1.11.8-g8c7bb8d and all also have the Colo it enabled pointing back to my HA server which is 192.168.X.X:5683
i then deleted onc shelly device and tried to re-add and got the following message
note that if i delete a shelly device and then reboot, HA does auto discover it
i then factory reset the shelly unit, and still did the same issue as above . i then tried adding to configration.yaml a line to change the ColoIT port and then set it to the new port on a shelly, and no luck there either
i then decided to install a new install of HA on my VM (using the same hyper-v instance but with a new virtual disk,) meaning it kept the same IP, and then restored from a backup which was done two days ago when these were working with no luck, i then done another fresh install and starting a new HA system, which also done the same, and then reverted back to a older HA image i had with 8.1 and this also failed. i also tried changing IP addresses of the HA but keeping the same MAC of the VM and also no help there
after the tests above i believe i have ruled out the shellys and HA but the issue is still there, i can log into the units via web and control them with no issues and also i can confirm there is no firewall or blocking on the network as all these devices are on the same subnet
any help here would be greatly appreciated
Thanks
What version of Home Assistant Core has the issue?
core-2022.7.3
What was the last working version of Home Assistant Core?
core-2022.7.3
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
logs turned off
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
System Health
Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 15 July 2022 at 10:00 relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | ap-southeast-1-0.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 8.2 -- | -- update_channel | stable supervisor_version | supervisor-2022.07.0 agent_version | 1.2.1 docker_version | 20.10.14 disk_total | 30.8 GB disk_used | 3.8 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (10.0.0), File editor (5.3.3), MariaDB (2.4.0), Check Home Assistant configuration (3.11.0)Dashboards
dashboards | 1 -- | -- resources | 0 views | 5 mode | storageRecorder
oldest_recorder_run | 7 July 2022 at 09:10 -- | -- current_recorder_run | 13 July 2022 at 20:26 estimated_db_size | 207.78 MiB database_engine | mysql database_version | 10.4.19