blueman2

What version of ISY are you on? As I recall, you might need to be on 5.x in order to read z-wave values into variables.

I use the name "House Fan Low" for low speed. Alexa accepts: "Alexa, turn house fan on low" Which to me is very natural. Do NOT include the 'on' work in the name in the portal. Just "House Fan Low". I also have Medium and High. I also have just "House Fan" which I also set to medium.

If you use a State variable, you can simplify this: If 'Temperature / Upstairs Main' Temperature is > 0 Then Resource 'RespMainTemperature' Else - No Actions - (To add one, press 'Action') This works because State variables are only evaluated upon change. So if it changes, the IF becomes true and the THEN is executed. Well, so long as your temperature remains above 0. You could put > -255 to be safe!

I see your problem. You probably purchased a male and female Echo and left them in the same box too long. This is where Dots come from.

Sorry, memphis, I was traveling. But yes, you would create 2 network resources and trigger each one via a program so that the phrase is updated as needed.

My Dots are about 10' apart, and they still always both respond to any command. Frustrating. This is the entire reason I bought more Dots, but the feature is just not working for me. I need to have several in the Kitchen due noise from fans and appliances that make it hard for 1 Echo to reliably recognize commands. EDIT: well, if I put them about 12 feet apart, they do work as they are supposed to. Kind of add that they have this much of a distance required, but I guess it is done for some reason. Also, even 6 feet apart, they will work if there is a lot of background noise.

lets see. Buy 5, and get 20% more for free ($50 value / $250 purchase price). Or buy 6 and get 16.67% price reduction (50 savings / 300 value). I am going to demand the 20% free. I will refuse the 16.67% price reduction. I am so smart.

Working here. Another thing now offloaded from my RaspberryPi!

ESP is not working for me. Just got my new Dot and placed it next to my existing (gen 1) Dot. Both on same account. I ask time, they both answer and not in synch. Software version on Gen2 Dot is 561179520, on Gen1 Dot is 4172. What gives?

No worries. But do pass your thanks along to the people at 3PO-Labs who made all of this possible. They are doing it for free because they like what we are doing with Alexa for home automation.

Still odd. But fix your userID as I noted above (I editing my response with that catch) and see if that helps at all. Also, try shortening the <speak> command. just delete some of the words to shorten the sentence. Too long of a POST message sometimes causes problems.

This issues seems like an ISY problem. What version of ISY firmware are you running? However, I do see an issue with the page you attached. Your userID is invalid. You have too many letters. I think you repeated c43 twice maybe? because your ID is 3 letters too long. Copy/paste issue? But even this issue should not have caused the ISY to freeze and reboot! And while seeing your ID was helpful in fixing that issue, I recommend you block out at least a few of the letters in your ID when posting (remove the image above for now). Not a big issue, but someone could use your same ID (by accident or not) and overwrite your alexa responses.

I am happy to let everyone know that the creators of the RESPONDER tool that allows the Echo to respond to your requests has released their updated and much improved version. They also have changed their company name to 3PO Labs (homage to C-3PO the protocol droid for man-machine interactions). I have updated my the first post of this thread with a WIKI and instructions on how to use their new tool. I would appreciate it if someone would go through these instructions and let me know where I missed something, got something wrong, or need to add clarity. I will quickly update as I get feedback from people. Give it a try. And please thank the folks at 3PO-Labs. http://www.3po-labs.com/

And then some. Barry is not only a great code writer, he is a great person. Very giving of his time. Great to hear!!! Now, you should start experimenting with the ability of the Echo to provide responses to your questions! See the thread of 'Echo talks back'

Hooogaaaaan!

+1

The issue is that Amazon carefully controls the 'Actions' that follow the word "Alexa". The ones set aside to use with skills (which is what I use) are: Open, Ask, Tell, and maybe a couple other words. What is, Give me, etc are not allowed and controlled by Amazon. Of course, they have a different idea of how you would use 'tell'. They WANT you to use it to say "Alexa, Tell Izzy to do xxxx". And of course they also carefully control the Izzy and other skill names. But since what I am doing is considered development and only my Echo(s) can see my skills, I get to use any word I want after Tell, Ask or Open. "Tell me" just seemed easiest and most natural to use. Of course, playing around, I did of course create a response for "Alexa, Open a can of whup *** on my son". Alexa responds with "Would you like a 12 ounce can. 16 ounce can, or does he need a 55 gallon drum of whup ***?" Ah, the fun things you can do with alexa skills. EDIT: Well, color me wrong. "Give Me" is a proper 'action'. Hmmmm. Canadians always get their way. Actions include: ask begin do launch load open play resume run start talk to tell use give me can you give me I still prefer "Tell me.....". But the nice thing about this new tool DERP is creating is that you can decide for yourself how you want to talk to your Alexa. Just keep it clean.

I am continuing to tweak the ability for Alexa to provide responses to my queries. DERP Group is not quite ready to release their new UI for their tool, but is is looking VERY promising. My guess is another couple weeks or so. But one change I have made is to the intent. For all my queries, I am using the following syntax: "Alexa, Tell me xxxxx" I tried lots of different ideas, then tested them on my family and others who are new to the Echo. The initial idea of "Alexa, ask Home to tell me" was just too hard to remember. Then I realized that 'TELL' one of the Alexa invocations for skills, and since I am not bound by what Amazon approves for intents, I can use 'ME' as an intent. Alexa, tell me inside temperature Alexa, tell me outside temperature Alexa, tell me power usage Alexa, tell me fan speed Alexa, tell me pool pump status Alexa, tell me security status These really roll of the tongue alot easier than "Alexa, ask xxxx" because the 'ks' and 'sk' of Alexa and Ask create a tongue twister of sorts. Again, the Portal is easier, but I love being able to do away with 'Izzy' as a concept and just keep one woman in the conversation: Alexa. And I just like being in total control of the words I use to talk to Alexa and exactly what she responds with. I love throwing in some dry humor in her responses to give her a bit more personality.

It is sort of spread out in this thread. But just go to BWS Systems and use their ha-bridge software. It has instructions for use on a Pi. It is not geared towards the ISY, so you will need to customize the commands a bit, based on the above thread. I also use Barry Gordon's AWS config tool to make it all MUCH easier to configure. But you will need the latest 6.0.3 version which I do not think he has up on this site.

Just an update. The friendly folks at DERP Group who developed the A.S.K Responder saw how we are using their tool and are doing an upgrade so that it works even better for ISY users who want voice responses from Alexa. Update will come in the next week or so, and will allow you to better utilize the Invocation and Intent without creating so many user accounts/skills. It will make it much easier to use. They also have some longer term plans to add even more features. Pretty darn exciting to be able to customize Alexa to provide updates on just about anything that the ISY can track or store as a variable. And to be able to have her respond to whatever words you can think of for the intent.

??? I have 4 echos now, all on one account. They work fine controlling my lights and answering questions about the status of my ISY devices and variables. But then, I run my own Hue emulator and wrote my own Alexa skills. So I do not use the portal. I like having the extra control over the Echo and the ability to tailor things a bit more.

No need to cancel. In fact, there is no code or anything you need for the $10. Anyone who already owns a dot, and buys one before the release date, gets $10 store credit automatically. Nothing you need to do.

The thing I am most excited about is the software update to do a better job of selecting the echo nearest the user!! I already have 4 echos and I often get anywhere for 1-4 timers going at once because they all hear me. Annoying. BTW, they are giving $10 credit for people who already bought Gen1 dot (me). Also, they give a $50 discount on a 6 pack, $250!!! With both credits, I am getting a set of 6 for $40 each!!

This has been doable all along. You just need to use the intensity.byte variable: rest/nodes/13.72.4C.1/cmd/DON/${intensity.byte} for on URL The Fanlinc instructions say what the levels are for low, med, and High. But I think High is 100%, Med 50-99, low 49 and below.

Barry, just to let you know, I just upgraded to the latest HA_bridge v3.1.0 and your AWSconfig v6.0.3 still works great! Yes, the portal is wonderful but I love running an emulator on my own system for complete control.