Replies: 3 comments 3 replies
|
Thanks for your feedback! We are currently not showing more details in the HA logs as the device snapshots submitted might be significantly bigger in size for people depending on the amount of devices included. Did you know that in order to see what is being sent in more detail you also can refer to the "Preview device analytics" option in the Analytics section - use the 3 dots on the right top corner to access it. That's providing more insights on the submission. But yes, agree, we can iterate on a more verbose logging on what is submitted in the logs, like showing a summary of what was submitted, e.g. "x devices based on y integrations and z entities" as a sensible basis. We don't want to over bloat logging for that. What do you think? |
|
Regarding the note to the Preview option ref #136 for more verbosity. |
|
There was progress on #136 :) So, I'm going to close this discussion for now as the more prominent "Preview device analytics" should cover it for now. |
Uh oh!
There was an error while loading. Please reload this page.
The INFO-level logging of the device analytics sent should be more elaborate, in line with HA and OHF pledge to privacy and openness on how data is used. Currently, the Device Database submission logs:
2026-02-03 20:21:33.895 INFO (MainThread) [homeassistant.components.analytics] Submitted snapshot analytics to Home Assistant serversHowever, the other analytics are waaaay more verbose in the logs and provide clarity on the submissions:
2026-02-03 19:52:26.952 INFO (MainThread) [homeassistant.components.analytics] Submitted analytics to Home Assistant servers. Information submitted includes {'uuid': '228c4c6xxxxxxxx7a3624e', 'version': '2026.2.0b3', 'installation_type': 'Home Assistant Container', 'certificate': False, 'integrations': ['waze_travel_time', 'rest_command', 'androidtv_remote', 'zone', 'sql', 'history', 'input_select', 'fully_kiosk', 'bthome', 'binary_sensor', 'homeassistant', 'input_number', 'goodwe', 'person', 'switch', 'tts', 'roborock', 'recorder', 'switch_as_x', 'group', 'downloader', 'xiaomi_ble', 'energy', 'diagnostics', 'http', 'logbook', 'dhcp', 'sonos', 'input_text', 'mobile_app', 'history_stats', 'google', 'smartthings', 'esphome', 'stream', 'google_drive', 'reolink', 'logger', 'workday', 'homeassistant_alerts', 'spotify', 'zeroconf', 'google_assistant', 'tod', 'picnic', 'media_source', 'timer', 'ssdp', 'zwave_js', 'sun', 'alert', 'command_line', 'script', 'go2rtc', 'webhook', 'co2signal', 'bluetooth', 'version', 'threshold', 'application_credentials', 'my', 'tuya', 'input_boolean', 'home_connect', 'dsmr_reader', 'forecast_solar', 'nut', 'input_datetime', 'notify', 'cloud', 'template', 'cast', 'ping', 'mqtt', 'backup', 'rituals_perfume_genie', 'utility_meter', 'smtp', 'google_generative_ai_conversation', 'sensor', 'light', 'philips_js', 'frontend', 'lovelace', 'automation'], 'custom_integrations': [{'domain': 'ev_smart_charging', 'version': <AwesomeVersion SemVer '2.5.1'>}, {'domain': 'xiaomi_home', 'version': <AwesomeVersion SemVer '0.4.7'>}, {' {'domain': 'kia_uvo', 'version': <AwesomeVersion SemVer '2.49.1'>}], 'state_count': 2061, 'automation_count': 106, 'integration_count': 85, 'user_count': 6}I feel that this should be fixed before 2026.2 releases into the wild today, as both HA and the OHF always promise full openness on how analytics data are used and one can now simply not see what is submitted to the device database.
Related issue at HA-Core: home-assistant/core#162196
All reactions