Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mht

Pages: [1]
1
Command Builder Reference / Re: Updated payload xml doesn't work
« on: May 15, 2015, 07:23:30 AM »
Thanks for your effort to assist me!

After a server restart and a rebuild of the vera payload xml I got it to work. Some of my problems can be explaind by the fact that I had renamed and done a lot of other changes on my vera.

2
Command Builder Reference / Re: Updated payload xml doesn't work
« on: May 14, 2015, 07:24:39 PM »
I can't get VC to recognize my commands when using the name on the newly added devices. The names for those devices is present in the payload xml file used in the command.

When running the command "Show active commands" I don't get all the possible options that are present in the payload xml. Is the command "Show active commands" supposed to show all entries in the corresponding payload xml? If so I don't think my problem has to do with voice recognition since all the names in the payload xml aren't showing in the active commands list produced.

I have deleted all the vera xml files and the had VC create them again from scratch. That hasn't helped.

I will try a few other things tomorrow including reinstalling VC.



3
Command Builder Reference / Updated payload xml doesn't work
« on: May 14, 2015, 05:09:26 PM »
I have some commands with payload xml to turn on/off devices through my Vera system. After installing new devices I have refreshed the payload xml. I have looked att the payload xml file and verified that it now contains the new devices.  When I try to use the commands refering to that payload xml I cant get it to work. I have also verified that my command is refering to the right xml file. I have purge cache and done a full restart with no effect.

When using the pre installed help command to show avaible commands, the new devices is also missing as avaible payloads.

What am I doing wrong?

4
General Discussion / Re: Timestamp to readable string
« on: April 30, 2015, 07:27:16 AM »
Tank you!

I follow your example. It didnt work at first. I found out that I had to add time library first.

Code: [Select]
<?xml version="1.0" encoding="utf-16"?>
<!--VoxCommando 2.1.4.6-->
<command id="667" name="convert time stamp" enabled="true" alwaysOn="False" confirm="False" requiredConfidence="0" loop="False" loopDelay="0" loopMax="0" description="">
  <action>
    <cmdType>PY.ExecString</cmdType>
    <params>
      <param>import time; result= time.ctime(1430337630)</param>
    </params>
    <cmdRepeat>1</cmdRepeat>
  </action>
  <action>
    <cmdType>OSD.ShowText</cmdType>
    <params>
      <param>The time is {LastResult}</param>
    </params>
    <cmdRepeat>1</cmdRepeat>
  </action>
  <phrase>convert time stamp</phrase>
</command>

5
General Discussion / Timestamp to readable string
« on: April 29, 2015, 05:13:17 PM »
I have a timstamp (date and time) in this format: 1430337630

How do I convert this timestamp to a readable time string?

6
General Discussion / Re: VC on Windows Server - no microphone input
« on: April 27, 2015, 03:42:20 PM »
As I understand your recommended solution I need to RDP the server at least once to start a session and run VC.

My goal is to have a "low maintenace" setup. I.e. a server that can be restarted automatically (in case of power loss) and without need for user action to resume full operation. For that reason I think I need to run VC as a service.

Can it be so bad that there is no way to allow windows server to access input like microphone without an active console? Seems like I have to do some serious Googling on this issue...



7
General Discussion / VC on Windows Server - no microphone input
« on: April 26, 2015, 03:08:52 PM »
I am running VC (VoxcommandoSP.exe) on a Windows Server 2012. In my setup I use pocketcontrol (pocketaudio) as microphone input. I dont use speaker in my setup. Instead I use "Speak2Wav".

When the console is active (user logged in and account not locked) it all works fine. But as soon as the console is non-active (locked) voxcommand itself runs OK exept that it doesn't get sound from the microphone. I can se that pocketcontrol has recieved audio during the non-active period but voxcommande doesn't seems to get the sound input.

In the log file i found this entry:
Input error, InvalidOperationException: Audio output and input are not supported for non-active console sessions.

A SAPI error?

Any ideas on how to do a workaround for this? Is anyone running VC as a Service?


Pages: [1]