El Burro

tried this but to no avail: ```MariaDB [(none)]> SET time_zone = 'Europe/Berlin'; Query OK, 0 rows affected (0.000 sec) MariaDB [(none)]> SELECT @@GLOBAL.time_zone, @@SESSION.time_zone; +--------------------+---------------------+ | @@GLOBAL.time_zone | @@SESSION.time_zone |...

This is probably the problem: `2024-01-10 12:13:18.832 DEBUG (MainThread) [homeassistant.components.fritz.common] enity_data: {'call_deflections': {}, 'entity_states': {'external_ip': '192.168.2.2', 'external_ipv6': '::', 'device_uptime': datetime.datetime(2023, 10, 4, 13, 39, 57, 168745, tzinfo=datetime.timezone.utc), 'connection_uptime': datetime.datetime(2024, 1,...

same error here - 03.02.2024

https://jitsi.org/blog/march-update-new-toolbar-ui-virtual-backgrounds-and-more/

same problem here - long periods of smaller data - started two days ago out of nowhere 

> the hint from @donbcd will help you a lot to identify the root cause of the problem, if the log shows the 'Thanks for nothing...' message, then you can...

as i cannot see that from the debug log: are there more values returned by the API like timestamp (hence the assumption that senec is travelling back in time)?

As my connection is highly volatile (T-DSL Hybrid, DSL+LTE aggreated with QOS for shared medium LTE) it would be cool to see the average also in the daily / weekly...