search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.78k stars 30.88k forks source link

Ambiguous log entries. Need module/add-on/script that causes error. #38076

Closed unw1red closed 3 years ago

unw1red commented 4 years ago

The problem

Spoke to Franck about ambiguous log entries. Trying to troubleshoot errors/warnings and the indication of what add-on/module/script that caused it is not apparent. The need to troubleshoot issues is dependent upon data. Please help with adding more data or requiring collaborators to have more descriptive syntax in their log entries. Example listed below.

Environment

Running Home-Assistant-Core under Docker on UNRaid. I do not believe this issue is platform dependent except for Hass.io possibly. This is not a new issue, but a continuation of the problem.

Problem-relevant configuration.yaml

N/A

Traceback/Error logs

Log Details (ERROR) Logger: libav.NULL Source: components/stream/worker.py:72 First occurred: July 21, 2020, 5:50:06 PM (2 occurrences) Last logged: 10:16:55 AM

sps_id 32 out of range ```txt



## Additional information

There are many log entries that fall within this issue. The above entry is simply an example. If this is not the proper location for the issue, please let me know. If you would like the numerous examples from my logs, please also let me know.
probot-home-assistant[bot] commented 4 years ago

Hey there @hunterjm, mind taking a look at this issue as its been labeled with an integration (stream) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)

JOHLC commented 4 years ago

I am also gettting sps_id 32 out of range

When the stream component is setup

github-actions[bot] commented 3 years ago

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.

unw1red commented 3 years ago

@hunterjm, have you had a chance to look at this issue?

System Health

version 2021.1.5
installation_type Home Assistant Container
dev false
hassio false
docker true
virtualenv false
python_version 3.8.7
os_name Linux
os_version 5.10.1-Unraid
arch x86_64
timezone America/New_York
Home Assistant Community Store GitHub API | ok -- | -- Github API Calls Remaining | 4951 Installed Version | 1.10.1 Stage | running Available Repositories | 709 Installed Repositories | 14
AccuWeather can_reach_server | ok -- | -- remaining_requests | 11
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | March 1, 2021, 7:00 PM relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | true can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Lovelace dashboards | 2 -- | -- mode | storage views | 11 resources | 8
github-actions[bot] commented 3 years ago

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.