ahwman

I upgraded my ISY firmware last night using the portal to v4.4.6 and everything seemed to go fine. Then this morning, I noticed that the heat came on an hour late as well as other timed events. I then checked my admin console and sure enough the time is one hour behind. I've tried rebooting, resyncing with the time server and even resetting my location, however it remains an hour behime... Any ideas how to correct this? Chuck

Michel, I'm happy to hear things have gotten better for you. Unfortunately it's going the other direction for me as I woke up to yet more device names that just stopped working as of last night. If Amazon continues to strip available device names, the Echo's will become useless to me and perhaps others trying to control more than just lights and thermostats. Very disappointing as I just don't understand the benefit by taking away functionality... Chuck

I've noticed a new issue that is troublesome. Sometimes commands are being repeated twice. Example: "Alexa, turn on advance" which I use to skip on my TiVo is now sometimes executing twice. This behavior is occurring intermittently with all of my commands now. I surely hope these issues are temporary... Chuck

Not a big deal, but just wondering why the ISY admin console must be reinstalled after every Java update? Thanks, Chuck

Thanks for the confirmation Mochel. I guess all we can do is let Amazon do their upgrades and see where the dust settles.. Hoping for the best, Chuck

Recently I've noticed that when speaking on/off commands, they will get executed, however the Echo will continue to show the blue light ring as though it's still processing and a long delay before I hear "Ok".

That's very encouraging Michel. Thanks for keeping us in the loop my friend. Chuck

I couldn't agree more. I had to redo many of my command words as well as re-learn them. I certainly hope Amazon will be receptive to customer feedback regarding this issue. Time will tell... Thankfully we have an amazing support team here at UDI that has our back. Chuck

That is very odd. I can't imagine that this is by design. Crossing my fingers Amazon is expedient in getting this resolved...

I was able to get my tv channels working by appending channel to the name without a space. Example: Turn on HGTVChannel" works fine for me...

Thanks again my friend! Chuck

Please add the following to the list: • Forward • Reverse (now plays song called reverse) • Guide Thanks so much Michel. You guys do such a great job!! You certainly get an A+ in my book for superb support of your products and services... Chuck

I've noticed this very same thing. I'm really hoping that Amazon is working behind the scenes to correct this. I spoke with a customer service agent this afternoon who happened to be very nice, however didn't seem to have the slightest grasp as to what I was talking about even after a great deal of explanation. That said, I spent several hours this evening crafting new device names which Amazon apparently deems as acceptable. Sadly however, some are out of context due to these crazy limitations. My favorite new hickup is issuing a command that used to work and now instead plays a song from Amazon Prime . Crossing my fingers these issues get ironed out as I've grown to love my Echo's... Chuck

Michel, This document is read only. I requested permission to edit it and once I receive permission I will add to this list... Chuck

Michel, That would be very helpful as I'm eager to hear Amazon's response to this frustrating situation. I've never used Google docs so I could either attach the names here or use guidance as to how you would like them submitted. On a side note, here are two questions I would like to have answered: Asking the Echo to "Turn on phone" fails with a short tone, however using the phrase "Dim phone" is understood. Why would the phrase "Turn on" fail, yet "Dim" work for the same word? Also, what is the purpose of the tone after issuing a non working command? Thanks Michel, Chuck

Michel, Do you think these issues will get ironed out and that we will regain the use of the device names we have been using prior to this transition? Or, does it appear that Amazon for some crazy reason has eliminated the use of various device names going forward? By the way, I'm also noticing that my Echo's are not recognizing several device names as accurately as they used to... Thanks so much for you hard work! Chuck

I've noticed this behavior with several keywords. Amazon has to fix this ASAP... I've sent feedback to Amazon, however has anyone called them and spoke with a tech about this?

I'm in the exact same boat and spent hours setting up all of my commands on IFTTT using the Maket channel and the latency is plain terrible. I sure hope Amazon has a fix for this and doesn't leave us in this predicament...

Thanks Michel, I will be interested to find out why Amazon would remove or limit our device names. It has really caused me big issues, since I use my Echo's to control much more than just lighting. Everything has been working perfectly for months until just recently... Chuck

Tried Tried this many times, problem still exists...

I sure hope so, as my set up is a mess right now with so many commands not being recognized. Also, I noticed that some commands will work for "On" yet will fail when invoking the "Off" command. Crossing my fingers this gets fixed soon if at all... Chuck

I'm just curious how Amazon is marketing this as an enhancement??

Guys, there's no question that Amazon is yet again making changes in the background as I also noticed today that the verbiage has changed when asking Alexa how much time is left on a timer. I'm concerned as to why all of a sudden so many words are no longer recognized in regards to the connected home functionality. Also, what the heck does the tone mean after invoking a failed request? I hope others will voice their concern to Amazon so they take this seriously. It's causing me a huge problem.. Chuck

It's not a latency issue I'm referring to but rather the fact that Amazon has altered the list of connected home command names which are now recognized. If you're not using any exotic command names like I am, you probably won't notice it. However if you're doing more than simple lighting commands, such as TV, DVR, etc which require more exotic command names, you will notice what I'm saying... Now I must come up with many new command names and HOPE Amazon doesn't mess with them yet again... Chuck

Well, it looks like Amazon is at it again - making major changes behind the scenes with zero warning to users. All of a sudden as of this evening, many of my connected home voice commands are no longer understood. These same commands have been working flawlessly for months... Example: I have a command called "Guide" which populates my TiVo guide, which no longer works. Instead I hear a quick tone on my Echo. I have another command called "Reverse" which would trigger the replay command on my TiVo and now Echo tries to play the song called "Reverse" from Amazon Prime. It's so very frustrating when you have everything working as you like and then Amazon just decides to make major changes to how things work and you're screwed... Anyone else seeing this?