You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new go2rtc integration is often flooding my logs with errors that look like this:
2024-11-03 10:38:45.514 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140712495597024] Error unsubscribing from subscription: functools.partial(<bound method Camera.close_webrtc_session of <entity camera.front_path=recording>>, '01JBSN3JDPAZ41312BMHZZ8SNJ')
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/connection.py", line 248, in async_handle_close
unsub()
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 854, in close_webrtc_session
self._webrtc_provider.async_close_session(session_id)
File "/usr/src/homeassistant/homeassistant/components/go2rtc/__init__.py", line 245, in async_close_session
ws_client = self._sessions.pop(session_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: '01JBSN3JDPAZ41312BMHZZ8SNJ'
I think this is due to my changing the dashboard and having some webviews (like my 2 tablets) still open with the old frontend, but it tends to flood my logs every so often. I haven't really gotten to the bottom of what's causing it other than refreshing the browser page on my two tablets tends to do it. It would be better IMO if this sort of failure was handled more gracefully. See below for the frequency of the logs.
Further the documentation page in the manifest.json for the go2rtc component doesn't exist, even in the https://rc.home-assistant.io/xxx tree.
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (go2rtc) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of go2rtc can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign go2rtc Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
They're created with the Frigate CC and it seems to repeat for all of them. I can open an issue in their repo if you think it's related to the integration.
The problem
The new go2rtc integration is often flooding my logs with errors that look like this:
I think this is due to my changing the dashboard and having some webviews (like my 2 tablets) still open with the old frontend, but it tends to flood my logs every so often. I haven't really gotten to the bottom of what's causing it other than refreshing the browser page on my two tablets tends to do it. It would be better IMO if this sort of failure was handled more gracefully. See below for the frequency of the logs.
Further the documentation page in the
manifest.json
for thego2rtc
component doesn't exist, even in the https://rc.home-assistant.io/xxx tree."documentation": "https://www.home-assistant.io/integrations/go2rtc",
What version of Home Assistant Core has the issue?
core-2024.11.0b2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Go2RTC
Link to integration documentation on our website
Can't find a doc page for go2rtc
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: