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

Error in log - i don't know what cause it. #104167

Closed
vampywiz17 opened this issue Nov 18, 2023 · 4 comments
Closed

Error in log - i don't know what cause it. #104167

vampywiz17 opened this issue Nov 18, 2023 · 4 comments

Comments

@vampywiz17
Copy link

The problem

Hello there,

I see this in log. It possible that video stream cause it? (i use Hikvision integration)

What version of Home Assistant Core has the issue?

core-2023.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-11-18 15:26:56.859 ERROR (MainThread) [frontend.js.latest.202310302] Uncaught error from Chrome 119.0.0.0 on Windows 10
TypeError: Cannot read properties of undefined (reading 'createTimeRange')
/@videojs/[email protected]/dist/videojs-http-streaming.js:2541:52
/@videojs/[email protected]/dist/videojs-http-streaming.js:5:77
/@videojs/[email protected]/dist/videojs-http-streaming.js:6:3

Additional information

No response

@home-assistant
Copy link

Hey there @home-assistant/frontend, mind taking a look at this issue as it has been labeled with an integration (frontend) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of frontend 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 frontend Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


frontend documentation
frontend source
(message by IssueLinks)

@davidjac
Copy link

davidjac commented Nov 21, 2023

Am getting Similar error. Chrome runs very slow Appears to be fine in App,

Logger: frontend.js.latest.202310302
Source: components/system_log/init.py:300

Uncaught error from Chrome 119.0.0.0 on Windows 10 TypeError: Cannot read properties of null (reading 'removeEventListener') renderHeading (src/components/ha-dialog.ts:51:24) apply (src/scoped-custom-element-registry.js:262:44) mainWindow.history.pushState (src/dialogs/make-dialog-manager.ts:129:7)
Uncaught error from Chrome 119.0.0.0 on Windows 10 TypeError: Cannot read properties of undefined (reading 'entity_id') _keyFunction (src/components/data-table/ha-data-table.ts:362:56) keyFunction (src/virtualize.ts:116:41) r (src/directives/repeat.ts:56:28) ct (src/directives/repeat.ts:93:52) update (src/directive.ts:134:16) _$AS (src/lit-html.ts:1085:23) S (src/lit-html.ts:1362:12) _$AI (src/async-directive.ts:366:18) setValue (src/virtualize.ts:139:13) dispatchEvent (src/Virtualizer.ts:802:23)

Works fine in App

@MartinHjelmare
Copy link
Member

For every uncaught error that is logged by the frontend.js.* logger, please open an issue in the frontend issue tracker and link back to this issue. Make sure to fill in the issue template for the frontend appropriately. If the frontend team confirms that it's a frontend issue, we can close here.

https://github.com/home-assistant/frontend/issues/new/choose

A similar error as the undefined _keyFunction error was fixed some weeks ago for an earlier frontend version:
home-assistant/frontend#18372

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants