Economy-Modus not working

[StormCh]

What version of Integration has the issue?

The service sends API requests (updates) to ipv64 despite the fact that the IP has not changed

System Health details

System Information

version	core-2025.5.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.3
os_name	Linux
os_version	6.12.23-haos
arch	aarch64
timezone	Europe/Berlin
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4993
Installed Version	2.0.5
Stage	running
Available Repositories	2018
Downloaded Repositories	29

Solcast Solar

can_reach_server	ok

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 15.2
update_channel	stable
supervisor_version	supervisor-2025.05.3
agent_version	1.7.2
docker_version	28.0.4
disk_total	114.1 GB
disk_used	16.9 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	odroid-n2
supervisor_api	ok
version_api	ok
installed_addons	Mosquitto broker (6.5.1), Batmon (1.82), File editor (5.8.0), Terminal & SSH (9.17.0), MariaDB (2.7.2), TasmoAdmin (0.31.5), ESPHome Device Builder (2025.5.2), MQTT Explorer (browser-1.0.3), Filebrowser (2.32.0)

Dashboards

dashboards	4
resources	11
views	17
mode	storage

Recorder

oldest_recorder_run	27. Mai 2025 um 18:50
current_recorder_run	10. Juni 2025 um 13:16
estimated_db_size	6546.33 MiB
database_engine	mysql
database_version	10.11.6

Checklist

• I have enabled debug logging for my installation.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).

Describe the issue

The service sends API requests (updates) to ipv64 despite the fact that the IP has not changed.
The counter is also not counting upwards. It count sometimes +2 or +3 or +4 etc..

Reproduction steps

Use the service a described

Debug logs

Dieser Fehler stammt von einer benutzerdefinierten Integration

Logger: custom_components.ipv64.coordinator
Quelle: custom_components/ipv64/coordinator.py:385
Integration: IPv64 (Dokumentation, Probleme)
Erstmals aufgetreten: 10. Juni 2025 um 13:16:45 (232 Vorkommnisse)
Zuletzt protokolliert: 11. Juni 2025 um 23:58:48

Update limit reached for XYZ.xyz.de: 64 of 64 used
Update limit reached for XYZ.xyz.de: 47 of 64 used

[dosubot]

Hi @StormCh! I'm Dosu and I’m helping the ipv64 team.

The Economy-Modus is designed to only send API updates when your IP changes, but from the code, it relies on comparing the current IP (fetched from an external service) with the last stored IP. If the stored IP is missing or can't be fetched, it will trigger an update anyway. Network issues or failures in fetching the current IP can also cause unnecessary updates, which might explain why you're seeing updates even when your IP hasn't changed. The counter increments are managed by the backend and read by the integration, so if multiple updates are triggered in quick succession (for example, due to retries or repeated failures), the counter can jump by more than one. Extensive debug logs in the integration should help pinpoint if the IP check is failing or if updates are being retried unexpectedly. All the main logic for this is in coordinator.py and is visible in the debug logs you enabled. If you see frequent errors or warnings about IP checks or network issues, that's likely the cause of the unexpected updates and counter jumps.
Source: coordinator.py implementation

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[Ludy87]

Hi @StormCh , ich habe hier zwei Systeme zu laufen, ohne dieses Problem. Kannst du bitte debug für die Integration aktivieren? Dort sollte dann ein Log-Eintrag sein, der dir die stored IP anzeigt, die sollte mit der current gleich sein.

[StormCh]

Just to clarify, till now I used the "Configuration" Service right from the integration. For now I added a automation cross-checking with the given IP from my Fritz.Box and if its not equal than run the ipv64 refresh service. I will have a look on debug files this evening.

[duczz]

Ich hab das Problem auch, er prüft durchgehend nicht nur bei IP Änderung

[Prof-Alec]

Bei mir geht es auch nicht. Habe das Interval vorerst auf 26 Minuten gestellt damit die Meldung "Update limit reached" nicht mehr auftaucht. Ich habe keine Funktion gefunden, um sie anderweitig abzuschalten.