Unable to determine the IPv4 addresses on integration starting up #360
Labels
bug
Something isn't working
Comments
|
Also, the integration continues to query devices that have been marked as |
|
Updated to v1.8.2, same thing happens. |
|
facing same issue starting from 1.8.1, it does not start unless you manually reload, then it works fine. |
|
Hm, thanks for reporting the issue and logs, @CoryAlbrecht. Seems like the I think we should introduce a new feature as spoken in #340. We should save the IP addresses in the config file and change them only if the IP is changed. That will allow us to rely on the saved IP instead of replying on auto-discovery feature. Plug it will allow the IP addresses to be manually set on the UI options :) @Raul-7-7, can you please check your logs if the issue is for the same reason. Does the integration also says you " We could not determine its IP address," on the startup? |
leikoilja
changed the title
|
@leikoilja Sorry for the delay, crazy week at work. Anyway, I was getting the same error, (IP address), however after upgrading to core-2021.10.4 for HA, I am unable to reproduce the issue, I rebooted over 10 times, Host, HA, you name it! no longer an issue (at least for me) integration loads no problem. |
|
Still having this problem after updating from 2021.11.4 to 2021.12.9 |
|
Doing a reload from the UI doe snot help. |
|
Ping. |
|
Hey, @CoryAlbrecht.
|
|
@leikoilja How do I do that? Issue #340 doesn't say, and neither does the top level README.md file. The only option shown on the HA integrations page is the update interval. |
|
Exactly that, @CoryAlbrecht. |
|
OK, I switched over to Docker containers rather than Supervised (as well as switching from a Ubuntu VM to a dedicated Debian box) and I believe that the issue I was having was related to this: home-assistant/supervisor#3127 The HA Supervisor requires that for multiple interfaces you enter a default gateway on every interface, and I had my VM on my private VLAN and my public VLAN so Supervisor wanted gateway on both of them. And, frustratingly, once you tried to set network stuff via the Supervisor you can't really unset because it refuses to save an interface that does not have a default gateway. You can change it with Long story short, that really screws up mDNS whether through |
|
Some good findings, @CoryAlbrecht, thanks for sharing them here. Might be useful for other people stumbling around the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Integration does not actually start monitoring Google Home devices on HA start up, never sees when alarms or timers are set because it was unable to determine the IPv4 addresses of the devices. Manual reload from the Integrations page is necessary.
Version of the integration
If you are unsure about the version check the github release here.
Logs
On start up of HA:
After reload of integration:
The text was updated successfully, but these errors were encountered: