What version of Integration has the issue?
v2.0.2
System Health details
System Information
| version |
core-2025.10.2 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| container_arch |
amd64 |
| user |
root |
| virtualenv |
false |
| python_version |
3.13.7 |
| os_name |
Linux |
| os_version |
6.12.43-haos |
| arch |
x86_64 |
| timezone |
Europe/Budapest |
| config_dir |
/config |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| HACS Data |
ok |
| GitHub API Calls Remaining |
4994 |
| Installed Version |
2.0.5 |
| Stage |
running |
| Available Repositories |
2293 |
| Downloaded Repositories |
7 |
Home Assistant Cloud
| logged_in |
false |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
Home Assistant Supervisor
| host_os |
Home Assistant OS 16.2 |
| update_channel |
stable |
| supervisor_version |
supervisor-2025.10.0 |
| agent_version |
1.7.2 |
| docker_version |
28.3.3 |
| disk_total |
30.8 GB |
| disk_used |
4.9 GB |
| nameservers |
fe80::1, 192.168.100.1 |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
oracle |
| board |
ova |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
File editor (5.8.0) |
Dashboards
| dashboards |
2 |
| resources |
2 |
| views |
1 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), enp0s3 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth7790278 (disabled), vethdb42660 (disabled), veth72496d7 (disabled), vethe8cc288 (disabled), vetheb6caf0 (disabled), vetha89fa40 (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), enp0s3 (192.168.100.67/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth7790278 (), vethdb42660 (), veth72496d7 (), vethe8cc288 (), vetheb6caf0 (), vetha89fa40 () |
| ipv6_addresses |
lo (::1/128), enp0s3 (2a01:36d:3200:451f::d/128, 2a01:36d:3200:451f:92cc:b637:62c8:2d21/64, fe80::28eb:11af:443:7b8/64), hassio (fe80::2400:b8ff:fe9b:95c2/64), docker0 (fe80::3895:caff:fed8:cd58/64), veth7790278 (fe80::f4d9:73ff:fe27:cd7c/64), vethdb42660 (fe80::54f5:d2ff:fe85:37ad/64), veth72496d7 (fe80::fa:6eff:fe3e:8184/64), vethe8cc288 (fe80::d017:faff:fef0:1ae9/64), vetheb6caf0 (fe80::c9b:e0ff:fefc:fd5f/64), vetha89fa40 (fe80::9096:dff:fe1d:9dc8/64) |
| announce_addresses |
192.168.100.67, 2a01:36d:3200:451f::d, 2a01:36d:3200:451f:92cc:b637:62c8:2d21, fe80::28eb:11af:443:7b8 |
Recorder
| oldest_recorder_run |
2025. október 2. 21:26 |
| current_recorder_run |
2025. október 13. 21:45 |
| estimated_db_size |
97.45 MiB |
| database_engine |
sqlite |
| database_version |
3.49.2 |
Checklist
Describe the issue
Hi,
Trying to use ipv6 only address for hass, but integration does not update ipv6 address, it only refreshes the sensor from the dns. See log below for manual update:
2025-10-13 22:52:16.333 DEBUG (MainThread) [custom_components.ipv64.coordinator] Manual IP address update triggered via service call for entry: xxxxxxxxxxxxxxxxxxxxxxxxxx
2025-10-13 22:52:16.333 DEBUG (MainThread) [custom_components.ipv64.coordinator] Updating data from IPv64.net (economy=False, force_refresh=True)
2025-10-13 22:52:16.720 DEBUG (MainThread) [custom_components.ipv64.coordinator] Received account info: {'account_status': 1, 'reg_date': '2025-09-26 21:38:11', 'dyndns_updates': 2, 'dyndns_subdomains': 1, 'owndomains': 0, 'healthchecks': 0, 'healthchecks_updates': 0, 'api_updates': 90, 'sms_count': 0, 'account': 'Standard', 'dyndns_domain_limit': 3, 'daily_update_limit': 64, 'owndomain_limit': 0, 'healthcheck_limit': 3, 'healthcheck_update_limit': 1024, 'dyndns_ttl': 60, 'api_limit': 512, 'sms_limit': 5, 'info': 'success', 'status': '200 OK', 'update_hash': 'hdhdhfhfgfgftetetegsgsgdfxxx', 'cdn_traffic_input': 0, 'cdn_traffic_output': 0, 'vpn_traffic_input': 0, 'vpn_traffic_output': 0, 'vpn_limit_reached': 0, 'account_info': None}
2025-10-13 22:52:16.764 DEBUG (MainThread) [custom_components.ipv64.coordinator] Checking subdomain mydomain.ipv64.net against config domain mydomain.ipv64.net
2025-10-13 22:52:16.809 INFO (MainThread) [custom_components.ipv64.coordinator] IP update successful for mydomain.ipv64.net: {'info': '', 'status': 'success', 'ip': {'ipv4': 'ignore'}}
Reproduction steps
- install
- set logging
- manual update
...
Debug logs
2025-10-13 22:52:16.333 DEBUG (MainThread) [custom_components.ipv64.coordinator] Manual IP address update triggered via service call for entry: xxxxxxxxxxxxxxxxxxxxxxxxxx
2025-10-13 22:52:16.333 DEBUG (MainThread) [custom_components.ipv64.coordinator] Updating data from IPv64.net (economy=False, force_refresh=True)
2025-10-13 22:52:16.720 DEBUG (MainThread) [custom_components.ipv64.coordinator] Received account info: {'account_status': 1, 'reg_date': '2025-09-26 21:38:11', 'dyndns_updates': 2, 'dyndns_subdomains': 1, 'owndomains': 0, 'healthchecks': 0, 'healthchecks_updates': 0, 'api_updates': 90, 'sms_count': 0, 'account': 'Standard', 'dyndns_domain_limit': 3, 'daily_update_limit': 64, 'owndomain_limit': 0, 'healthcheck_limit': 3, 'healthcheck_update_limit': 1024, 'dyndns_ttl': 60, 'api_limit': 512, 'sms_limit': 5, 'info': 'success', 'status': '200 OK', 'update_hash': 'hdhdhfhfgfgftetetegsgsgdfxxx', 'cdn_traffic_input': 0, 'cdn_traffic_output': 0, 'vpn_traffic_input': 0, 'vpn_traffic_output': 0, 'vpn_limit_reached': 0, 'account_info': None}
2025-10-13 22:52:16.764 DEBUG (MainThread) [custom_components.ipv64.coordinator] Checking subdomain mydomain.ipv64.net against config domain mydomain.ipv64.net
2025-10-13 22:52:16.809 INFO (MainThread) [custom_components.ipv64.coordinator] IP update successful for mydomain.ipv64.net: {'info': '', 'status': 'success', 'ip': {'ipv4': 'ignore'}}
What version of Integration has the issue?
v2.0.2
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Network Configuration
Recorder
Checklist
Describe the issue
Hi,
Trying to use ipv6 only address for hass, but integration does not update ipv6 address, it only refreshes the sensor from the dns. See log below for manual update:
Reproduction steps
...
Debug logs