Plugin: SageTCPServer

[GMan78]

Hey Fonceur, again, loving TaSage and SageTCPServer...am about to buy 2 or 3 additional licenses for both Android and IOS platforms. Thanks for the excellent solution!

So you may recall I was asking earlier about the custom buttons feature. I setup the SageTCPServer with custom buttons using the EXE command to pass parameters to my IR controller (LM Remote KeyMap). I was thrilled to get full control from my Android phone of my audio matrix switch using this method. I pulled off some really fancy footwork and could not wait to get this working for my clients as well. Unfortunately that's where I hit a roadblock. Apparently the EXE command executes only on the PC which is running SageTCPServer. The result is that I cannot have the executable run on the client PC from which I am currently commanding TaSage. This must occur in order to differentiate the source output for the matrix switch I am controlling. I was hoping that the custom button EXE commands sent to SageTCPServer would pass to the client computer that requested they be executed just as they do for the pre-programmed remote control buttons.

Please help! I'm so close to achieving my dream of having whole home audio control from my mobile device...don't want to crash and burn on this... Any ideas greatly appreciated...

George

[Fonceur]

Originally Posted by GMan78

Apparently the EXE command executes only on the PC which is running SageTCPServer.

Right, it is basically running a DOS prompt from the SageTV server...

The result is that I cannot have the executable run on the client PC from which I am currently commanding TaSage.

Looking at the SageTV API, I do see a command that might work for that... If I get it to work, I'll post a new version...

[GMan78]

That would totally ROCK! Good Luck!

George

[Fonceur]

Version 2.2.9

Added support for EXC:Program.exe|paramater1|parameter2|...|parameterN


Contrary to command EXE which gets executed on the SageTV server, this command will be executed on the SageTV client... It should take any number of parameters, just separate them by |.

[GMan78]

Awesome!!!

I'm taking the kids swimming and then to fireworks... can't wait to get home and try this. Probably in about 6 hours...

THANK YOU!

[GMan78]

EXC DID IT! IT'S WORKING BEAUTIFULLY! Just a friggin fantastic soltution. Off to the store to my more licenses for my other phones!

THANK YOU FONCEUR!!!! Excellent Support! Superb Application! Makes me think I should start playing with CQC just so I can do more business with you...

[Fonceur]

Version 2.3.0

- Properly handles empty Title in imported videos.


That seems to be an issue with newer BMT versions... Though I'm simply copying the Episode field to the Title one, so you might end up with some episode titles instead of regular title...

[Fonceur]

Version 2.3.1

- Fix: was not cleaning up properly on Media server/Client disconnect.

[that_kid]

I've been having hit or miss success with this plugin. It's probably some extender giving me issues but now when I enable this plugin my sage service stops after a while. Sage will begin to load up then at some point bam it's down. I even recbuilt my server a few weeks ago and I still expericne the same issue which is leading me to believe I need to look at something else. Ayhow I included my logs just in case.

[Fonceur]

Originally Posted by that_kid

It's probably some extender giving me issues but now when I enable this plugin my sage service stops after a while.

You seem to have 3 clients/extenders trying to use the same port 9279... So with SageTV and its service shutdown, edit Sage.properties and make sure to use unique ports.

[that_kid]

yup that'll do it, thanks I'll go fix that right now.

[enthilzha]

I'll echo the fact that I'm LOVING SageTCPServer. I'm running into any issue where I recently changed to a new DHCP server so the IPs of all of my extenders has changed. I've got 4 HD300s that used to get restarted flawlessly after I have my Sage server reboot at 3AM. Now none of them are rebooting and I'm noticing in the logs that SageTCPServer seems to be using their old address:

Sun 10/16 23:10:52.163 [SageTV@4aa0ce] [[SageTCPServer]]: Starting extender
Sun 10/16 23:10:52.165 [SageTV@4aa0ce] [[SageTCPServer-Player:9260]]: TCPServerPlayer: 0023a5000966, port = 9260,ip = 10.1.2.203
Sun 10/16 23:10:52.355 [SageTV@4aa0ce] Arp: stdout:
Sun 10/16 23:10:52.356 [SageTV@4aa0ce] Arp: stdout: Interface: 10.1.2.101 --- 0xa
Sun 10/16 23:10:52.356 [SageTV@4aa0ce] Arp: stdout: Internet Address Physical Address Type
Sun 10/16 23:10:52.356 [SageTV@4aa0ce] Arp: stdout: 10.1.2.1 00-25-83-67-fe-43 dynamic
Sun 10/16 23:10:52.357 [SageTV@4aa0ce] Arp: stdout: 10.1.2.100 00-1f-d0-95-4a-95 dynamic
Sun 10/16 23:10:52.357 [SageTV@4aa0ce] Arp: stdout: 10.1.2.102 00-21-6a-58-0e-b6 dynamic
Sun 10/16 23:10:52.357 [SageTV@4aa0ce] Arp: stdout: 10.1.2.255 ff-ff-ff-ff-ff-ff static
Sun 10/16 23:10:52.357 [SageTV@4aa0ce] Arp: stdout: 224.0.0.22 01-00-5e-00-00-16 static
Sun 10/16 23:10:52.357 [SageTV@4aa0ce] Arp: stdout: 224.0.0.252 01-00-5e-00-00-fc static
Sun 10/16 23:10:52.358 [SageTV@4aa0ce] Arp: stdout: 228.5.6.7 01-00-5e-05-06-07 static
Sun 10/16 23:10:52.358 [SageTV@4aa0ce] Arp: stdout: 229.111.112.12 01-00-5e-6f-70-0c static
Sun 10/16 23:10:52.358 [SageTV@4aa0ce] Arp: stdout: 239.255.255.250 01-00-5e-7f-ff-fa static
Sun 10/16 23:10:52.358 [SageTV@4aa0ce] Arp: stdout: 239.255.255.253 01-00-5e-7f-ff-fd static

10.1.2.203 was the previous IP of one of the extenders.

Basic question - how does SageTCPServer learn an extender's IP address and is it possible to pre-program it (I'm fine doing a DHCP reservation for my extenders)? Looking forward to trying TASage when upgrade my Blackberry in a few weeks.

[Fonceur]

Originally Posted by enthilzha

Basic question - how does SageTCPServer learn an extender's IP address and is it possible to pre-program it (I'm fine doing a DHCP reservation for my extenders)?

Basically, when a client connects to SageTV itself, there is a trigger for it. That's when SageTCPServer grabs the IP and updates Sage.properties.

In principle it should auto-correct itself after the extenders have reconnected, which might be why it didn't work on the initial restart. If you have already restarted SageTV since, then I guess it didn't work for that case. If you stop SageTV and its service, you can edit the Sage.properties file and you should be able to find some lines where those old addresses are, just delete them and they will get recreated.

[RandyJohnson]

Fonceur...

Regarding sageTCPServer version 2.3.1..

I just recently upgraded to this release and I am noticing that the pluging has now gotten very chatty..

Even when the sage playbacks are sitting on the Home page I noticed that the following string is being sent every second from the plugin for each playback box:

\x02PLM:Stop\x03

Is there a need for this much communication? Or do I need to respond to this string with something to shut it up?

I started to playback video and the string switched to:

\x02PLM:Play\x03


Thanks in advance...

Randy

[Fonceur]

Originally Posted by RandyJohnson

Is there a need for this much communication?

That's the "keep alive" for the iOS/Android/CQC apps... I used to have it slower, but then people were complaining that it took too long for the client apps to notice a dropped communication...

[RandyJohnson]

Thanks

Since I am not really dealing with any feedback from the server, I am just going ignore anything being received from the server.

If possible could this be parameter driven for those of us who do not need the keep alive feature?

Randy

[Fonceur]

Originally Posted by RandyJohnson

If possible could this be parameter driven for those of us who do not need the keep alive feature?

If you don't want any feedback, just don't send the INI... If it's only the keep alive that you don't want, I should be able to add some configuration for that, probably increase the count before it is sent or such.

[RandyJohnson]

I am not sending the INI.

I am sending the following strings when I press the "1" key..

MODlayer\nCMD:1\n

and so forth for the various keys (1-0,Enter,Play, etc).

I have attached a screen shot of the various command strings that I am sending.

Prior to the most recent upgrade I had never seen any feedback from the sageTCPserver.

Randy

[Fonceur]

Originally Posted by RandyJohnson

I am not sending the INI.

OK, upgrade to 2.3.2, that should make it quiet again...

[RandyJohnson]

Fonceur..

Has the newer version been added to the Plugin library?

Thanks in advance...

Randy