Useful Skill for Alexa custom notifications

#1

This Alexa skill looks to be useful for sending custom notifications from node red to Alexa:

2 Likes

Alexa compatible motion sensor emulation
#2

Works like a charm. I activated the skill and then I used a simple Inject->HTTP Request->Debug. I put the entire message into the URL and boom, Alexa signaled I had a notification and when I said “Alexa read notifications” she did.

If I get some time, I may try to write a node to do this where the msg.payload would be what you want Alexa to say and you would put your access key into the node….

2 Likes

#3

Yes, I tried it using the same method. A dedicated node would be wonderful!

0 Likes

#4

Actually a simple change node works well too:

In this flow a Global variable holds the Access Code:

[{"id":"b1d912d3.a5ab6","type":"change","z":"af023adf.df3548","name":"","rules":[{"t":"set","p":"url","pt":"msg","to":"\"https://api.notifymyecho.com/v1/NotifyMe?notification=\"&payload&\"&accessCode=\"&$globalContext(\"AccessCode\")\t","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":330,"y":140,"wires":[["fcef3932.be8e38"]]}]
0 Likes

#5

@ghayne Brilliant!! no need for a dedicated node!

0 Likes

#6

However...this exposes your access code to anyone if you export tthe flow and send it to them...A dedicated node might still be best, what do you think?

0 Likes

#7

Is my Access Code in the flow I shared?

0 Likes

#8

No, I was just thinking about the possibility of forgetting (not that that is someting I ever do...umm at least I don't remember doing it) to remove the change node that stores it.

1 Like

#9

In that case yes, a dedicated node would be better for sharing flows :slight_smile:

0 Likes

#10

I’ve not diug into it but this node may be useful https://flows.nodered.org/node/node-red-contrib-credentials

1 Like

#11

Looks interesting @dceejay , but on reflection credentials stored in a Global variable are also safe from being exported, or am I wrong?

0 Likes

#12

Yes as long as you don’t export the node that sets it in the first place

1 Like

#13

Well usingnode-red-contrib-credentials the access Code is not exported when you export that node, but it is visible in the editor (original site) when you open the node or if you use the Context Data tab in the sidebar.

It is not like a password where once you enter it, it is not displayed anymore.

How do people feel about the Access Code being visable to anyone who uses the editor and looks at the nodes or Contex Data?

0 Likes

#14

Not good. Apologies for diverting the thread.

0 Likes

#15

Ok I give up. I'm not a coder - I'm a debugger (did tech support for many many years).

I struggled thru the online classes quite awhile ago and have forgotten everything since and after three hours of trying to remember things I'm done. I've sent a PM to one of the other members of the forum asking if they could whip it up.

0 Likes

#16

Hey guys (@ghayne, @zenofmud, @dceejay),

I have just published version 1.0.0 of node-red-contrib-alexa-notifyme. This node is a great mix of the following ingredients, which you can only find on a great open-source community like Node-RED:

  • A great idea from Garry
  • A basic node skeleton from 'one of the other members of the forum '
  • A pull-request and lots of test efforts from Paul

That is all you need folks ...
And of course an Amazon device, otherwise you are screwed (just like me) :wink:

5 Likes