fix: create correct url when using ipv6

[skgsergio]

Currently when using IPv6 I get the following errors:

2023-08-31 00:59:25.359 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/alarms
2023-08-31 00:59:25.361 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.364 ERROR (MainThread) [custom_components.google_home] Request from Cocina device error: https://2a02:9140:4d80:xxxx:2880:fef1:8065:ad8d:8443/setup/assistant/notifications
2023-08-31 00:59:25.368 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/alarms
2023-08-31 00:59:25.371 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.374 ERROR (MainThread) [custom_components.google_home] Request from Dormitorio device error: https://2a02:9140:4d80:xxxx:7ed9:5cff:fe1b:dcef:8443/setup/assistant/notifications
2023-08-31 00:59:25.376 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/alarms
2023-08-31 00:59:25.379 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/alarms/volume
2023-08-31 00:59:25.381 ERROR (MainThread) [custom_components.google_home] Request from Salón device error: https://2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce:8443/setup/assistant/notifications

This is due to a malformed URL when using IPv6, as the IPv6 needs to be placed between [], for example https://[2a02:9140:4d80:xxxx:3944:b4e3:bed3:fce]:8443/setup/assistant/notifications.

This PR detects if the IP is IPv6 and adds them.

[leikoilja]

Awesome, thanks for fixing it 🙌

[KapJI]

Please fix warnings found by linters.

[skgsergio]

Done! I did the PR not from my usual system and I had no linters installed 🤦🏼‍♂️

[KapJI]

There is another warning about using isinstance instead of type.

Hassfest errors are unrelated to this change.

[skgsergio]

Ok, I've ended up installing pre-commit it locally. I missed that one in the action log. That should be it. Sorry for the noise.

[Dillton]

Hello, just a note.

This error does not appear only when IPv6 is used.
I have my home network completely on IPv4 with IPv6 disabled on my router and this error appears only on HA startup/reboot in my case.
So I would like to know where the IPv6 adresses are coming from on Google devices.

Anyway it looks like this PR fixes my issue also so thank you very much @skgsergio
and I will keep monitoring this for few more days.

[KapJI]

It seems zeroconf may return ipv6 addresses sometimes when discovering Google Home devices. I guess it should be possible to disable this in zeroconf or make this configurable from integration settings. If someone is interested in working on this, PR is welcome.

[leikoilja]

i also noticed that we are a few minor versions behind with zeroconf leikoilja/glocaltokens#437 , so might be worth checking the release notes if there were meaningful fixes