Closed VenominousX closed 4 months ago
Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
Known issue. Error handling will be improved soon.
You can disable the OTA providers for now. See the ZHA docs page, copy the OTA YAML part, but change all providers to false
.
Other issue:
Docs:
Copy this YAML section into your configuration.yaml
, but change true
to false
everywhere. https://www.home-assistant.io/integrations/zha/#ota-firmware-updates
Nope, does not work with zha config. Is it possible to install a check that determines the manufacturers used and only activates the OTA function for the existing manufacturers used? I only have Aqara, Hue and INNR devices, as only manufacturers that are not listed in the ZHA Config. This is slightly annoying when you are disabled by functions for devices that you don't even use yourself.
Again, it's a known bug. Error handling will be improved soon.
Try this:
zha:
zigpy_config:
ota:
ikea_provider: false
ledvance_provider: false
salus_provider: false
sonoff_provider: false
inovelli_provider: false
thirdreality_provider: false
If it doesn't work, post the updated exception and integration diagnostics if they can be downloaded.
Yes, i have understood that this is a bug and that it will be fixed. The question i asked is also more about providing device-specific functions in the future if you also use these devices. For now i have restarted my system via mobile Hotspot so that everything like the security works. I am at work now, so I can't deal with it right now. Thank you for your answers.
12.02.2024 08:12:38 TheJulianJES @.***>:
Again, it's a known bug. Error handling will be improved soon.
Try this:
zha: zigpy_config: ota: ikea_provider: false ledvance_provider: false salus_provider: false sonoff_provider: false inovelli_provider: false thirdreality_provider: false
If it doesn't work, post the updated exception.
— Reply to this email directly, view it on GitHub[https://github.com/home-assistant/core/issues/110321#issuecomment-1938152349], or unsubscribe[https://github.com/notifications/unsubscribe-auth/APYRWIUHGFYINSMSCNF22ALYTG6GLAVCNFSM6AAAAABDEHA5MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGE2TEMZUHE]. You are receiving this because you authored the thread. [Verfolgungsbild][https://github.com/notifications/beacon/APYRWITKICVYQTWBGKC6NVLYTG6GLA5CNFSM6AAAAABDEHA5MGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTTQXNZ2.gif]
@TheJulianJES The configuration as you have posted it works. I had copied the yaml configuration from home-assistant.io/integrations/zha/#ota-firmware-updates this morning and set true => false, which doesn't work. Unfortunately I didn't have time to correct it this morning. Thanks for the hint.
The ZHA configuration after copy and paste and storing:
Looks like the sonoff line is missing on the website
The problem
I am currently having problems with my ISP, the Internet is not working. My Home Assistant is restarted every morning, which now leads to the problem that nothing works anymore.
No lights, no buttons, no monitoring - nothing that depends on ZHA works without internet. Wasn't Home Assistant's plan to not need this dependency to work?
If I use my mobile data to connect to the Internet as a test, everything starts. This is not a good solution.
What version of Home Assistant Core has the issue?
2024.2.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
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
home-assistant_zha_2024-02-12T06-45-05.174Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response