@garrettwp, I noticed with a few devices that I have (ones with long names?) "turn on <device_name>" works but "turn <device_name> on" does not. My device names are currently pretty bad for voice recognition. Everything is "<roomname> lamp", "<roomname> overhead", etc. Lots of name collisions! I have not done extensive testing, but I've been doing more and more control with voice commands and it is great.
I have three devices running 2.3 (Droid 2 Global and two Evo 3ds) I'm quite happy to help with testing in any way that would be helpful (for instance, renaming my devices, or running an exhausting list of commands, etc).
I have also been doing a lot of voice control as well (not only for testing but for day to day use). It has been performing pretty well for me as well. It helps to keep the device names simple, however you can say part of the name. For example if the name of the device is Kitchen Cabinet Lights, you can say
[Turn On] Cabinet Lights or
[Turn On] Kitchen Cabinet. As long as you say part of the name it should find any devices that contain that name and present a list if more than one is found. I am still tweaking and it will get better in the future.
I am trying to add more commands. The more I use it, I come up with more ideas and add them. I have now added control of thermostats and more status commands e.g. battery level, etc. More to come. I still need to write documentation for this as well.
If you have any suggestions or something you like to see in the voice recognition, please let me know. I should have an update released tonight / tomorrow that will fix more bugs and contain additional voice commands.
- Garrett
P.S. I have stopped adding any new features and will focus on getting the bugs worked out and finishing the voice recognition. Once everything seems pretty stable (hopefully soon), I will release to the market. I plan to have widgets, camera streaming, and other features in future releases (2.1 and newer).
