RAID5 wrote:Thanks for your help, I thought I needed to use the skill, I just asked Alexa to discover devices and they were found. Now it rocks!! Thanks again!!
Great - pleased it is now working for you.
RAID5 wrote:Thanks for your help, I thought I needed to use the skill, I just asked Alexa to discover devices and they were found. Now it rocks!! Thanks again!!
gmoeller wrote:... if I buy an Echo Dot and do the discovery procedure with the Echo Dot, would afterwards all devices be accessible by the Echo Gen2 as well? ...
$ lsof -i :1900
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
IndigoPlu 1280 tshort 10u IPv4 0x42d8f365c1781ae1 0t0 UDP *:ssdp
IndigoPlu 1280 tshort 13u IPv4 0x42d8f365c1782041 0t0 UDP *:ssdp
$
$ netstat -na | grep 8180
tcp4 0 0 192.168.1.2.8180 *.* LISTEN
tcp4 0 0 192.168.1.2.8180 192.168.1.169.43542 TIME_WAIT
tcp4 0 0 192.168.1.2.8180 192.168.1.169.52983 TIME_WAIT
tcp4 0 0 192.168.1.2.8180 192.168.1.184.62481 TIME_WAIT
$
GET /description.xml HTTP/1.1
Content-Type: application/json
User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AEORD Build/LVY48F)
Host: 192.168.1.2:8180
Connection: Keep-Alive
Accept-Encoding: gzip
HTTP/1.1 200 OK
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Content-type: application/xml
<?xml version="1.0"?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.2:8180/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>Alexa Hue Bridge</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>http://www.philips.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2012</modelName>
<modelNumber>929000226503</modelNumber>
<modelURL>http://www.meethue.com</modelURL>
<serialNumber>001788101fe2</serialNumber>
<UDN>uuid:8ecc3e54-f8b2-11e7-924f-a820662e4fb4</UDN>
<presentationURL>index.html</presentationURL>
<iconList>
<icon>
<mimetype>image/png</mimetype>
<height>48</height>
<width>48</width>
<depth>24</depth>
<url>hue_logo_0.png</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<height>120</height>
<width>120</width>
<depth>24</depth>
<url>hue_logo_3.png</url>
</icon>
</iconList>
</device>
</root>
POST /api HTTP/1.1
Content-Type: application/json
User-Agent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AEORD Build/LVY48F)
Host: 192.168.1.2
Connection: Keep-Alive
Accept-Encoding: gzip
Content-Length: 22
{"devicetype": "Echo"}
HTTP/1.1 503 Service Unavailable
Date: Sun, 14 Jan 2018 04:39:54 GMT
Server: Apache/2.4.28 (Unix) LibreSSL/2.2.7
Content-Location: websitesoff403.html.en
Vary: negotiate,accept-language
TCN: choice
Last-Modified: Wed, 20 Sep 2017 20:17:40 GMT
ETag: "631-559a4aae20100;561f69eb40400"
Accept-Ranges: bytes
Content-Length: 1585
Cache-Control: no-cache
Connection: close
Content-Type: text/html
Content-Language: en
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
/* HTML follows */
autolog wrote:It seems that the Echo (Gen2) doesn't work. ... Gen 2 Echo Dots do work AFAIK. ....
I'm sorry about the issue with connecting your Hue bridge via Echo device.
Upon checking, I've found that currently we are not facing any issue with connecting the Hue bridge with Echo device.
I apologies for the any miscommunication happened with previous conversation.
Since in this case, I request you to follow the below steps, to connect the Hue bridge:
Philips smart home devices with the V1 Hue Bridge (circle-shaped) are only compatible with:
- Amazon Echo (1st Generation)
- Amazon Echo (2nd Generation)
- Echo Plus
- Echo Dot
- Amazon Tap
The V2 Hue Bridge (square-shaped) required the Hue skill and is compatible with all Alexa devices.
jtburgess wrote:They why doesn't it work with the meethue.com web site. That has nothing to do with any Alexa device?
andThere are no bridges on your network
Please ensure that your bridge is turned on and that you are connected to the same network as your bridge.
2018-03-09 17:49:04.034 DEBUG Plugin.responder.respond Responder.respond called from address ('192.168.0.15', 50000)
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=100
EXT:
LOCATION: http://192.168.0.5:8178/description.xml
SERVER: FreeRTOS/7.4.2, UPnP/1.0, IpBridge/1.7.0
ST: urn:schemas-upnp-org:device:basic:1
USN: uuid:da151438-fa2b-11e7-a3f5-38c9862674d9
2018-03-09 17:49:04.034 DEBUG Plugin.responder.respond Responder.respond: creating output_socket
2018-03-09 17:49:04.034 DEBUG Plugin.responder.respond Responder.respond: calling output_socket.sendto
2018-03-09 17:49:04.035 DEBUG Plugin.responder.respond Responder.respond: closing output_socket
2018-03-09 17:49:04.035 DEBUG Plugin.responder.respond Responder.respond: UDP Response sent to ('192.168.0.15', 50000)
Users browsing this forum: No registered users and 13 guests