pynetgear: Router webui not accessible after using pynetgear
Version: 0.5.2 Router: Netgear R8000 Use case: homeassistant 0.89.2 device tracker
When I configured my device tracker and booted up homeassistant, I can no longer access the router’s web ui via direct IP or routerlogin.net but accessing the device via pynetgear
works just fine
I can ping the device just fine, but accessing the web ui fails with a connection refused message. Stopping homeassistant doesn’t resolve the issue either. Rebooting the router allows me to access the web ui again at least until I turn homeassistant back on
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 16 (8 by maintainers)
Those look like standard networking issues between the server and the R8000, not uncommon to see a few when you are iterating 1700+ times
A better way to override would be to override the device tracker as a
custom_component
, that way you aren’t editing core files.Let me know if there is anything that is unclear or missing from the CLI and I can try to make a fix to improve it. This first round was the best I could think of from my own perspective.