Messages

1

I will post new features here (LEGACY BOARD ONLY) / Re: Version 1.1.5.8

« on: September 24, 2013, 08:27:54 AM »

Hi James,

I just purchased the previous version a few days ago... will I be able to "activate" the latest version?

2

Other Plugins / Re: TCP Plugin

« on: September 24, 2013, 07:53:40 AM »

Yes, that is what I meant, some type of TCP server including those that allow telnet connections.

3

Other Plugins / Re: TCP Plugin

« on: September 23, 2013, 04:49:04 PM »

Thanks JJ,

So if I have more than two or three different processors I am connecting to I can run concurrent connections from a single instance of VOX, which would constitute as one client connection per processor. I have a limitation that I am aware of on my lighting processor that it cannot have more than 4 concurrent users sessions simultaneaously and in no case more than one by the same user log in at the same time. ( IE if i was logging in by an android app and VOX at the same time they would be independent user log ins.)

Thanks,

C.

4

Other Plugins / Re: TCP Plugin

« on: September 23, 2013, 10:50:08 AM »

Good morning,


I have a question that relates to the TCP plugin with respect to clients; can VOX connect to more than one TCP client at a time and keep the sessions concurrently open?

Thanks,

C.

5

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 05:08:22 PM »

As it turns out this is not working the way I have it currently configured. It seems that any feed back that comes from processor is perceived as the same event, although I can see in the pop up when i roll my mouse over the events that they are unique. The Event Icon they come under however is simply labelled the same name as the group of commands that I have created. What it boils down to is that even though i have dragged the event that I want to correspond to VC.on and the other event that i want to correspond to VC.off to the right locations to fire the approximate actions, any other event that comes in from my lighting processor kicks out an event that is labelled per my group of commands (even though underneath it is different feedback).

I think one quick work around would be to create a different command set just for the on and another just for the off, but it feels like the wrong way to go.

6

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 12:24:01 PM »

James,

not even sure I know how to do that. I did however successfully link my button press and button release events since they are being reported to command VC.on and VC.standby respectively (by dragging the events from the log to the command editor per Kalle's excellent YouTube Tutorial on working with events). So on the RF remote I can now push and hold the button, VC.on commands VOX to green, and it stays green until i release the button.

I will look at pasting code per your request later when I have more time on my hands. I am currently wrapped up in another project  

Thanks,

C.

7

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 10:03:07 AM »

I should also mention that this will now make it possible to have the RF Pico hand held control capable of "push to talk" on a single button as it reports one string for being depressed (command = VC.On) and another unique string for being released (command = VC.Standby). You can order these controls with two, three or five buttons, which would theoretically give them up to 10 different actions (5 for each button press and 5 for each button release). This could easily lend it to scrolling through plugin command sets for example to isolate your commands to a particular focus such as lighting, or XBMC or MediaMonkey for example.

8

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 09:59:01 AM »

Brilliant! = Success! Removing the terminator on my client connection was the key!

El Voxerino you have made my day!


Thanks!

Now I can start my ascent on the mountain of Conditional Logic!

L.

9

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 08:57:32 AM »

Hi Kalle,


this is what have been trying, I get "this link appears to be broken".

regards,

10

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 08:13:39 AM »

I feel like a one armed swimmer this morning...

I have looked through and through and see events being generated in the log such as VC.on or VC.standby, but I not seeing where this is triggered to be an event to show in the log in order for me to endeavor to dissect it and see how this could apply to what I am trying to do.

I have a feeling that somehow i need to have a running xml log that is being generated by the output of my lighting system and the command logic that i need to build the "event" that i am looking for must be based on this xml file and hone in on the string(s) that i am trying to monitor to drive the subsequent action... how to do this? I am also wondering if there is configuration that I need to do with the TCP web-server that is part of the TCP plugin..... I have activated it and see that it is started but when i try to browse to localhost or 127.0.0.1 I just get an error page... Do in need to set up the site under the windows management console somehow as well?

11

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 07:03:44 AM »

Ok I get it... i thought it was a command until i reread your message.  i have set it to the telnet port and will try a few things from there.

thanks for your help.

L.

12

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 06:53:42 AM »

Hi Kalle,

does the VC.Listen command keep the port open until it is closed otherwise?

I will try it and see what happens 

13

Other Plugins / Re: TCP Plugin

« on: September 20, 2013, 06:09:10 AM »

Hello James and Kalle,

I am stumped on what facility to use to 'catch' and output from my lighting system to have VOX treat as an event.

When I have my telnet client connected to the lightng processor and send valid commands to it via VOX, there is clearly feedback of the subsequent action in the processor being reported in the telnet client coming back from the lighting processor, but I have no idea how to have VOX set to "listen" to this output and base an event on this.

for example, if i send a string using TCP.client.write such as #device,20,2,3\x0d\x0a, i get feed back in my telnet client that affirms the action as "~device,20,2,3". It is this output that i would like to turn into an event to then send a VC.on command.

Any hint in the right way to do this?

L.

14

Other Plugins / Re: TCP Plugin

« on: September 19, 2013, 02:39:05 PM »

Hi Kalle,

I did see your post about your wrist adaptation of a wifi headset: stellar Idea! After reading your post and a few others linked to the James Lipsit Website where he uses the HAL2000 controller with very expensive Shure microphone set up for whole home control. My idea lies somewhere inbetween wherein you have the permanently installed mics around the house (or at least in the areas of interest of having voice control) but instead of the expense of the intelligent Shure backend equipment and HAL2000, the mic circuits could be toggled on and off with a relay on the lighting system (in this case a Lutron RadioRa2 system) and the VOX could be active listening or ignoring on the same commands that toggle the mic relays. This could be achieved using the small RF pico controls mentioned. The come with a "car visor" kit to add a clip that could be for your pocket or belt, a table top pedestal mount and the option of mounting on a wall with or without a faceplate (with a face plate is appears as any other light switch, but without a faceplate it is easy to remove and replace on the wall so you could "grab" it on your way into a room and replace it on your way out, giving it a "place" when you are looking for it).

There is an out of the box relay solution called a VCRX that integrates wirelessly with the Lutron system that has 6 keypad pushbuttons, 3 CCI inputs and 4 CCO outputs that can be programmed in the Lutron Software. Not perfect for everyone I will admit as Lutron can be expensive in it's own right, but that is the business that I am in. One thing for sure is that the Lutron RF technology if within proper working ranges is one of the most stable and bullet proof systems.

here is a link to the VCRX: http://www.lutron.com/TechnicalDocumentLibrary/Visor%20Controls_369-224a.pdf

you will notice that one of the inputs is labelled as a security input. it is possible to wire one of it's outputs back to this input to achieve something like: Yell for HELP and have VOX activate the output, the output activates security mode and you could have all of the lights in the house flash off and on (including the outside) and send a contact closure the security system.....

15

Other Plugins / Re: TCP Plugin

« on: September 19, 2013, 11:44:19 AM »

Thanks James,


the wheels are turning! The feed back logging AND Monitoring is going to open a lot of other possibilities. For example, they make a PICO control for the lighting system which is a very small RF control that you could clip to your shirt pocket, put in your pocket or purse or mount on a small table top "pedestal". It is a very economical device to give you remote control of lights or whole scenes on the system. Imagine now if you used one such device to send a command to the lighting system, which is monitored by VOX that then tells VOX to either Listen or not Listen. You could simplify a distributed Mic system for whole home control immensely with this method of toggling VOX to listen or not I would think with a manual "push to talk" approach. Working in VoX's soft mute feature could be activated as the VOX listen command is executed as well. This would ensure the commands spoken when loud media is playing are a non issue for the Start Listening command as well as the subsequent commands unitil the PICO control tell VOX to (or your voice command VOX) to stop listening.

Here is a link to a PICO control: http://www.lutron.com/en-US/Products/Pages/Components/PicoWirelessController/Models.aspx