I only get off for the echo device even if i tell it to switch my device on about node-red-contrib-amazon-echo

[datech]

The issue has to be fixed in version 0.1.6

[datech]

Hello Niggl,

Can you confirm that you experience the same behavior if you use Alexa app to control the device?

[nicolaiort]

Thank you for the quick response,
sadly controlling the device through the Alexa app leads to the same behavior.
The app tells me i switched the device on and after like 1 or 2 seconds the state of the device in the Alexa app turns back to off - the message is still 100% the same.

[datech]

I don't see anything odd in you setup, except the fact that the debug message contains topic “Lampe”, which is not configured in the Amazon Echo Device Node.

This package is confirmed to work with Echo Dot 2 and 3 Gen. What is your Echo device?

[nicolaiort]

Sorry for not mentioning that, while trying to troubleshoot I tried setting the Topic of the Echo device Node to "Lampe" and some other things to extrapolate the effect on the problem. Non of these topic changes had any effect.

I'm using a Echo Dot Gen 2 with a recently updated Firmware.

[datech]

This package is using Node-Red context functionality to store states of Amazon Echo devices. Context storing is available Since Node-Red 0.19 version. Could you check your Node-Red version? Also, is there any errors in the Node-Red console?

[nicolaiort]

I'm using Node-Red v0.19.5.
Since I'm not able to have a look at the Node red console today, I'll post my console log tomorrow.
I'll also try to repeat the issue with newer node red versions.

[nicolaiort]

The console doesn't spit out any errors.
I now also tired a fresh new installation of node-red on a fresh debian installation, it still doesn't work

[datech]

When Echo sends commands to Node-Red the hub node will print such debug messages in the console:

20 Jan 22:19:44 - [debug] Request body: {"on":true}
20 Jan 22:19:49 - [debug] Request body: {"on":false}
21 Jan 20:25:21 - [debug] Request body: {"on":true}

I suppose that you have such "on":true messages in the log, which will mean that Echo is sending correct request to the hub and the issue is somewhere else.

[nicolaiort]

The debug output from the Hub object:
{"on":false,"bri":254,"hue":0,"sat":254,"ct":199,"colormode":"ct","payload":"off","deviceid":"f55884ef54c378","topic":"","_msgid":"71ffc37a.f7582c"}

[datech]

Yep, this message looks ok, but I was referring Node-Red console. The debug messages have to be printed in the Node-Red console on every request coming from the Echo device.

[nicolaiort]

The only stuff printed out on the console is this:

[debug:ECHOHUB] { on: false, bri: 254, hue: 0, sat: 254, ct: 199, colormode: 'ct', payload: 'off', deviceid: '2ba79edcf38572', topic: '', _msgid: '903ebfa1.b096a' } 23 Jan 18:18:36 - [info] [debug:ECHODEVICE] { on: false, bri: 254, hue: 0, sat: 254, ct: 199, colormode: 'ct', payload: 'off', deviceid: '2ba79edcf38572', topic: '', _msgid: '903ebfa1.b096a' }
Which just is the debug message from the Hub and device, both still say off even though it told the echo dot to turn them on.

I'm sorry for the case of me just missing something easy.

[datech]

The messages you’ve sent are debug message of 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:

$ node-red
23 Jan 20:19:04 - [info] 

Welcome to Node-RED
===================

23 Jan 20:19:04 - [info] Node-RED version: v0.19.5
23 Jan 20:19:04 - [info] Node.js  version: v8.15.0
23 Jan 20:19:04 - [info] Linux 4.15.0-29-generic x64 LE
23 Jan 20:19:04 - [info] Loading palette nodes

At the same console you can see the body of all requests coming from Alexa. For example:

23 Jan 20:22:29 - [debug] Request body: {"bri":128}
23 Jan 20:22:35 - [debug] Request body: {"hue":0,"sat":254}
23 Jan 20:22:57 - [debug] Request body: {"on":false}

[nicolaiort]

I'm aware of the console, but the only output it gave me is the one in my last comment.

Either way I'll start another run later today and check if anything slipped through.

[nicolaiort]

So i just did a brand new install of of node-red on Debian 9.0 (don't worry about the hostname - this Debian install never had iobroker on it)

It still didn't work, but here is all the data i gathered:

Screenshot of a ssh connection to the Debian box with the node-red console

Screenshot of the node-red webinterface

Video of asking my echo dot to turn the testdevice on:
https://youtu.be/fvdaKwdc7O4

Video of asking my echo dot to turn the testdevice off:
https://youtu.be/e1ts4nOTdQE

The whole flow:
https://pastebin.com/0bXZrvh7

Sorry for bothering you and thanks for your help :)

[datech]

At least Alexa is saying “Okay” all the time :)

Can you edit the /root/.node-red/settings.js to set logging to debug and try again to turn on the device, but this time from the Alexa mobile app instead of using a voice command.

Here is how I've set the logging to debug:

    logging: {
        // Only console logging is currently supported
        console: {
          ...
            level: "debug",
           ...
        }
    },

[nicolaiort]

Thx for the tip, but even using this setting and trying node-red -s /root/.node-red/settings.js and node-red -u the console outputs nothing related to alexa/echo :/

[datech]

Just for reference, how my console is looking:

Welcome to Node-RED
===================

25 Jan 20:25:10 - [info] Node-RED version: v0.19.5
25 Jan 20:25:10 - [info] Node.js  version: v11.7.0
25 Jan 20:25:10 - [info] Linux 4.15.0-29-generic x64 LE
25 Jan 20:25:10 - [info] Loading palette nodes
25 Jan 20:25:10 - [debug] Module: node-red-contrib-amazon-echo 0.1.4
25 Jan 20:25:10 - [debug]         /home/vagrant/.node-red/node_modules/node-red-contrib-amazon-echo
25 Jan 20:25:10 - [debug] Module: node-red-node-email 0.1.29
25 Jan 20:25:10 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-email
25 Jan 20:25:10 - [debug] Module: node-red-node-feedparser 0.1.14
25 Jan 20:25:10 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
25 Jan 20:25:10 - [debug] Module: node-red-node-rbe 0.2.4
25 Jan 20:25:10 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
25 Jan 20:25:10 - [debug] Module: node-red-node-twitter 1.1.4
25 Jan 20:25:10 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
25 Jan 20:25:11 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
25 Jan 20:25:11 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
25 Jan 20:25:11 - [info] Settings file  : /home/vagrant/.node-red/settings.js
25 Jan 20:25:11 - [info] Context store  : 'default' [module=memory]
25 Jan 20:25:11 - [info] User directory : /home/vagrant/.node-red
25 Jan 20:25:11 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Jan 20:25:11 - [info] Flows file     : /home/vagrant/.node-red/flows_vagrant.json
25 Jan 20:25:11 - [debug] loaded flow revision: 0ef50f34a6320182092e53a47e7c8ac5
25 Jan 20:25:11 - [debug] red/runtime/nodes/credentials.load : user provided key
25 Jan 20:25:11 - [debug] red/runtime/nodes/credentials.load : default key present. Will migrate
25 Jan 20:25:11 - [debug] red/runtime/nodes/credentials.load : keyType=user
25 Jan 20:25:11 - [info] Starting flows
25 Jan 20:25:11 - [debug] red/nodes/flows.start : starting flow : global
25 Jan 20:25:11 - [debug] red/nodes/flows.start : not starting disabled flow : 68b5755a.958bec
25 Jan 20:25:11 - [debug] red/nodes/flows.start : starting flow : 1966cd69.3766d3
25 Jan 20:25:11 - [info] Started flows
25 Jan 20:25:11 - [info] Server now running at http://127.0.0.1:1880/
25 Jan 20:25:17 - [debug] Request body: {"on":true}
25 Jan 20:25:23 - [debug] Request body: {"bri":128}
25 Jan 20:25:27 - [debug] Request body: {"on":false}

I've updated my Node.js to v11.7.0, but still cannot reproduce it.

If you send an the following HTTP PUT request to the hub it will simulate the Alexa request:

curl -d '{ "on": true, "bri": 200 }' -H "Content-Type: application/json" -X PUT http://<your-node-red-ip>:80/api/c6260f982b43a226b5542b967f612ce/lights/<your-device-id>/state

Just replace "your-node-red-ip" and "your-device-id".
The output should be similar to this:

[{"success":{"/lights/1/state/bri":133}},{"success":{"/lights/1/state/on":true}},{"success":{"/lights/1/state/hue":0}},{"success":{"/lights/1/state/sat":254}},{"success":{"/lights/1/state/ct":199}}]T

As a result it will turn on the device and set the brightness to 50%

[nicolaiort]

My output:
[{"success":{"/lights/1/state/bri":200}},{"success":{"/lights/1/state/on":true}},{"success":{"/lights/1/state/hue":0}},{"success":{"/lights/1/state/sat":254}},{"success":{"/lights/1/state/ct":199}}]

[datech]

Did this change the device node payload to "on": true?

[nicolaiort]

Actually i did 👍

[wongnam]

FYI

• I see this issue on my case now. with Echo Dot 1st Gen and 2nd Gen at port:8000. Also press the button in Alexa app to turn it on but after 5s it will return to off. in debug node i always see the result is On:false even i tell Alexa to on.
• Only my Echo Dot 3rd Gen is running normally as expect at port 80 NAT to 8000.

[nicolaiort]

Now everything works, thank u very much