search

mabunixda / node-red-contrib-alexa-home

MIT License
32 stars 10 forks source link

Issue after updating to 1.x with device discovery #16

Closed tribbles3 closed 5 years ago

tribbles3 commented 5 years ago

Posting this here because it looks like the other issue thread has been closed.

I did the latest update and can longer access any of the nodes/devices. I tried discovering devices, nothing was found and then I tried creating a new device and that was not discovered either. I noticed that none of the nodes are displaying any status information under the node whereas before the was status information.

mabunixda commented 5 years ago

There might be a problem again at the moment. I will try a test setup if there exists a workaround and i have to dig into the available alexa documentation. Right now i just found that the maximum response size is 24k - but at the moment this happens already a 14k response size. I am also wondering what a real hue hub does when these limits apply...

stephjj commented 5 years ago

I have found the problem for my case. It's a conflict with node-red-contrib-alexa-home-skill Capture

SamNitro commented 5 years ago

I can add 35 devices after that all my devices go offline. Does one have a solution for it?

EDIT: pi@FHEM:~ $ curl -sv http://10.1.1.3:1880/api/abc/lights 2>&1 | grep Content-Length < Content-Length: 13981

14.000 Round 35 Devices 24.000 Round 60 Devices

Original Hue 50 Devices

EDIT2: if I disconnect my echo dot 1.gen all my devices are not available

3ative commented 5 years ago

@mabunixda So I upgraded to this new version today and I'm having the same issues as everyone else The previous worked perfectly, for me.

How do I get the old version installed back in?

mabunixda commented 5 years ago

i am still working on a workaround of this limitation.

@3ative go to your userdirectory of node-red and edit the package.json - set the version 0.3.5 in there.

@SamNitro also if you have less devices they are still not available when the 1.gen is disconnected?

3ative commented 5 years ago

@mabunixda Thanks, I'll try that later... But, found another node that works like your old one, for the moment.

SamNitro commented 5 years ago

I will not be home until tomorrow, then I will test it.

mabunixda commented 5 years ago

@3ative which one? there seems to be a firmware upgrade on the alexa devices on the last days.

i just got the same problem with my deployment at home which was running now since release 1.0 very smooth and much more reactive then the 0.x version. And also on other alexa node-red nodes the same issues start appearing.

3ative commented 5 years ago

@mabunixda It's : node-red-contrib-alexa-local - https://flows.nodered.org/node/node-red-contrib-alexa-local Current version shows: 0.3.24

mabunixda commented 5 years ago

Discovery is working again in my deployment. I also got a fix set up for the limitation of maximum devices. This fix is still not stable but will become released by today or at least tomorrow!

SamNitro commented 5 years ago

Yes, when i disconnect my Dot 1Gen, the Device are not available (With 17 Devices)

mabunixda commented 5 years ago

@SamNitro your other devices are gen3 right?

SamNitro commented 5 years ago

I have -Dot Gen2 -Dot Gen3 -Spot

SamNitro commented 5 years ago

Sorry my First Dot is 2nd Gen

jaburges commented 5 years ago

Hi there, as per the others I seem to have an issue with discovery since 1.0.4

My old nodes work, but i'm unable to add any new ones? i've tried with node-red:v10 docker now trying with 0.20.7-v8

devices I've tried from alexa.amazon.com dot gen3 spot show 1 show 2 fire tablet echo 1

any ideas on how to solve this? 9 nodes and a controller (want to add 3 more) EDIT: uninstalling (restarting) and reinstalling doesnt work either :(

mabunixda commented 5 years ago

@jaburges are you running the old version and new version in docker?

devzeb commented 5 years ago

I'm having the same issue, alexa is not able to discovery any devices. I'm running version 1.0.4 of this plugin on linux mint, without docker. I'm trying to run discovery using echo dot gen 3.

The controller on the node-red webpage is displaying "setup requested".

Debug Output:

27 Aug 22:23:08 - [info] Flows starten
27 Aug 22:23:08 - [debug] red/nodes/flows.start : starting flow : global
27 Aug 22:23:08 - [debug] red/nodes/flows.start : starting flow : 71be1ebd.5d865
27 Aug 22:23:08 - [debug] No Alexa Home Controller available
27 Aug 22:23:08 - [info] [alexa-home-controller:Alexa Controller] Alexa Controller - alexa-home - Starting SSDP
27 Aug 22:23:08 - [debug] Alexa Controller - announcing: http://*:1880/alexa-home/setup.xml
27 Aug 22:23:08 - [info] Assigning alexa-home nodes to this controller
27 Aug 22:23:08 - [info] Flows gestartet
27 Aug 22:23:12 - [debug] Setup was requested
27 Aug 22:23:12 - [debug] Alexa Controller - Handling setup request
27 Aug 22:23:12 - [debug] Alexa Controller - sending baseUrl http://192.168.178.200:1880

Using WireShark I'm able to see my pc sending the settings.xml file to the echo device. I'm not experienced in using Wireshark, but there are a couple of red lines, don't know if they are relevant though. See attached screenshot. Bildschirmfoto vom 2019-08-27 22-54-09

jaburges commented 5 years ago

@jaburges are you running the old version and new version in docker?

i've not rolled back to an older version, but yes its all docker based, although based on the above it seems its not isolated to docker. (i'm also able to send POST requests to the docker as i use that for sending motion detection messages from my cameras to Node-Red)

mabunixda commented 5 years ago

The ssdp discovery and also http information is now handled in another way on version 1.1.0. Please retest your installations with this version. The new version is better capable of higher amount of items.

devzeb commented 5 years ago

Unfortunately, my installation is still not able to discovery any devices using version 1.1.0.

Flow: Bildschirmfoto vom 2019-08-28 17-16-33

Debug Output:

28 Aug 17:12:11 - [info] Node-RED Version: v0.20.7
28 Aug 17:12:11 - [info] Node.js  Version: v12.8.0
28 Aug 17:12:11 - [info] Linux 4.15.0-58-generic x64 LE
28 Aug 17:12:12 - [info] Paletten-Nodes werden geladen
28 Aug 17:12:12 - [debug] Module: node-red-contrib-alexa-local 0.3.24
28 Aug 17:12:12 - [debug]         /home/seb/.node-red/node_modules/node-red-contrib-alexa-local
28 Aug 17:12:12 - [debug] Module: node-red-contrib-amazon-echo 0.1.8
28 Aug 17:12:12 - [debug]         /home/seb/.node-red/node_modules/node-red-contrib-amazon-echo
28 Aug 17:12:12 - [debug] Module: node-red-node-email 1.6.2
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-email
28 Aug 17:12:12 - [debug] Module: node-red-node-feedparser 0.1.14
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
28 Aug 17:12:12 - [debug] Module: node-red-node-rbe 0.2.5
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
28 Aug 17:12:12 - [debug] Module: node-red-node-sentiment 0.1.4
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-sentiment
28 Aug 17:12:12 - [debug] Module: node-red-node-tail 0.0.2
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-tail
28 Aug 17:12:12 - [debug] Module: node-red-node-twitter 1.1.5
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
28 Aug 17:12:12 - [debug] Module: node-red-contrib-alexa-home 1.1.0
28 Aug 17:12:12 - [debug]         /usr/lib/node_modules/node-red-contrib-alexa-home
28 Aug 17:12:12 - [warn] rpi-gpio : Raspberry Pi-spezifische Nodes inaktiv
28 Aug 17:12:12 - [warn] rpi-gpio : Pi RPi.GPIO-Python-Bibliothek nicht gefunden
28 Aug 17:12:12 - [info] Einstellungsdatei: /home/seb/.node-red/settings.js
28 Aug 17:12:12 - [info] Kontextspeicher: 'default' [ module=memory]
28 Aug 17:12:12 - [info] Benutzerverzeichnis: /home/seb/.node-red
28 Aug 17:12:12 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
28 Aug 17:12:12 - [info] Flow-Datei: /home/seb/.node-red/flows_seb-desktop.json
28 Aug 17:12:12 - [info] Server wird jetzt auf http://127.0.0.1:1880/ ausgeführt.
28 Aug 17:12:12 - [debug] loaded flow revision: 0317f91252bc0ea2ac2d840d55163289
28 Aug 17:12:12 - [debug] red/runtime/nodes/credentials.load : no user key present
28 Aug 17:12:12 - [debug] red/runtime/nodes/credentials.load : using default key
28 Aug 17:12:12 - [debug] red/runtime/nodes/credentials.load : keyType=system
28 Aug 17:12:12 - [warn] 

---------------------------------------------------------------------
Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom System generierten Schlüssel verschlüsselt.

Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren geht, werden Ihre Berechtigungsnachweise
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen und erneut eingeben.
Ihre Berechtigungsnachweise.

Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option 'credentialSecret' in
Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise erneut verschlüsseln.
Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer Änderung verwenden.
---------------------------------------------------------------------

28 Aug 17:12:12 - [info] Flows starten
28 Aug 17:12:12 - [debug] red/nodes/flows.start : starting flow : global
28 Aug 17:12:12 - [debug] red/nodes/flows.start : starting flow : 71be1ebd.5d865
28 Aug 17:12:12 - [info] [alexa-home-controller:Alexa Controller] 0 - alexa-home - Starting SSDP
28 Aug 17:12:12 - [info] [alexa-home-controller:Alexa Controller] 0 - announcing: http://*:60000/alexa-home/setup.xml
28 Aug 17:12:12 - [info] Assigning alexa-home nodes to this controller
28 Aug 17:12:12 - [info] Flows gestartet
28 Aug 17:12:17 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /alexa-home/setup.xml
28 Aug 17:12:17 - [debug] Alexa Controller/0 - Handling setup request

Wireshark: Bildschirmfoto vom 2019-08-28 17-14-51

If you need any further information, just let me know

mabunixda commented 5 years ago

@derSebbl Can you get me the output of http://192.168.178.200:60000/alexa-home/setup.xml ? remembering wireshark output correct 200 is your computer and 112 the alexa device?

From your log and the output the registration process stops after fetching the setup information and no data about the nodes is requested from alexa. There might be a problem again with the correct ip in this document.

What is the request about HTTP/1.1 200 OK before /aelxa-home/setup.xml request? ( just wondering )

Are you running on https? then i might got a regression issue within the code 👎

devzeb commented 5 years ago

Yes, you are correct about the IPs. 200 is the desktop and 112 is the echo dot.

I'm not running on https, as far as I know. I haven't changed any https related settings.

Here is the output from setup.xml:

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>https://192.168.178.200:60000</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>
Amazon-Echo-NodeRed-Bridge https://192.168.178.200:60000
</friendlyName>
<manufacturer>Royal Philips Electronics</manufacturer>
<manufacturerURL>https://nitram.at</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2012</modelName>
<modelNumber>1100110011001100</modelNumber>
<modelURL>http://meethue.com</modelURL>
<serialNumber>93eadbeef14</serialNumber>
<UDN>uuid:f6543a06-da50-11ba-8d8f-b8d6648d770bd8</UDN>
<serviceList>
<service>
<serviceType>(null)</serviceType>
<serviceId>(null)</serviceId>
<controlURL>(null)</controlURL>
<eventSubURL>(null)</eventSubURL>
<SCPDURL>(null)</SCPDURL>
</service>
</serviceList>
<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>

The "HTTP/1.1 200 OK" request contains the following payload:

0000   3c 72 6f 6f 74 20 78 6d 6c 6e 73 3d 22 75 72 6e   <root xmlns="urn
0010   3a 73 63 68 65 6d 61 73 2d 75 70 6e 70 2d 6f 72   :schemas-upnp-or
0020   67 3a 64 65 76 69 63 65 2d 31 2d 30 22 3e 0a 20   g:device-1-0">. 
0030   20 20 20 3c 73 70 65 63 56 65 72 73 69 6f 6e 3e      <specVersion>
0040   0a 20 20 20 20 20 20 20 20 3c 6d 61 6a 6f 72 3e   .        <major>
0050   31 3c 2f 6d 61 6a 6f 72 3e 0a 20 20 20 20 20 20   1</major>.      
0060   20 20 3c 6d 69 6e 6f 72 3e 30 3c 2f 6d 69 6e 6f     <minor>0</mino
0070   72 3e 0a 20 20 20 20 3c 2f 73 70 65 63 56 65 72   r>.    </specVer
0080   73 69 6f 6e 3e 0a 20 20 20 20 3c 55 52 4c 42 61   sion>.    <URLBa
0090   73 65 3e 68 74 74 70 73 3a 26 23 78 32 46 3b 26   se>https:&#x2F;&
00a0   23 78 32 46 3b 31 39 32 2e 31 36 38 2e 31 37 38   #x2F;192.168.178
00b0   2e 32 30 30 3a 36 30 30 30 30 3c 2f 55 52 4c 42   .200:60000</URLB
00c0   61 73 65 3e 0a 20 20 20 20 3c 64 65 76 69 63 65   ase>.    <device
00d0   3e 0a 20 20 20 20 20 20 20 20 3c 64 65 76 69 63   >.        <devic
00e0   65 54 79 70 65 3e 75 72 6e 3a 73 63 68 65 6d 61   eType>urn:schema
00f0   73 2d 75 70 6e 70 2d 6f 72 67 3a 64 65 76 69 63   s-upnp-org:devic
0100   65 3a 42 61 73 69 63 3a 31 3c 2f 64 65 76 69 63   e:Basic:1</devic
0110   65 54 79 70 65 3e 0a 20 20 20 20 20 20 20 20 3c   eType>.        <
0120   66 72 69 65 6e 64 6c 79 4e 61 6d 65 3e 41 6d 61   friendlyName>Ama
0130   7a 6f 6e 2d 45 63 68 6f 2d 4e 6f 64 65 52 65 64   zon-Echo-NodeRed
0140   2d 42 72 69 64 67 65 20 68 74 74 70 73 3a 26 23   -Bridge https:&#
0150   78 32 46 3b 26 23 78 32 46 3b 31 39 32 2e 31 36   x2F;&#x2F;192.16
0160   38 2e 31 37 38 2e 32 30 30 3a 36 30 30 30 30 3c   8.178.200:60000<
0170   2f 66 72 69 65 6e 64 6c 79 4e 61 6d 65 3e 0a 20   /friendlyName>. 
0180   20 20 20 20 20 20 20 3c 6d 61 6e 75 66 61 63 74          <manufact
0190   75 72 65 72 3e 52 6f 79 61 6c 20 50 68 69 6c 69   urer>Royal Phili
01a0   70 73 20 45 6c 65 63 74 72 6f 6e 69 63 73 3c 2f   ps Electronics</
01b0   6d 61 6e 75 66 61 63 74 75 72 65 72 3e 0a 20 20   manufacturer>.  
01c0   20 20 20 20 20 20 3c 6d 61 6e 75 66 61 63 74 75         <manufactu
01d0   72 65 72 55 52 4c 3e 68 74 74 70 73 3a 2f 2f 6e   rerURL>https://n
01e0   69 74 72 61 6d 2e 61 74 3c 2f 6d 61 6e 75 66 61   itram.at</manufa
01f0   63 74 75 72 65 72 55 52 4c 3e 0a 20 20 20 20 20   cturerURL>.     
0200   20 20 20 3c 6d 6f 64 65 6c 44 65 73 63 72 69 70      <modelDescrip
0210   74 69 6f 6e 3e 50 68 69 6c 69 70 73 20 68 75 65   tion>Philips hue
0220   20 50 65 72 73 6f 6e 61 6c 20 57 69 72 65 6c 65    Personal Wirele
0230   73 73 20 4c 69 67 68 74 69 6e 67 3c 2f 6d 6f 64   ss Lighting</mod
0240   65 6c 44 65 73 63 72 69 70 74 69 6f 6e 3e 0a 20   elDescription>. 
0250   20 20 20 20 20 20 20 3c 6d 6f 64 65 6c 4e 61 6d          <modelNam
0260   65 3e 50 68 69 6c 69 70 73 20 68 75 65 20 62 72   e>Philips hue br
0270   69 64 67 65 20 32 30 31 32 3c 2f 6d 6f 64 65 6c   idge 2012</model
0280   4e 61 6d 65 3e 0a 20 20 20 20 20 20 20 20 3c 6d   Name>.        <m
0290   6f 64 65 6c 4e 75 6d 62 65 72 3e 31 31 30 30 31   odelNumber>11001
02a0   31 30 30 31 31 30 30 31 31 30 30 3c 2f 6d 6f 64   10011001100</mod
02b0   65 6c 4e 75 6d 62 65 72 3e 0a 20 20 20 20 20 20   elNumber>.      
02c0   20 20 3c 6d 6f 64 65 6c 55 52 4c 3e 68 74 74 70     <modelURL>http
02d0   3a 2f 2f 6d 65 65 74 68 75 65 2e 63 6f 6d 3c 2f   ://meethue.com</
02e0   6d 6f 64 65 6c 55 52 4c 3e 0a 20 20 20 20 20 20   modelURL>.      
02f0   20 20 3c 73 65 72 69 61 6c 4e 75 6d 62 65 72 3e     <serialNumber>
0300   39 33 65 61 64 62 65 65 66 31 34 3c 2f 73 65 72   93eadbeef14</ser
0310   69 61 6c 4e 75 6d 62 65 72 3e 0a 20 20 20 20 20   ialNumber>.     
0320   20 20 20 3c 55 44 4e 3e 75 75 69 64 3a 66 36 35      <UDN>uuid:f65
0330   34 33 61 30 36 2d 64 61 35 30 2d 31 31 62 61 2d   43a06-da50-11ba-
0340   38 64 38 66 2d 62 38 64 36 36 34 38 64 37 37 30   8d8f-b8d6648d770
0350   62 64 38 3c 2f 55 44 4e 3e 0a 20 20 20 20 20 20   bd8</UDN>.      
0360   20 20 3c 73 65 72 76 69 63 65 4c 69 73 74 3e 0a     <serviceList>.
0370   20 20 20 20 20 20 20 20 20 20 20 20 3c 73 65 72               <ser
0380   76 69 63 65 3e 0a 20 20 20 20 20 20 20 20 20 20   vice>.          
0390   20 20 20 20 20 20 3c 73 65 72 76 69 63 65 54 79         <serviceTy
03a0   70 65 3e 28 6e 75 6c 6c 29 3c 2f 73 65 72 76 69   pe>(null)</servi
03b0   63 65 54 79 70 65 3e 0a 20 20 20 20 20 20 20 20   ceType>.        
03c0   20 20 20 20 20 20 20 20 3c 73 65 72 76 69 63 65           <service
03d0   49 64 3e 28 6e 75 6c 6c 29 3c 2f 73 65 72 76 69   Id>(null)</servi
03e0   63 65 49 64 3e 0a 20 20 20 20 20 20 20 20 20 20   ceId>.          
03f0   20 20 20 20 20 20 3c 63 6f 6e 74 72 6f 6c 55 52         <controlUR
0400   4c 3e 28 6e 75 6c 6c 29 3c 2f 63 6f 6e 74 72 6f   L>(null)</contro
0410   6c 55 52 4c 3e 0a 20 20 20 20 20 20 20 20 20 20   lURL>.          
0420   20 20 20 20 20 20 3c 65 76 65 6e 74 53 75 62 55         <eventSubU
0430   52 4c 3e 28 6e 75 6c 6c 29 3c 2f 65 76 65 6e 74   RL>(null)</event
0440   53 75 62 55 52 4c 3e 0a 20 20 20 20 20 20 20 20   SubURL>.        
0450   20 20 20 20 20 20 20 20 3c 53 43 50 44 55 52 4c           <SCPDURL
0460   3e 28 6e 75 6c 6c 29 3c 2f 53 43 50 44 55 52 4c   >(null)</SCPDURL
0470   3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 3c 2f   >.            </
0480   73 65 72 76 69 63 65 3e 0a 20 20 20 20 20 20 20   service>.       
0490   20 3c 2f 73 65 72 76 69 63 65 4c 69 73 74 3e 0a    </serviceList>.
04a0   20 20 20 20 20 20 20 20 3c 70 72 65 73 65 6e 74           <present
04b0   61 74 69 6f 6e 55 52 4c 3e 69 6e 64 65 78 2e 68   ationURL>index.h
04c0   74 6d 6c 3c 2f 70 72 65 73 65 6e 74 61 74 69 6f   tml</presentatio
04d0   6e 55 52 4c 3e 0a 20 20 20 20 20 20 20 20 3c 69   nURL>.        <i
04e0   63 6f 6e 4c 69 73 74 3e 0a 20 20 20 20 20 20 20   conList>.       
04f0   20 20 20 20 20 3c 69 63 6f 6e 3e 0a 20 20 20 20        <icon>.    
0500   20 20 20 20 20 20 20 20 20 20 20 20 3c 6d 69 6d               <mim
0510   65 74 79 70 65 3e 69 6d 61 67 65 2f 70 6e 67 3c   etype>image/png<
0520   2f 6d 69 6d 65 74 79 70 65 3e 0a 20 20 20 20 20   /mimetype>.     
0530   20 20 20 20 20 20 20 20 20 20 20 3c 68 65 69 67              <heig
0540   68 74 3e 34 38 3c 2f 68 65 69 67 68 74 3e 0a 20   ht>48</height>. 
0550   20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 3c                  <
0560   77 69 64 74 68 3e 34 38 3c 2f 77 69 64 74 68 3e   width>48</width>
0570   0a 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20   .               
0580   20 3c 64 65 70 74 68 3e 32 34 3c 2f 64 65 70 74    <depth>24</dept
0590   68 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 20   h>.             
05a0   20 20 20 3c 75 72 6c 3e 68 75 65 5f 6c 6f 67 6f      <url>hue_logo
05b0   5f 30 2e 70 6e 67 3c 2f 75 72 6c 3e 0a 20 20 20   _0.png</url>.   
05c0   20 20 20 20 20 20 20 20 20 3c 2f 69 63 6f 6e 3e            </icon>
05d0   0a 20 20 20 20 20 20 20 20 20 20 20 20 3c 69 63   .            <ic
05e0   6f 6e 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20   on>.            
05f0   20 20 20 20 3c 6d 69 6d 65 74 79 70 65 3e 69 6d       <mimetype>im
0600   61 67 65 2f 70 6e 67 3c 2f 6d 69 6d 65 74 79 70   age/png</mimetyp
0610   65 3e 0a 20 20 20 20 20 20 20 20 20 20 20 20 20   e>.             
0620   20 20 20 3c 68 65 69 67 68 74 3e 31 32 30 3c 2f      <height>120</
0630   68 65 69 67 68 74 3e 0a 20 20 20 20 20 20 20 20   height>.        
0640   20 20 20 20 20 20 20 20 3c 77 69 64 74 68 3e 31           <width>1
0650   32 30 3c 2f 77 69 64 74 68 3e 0a 20 20 20 20 20   20</width>.     
0660   20 20 20 20 20 20 20 20 20 20 20 3c 64 65 70 74              <dept
0670   68 3e 32 34 3c 2f 64 65 70 74 68 3e 0a 20 20 20   h>24</depth>.   
0680   20 20 20 20 20 20 20 20 20 20 20 20 20 3c 75 72                <ur
0690   6c 3e 68 75 65 5f 6c 6f 67 6f 5f 33 2e 70 6e 67   l>hue_logo_3.png
06a0   3c 2f 75 72 6c 3e 0a 20 20 20 20 20 20 20 20 20   </url>.         
06b0   20 20 20 3c 2f 69 63 6f 6e 3e 0a 20 20 20 20 20      </icon>.     
06c0   20 20 20 3c 2f 69 63 6f 6e 4c 69 73 74 3e 0a 20      </iconList>. 
06d0   20 20 20 3c 2f 64 65 76 69 63 65 3e 0a 3c 2f 72      </device>.</r
06e0   6f 6f 74 3e                                       oot>
                                  ..
mabunixda commented 5 years ago

@derSebbl ok - you are not running nodered on https? Can you check your settings.js about a section https: {} ? Can you try following request: https://192.168.178.200:60000/api/x/lights ?

I probably must disable the forwarding of https configuration from nodered to the alexa webserver :(

devzeb commented 5 years ago

I haven't changed anything https related, so I don't think that I'm running the service as https... I'm pretty much running a fresh installation of node-red with only a few modules installed.

The request url doesn't work, the output is:

Diese Website kann keine sichere Verbindung bereitstellen 192.168.178.200 hat eine ungültige Antwort gesendet.
ERR_SSL_PROTOCOL_ERROR
devzeb commented 5 years ago

The section about https: {} is not active (commented out), check the attached file: settings.js.txt

mabunixda commented 5 years ago

which node and npm versions are you using?

devzeb commented 5 years ago

which node and npm versions are you using?

Don't know how to check that, I'm fairly new to linux, could you please give me a hint?

mabunixda commented 5 years ago

node --version npm --version

should do the job

devzeb commented 5 years ago

node --version: v12.8.0 npm --version: 6.11.2

mabunixda commented 5 years ago

@derSebbl can you try the request without https again?

devzeb commented 5 years ago

http://192.168.178.200:60000/api/x/lights returns the following:

{"8a59f7540553e8": {"state": {"on": false,"bri": 0,"hue": 0,"sat": 254,"effect": "none","xy": [0.0,0.0],"ct": 199,"colormode": "ct","reachable": true},"swupdate": {"state": "noupdates","lastinstall": "2019-08-28T18:28:52"},"type": "Extended color light","name": "Gerät-wesdk","modelid": "LCT007","manufacturername": "Philips","productname": "Hue color lamp","swversion": "5.105.0.21169"},"43bb26fce6bd38": {"state": {"on": false,"bri": 0,"hue": 0,"sat": 254,"effect": "none","xy": [0.0,0.0],"ct": 199,"colormode": "ct","reachable": true},"swupdate": {"state": "noupdates","lastinstall": "2019-08-28T18:28:52"},"type": "Extended color light","name": "Gerät-7fs9da","modelid": "LCT007","manufacturername": "Philips","productname": "Hue color lamp","swversion": "5.105.0.21169"},"last": {}}

Also the controller node in node-red switches to "lights list requested: 1" when opening that link manually.

devzeb commented 5 years ago

Could this be a network related issue? I'm also unable to get the module "node-red-contrib-alexa-local" to work on my setup, even though I was able to successfully use it last week on another network / pc.

mabunixda commented 5 years ago

according to your logs aexa is detecting the installation by ssdp via udp. the provided information is forwarded about setup.xml was correct forwarded to alexa ( with http ) and setup.xml was fetched by alexa. but somehow alexa does not fetch the information about the devices. the baseurl in setup.xml was on https and misleading but should not affect this. i fixxed this within 1.1.1

you might update the settings.js to get debugging logs and change the level of the console to debug. logging: { console: { level: "debug", metrics: false, audit: false } }

mabunixda commented 5 years ago

Please Just Install one Alexa node. This might create awesome Side effects in all  nodes. I saw 3 different Alexa nodes

Am 28. Aug. 2019, 21:04, um 21:04, Sebastian Michel notifications@github.com schrieb:

Tried version 1.1.1, updated settings.js to display debug messages. No change yet, log:

28 Aug 21:02:49 - [info] Node-RED Version: v0.20.7
28 Aug 21:02:49 - [info] Node.js  Version: v12.9.1
28 Aug 21:02:49 - [info] Linux 4.15.0-58-generic x64 LE
28 Aug 21:02:49 - [info] Paletten-Nodes werden geladen
28 Aug 21:02:49 - [debug] Module: node-red-contrib-alexa-local 0.3.24
28 Aug 21:02:49 - [debug]        
/home/seb/.node-red/node_modules/node-red-contrib-alexa-local
28 Aug 21:02:49 - [debug] Module: node-red-contrib-amazon-echo 0.1.8
28 Aug 21:02:49 - [debug]        
/home/seb/.node-red/node_modules/node-red-contrib-amazon-echo
28 Aug 21:02:49 - [debug] Module: node-red-node-email 1.6.2
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-email
28 Aug 21:02:49 - [debug] Module: node-red-node-feedparser 0.1.14
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
28 Aug 21:02:49 - [debug] Module: node-red-node-rbe 0.2.5
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
28 Aug 21:02:49 - [debug] Module: node-red-node-sentiment 0.1.4
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-sentiment
28 Aug 21:02:49 - [debug] Module: node-red-node-tail 0.0.2
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-tail
28 Aug 21:02:49 - [debug] Module: node-red-node-twitter 1.1.5
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
28 Aug 21:02:49 - [debug] Module: node-red-contrib-alexa-home 1.1.0
28 Aug 21:02:49 - [debug]        
/usr/lib/node_modules/node-red-contrib-alexa-home
28 Aug 21:02:49 - [warn] rpi-gpio : Raspberry Pi-spezifische Nodes
inaktiv
28 Aug 21:02:49 - [warn] rpi-gpio : Pi RPi.GPIO-Python-Bibliothek nicht
gefunden
28 Aug 21:02:49 - [info] Einstellungsdatei:
/home/seb/.node-red/settings.js
28 Aug 21:02:49 - [info] Kontextspeicher: 'default' [ module=memory]
28 Aug 21:02:49 - [info] Benutzerverzeichnis: /home/seb/.node-red
28 Aug 21:02:49 - [warn] Projekte inaktiviert:
editorTheme.projects.enabled=false
28 Aug 21:02:49 - [info] Flow-Datei:
/home/seb/.node-red/flows_seb-desktop.json
28 Aug 21:02:49 - [info] Server wird jetzt auf http://127.0.0.1:1880/
ausgeführt.
28 Aug 21:02:49 - [debug] loaded flow revision:
f03117b5b87f2a80684e6d267db6b0ba
28 Aug 21:02:49 - [debug] red/runtime/nodes/credentials.load : no user
key present
28 Aug 21:02:49 - [debug] red/runtime/nodes/credentials.load : using
default key
28 Aug 21:02:49 - [debug] red/runtime/nodes/credentials.load :
keyType=system
28 Aug 21:02:49 - [warn] 

---------------------------------------------------------------------
Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom
System generierten Schlüssel verschlüsselt.

Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren
geht, werden Ihre Berechtigungsnachweise
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen
und erneut eingeben.
Ihre Berechtigungsnachweise.

Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option
'credentialSecret' in
Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise
erneut verschlüsseln.
Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer
Änderung verwenden.
---------------------------------------------------------------------

28 Aug 21:02:49 - [info] Flows starten
28 Aug 21:02:49 - [debug] red/nodes/flows.start : starting flow :
global
28 Aug 21:02:49 - [debug] red/nodes/flows.start : starting flow :
71be1ebd.5d865
28 Aug 21:02:49 - [info] [alexa-home-controller:Alexa Controller] 0 -
alexa-home - Starting SSDP
28 Aug 21:02:49 - [info] [alexa-home-controller:Alexa Controller] 0 -
announcing: http://*:60000/alexa-home/setup.xml
28 Aug 21:02:49 - [info] Assigning alexa-home nodes to this controller
28 Aug 21:02:49 - [info] Flows gestartet
28 Aug 21:03:14 - [info] [alexa-home-controller:Alexa Controller] 60000
-> /alexa-home/setup.xml
28 Aug 21:03:14 - [debug] Alexa Controller/0 - Handling setup request

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/mabunixda/node-red-contrib-alexa-home/issues/16#issuecomment-525880032

devzeb commented 5 years ago

Got confused by the package id not being updated (still 1.1.0 instead of 1.1.1). I deleted the comment because I thought I didn't install the correct module.

Log with only one Alexa device and version 1.1.1:

28 Aug 21:11:40 - [info] Node.js  Version: v12.9.1
28 Aug 21:11:40 - [info] Linux 4.15.0-58-generic x64 LE
28 Aug 21:11:40 - [info] Paletten-Nodes werden geladen
28 Aug 21:11:40 - [debug] Module: node-red-contrib-alexa-local 0.3.24
28 Aug 21:11:40 - [debug]         /home/seb/.node-red/node_modules/node-red-contrib-alexa-local
28 Aug 21:11:40 - [debug] Module: node-red-contrib-amazon-echo 0.1.8
28 Aug 21:11:40 - [debug]         /home/seb/.node-red/node_modules/node-red-contrib-amazon-echo
28 Aug 21:11:40 - [debug] Module: node-red-node-email 1.6.2
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-email
28 Aug 21:11:40 - [debug] Module: node-red-node-feedparser 0.1.14
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
28 Aug 21:11:40 - [debug] Module: node-red-node-rbe 0.2.5
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
28 Aug 21:11:40 - [debug] Module: node-red-node-sentiment 0.1.4
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-sentiment
28 Aug 21:11:40 - [debug] Module: node-red-node-tail 0.0.2
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-tail
28 Aug 21:11:40 - [debug] Module: node-red-node-twitter 1.1.5
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
28 Aug 21:11:40 - [debug] Module: node-red-contrib-alexa-home 1.1.0
28 Aug 21:11:40 - [debug]         /usr/lib/node_modules/node-red-contrib-alexa-home
28 Aug 21:11:40 - [warn] rpi-gpio : Raspberry Pi-spezifische Nodes inaktiv
28 Aug 21:11:40 - [warn] rpi-gpio : Pi RPi.GPIO-Python-Bibliothek nicht gefunden
28 Aug 21:11:40 - [info] Einstellungsdatei: /home/seb/.node-red/settings.js
28 Aug 21:11:40 - [info] Kontextspeicher: 'default' [ module=memory]
28 Aug 21:11:40 - [info] Benutzerverzeichnis: /home/seb/.node-red
28 Aug 21:11:40 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
28 Aug 21:11:40 - [info] Flow-Datei: /home/seb/.node-red/flows_seb-desktop.json
28 Aug 21:11:40 - [info] Server wird jetzt auf http://127.0.0.1:1880/ ausgeführt.
28 Aug 21:11:40 - [debug] loaded flow revision: 419e465c2e048d1a93bfda89d4e56055
28 Aug 21:11:40 - [debug] red/runtime/nodes/credentials.load : no user key present
28 Aug 21:11:40 - [debug] red/runtime/nodes/credentials.load : using default key
28 Aug 21:11:40 - [debug] red/runtime/nodes/credentials.load : keyType=system
28 Aug 21:11:40 - [warn] 

---------------------------------------------------------------------
Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom System generierten Schlüssel verschlüsselt.

Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren geht, werden Ihre Berechtigungsnachweise
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen und erneut eingeben.
Ihre Berechtigungsnachweise.

Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option 'credentialSecret' in
Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise erneut verschlüsseln.
Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer Änderung verwenden.
---------------------------------------------------------------------

28 Aug 21:11:40 - [info] Flows starten
28 Aug 21:11:40 - [debug] red/nodes/flows.start : starting flow : global
28 Aug 21:11:40 - [debug] red/nodes/flows.start : starting flow : 71be1ebd.5d865
28 Aug 21:11:40 - [info] [alexa-home-controller:Alexa Controller] 0 - alexa-home - Starting SSDP
28 Aug 21:11:40 - [info] [alexa-home-controller:Alexa Controller] 0 - announcing: http://*:60000/alexa-home/setup.xml
28 Aug 21:11:40 - [info] Assigning alexa-home nodes to this controller
28 Aug 21:11:40 - [info] Flows gestartet
28 Aug 21:11:44 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /alexa-home/setup.xml
28 Aug 21:11:44 - [debug] Alexa Controller/0 - Handling setup request
devzeb commented 5 years ago

Let me know if I can help you any further by providing additional information. I really want to get this module working ;)

nepeee commented 5 years ago

Same problem but for me, there is a tcp server on port 60000 but it don't respond to the http request: netstat -ltnp | grep -w ':60000' tcp6 0 0 :::60000 :::* LISTEN 10783/node-red

wget http://localhost:60000/api/x/lights --2019-08-28 21:34:45-- http://localhost:60000/api/x/lights Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:60000... connected. HTTP request sent, awaiting response...

And no response.

Also i has a problem with the update because de express module is not installed: [node-red-contrib-alexa-home/alexa-home-controller] Error: Cannot find module 'express'

I used 1.1.0 version.

mabunixda commented 5 years ago

@nepeee which node/npm version are you using?

holomekc commented 5 years ago

For me it also does not work. When i have https configured I see no logs regarding alexa during discovery. When I use http I can see logs indicating that setup.xml is requested and then it stops

I use: Node-Red: 0.20.7 Node.js: 11.15.0 Npm: 6.7.0

Version 1.1.1 is not published yet or is it?

devzeb commented 5 years ago

For me it also does not work. When i have https configured I see no logs regarding alexa during discovery. When I use http I can see logs indicating that setup.xml is requested and then it stops

I use: Node-Red: 0.20.7 Node.js: 11.15.0 Npm: 6.7.0

Version 1.1.1 is not published yet or is it?

Version 1.1.1 is already available here on github, check the releases tab: https://github.com/mabunixda/node-red-contrib-alexa-home/releases

To install it:

devzeb commented 5 years ago

@mabunixda the only alexa plugin which is working on my setup is: https://github.com/datech/node-red-contrib-amazon-echo

you might wanna check on how they implemented the communication between alexa and the module

devzeb commented 5 years ago

@mabunixda Trying to find out if I can get it to work, I forwarded port 80 on my pc to port 60000 using: sudo iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 60000

This results in an additional successful step in registration. Alexa is still saying "I could not find any new devices", but the function AlexaHomeController.handleRegistration is now called (the node in node-red changes to "registration success").

Log:

29 Aug 10:15:15 - [info] Node-RED Version: v0.20.7
29 Aug 10:15:15 - [info] Node.js  Version: v12.9.1
29 Aug 10:15:15 - [info] Linux 4.15.0-58-generic x64 LE
29 Aug 10:15:15 - [info] Paletten-Nodes werden geladen
29 Aug 10:15:15 - [debug] Module: node-red-node-email 1.6.2
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-email
29 Aug 10:15:15 - [debug] Module: node-red-node-feedparser 0.1.14
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
29 Aug 10:15:15 - [debug] Module: node-red-node-rbe 0.2.5
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
29 Aug 10:15:15 - [debug] Module: node-red-node-sentiment 0.1.4
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-sentiment
29 Aug 10:15:15 - [debug] Module: node-red-node-tail 0.0.2
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-tail
29 Aug 10:15:15 - [debug] Module: node-red-node-twitter 1.1.5
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
29 Aug 10:15:15 - [debug] Module: node-red-contrib-alexa-home 1.1.0
29 Aug 10:15:15 - [debug]         /usr/lib/node_modules/node-red-contrib-alexa-home
29 Aug 10:15:15 - [warn] rpi-gpio : Raspberry Pi-spezifische Nodes inaktiv
29 Aug 10:15:15 - [warn] rpi-gpio : Pi RPi.GPIO-Python-Bibliothek nicht gefunden
29 Aug 10:15:15 - [info] Einstellungsdatei: /home/seb/.node-red/settings.js
29 Aug 10:15:15 - [info] Kontextspeicher: 'default' [ module=memory]
29 Aug 10:15:15 - [info] Benutzerverzeichnis: /home/seb/.node-red
29 Aug 10:15:15 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false
29 Aug 10:15:15 - [info] Flow-Datei: /home/seb/.node-red/flows_seb-desktop.json
29 Aug 10:15:15 - [info] Server wird jetzt auf http://127.0.0.1:1880/ ausgeführt.
29 Aug 10:15:15 - [debug] loaded flow revision: abcd452a3bc1df67f0bc485bed510b72
29 Aug 10:15:15 - [debug] red/runtime/nodes/credentials.load : no user key present
29 Aug 10:15:15 - [debug] red/runtime/nodes/credentials.load : using default key
29 Aug 10:15:15 - [debug] red/runtime/nodes/credentials.load : keyType=system
29 Aug 10:15:15 - [warn] 

---------------------------------------------------------------------
Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom System generierten Schlüssel verschlüsselt.

Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren geht, werden Ihre Berechtigungsnachweise
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen und erneut eingeben.
Ihre Berechtigungsnachweise.

Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option 'credentialSecret' in
Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise erneut verschlüsseln.
Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer Änderung verwenden.
---------------------------------------------------------------------

29 Aug 10:15:15 - [info] Flows starten
29 Aug 10:15:15 - [debug] red/nodes/flows.start : starting flow : global
29 Aug 10:15:15 - [debug] red/nodes/flows.start : starting flow : 71be1ebd.5d865
29 Aug 10:15:15 - [info] [alexa-home-controller:Alexa Controller] 0 - alexa-home - Starting SSDP
29 Aug 10:15:16 - [info] [alexa-home-controller:Alexa Controller] 0 - announcing: http://*:60000/alexa-home/setup.xml
29 Aug 10:15:16 - [info] Assigning alexa-home nodes to this controller
29 Aug 10:15:16 - [info] Flows gestartet
29 Aug 10:15:17 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /alexa-home/setup.xml
29 Aug 10:15:17 - [debug] Alexa Controller/0 - Handling setup request
29 Aug 10:15:17 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:17 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:17 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:28 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:28 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:28 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:33 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:33 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:33 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:38 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:38 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:38 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:43 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:43 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:43 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:48 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:48 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:48 - [debug] Alexa Controller/0 - Handling registration request
29 Aug 10:15:53 - [info] [alexa-home-controller:Alexa Controller] 60000 -> /api
29 Aug 10:15:53 - [info] [alexa-home-controller:Alexa Controller] Request body: {"devicetype":"Echo"}
29 Aug 10:15:53 - [debug] Alexa Controller/0 - Handling registration request

Wireshark: The selected line and the following lines repeat a couple of times before discovery times out. alexa-1

mabunixda commented 5 years ago

The bad thing is that all versions are working on my deployment using docker and also in the dev environment i am using - but this is also a docker based stuff :-(

Yeah i gonna work through this with wireshark and also a local installation of nodered

devzeb commented 5 years ago

As the next api calls are dependent on a "username" (as far as I understand the code), username should not be undefined right? In handleRegistration the variable "request.params.username" is undefined, resulting in this json response:

[
    {
        "success":
        {
            "username": ""
        }
    }
]

Edit: after manually changing the username to "c6260f982b43a226b5542b967f612ce" my alexa is able to discovery the device.

So the steps to get it working are:

mabunixda commented 5 years ago

Alexa devices are quite dump and are not depending on the standard communication definition of hue devices. If they would, then this call should be on port 60000 :( To overcome your port redirection you can start node-red with ALEXA_PORT=80

devzeb commented 5 years ago

start node-red with ALEXA_PORT=80

how do I do that exactly? sorry, I'm not experienced in node-red at all...

devzeb commented 5 years ago

Just fyi: This is definitely a Echo Gen 3 related issue. People are having the same issue in other projects, e.g. https://github.com/bwssytems/ha-bridge/issues/1022

mabunixda commented 5 years ago

yeah already got this but it is hard to test without this device :( I gonna review those changes ...

mabunixda commented 5 years ago

@derSebbl Can you do add following line in alexa-home-controller.js / handleRegistration

console.log(JSON.stringify(request.body))

and post the output ?

In the meantime i am adding a fix to this routine.

devzeb commented 5 years ago

Sure thing, here you go: JSON.stringify(request.body) in handleRegistration outputs: {"devicetype":"Echo"}