-
Notifications
You must be signed in to change notification settings - Fork 207
Depreciation: lovelace_data['resources'] instead of lovelace_data.resources #797
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
Comments
I also get this error still. Would hate to have to switch to the legacy WebRTC, since i really enjoy the ability to control which stream protocol to use. |
I also get this message. Detected that custom integration 'webrtc' accessed lovelace_data['resources'] instead of lovelace_data.resources at custom_components/webrtc/utils.py, line 129: resources: ResourceStorageCollection = hass.data["lovelace"]["resources"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/AlexxIT/WebRTC/issues |
I also get this message. Detected that custom integration 'webrtc' accessed lovelace_data['resources'] instead of lovelace_data.resources at custom_components/webrtc/utils.py, line 129: resources: ResourceStorageCollection = hass.data["lovelace"]["resources"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/AlexxIT/WebRTC/issues |
Dear All, I am having the same warning: Detected that custom integration 'webrtc' accessed lovelace_data['resources'] instead of lovelace_data.resources at custom_components/webrtc/utils.py, line 129: resources: ResourceStorageCollection = hass.data["lovelace"]["resources"]. This will stop working in Home Assistant 2026.2, please create a bug report at https://github.com/AlexxIT/WebRTC/issues Do you have any solution for that? Br. Rafael |
I have changed line 129 as follows. |
Dear CH-1967, I made the change and it works. Thanks a lot for that. Br. |
Got this warning in my logs, thought you should know.
The text was updated successfully, but these errors were encountered: