Skip to content
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

making state visible to echo device #138

Closed
aseedorf opened this issue Jul 23, 2020 · 10 comments
Closed

making state visible to echo device #138

aseedorf opened this issue Jul 23, 2020 · 10 comments

Comments

@aseedorf
Copy link

I can switch a device by node-red with this node and also with alexa (echo dot, mobile...).
But the state-change if done with the node is not visible with e.b. my mobile.
the mobile thinks, the "old" state of the device is the actual state.
the amazon echo hub has the ability to use a state as input, but how do i get it to the correct device?
so, how do i have to build up the msg.payload to get the state to the device via amazon alexa hub?

@datech
Copy link
Owner

datech commented Sep 11, 2020

Check the following wiki: https://github.com/datech/node-red-contrib-amazon-echo/wiki/Integration-with-Sonoff-Tasmota

Also you may want to check the Node help of Alexa Echo Hub node as reference to the supported attributes.
Don't forget the change the Process input setting as by default the hub will ignore the input

@fmuntean
Copy link

fmuntean commented Oct 3, 2020

I have the same issue:
I am passing the msg.payload as described but the status is not changed on Alexa App.
Is there something I am missing?
I am passing the deviceid, on, and bri variables inside the payload.
I also set the Process input to Process

@aqWCfFgvp81SqO
Copy link

Same here. It was working (last I checked was a few months ago), but now it is not. Still troubleshooting through it. Seems as though all input is ignored.

@I3imbel
Copy link

I3imbel commented Nov 22, 2020

I had the same issue yesterday. The problem was, that I was not able to enable the process input.
So I exported the Amazon Echo Hub knot, edited the processinput from 0 to 1 in a text editor and imported it back.
After a Node Red restart it worked just fine.

@aqWCfFgvp81SqO
Copy link

I had the same issue yesterday. The problem was, that I was not able to enable the process input.
So I exported the Amazon Echo Hub knot, edited the processinput from 0 to 1 in a text editor and imported it back.
After a Node Red restart it worked just fine.

Amazon Echo Hub knot ??

Did you intend to type node?

@I3imbel
Copy link

I3imbel commented Nov 23, 2020

I copied the knot in the text editor, changed the number behind the process input and imported it back to the flow:

image

@pwcutajar
Copy link

HI

A bit new to this, i have a flow that turns a tasmota device on and off, but cant work out how to tell alexa its on or off. the above has been done can anybody show me / discuss what im doing wrong? its a sonoof mini with an external switch hence i need to feed the power state back.

cheers

@fmuntean
Copy link

when I export the node as JSON my node has the processingInput:1 but still not working.

@pwcutajar
Copy link

ip put this in a function

var nodeid="f49dfa34.2e1fb8";

if (msg.payload == "ON"){
msg.payload = {
on: true,
nodeid: nodeid
}

} else if(msg.payload == "OFF"){
msg.payload = {
on: false,
nodeid: nodeid
}
}

return msg;

then put it between the MQTT listen and the Alexa hub. You MUST edit the node id (top line) to match that of the alexa device node.

I have noticed that this works perfect on the alexa andriod app but my echo show 5 doesnt change the lights status unless to click away from the the device view and re select it. it doesnt seem to refresh the graphic.

@datech
Copy link
Owner

datech commented Apr 30, 2024

For more information on why it is not supported, please see #196.

@datech datech closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants