Closed Semag closed 8 years ago
jimboca
commented
8 years ago Hi Semag,
I am having the same issue trying to interface this to the Amazon Echo and Andy made some suggested changes https://github.com/falk0069/hue-upnp/issues/2 which I tried but need to double check again since I left on vacation shortly after that. I hope to get back to it next week sometime. I was able to get it working with my Harmony Hub, so it does work, but something is not sent that other hubs expect.
Semag
commented
8 years ago Thanks Jimboca- I read through your thread again.
I think i'm going to try to use the real interface MAC address and see if that does anything.
The other part is I'm using the cheaper Harmony Hub, not the ultimate - but I think the base stations are the same?
Also- is the Hub supposed to request encoding GZIP, deflate?
GET /description.xml HTTP/1.1
connection: keep-alive
accept-language: en-us
accept-encoding: gzip, deflate
user-agent: LuaSocket/2.0.2 Pimento/3.12.9
accept: */*
te: trailers
host: 192.168.1.10
falk0069
commented
8 years ago Semag,
This does look like the same issue Jimboca is having. The Hub gets far enough to request the description.xml but then does not turnaround and start making the JSON calls. This is very confusing. As for the accepting gzip/deflate, that is normal. It just means that it accepts these compressions but it isn't required. I looked through some of my old traces and they looked the same, so we'd expect the hub to send that.
I just tried a few remove and re-add attempts with my hub and it is still work, but oddly I'm not seeing it request the description.xml either using tcpdump. Maybe something is cached for me. I'm getting tired and might be missing something. I'm going to try looking at it more tomorrow.
Thanks --Andy
Semag
commented
8 years ago @falk0069 @jimboca
Guys- Great news!
I found my hub wasn't updated (Previously the "sync" would update, but the new 4.X software required a manual upgrade).
After upgrading to 4.X - it works!!!! I'm so excited, this is radical - I'm going to go play with seeing if I can get WOL working - and then the possibilities are endless!
Semag
commented
8 years ago Super awesome - totally works. Love it and got the external script call to work.
Now, my Harmony can issue remote commands (hauppauge remote) after the PC is booted and launch whatever i want - but the biggest issue was i could NOT use the remote to turn on the media PC. You've totally fixed that @falk0069 - you're my hero
falk0069
commented
8 years ago Semag,
That is exactly why I did this...that and being able to control my Wemo devices too. I'm still concerned that there might be a problem because it appears that the new firmware never requests the description.xml and just assumes the JSON API URL is the same IP that the description.xml lives. Not a bad assumption, but I believe this might be related to jimboca's issue and the Echo device. In any case, I'm glad you are up and running.
Semag
commented
8 years ago If it would help I can get you a new tcpdump and a new log capture.
I think the xml/http request are case sensitive too (Basic:1 versus basic:1)
I found a way to launch Pandora via command-line (pianobar) and auto start a station.
This opens the door for that rad "walk through the door and music starts playing" type of automation :)
On Sat, Sep 19, 2015, 12:41 PM falk0069 notifications@github.com wrote:
Semag,
That is exactly why I did this...that and being able to control my Wemo devices too. I'm still concerned that there might be a problem because it appears that the new firmware never requests the description.xml and just assumes the JSON API URL is the same IP that the description.xml lives. Not a bad assumption, but I believe this might be related to jimboca's issue and the Echo device. In any case, I'm glad you are up and running.
— Reply to this email directly or view it on GitHub https://github.com/falk0069/hue-upnp/issues/3#issuecomment-141701133.
Hey falk0069-
Love this idea - found this trying to get WOL support for my hub.
I feel like I'm so close but i'm not sure why the discovery isn't completing.
I can see from the log that it is doing the GET - which is good, it is making it past the initial SEARCH, but then the desscription.xml (which is sent, i can see it on tcpdump) isn't seeming to trigger a completion by the hub.
Any thoughts?
(I know there's a couple other IP's doing some UPnP on the network - sorry for thet clutter in the log).
Here's what I get on that final tcpdump in that part: