-
Notifications
You must be signed in to change notification settings - Fork 199
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
New set up discovery issues, UPNP discovery address not found? #1377
Comments
So, that message is a warning. It should not change the functionality. Turn on Trace UPNP Calls in the Bridge Control Tab and then turn on debug for com.bwssystems.HABridge.BridgeSettings in the Logs tab at the bottom. Post the output of the info here |
Okay, thanks for the reply. I have turned on the logging as you requested and the output of the log is below. By the way, when I save the bridge set in sort reinitialize the bridge, the message about waiting for completion never goes away. I don't know if that's relevant, just thought I should mention it.
|
@bwssytems Please let me know if there's anything else you would like me to try or other information I can provide. |
@bwssytems Apologies, it appears that some of the settings didn't take effect until I restarted the Raspberry Pi. So here is a fresh log.
|
I have confirmed that UPNP is enabled on my router, as well. |
Actually, to follow up on that, I am able to discover other devices with my Echo Show, so it's probably not the network settings, I'm guessing. |
@bwssytems I tried deleting the configuration file and starting up the bridge from the command line. I re-enabled the link button and the UPNP traces. I'm now definitely seeing queries from the Echo, but for some reason it's not discovering the devices. I did also try changing the seed and renumbering the devices. I don't know if it matters, but I'm using an Echo Show 5 (I believe it is second-generation). Is there any reason to believe that I need to try with an Echo Dot instead? Also, I noticed that the device IDs have a hyphen in between the last two set of numbers, rather than a colon. But I can't recall whether that's normal.
|
I was able to resolve this. I had to disable the HA bridge service, and then start it manually from the command line. This appears to be because the static IP addresses not known when the service starts, so discovery will not work if running the service from boot. Then, I also had to enable the nine octet option for the unique device IDs, after which discovery was successful. |
Greetings, I am trying to set up habridge on a new Raspberry Pi but I'm running into some issues. It's been a really long time since I last did this, so I think I'm just missing something. I am getting the following warning in my log, and my Echo is not discovering any devices when I press the link button.
I read somewhere that this might be because the device might not be using a static IP, but I edited the DHCP config to use this address as a static IP. I also tried changing the bridge settings to use 0.0.0.0 as the discovery address, but when I did that it said that it could not resolve the IP of the host. Hopefully someone can point me in the right direction.
The text was updated successfully, but these errors were encountered: