Alexa Announcements Not Working

[mulu]

I used NodeRed in the past to make announcements over Alexa devices. However, I can't get this to work anymore. Basically, I set up a virtual device which has the main/parent device and then 1 Control. For the control I deleted all the on/off status. Then I use an event to set the device string to what I want to announce. Then I have another event that clears the device string after 1s. I can see this working, i.e. it sets the string and then resets it. However, NodeRed doesn't seem to pick it up, or at least I don't hear any announcements. I checked the HS log but don't see any errors.

[Kevb]

Try setting the "clear the device string" event to 5s after the "announce" event. I had the same issue if the wait time is too small.

[ksum]

What does your Ignore if blank function node do? Probably more efficient to do that some other way. A Switch node set to is not null would possibly do the same based on the name and it uses 1/4 the resources of a function node.

Also note that most of the Alexa contribs seem to need you to re-initialize Alexa and many have a simple flow to do this every hour, couple hours. I say most because there are many forks of the contrib and I have not looked at all of them. The cakebaked one was supposed to get around this but I have seen reports to the contrary.

[Kevb]

I use the "Ignore if blank" node because that is what was described here: https://forums.homeseer.com/forum/ho...E2%80%9D-guide

I don't have any programming experience, so it's easier for me to just copy what's already been done. The cakebaked contrib has worked flawlessly for me, but you do need to create a filename to save your proxy settings. I'm not home so can't give more help with that now.

[ksum]

Yes, the original post there was made based on some less than desirable information. Unfortunately too many people in the home automation world use the Function node where other standard nodes will do. Either should work, and yes, on a system with just a few flows it won't matter too much, but tests by the Node Red developers have proven that the Function node is slower and loads more resources for each instance. You can replace that with a Switch node which looks like this if you like, or leave it as is:

Explanation: Switch is just a fancy If... Else If... Else If... Else node. It can handle multiple If statements or be used for just one. I believe that as a result of the name, many overlook it as a simple If ___ Continue item, but that is part of the use. I know I looked for a long time for an If node before realizing this did it for me.

[mulu]

I think I figures this out. I had the workflow to update the cookie but it showed "ready" so I figured maybe it didn't actually execute. So I manually executed it and then ran my HS event. Now the announcement came through. So something is wrong with that workflow.

[ksum]

At the bottom of your Inject Node, set the repeat interval to whatever you prefer. Some have said 6 hours, others use 3. The sample below uses 1 hour as shown in the circled area.

[mulu]

ksum Indeed, that wasn't set. I set it to 3h. Thanks a lot.