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
Does it work with Echo Plus? #5
Comments
Hello, Yes, it is confirmed that package is working with Echo Dot 2 and 3 gen. I don’t have Echo Plus to test the integration and no one has confirmed that is working on such device. Do you experience any issues on Echo Plus? |
I'll test it soon! :) Is Echo Plus a 3rd generation? Maybe.. |
Great! All types of Echo devices have to be supported including 2rd gen of Echo Plus, as this package is simulating Philips Hue hub which is supported by all Echo generations. Let me know if you have any problem. |
Got it! I can test it only tomorrow! |
I can confirm that it works on echo plus 3rd gen. |
Thanks for checking this out! On your question: |
Thanks for answering, no performance degradations, only long time to install it. Is it normal to have 4-5 minutes for install? |
Hi friend, I tested it, I mean I deployed the both nodes on the flow and I have suddenly and error, unable to start on port 80. I tried to change port, same result. WHat is wrong? The Http server does not start? In console I read this. [error] Error: listen EACCES: permission denied 0.0.0.0:80 |
Ok, searching with google I found that for open low ports I need to execute EACCES with root privileges, and I can confirm it is the problem because if I choose a high port it starts correctly. UPDATE: I tried run node red from root account, bad idea, I've had an empty flow as result and try to install on it the module in console I had: |
Somebody suggested solutions: Try authbind: http://manpages.ubuntu.com/manpages/hardy/man1/authbind.1.html After installing, you can add a file with the name of the port number you want to use in the following folder: /etc/authbind/byport/ Give it 500 permissions using chmod and change the ownership to the user you want to run the program under. After that, do "authbind node ..." as that user in your project.Another approach is to make port redirection: sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 900 -j REDIRECT --to-port 3000 And run your server on >1024 port: require('http').createServer().listen(3000); ps the same could be done for https(443) port by the way.
The last one seems the cleanest.. |
Yes, port 80 is required. I’ve listed it in the doc. All new Echo devices will try to connect to port 80. Here (#1) we’ve had a discussion around this topic. There are a lot of different solutions. Here are just two of them
|
Thanks for answer, Another question, I've heard about control Alexa by the "skills", do you know this? I'm new to Alexa.. |
For option 2 you have to run the Node-Red in a docker container. Here is a how to do it: https://nodered.org/docs/platforms/docker About skills: This module doesn't use any cloud services. So, you can do the same with modules that utilize skills, if you don't mind to send data to the cloud. |
you perfect cleared me, so NAT is the solution. Please clear me how can I NAT, I mean, is it enough to do that and leave for example 8000 in the module? (with nat the server will listen to original 8000 and natted 80). |
Just edit the Amazon Echo Node to use port 8000, this will run the Hue hub on port 8000. Next step is to use iptables to forward port 80 to 8000. |
I think I soved it, I typed the following commands: |
@Barabba11 Just tried it. I confirm that your solution work as a charm. Thank you very much. |
@wongnam Can you confirm that device discovery process is working if it is initiated from Echo Dot 1st gen? Thanks in advance |
@datech I have just disconnected all Echo Dot gen 1 and 2, only 1 Echo Dot 3rd gen is up, I can confirm that it can discover your node as expected on port 8000 with NAT solution(port 80 ->8000). |
@wongnam I'm glad you like it :) It was confirmed that it is working with Echo Dot 2nd and 3rd generations, but no one has tested it with Echo 1st gen. As you have such device can test the module with it? Thanks |
Ok works, just noticed that the message exiting from node ha no topic, even if I specified one. |
@Barabba11 It works as its way, no issue at all. 1/23/2019, 3:13:08 PMnode: 7ba9259b.2cbccc |
ok I got where was the problem, I didn't connect the node Hub with the device node. Now I did and I receive the right topic.. |
mates, i've an issue.. |
Can you test this from the Alexa app? Also you can check what Alexa is sending to the Amazon Echo Hub node in the Node-Red console. All Alexa commands are logged as debug messages in the console like these:
|
@datech My Echo Dot 1st gen and also Echo Dot 2nd gen do not detect HUB/Device node. Even i do not use NAT, I just use port >1024. I don't know why. |
wongnam use NAT (why not, nothing to install, just configure how linux manage IP protocol) and see if it helps. If not, check if the http server port is reachable from the same wifi where alexa is connected, chances are you have network problem |
datech I'm not sure I'm doing right debug. Can you please test yourself how Alexa outputs after request "regulate it at 80% " and @switch on it"? In my opinion they are the same as your module outputs, but maybe, maybe there is some other data that can change and you descard from outputing in the module, please check. |
The messages you’ve sent are debug message of the nodes. There is one more way to debug Node-Red - it’s to check the Node-Red console. In Node-Red console you can see all log messages printed by the Node-Red process. When you start the Node-Red you will usually see something like this:
At the same console you can see the body of all requests coming from Alexa. For example:
Set brightness to 50%
Set color to red
Turn off the device Do you have such logs in your Node-Red console, when you change the device settings from the Alexa mobile app? |
Maybe I wrote it not cleared and you don't understand, you better than me know the object we see in node red outputed from Alexa. If there are all parameters that Alexa outputs we can't do nothing, the two packets generated by "regulate it to 80%" and "switch it on" (and previously was 80% too) are equal, and we can't distinguish them. |
@Barabba11 I don't know that i understood your comment yet, but i am using this node without issue. update: only one thing is strange that when i change the Bri:value only, the node does not turn on the light as Alexa app did. Below flow is a simulation the feedback of device that send value to Hub.
|
@Barabba11 Example 1:
After this sequence of commands the device will be in the following state: If you say at this point "turn on" the state of the device will be: So, the color and brightness are not cleared after the device is turned off. Example 2:Device state is:
I cannot control what Alexa is sending to the hub, I can override if I have to, but the described examples are the default Alexa behavior I hope this answer your question. |
Yes, thank you guys, I just needed to hear "yes I tried myself and you are right, the two ouptus are equal and there is no way to distinguist them' |
You can base on Colormode:ct , Colormode:hs to filter it. |
You say it supports 2 and 3rd generation, Echo Plus is included? Thank you a lot for your kind answer
The text was updated successfully, but these errors were encountered: