Open jasonwragg opened 1 month ago
Hey there @nmaggioni, mind taking a look at this issue as it has been labeled with an integration (snmp
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
snmp documentation snmp source (message by IssueLinks)
As far as I remember this is the usual behavior for unreachable network devices. In my testing I see that once the default timeout is reached the integration is marked as failed, an error is logged, but startup completes anyway. Does your instance get indefinitely stuck instead?
Yes it seems to block everything else from loading and never times out.
I tested the config you posted and startup completes correctly (it takes ~1min due to timeouts, but it finishes). Please post your logs and possibly your full config so we can check if there's anything else that's going haywire.
You also have a lone 192.168.1.37
between your sensors (Pithos Disk2 State
), I suppose that's meant to point at 192.168.1.50
like the others?
192.168.1.37 is my other NAS but that was up at the time. It should be in a different file.
I'm not at home at the moment, i'll post later when I'm back.
The problem
If a monitored device is not available during the Home Assistant startup hangs until it is available again.
What version of Home Assistant Core has the issue?
2024.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
SNMP
Link to integration documentation on our website
https://www.home-assistant.io/integrations/snmp/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response