4 ms·

>at the moment I feel like Alexa still has a sizable lead. Do you really? I have 4 Echo & Echo Dots too and I love them, but the level of smart home integratio

>at the moment I feel like Alexa still has a sizable lead. Do you really? I have 4 Echo & Echo Dots too and I love them, but the level of smart home integration is incredibly basic... "turn on the X (light)", "set the X (light) to 50%", "set the heat to 20" and "trigger find my phone". (edit: this post sounds pretty negative, it's mostly frustration because the speech recognition is actually really good, so when it fails it's really noticeable & the shallowness of comprehension of what I'm actually saying to it is so shocking when the speech recognition tech is that good) It will fairly often mishear light names (like my bedroom light, it confuses my name with "Theatre"), the integration will fail to contact a light (and instead of retrying the echo just says "I couldn't contact light X". It doesn't understand the room it's in (so I'm constantly having to name lights, rather than just tell it to turn on the light, or dim it). I feel like the level of integration needed from people like Hue and Nest is so simple that even the most basic integration into a competitor (with just as good / better mic+voice tech) could blow Alexa away overnight... it actually feels like something you could build in a few hours with access to the Alexa processing repo. ...which really kills me, because as you say Alexa is better than anything out there, but it feels like all they're doing is adding funny responses to pre-canned phrases rather than trying to seriously improve their smart home proposition or trying to tackle the context/discoverability problem

supergeek133 9y ago
> It will fairly often mishear light names (like my bedroom light, it confuses my name with "Theatre"), the integration will fail to contact a light (and instead of retrying the echo just says "I couldn't contact light X". It doesn't understand the room it's in (so I'm constantly having to name lights, rather than just tell it to turn on the light, or dim it). We tell our customers to put their alexa devices into groups in the alexa app. It tends to help your situation quite a bit. For instance for our Lyric thermostats the default name assigned is "Lyric". So you can imagine the things that happen when telling your Alexa to "Make Lyric Warmer". Haha. That being said, the challenge for them is "Making a light a light, and making a thermostat a thermostat" and knowing every time when someone says "turn on X" they're talking about that thing. I've noticed my Google Home does a better job at being 'fuzzy' in that regard.
- garblegarble 9y ago
  >We tell our customers to put their alexa devices into groups in the alexa app. It tends to help your situation quite a bit. For instance for our Lyric thermostats the default name assigned is "Lyric". So you can imagine the things that happen when telling your Alexa to "Make Lyric Warmer". Haha. I'm not sure I understand - are you saying there's a way to put an Echo into a group so it understands where it is in some way? I don't see that option in the app anywhere, but maybe I'm just missing it! If you mean to put the devices into groups so you can control multiple devices at once or come up with names that the speech recognition doesn't misunderstand, I do that - but at a certain point I gave up because the names would have no connection to the actual lights (my bedroom light is my name, which is a pretty common name - but the Echo mishears it pretty regularly). I can't help but think that for my case when Alexa knows I'm talking about a device & no device matches the understood text it should look at the other possible interpretations of the voice data to see if any of the likely ones. The majority of my problems come from the lack of basic contextual understanding of where the Echo device exists in the house, which is a much more solvable problem than trying to consider multiple alternative interpretations of a device name!
  - PKop 9y ago
    I'd be willing to bet, the speech recognition is tuned to recognize common vocabulary over proper names. So it is purposely choosing "theatre" instead of "Peter?". I've name my bedroom light "bedroom". So.. turn on "bedroom". Or turn on "table", turn on "window". It will probably recognize something like that more consistently than your name.
    - garblegarble 9y ago
      >I'd be willing to bet, the speech recognition is tuned to recognize common vocabulary over proper names. So it is purposely choosing "theatre" instead of "Peter?". Yeah, I think that's the case: it will usually get "Peter" but maybe 3 times a week it hears "Theatre". The problem is we have multiple bedrooms - so we'd need to come up with unique but common and unambiguous names that also feel natural to each person (which is the hard problem - we have 13 hue lights, 6 smart switches, a nest & a few software defined switches that do things like send commands to the TV to switch to specific apps)... or just add a new device group for each common mispronunciation and call it a day. The reason I'm so insistent about Alexa understanding more about context is that within a room there are obvious, common vocabulary short names for devices, but coming up with a natural global naming structure within a house is less obvious (we experimented with calling the bedrooms front/middle/back but that phrasing isn't natural) Basic room contextual information would also make for a really natural configuration UI within the app: you create Rooms, you add your Smart Home Devices (optionally assigning each a name within the room) and your Echo to a room. When matching against a "(Turn|Switch) (on|off) :device" expression, it can first match against room-specific names and then fall back on global names.

supergeek133 9y ago

> It will fairly often mishear light names (like my bedroom light, it confuses my name with "Theatre"), the integration will fail to contact a light (and instead of retrying the echo just says "I couldn't contact light X". It doesn't understand the room it's in (so I'm constantly having to name lights, rather than just tell it to turn on the light, or dim it). We tell our customers to put their alexa devices into groups in the alexa app. It tends to help your situation quite a bit. For instance for our Lyric thermostats the default name assigned is "Lyric". So you can imagine the things that happen when telling your Alexa to "Make Lyric Warmer". Haha. That being said, the challenge for them is "Making a light a light, and making a thermostat a thermostat" and knowing every time when someone says "turn on X" they're talking about that thing. I've noticed my Google Home does a better job at being 'fuzzy' in that regard.

garblegarble 9y ago
>We tell our customers to put their alexa devices into groups in the alexa app. It tends to help your situation quite a bit. For instance for our Lyric thermostats the default name assigned is "Lyric". So you can imagine the things that happen when telling your Alexa to "Make Lyric Warmer". Haha. I'm not sure I understand - are you saying there's a way to put an Echo into a group so it understands where it is in some way? I don't see that option in the app anywhere, but maybe I'm just missing it! If you mean to put the devices into groups so you can control multiple devices at once or come up with names that the speech recognition doesn't misunderstand, I do that - but at a certain point I gave up because the names would have no connection to the actual lights (my bedroom light is my name, which is a pretty common name - but the Echo mishears it pretty regularly). I can't help but think that for my case when Alexa knows I'm talking about a device & no device matches the understood text it should look at the other possible interpretations of the voice data to see if any of the likely ones. The majority of my problems come from the lack of basic contextual understanding of where the Echo device exists in the house, which is a much more solvable problem than trying to consider multiple alternative interpretations of a device name!
- PKop 9y ago
  I'd be willing to bet, the speech recognition is tuned to recognize common vocabulary over proper names. So it is purposely choosing "theatre" instead of "Peter?". I've name my bedroom light "bedroom". So.. turn on "bedroom". Or turn on "table", turn on "window". It will probably recognize something like that more consistently than your name.
  - garblegarble 9y ago
    >I'd be willing to bet, the speech recognition is tuned to recognize common vocabulary over proper names. So it is purposely choosing "theatre" instead of "Peter?". Yeah, I think that's the case: it will usually get "Peter" but maybe 3 times a week it hears "Theatre". The problem is we have multiple bedrooms - so we'd need to come up with unique but common and unambiguous names that also feel natural to each person (which is the hard problem - we have 13 hue lights, 6 smart switches, a nest & a few software defined switches that do things like send commands to the TV to switch to specific apps)... or just add a new device group for each common mispronunciation and call it a day. The reason I'm so insistent about Alexa understanding more about context is that within a room there are obvious, common vocabulary short names for devices, but coming up with a natural global naming structure within a house is less obvious (we experimented with calling the bedrooms front/middle/back but that phrasing isn't natural) Basic room contextual information would also make for a really natural configuration UI within the app: you create Rooms, you add your Smart Home Devices (optionally assigning each a name within the room) and your Echo to a room. When matching against a "(Turn|Switch) (on|off) :device" expression, it can first match against room-specific names and then fall back on global names.