-
Notifications
You must be signed in to change notification settings - Fork 81
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
trace backs on what look like basic connection error #161
Comments
Does this put the integration into an unusable state after this happens? |
Wifi will have these issues and these are very low powered devices so connection issues aren't uncommon. I setup mine and haven't seen this. |
Main issue here is that this is filling my Home assistant log with Tracebacks instead of maybe a trapped graceful Lost connection warning or something.. which seems recent.. The doorbell is on the edge of my wifi coverage even with me putting a meshed AP closer too it..
I have rebooted the cam and will see if I can get better wifi performance.. I live in a fairly congested wifi area and the AD110 is 2.4Ghz only so it is fairly common for a close by neighbours AP to auto switch channels and cause interference. |
Got it. I will only log a single line going forward but log the full stack trace as a debug log. Those who want the full stack trace can enable debug logs if they need it. |
Logging updated in https://github.com/rroller/dahua/releases/tag/0.9.37 Please try that |
Sounds like a good solution. Will test it out when I get a chance. |
Got the following after rebooting and letting it run for a few hours..
|
Version of the custom_component
0.9.36
Logs
Describe the bug
AD110 is slow and sometimes drops off WiFi if it roams APs etc.. This looks like a simple connection failure causes a unstrapped error.
The text was updated successfully, but these errors were encountered: