Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Alexa unable to discover recently added devices to ha-bridge #1215

Closed
dye46 opened this issue Jun 2, 2020 · 11 comments · Fixed by #1266
Closed

Alexa unable to discover recently added devices to ha-bridge #1215

dye46 opened this issue Jun 2, 2020 · 11 comments · Fixed by #1266
Labels
duplicate question
Milestone
5..4.0

Comments

@dye46
Copy link

dye46 commented Jun 2, 2020 •
edited
Loading

I use ha-bridge to control my VLC music servers and X10 automation equipment. I've been using it successfully for quite a while.

In early experimentation (2018), I had this same "newly added device discovery" issue. Google came up with no real answer other than "delete all your devices and rediscover" which seemed hoaky but worked. At the time I wiresharked a little and ha-bridge was answering the the port 80 HTTP discovery with an XML file including the newly added devices(!)...but still no dice.

ha-bridge host: PC running up-to-date Ubuntu LTS 16.04
ha-bridge version: ha-bridge-5.3.0.jar
2 Alexa echo dots plus a fire TV stick
everything on the same LAN

I add network radio stations to my VLC playlist quite often, and the wiping out my device list each time is getting a little tedious. I did try changing UPNP Send Delay to 250, too. I also tried quitting and restarting ha-bridge, too. No Joy.

It is 2020 now and I still have the same problem. Is this a dup of another issue, or ???
I would be eager to assist if needed.
@bwssytems
Copy link
Owner

IF you turn on trace upnp from the bridge control tab, you will see any exchange of info on discovery in the debug messages. Post your log after you have done a discovery with this flag on.

@dye46
Copy link
Author

dye46 commented Jun 24, 2020

Everything after the save (changed debug settings) and the "no new devices discovered" message.

habridge-debug.txt

@dye46
Copy link
Author

dye46 commented Jul 15, 2020

Did anything in the trace show anything? I can try to get wireshark/tcpdump data if that would be helpful. What should I be looking for in the trace, and on the wire? I was puzzled because the XML data sent by ha-bridge in the HTTP request did have all the new devices I added, but for some reason still get the "no new devices" message from alexa.

@bwssytems
Copy link
Owner

It just shows 2 devices requesting info at 192.168.1.17 and 192.168.1.80, but you cutoff the log too early and cannot see any other messages.

@bwssytems
Copy link
Owner

Have you tried the new RC4. Discovery has had issues of late and are now updated on the habridge side

@bwssytems bwssytems added this to the 5.3.1 milestone Dec 8, 2020
@dougdalton
Copy link

dougdalton commented Dec 9, 2020 via email

@dougdalton
Copy link

dougdalton commented Dec 9, 2020 via email

@bwssytems
Copy link
Owner

Since you are not the OP, I'm not sure what your whole situation is. I need the log from the start of the habridge to see if there is anything in the setup that is shown when trace upnp is on and also a short description of the behavior you are having.

THanks

@audiofreak9
Copy link
Collaborator

@bwssytems I'm wondering if @dougdalton updated their device numbers? This is also required to conform to Alexa's new discovery requirements.

@dougdalton Please read this and this.

This was referenced Dec 12, 2020
Closed
Merged
bwssytems added a commit that referenced this issue Dec 14, 2020
@bwssytems
Merge pull request #1266 from bwssytems/dev_branch_5.3.x
b3f2c25 
Dev branch 5.3.x to create v5.4.0

#1044 Alexa app, error "Device doesn't support requested value" bug question
#1118 Device status update in Alexa App is not working correctly for ha-bridge devices bug duplicate question
#1126 Can't get XY ColorData into URL enhancement question
#1127 Can't get separate hue, saturation and brightness enhancement question
#1128 Wrong color calucation in HS mode bug question
#1131 Changing color temperatur is not working correctly bug question
#1132 Conversion from CIE to RGB incorrect bug question
#1139 Device ID creation fails bug question
#1150 Home Assistant gets null exception during initialization bug question
#1170 Alexa not sending the correct color codes duplicate
#1171 Please add option: If bright request present with on, only send dim enhancement
#1184 Alexa will not discover HABridge question
#1191 When "Use UPNP Address Interface Only" is selected, echo cannot find ha-bridge bug
#1210 [Enahnacement] Have link button timeout be configurable enhancement
#1215 Alexa unable to discover recently added devices to ha-bridge duplicate question
#1227 Feature request: ${intensity.previous} value passing control enhancement
#1239 HA-Bridge has suddenly given up itself - Exception in thread "main" java.lang.NullPointerException bug question
#1243 Alexa device discovery now broke question
#1253 HABridge hue ColorDecode 0 0 0 bug question
#1256 Homeassistant devices not appearing bug question
@dye46
Copy link
Author

dye46 commented Jan 10, 2021

Holidays kind of swamped me, I'm the OP.

For pulling UDP and uPNP traffic, is there a simple tcpdump command-line filter that will extract what bwssystems needs for debugging? Or is something like a complete dump and advanced Wireshark filters needed?

I will update mine to the new revision before I investigate further but it would help me (and others?) if my above question answered. I know how to use both filters but not that familiar with the specific HUE UDP/uPNP discovery/handshake process which would help separate the wheat from the chaff. The web traffic is pretty straightforward (segragated by the TCP stream) and I actually see the habridge's topology report contain the new additions.

What is the preferred way of adding ha-bridge Hue emulated devices, anyhow? I usually told my single alexa to "discover devices" but the app itself makes you choose the built-in Hue capability and then say which Hub type. If I say type V2 it wants me to log into the Hue system, so I have always been using V1. I am guessing they will probably drop support for V1 sometime in the future since they are trying to take this simple tech and Moneyize it for themselves.

I can also generate traces before my bridge 5.3.0 to 5.3.1 update, and after too if that will help.

@bwssytems
Copy link
Owner

Please see the readme on the github page which has a description of the upnp and also at https://developers.meethue.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate question
Projects
None yet
Milestone
5..4.0
Development

Successfully merging a pull request may close this issue.

Dev branch 5.3.x bwssytems/ha-bridge
4 participants
@dougdalton @audiofreak9 @bwssytems @dye46