Open thany opened 7 months ago
Hey there @flacjacket, mind taking a look at this issue as it has been labeled with an integration (amcrest
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
amcrest documentation amcrest source (message by IssueLinks)
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.
Please don't close. Issue just hasn't been picked up yet.
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.
Please don't close. Issue just hasn't been picked up yet.
The problem
The Amcrest integration, after correctly setting it up in the configuration.yaml, refuses to start when the camera happens to be offline. So the whole integration doesn't load.
This is not okay. While HA is starting, and loading its integrations, the wifi and/or camera firmware might still be in the process of booting up as well (and no, delaying HA startup is not a solution). This means that any reboot might destroy the Amcrest integration if the camera just so happens to be unreachable for a moment.
The integration should load up normally, but in offline state. When the camera comes online, the integration would start working. This is how all integrations work (afaict) and that is the most sensible way of doing this. It's not okay to require wifi to work, and for the camera's firmware to be up & running, before it's "safe" to start or reboot HA.
Especially since this integration is part of HA core, I would not expect it to be like this.
What version of Home Assistant Core has the issue?
2024.2.0
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
amcrest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/amcrest
Diagnostics information
(can't do this, as the whole integration fails to start/load)
Example YAML snippet
Just make sure the camera is not reachable.