You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, when DNS resolution failed for a device, the Ping Integration properly reported it as offline.
But since Home Assistant Core 2024.6.2 (or possibly a bit earlier), DNS resolution failure makes the entity Unavailable.
This is a real problem because many DHCP-based resolvers (such as DNSMasq) will rightfully fail DNS resolution for offline devices, as soon as the DHCP lease has expired.
Could the prior (ideal) behavior be restored please? Or at the very least, could a setting be added?
Thanks in advance 👍😊
What version of Home Assistant Core has the issue?
2024.6.2
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
Ping
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Hey there @jpbede, mind taking a look at this issue as it has been labeled with an integration (ping) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of ping can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign ping Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
Previously, when DNS resolution failed for a device, the Ping Integration properly reported it as offline.
But since Home Assistant Core 2024.6.2 (or possibly a bit earlier), DNS resolution failure makes the entity Unavailable.
This is a real problem because many DHCP-based resolvers (such as DNSMasq) will rightfully fail DNS resolution for offline devices, as soon as the DHCP lease has expired.
Could the prior (ideal) behavior be restored please? Or at the very least, could a setting be added?
Thanks in advance 👍😊
What version of Home Assistant Core has the issue?
2024.6.2
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
Ping
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: