Friday, June 28, 2019

Alexa vs Google revisited.

As so many of these this started as a reply to a question on a Facebook group. In this case what is up the Google Assistant and Homeseer? After a rather lengthy response I thought I should flesh it out even more an post it here. I'm just comparing my experience living with them nt side by side features. In my opinion both Amazon and Google are trying to push hard into siloed home automation which is just wrong. Interoperability is the future and local control is a must. Expect to see local (cloud independent) voice assistants REAL soon.

I find I'm using Google Home less and less. Mainly I use Home when Alexa is one of her moods (had another badly weighted update pushed) but things seem to have peaked with Google Home.
For an example it used to be "tell Harmony to turn on TiVo."
Then is was just "turn on TiVo"
But then "Turn on TiVo" got you "Do you want to use Harmony for that?" "Yes". In diff voice "Turning on TiVo".
Then "Turn on TiVo" got you "Do you want to use Harmony for that?" "Yes." "I don't recognize your voice."
Now back to "Tell Harmony to turn on TiVo." and half the time it says it does not recognize my voice. Which is even more irksome considering how often it responds to someone on the TV or a podcast just saying Google without even the hey. Not to mention all the times I'm not sure what triggered it.

Sorry but having to remember which thing this week to ask to turn something on or off on top of the name for the thing I had to give it so it did not sounds like something else, is just is not going to get you market share. Especially if it keeps telling me it will not do stuff cause it does not recognize my voice. Granted maybe if I spent more time tweaking it I could improve it a bit but that kind of misses the point of it and I've not had to mess with Alexa other than adding devices and alias TV to TiVo after one especially bad update. Though I have to admit recently I added my "Good morning" "routine" so instead of just telling Homeseer to put the house in day mode it also tells me some fun fact and the weather.

I should note too Google is more likely to false trigger and to just not respond than Alexa if it does not know what to do. So it might be having trouble listening when you think it is down. Though Alexa is getting more like Home in that respect. I keep the notification sounds on so I know when they think they heard something but ignored it. Which is why I just do not get people that complain about Alexa saying OK. But then I work in IT so I kind of expect a certain amount of errors. Like saying "thank you" to end a follow on sequence it just makes sense from a programmer's mindset.

Anyway contrast the above with Alexa will generally get a voice command at least by the third try if I have not triggered it some other way before that. Some responses just make you go huh? Like the other yesterday when I said "Alexa , turn on video", a command to switch my main video stream from the triggered security cams back to what I was watching and unpause. Her response, "I can not find a device named lamp." Then too I started putting Echo buttons about as backups / quicker response for things like sending OK / Select to the device currently playing video or signalling the house to go into away mode. They light up green instead of saying OK so you know the command got through. Used to have an Echo button for TiVo skip too before they made that automatic. Planning on getting some more Prime day. Note you can only pair 4 to an Alexa and they are only reliable to around 20 feet though a wall. At 2 for $14 (on sale price) hard to beat for when you just need an easy to hit button. Like advancing to the next show while washing dishes with the volume up. Both seem able to pick your voice out of impressive levels of room noise but you can only expect so much.

Note too IFTTT has been having a ton of issues with Homeseer, among others, lately. So I wonder sometimes which end it is truly on. Or if maybe something in the middle is the iffy bit. Which why you always have back methods for every trigger no matter the interface. Even the local ones.

Thursday, June 13, 2019

Answer to what can I do with X?

Another post I'm seeing a lot lately, especially with Wyze adding sensors and bulbs to their line up, is what can I do with X? This of course is backward thinking, trying to find a problem for a solution. You don't hear about a great plastic surgeon and then start asking people what you ought to get fixed. You go looking for a plastic surgeon when you think surgery is the fix for a problem you have. In the same way you dive into home automation to make some aspect of your life easier that is troubling you. Odds are you are not going to be happy with the outcome of finding a problem for your solution. But you a good solution to a problem is always a joy.

So the first thing you want to do is come up with a list of things you would like to fix / make easier in your life. Don't worry about if there is something out there to do it or how hard you think it might be. That comes later. Also go overboard here. You will probably find automation is out there is more capable than you thought. For example you might be thinking you would like to be able to turn lights on and off with your voice but wouldn't really like those lights to turn of when you enter and off when you leave all own their own and only use voice control as a backup? The cost difference between remote / voice control and automation is not that much when you are talking more than a couple things.

Prioritize that list.

Next do some research to find what options you have to automate each of those options. Be sure to note costs and needed skills for each option. (Some options might require coding or even hardware modification though most probably will not.) Also lean toward local control, works without talking to a cloud service, where possible.

Now see which hubs and devices (that work together) solved the most problems for YOU in the easiest way. There will probably be compromises to be made at this point. Note you want to lean toward devices that work with the most hubs so you are less likely to need to replace them later when you upgrade. And yes you will need to upgrade or abandon your setup at some point. That is just the state of the world. See Is the cloud over? for just some of the examples of services and devices that have gone away recently. Also drives home why you want to avoid cloud services for your logic whenever possible since there have been many more outages than shutdowns.

Lastly make a plan how start and grow. Odds are you will need a logic hub (as in SmartThings, Wink, Vera, Hubitat or Homeseer not gateway hubs like Hue. Lightify or Google Home) to start even if you plan to start with just remote / voice control unless you are OK with starting over later. Depending on the logic hub you start with this might be a significant outlay in money and or time. So go for the highest priority problem on your list you think you can tackle. Note however you might want to start with an easier one if that top one requires you to learn new skills or depends on equipment needed for other solutions as well. You want to avoid having to recode, repair or replace if possible. For example if controlling lights if top priority you might want to start with a Hue gateway and bulbs and a basic voice assistant. Then you could add all the Hue devices to a logic hub without having to repair all the devices directly as you would have had to do if you bought one of the voice assistants with a built in gateway. If you had gone with "works with" bulbs or switches you would probably need to replace them when you upgrade to logic hub.