-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
A new Skybell Task Exception error #13922
Comments
The error comes from the dependency |
My apologies for not submitting a "PR to home assistant" properly for a component dependency issue. I'm not clear on what needs to be done to submit this package fix request properly. |
First try to open an issue in the skybellpy source repository. |
Ok, thanks Martin. I found skybellpy under @MisterWil personal repo. It wasn't obvious how to open an issue, but finally found the link under the "+". |
Home Assistant release with the issue:
"version": "0.67.0"
Last working Home Assistant release (if known):
66.1 (not certain as I may not have looked at the logs to see if the error was already presentthen)
Operating environment (Hass.io/Docker/Windows/etc.):
RPI3 with 32gb Sdcard, running Hass.io/Resin-OS image
Component/platform:
https://www.home-assistant.io/components/skybell/
Description of problem:
The Skybell doorbell is actually functioning fine via this add-on. The issue is with a Task exception error that occurs every 30 seconds that spams the log file. This has happened before and was fixed, but now it is occurring with a different piece of code that skybell.py references.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):skybell:
Traceback (if applicable):
Additional information:
There have been several other reports of this same "distutils has no attribute util" error with different components. They are being closed as answered, referencing this issue . If this slight change to how distutils is being called is all that is needed, please will someone update skybell.py with this fix for the next release? I'm happy to test it first as a custom component before release.
The text was updated successfully, but these errors were encountered: