Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unused data found during update #286

Open
warmfire540 opened this issue Jun 22, 2024 · 4 comments
Open

Unused data found during update #286

warmfire540 opened this issue Jun 22, 2024 · 4 comments

Comments

@warmfire540
Copy link

The following warning is logged during HA startup.

Logger: custom_components.emporia_vue
Source: custom_components/emporia_vue/__init__.py:481
integration: Emporia Vue ([documentation](https://github.com/magico13/ha-emporia-vue), [issues](https://github.com/magico13/ha-emporia-vue/issues))
First occurred: 7:27:51 PM (1 occurrences)
Last logged: 7:27:51 PM

Unused data found during update. Unused data: {'75822-Balance-1MIN': <pyemvue.device.VueDeviceChannelUsage object at 0x7f87a35790>}

It's possible to see how to resolve?

@magico13
Copy link
Owner

It's not an issue if it happens during startup and you're seeing whatever is logged still showing up as a device, in this case only the Balance sensor. Balance and a few others aren't "real" and only show up when requesting usage data, not when requesting the list of devices, so they're "extra" data returned when the first poll happens. It'll get added to Home Assistant at that point and future polling will know to look for it.

It's a side effect of the partial rewrite of the startup logic and part of an attempt to allow adding and removing Emporia devices without having to restart the integration. That's not complete, so you do still have to restart if you add a smart plug, but the startup is a bit more resilient to devices not returning data in the first poll in the current state.

@warmfire540
Copy link
Author

Ok that's a solid explanation. Anything I can do to suppress this warning since it will correct itself or is not too relevant?

I have an integration that reports on warnings/errors - so trying to shore up a few last warnings.

@magico13
Copy link
Owner

Unfortunately no, I'll have to change it to an info level message for it to go away, sorry.

@rcmaehl
Copy link

rcmaehl commented Jul 10, 2024

Having a similar log entry, but not exactly the same. Warns it'll be broken in 2025.1

2024-07-10 18:57:43.682 WARNING (MainThread) [custom_components.emporia_vue] Unused data found during update. Unused data: {'284890-Balance-1MIN': <pyemvue.device.VueDeviceChannelUsage object at 0x7f3f4ad5b500>}
2024-07-10 18:57:44.068 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'emporia_vue' calls async_forward_entry_setup for integration, emporia_vue with title: Customer 165989 and entry_id: e27c67ca15889d0e6c5c99ea2574f39b, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/emporia_vue/__init__.py, line 326: hass.async_create_task(, please create a bug report at https://github.com/magico13/ha-emporia-vue/issues
2024-07-10 18:57:44.112 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration emporia_vue with title: Customer 165989 and entry_id: e27c67ca15889d0e6c5c99ea2574f39b, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants