-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
UPnP/IGD and AsusWRT Error with Pi-hole in System #26869
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
Comments
Hey there @kennedyshead, mind taking a look at this issue as its been labeled with a integration ( |
Hey there @robbiet480, mind taking a look at this issue as its been labeled with a integration ( |
A few checks, can you, from your own computer, connect to http://192.168.x.x:34575 ? Also, was the integration itself set up and 'initialized'? I.e., do you see the UPnP sensors (traffic counters etc) in your home assistant? |
Hey Steven, sorry for the slow reply. I cannot access that URL in my web browser - the router doesn't seem to be responding to http requests on that port (with or without pihole running btw). However, previously they were working and pulling the upnp sensors in HA. They no longer pull the data and instead flood the log files with the above error. I noticed my router is not running merlin (if that matters) and so only has telnet, not SSH enabled. |
Did you change the IP to you routers IP? Also, have you tried removing and adding the integration? Is there anything else that has changed? Not sure what merlin is, the point is that it should be running a UPnP/IGD server. If you haveshell- access to the home-assistant environment you can run this to discover/search for the UPnP devices on your network:
This will output something like:
|
I got also this error. I added this upnp by integration and after a while it throws this error:
trying this in browser gives me connection refused.. . Re-adding the integration will work a certain time but will fail after a while |
Not sure what is happening. Your device might be blocking the updates as a means of protection. Does it work again later on, or only if you re-add the integration? |
Indeed it works again after re adding the component
Steven Looman <notifications@github.com> schrieb am So., 10. Nov. 2019,
18:21:
… Not sure what is happening. Your device might be blocking the updates as a
means of protection.
Does it work again later on, or only if you re-add the integration?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#26869>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFUA73CHIMZIRXEPCKEJSDQTA7JJANCNFSM4IZXXCBA>
.
|
Does it eventually work again, without re-adding the integration? I.e., does your router start responding again after a while, without you doing anything? |
I did not really follow this up the last days. but all of udden the sensor stops collecting data and there are error logs regarding that hass cannot connect to the router... restarting hass fixes it. Also i noticed my keyfile and if using the sensors from the component breaks this component somehow. i am using last dev veriosn 0.102.0b2 for the moment. |
What do you mean by keyfile? Do you know how to use custom components? It is worth trying to re-initialize the backend of this component periodically, but I don't want to change it before it is certain this works. |
@StevenLooman i meant the ssh keyfile instead of password. It breaks my asuswrt component completly. I would go for a custom component yeah. I have the feeling something is broken with asuswrt component for the moment. |
@thundergreen @StevenLooman Didn't mean to leave you both hanging but I've just switched to a NetGear Orbi and I'm no longer having issues with the UPnP/IGD component. The last router I had issues on was my Asus RT-AC1750. So it seems the problem is only for Asus routers. |
@thundergreen Hi sorry for the delay. I have changed the sensors of the Do you know what to do with this? You can either create a custom component (recommended, copy the files from the |
in addition to this and my issue #30896 (which was marked as duplicate) i also get some timeout errors but sesnors work. Of course till next restart.
|
same issue as jacekpaszkowski with the timeout error. Home Assistant 0.104.2. Sometimes after removing the entities and restarting they come back. Any way to force a rediscovery? |
Nothing has changed in recent versions of Home Assistant. Reinitialization (not rediscovery) is done in the commit from this comment, albeit in a hacky and certainly not a production-usable way. Please test this if you have the means and knowledge on how to do so. |
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. |
A lot has changed with #33108 and will be included in the next release. This can be closed @robbiet480 . |
Uh oh!
There was an error while loading. Please reload this page.
Home Assistant release with the issue:
0.99.2
Last working Home Assistant release (if known):
Not sure
Operating environment (Hass.io/Docker/Windows/etc.):
Component/platform:
AsusWRT and/or UPnp/IGD Integration
Description of problem:
Fails to connect to the router when Pi-hole is installed on the system. Does not create any blocked entries within pi-hole so do not believe the traffic is being blocked.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):None - UPnP/IGD integration in Hassio with Asus WRT router
Traceback (if applicable):
Additional information:
Log file gets spammed with entries every minute for:
The text was updated successfully, but these errors were encountered: