Quote from: Pringles on July 03, 2016, 11:07:00 PM
Yes I was using the command editor...(Looking for hidden cams in my house...)..Voice command works! Thanks for the assistance!

You mean you didn't read the EULA!? Cancel the simulation! Why isn't it learning?

Quote from: PegLegTV on May 13, 2016, 05:45:46 PM
the second device (or Eventghost with AutoRemote plugin) is needed to receive the AutoRemote message from your phone when you are outside your local network, as there is no AutoRemote plugin for Voxcommando

ahhh gotcha. Yeah, I just go with Eventghost and the AutoRemote plugin. Wasn't thinking about how to do it without that.

Sorry I just kind of scanned over this, but I have VC setup to determine if the command came from my phone remotely or was issued locally at the computer. If it was sent via my phone, VC will send an autoremote message to my phone, which will be passed to tasker and my phone can actually speak responses that would have been local. No need for a local device. Straight from VC to the phone. Is there something I'm missing here that requires that second device?

I'm trying to follow along with what you all are doing here. Is the IR blaster a wireless one that receives its commands from VC? Maybe I'm just confused.

That's what I figured. Awesome news though! James is a tireless slave to our petty wishes 

Hey James, is the issue with the ability to just connect or is it because everything you were doing to pull stuff from the calendar was changed with the API? I know over on the vera forums they adjusted some steps to get the connection back and I wasn't sure if you had seen that. They basically have you set up a service account and then share your calendar with the service account. Once that's done, the plugin is able to pull calendar events again.

http://forum.micasaverde.com/index.php/topic,26692.0.html

Yeah, I'll give the regular version a shot and see how it goes. Do I need to still use the kinect speech recognition or do I switch to the regular one and not worry about the kinect beam forming and whatnot?

Yeah nime5ter, I think I can get away with using increments like that and just catch special cases like 21/22 jump street.

James, I'm using the latest VC 2.1.2.9 and the MS speech recognition for kinect-us

  They only realize they've made a mistake when they skip version numbers. I patiently await the jump from 11 to 13 (13 being bad luck we might get straight to 14 if we're lucky).

So am I correct in the understanding I need to make a payload tying each word with each number i.e one - 1 to the highest number I'll likely need? Dear god, 2001 A Space Odyssey will be the death of me. HAL!

Ok, the freeze was not actually a freeze at all, just a bit of a hang. Also, not caused by VC, but rather when vera decides it wants to act up and take too long to respond to a status check of a device. I'm guessing this is more of a UI7 issue still as those on UI5 don't seem to run into this very much, but it seems to happen after messing with stuff like PLEG a bit and can be resolved by a precautionary reboot of the vera after several changes are made.

On another note, I read where you said kinect can't interpret numbers correctly and needs a payload iirc. Is there a quick way to do this or will I literally have to go through each number connecting one-1 and so on?

Awesome on the sound setup. I'm gonna mess with that today. I'll test and see what caused the VC freeze and if I can duplicate it.

She got preoccupied with something and I seized my opportunity  . Here's the log with AEC on and you can see after the movie starts it just starts firing off the same error over and over.

Ok, give me a little time to create that log for you. The stink eye has returned and chances of sleeping on the couch are rising lol. I'm with you on the pass-through, but I've heard a few disagree. I think VC even freezes if I ask for it to do a few things that require TTS while xbmc is running. Anyway, I'll get you the log in a bit. Btw, how do you get the sound to the TV from your setup?

lol duh me...just use the load event to close it. Thanks!

Well, I can tell you it has something to do with the sound output of XBMC on my HTPC and the Kinect AEC setting. If I change the sound output from WASAPI HDMI to DirectSound HDMI, I am able to use XBMC normally until I play any music or video. Doing that brings back the Wave.Reco.Complete event and hangs Vox. Turning off AEC allows everything to work normally with kinect.

So, this is probably something unique to my setup maybe. I go from HTPC to receiver using HDMI and I have passthrough enabled, but not sure I actually need that as my HTPC can handle DTS-HD and whatnot on its own. No matter which output I use, Vox always throws an error on the TTS.SpeakSync that is set to fire when you start playing a movie and it doesn't actually say anything. Otherwise, TTS works normally.

Not sure if it's worth your time to look at a log as this seems specific to something in my setup, but I can make it throw the repeating Wave.Reco.Complete and get you the log if you'd like.