Tim McDermott

The delivery date for my Dot seems to be holding fast at 3/31, to ship tomorrow. we'll see.

I agree that Amazon ought to publish some sort of release notes detailing the contents of updates, especially given we appear not to be given a choice as to whether they are installed. It appears to me that Amazon is torn between keeping the Echo family of devices on the level of "appliances" with little need for user interaction to maintain and the more sophisticated device they've ended up being.

By "reboot" I mean to say power-cycled.

A simple reboot of IZZY took care of this for me. Given the number of us effected I feel pretty sure we all didn't suffer a simultaneous power outage;-)

Just an observation, but to an outsider, we would likely appear to be some pretty wacky folks. Who other than true geeks would be troubleshooting their smarthomes at 3 (or 4) in the morning. I'm not sure exactly why time I began experiencing the problem, but I believe it was around then for me as well.

Perhaps this is accounting for my problems with Connected Home: Although I've changed nothing with my configuration, as of last evening when I issue a request to turn on/off a previously discovered device I get a new error response "Sorry the device XXXX is not responding. Please check its network connection and power supply." Interestingly, the IZZY skill works fine with the same device. Apparently Amazon has made some change. I'll try rebooting IZZY and report my results.

Thanks, Jimbo.

I guess I didn't express myself clearly. I do not use sub-accounts. The names of my devices are specific enough that I don't need them. Let's hope that Amazon addresses this issue in their upcoming v2 of Connected Home.

I figured there was a down-side to the sub-account route. Fortunately, my naming conventions obviate them.

I, too have noticed this non-linearity. Although it shouldn't be a big deal, it is kind of annoying.

Madcodger, although I haven't followed it closely and I may be mistaken, I thought that setting up sub-accounts for individual Echoes was a way to address this need. I haven't had the need for this and therefore haven't set up sub-accounts, but I don't know what other utility they serve.

I have what seems to be a similar problem. I had two groups in Connected home "Guest Day" and "All Day." Until I removed the word "Day" from "Guest Day" I would receive the "I've found several devices matching that name" error upon issuing a command to turn on or off.

I, too would find this enhancement useful. I have a couple of LED fixtures that would benefit from coarser granularity to dimming commands.

Although it is easy to overlook, one feature the Dot offers that the Echo does not is the 3.5mm (line?) output. I plan on connecting a Dot to my audio distribution system via this feature for Pandora, et al.

Stu, Yes to both. I guess they've forgotten I'm a Prime member who was one of the first to order an Echo and have already successfully ordered a Dot.

Interesting that I just got the ol' 404 for the "More Info." URL in Amazon's announcement E-Mail for the Dot on my home computer, and searches on their Website for "Amazon Dot' return no applicable results. Also, if I go to Amazon's page for the Tap device, the Dot is shown at the top of the page as another Alexa-enabled device. That link yields a 404 as well. Works fine on my phone, however. Are they trying to limit access, or am I missing something here?

Although I already have sufficient coverage with my existing two Echos, I couldn't resist ordering a Dot speculatively given the price premium Echo remotes commanded when they went out of stock. The ease in ordering was downright scary, I might add.

FYI, I've discovered that the word "percent" is indeed optional, unless the context is a group created in the Echo App.; then it seems to be necessary.

Kevin, You might want to look in the Echo App. to make sure thee aren't duplicate items. There was a recent glitch where items ended up being duplicated. The happened to me and resulted in the same type error responses form Alexa. Simply deleting all devices and rediscovering will resolve.

Stu, I have found it to be the case that spoken names must be changed thru the portal, but it begs the question why, In the Administrative Console, there is a field for spoken name as a property of devices and instructions for populating it? I learned by experience that populating this field doesn't appear to accomplish anything. Stu, I have found it to be the case that spoken names must be changed thru the portal, but it begs the question why, In the Administrative Console, there is a field for spoken name as a property of devices and instructions for populating it? I learned by experience that populating this field doesn't appear to accomplish anything.

Coincidently, I was corresponding with Michel regarding this very issue. I think I ended up believing the settings eventually "took" after some time had elapsed or some action had happened. Sent from my D5803 using Tapatalk

I do not frequently post to this forum, but your post and the subsequent replies have crystallized some thoughts. I have been a home automation hobbyist for many years. I think I even still have an ultrasonic X-10 controller and remote in my box of outgrown hardware. Over the years I have followed the Insteon branch of evolution, if for no other reason than it is one of the few protocols that made an effort at backward compatibility with X10. I believe Insteon to be the best DIY home automation protocol, but an underdog nonetheless in a market dominated by a few RF-only protocols like Z-Wave and the like. I have seen seemingly countless "hubs," many with major backers, come and go. UDI has stuck it out and is one of the few vendors in the DIY home automation space to support Insteon, and by extension X10. I have been a customer of UDI since their ISY99i days. From a value proposition perspective, I find UDI unparalleled in the industry. I have found their products to be rock solid and a good long-term investment. Additionally, my experience has shown the support staff to be knowledgeable, helpful and enthusiastic. UDI is one of the few, if not only vendors that provides, with no monthly charge, remote access without the necessity for port forwarding. Their system of modules provides a way of funding the considerable development costs for extensions to their product while keeping down user costs via the a la carte pricing. Yes, I am a fan of UDI and I believe, if you give them a chance, you will be too Tim McDermott

Sorry, I couldn't resist since Huddadudda is a gluten for punishment.

It may have something to do with celiac disease.