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
Task exception in device tracker #27257
Comments
This comment has been minimized.
This comment has been minimized.
Issue also exist in 0.100.2 |
Issue also exist in Home Assistant 0.101.1 |
Issue exists in 0.101.2 as well Has anyone found a workaround for this yet? |
same issue, only when starting HA as it look likes |
I just checked it, the library was updated after this issue was created. So it might be unrelated. (#27699) |
If it helps, I am using FritzConnection version 0.8.4.... |
After having no problems in 101.x the error reappered massive after the update on 102.1
69 Times since 00:42 Btw: my wife's got a new phone last week. I activated device tracking for it. |
I had the same issue with my main HA instance reporting this 'NewIPAddress' error. I will post a PR in the coming day with the fix. Some imports has to be fixed as the component's project structure changed between versions. |
It seems updating to new fritzconnection does resolve the problem. We shall raise the bug (or move this one) to update the docker image. |
Bad news... over the night, issue occurred more many times... So updating the fritzconnection, doesn't resolve the issue for me.
|
is there any way, to disable these errors (using configuration) from the log file ? I made below configuration but without help... logger:
default: error
logs:
fritzconnection: fatal |
Home Assistant release with the issue:
99.1
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration: https://www.home-assistant.io/integrations/device_tracker/
Description of problem:
Several warnings in Home Assistant log file "Error doing job: Task exception was never retrieved"
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: