Plugin: SageTCPServer

[brewston]

Originally Posted by Fonceur

- Auto reboot of extenders: there is (was?) a known issue with the extenders, where they don't resync with the SageTV server in case of a restart. So now whenever the plugin is restarted, it reboots all the extenders (can be disabled in the plugin configuration). Ideally it should only be when SageTV is restarted, and not the plugin itself, but in reality updating the plugin requires a restart of SageTV anyway...

This is a cool feature, thanks ! I normall end up telnet'ing into my clients to restart them. I noticed it does a complete reboot ? is that necessary ? I normally just killall waitpower which starts up miniclient.

[Fonceur]

Originally Posted by brewston

This is a cool feature, thanks ! I normall end up telnet'ing into my clients to restart them. I noticed it does a complete reboot ? is that necessary ? I normally just killall waitpower which starts up miniclient.

Actually, it was using the Hauppauge reboot sequence, which was doing both. In the next iteration it will be a simple reboot.

If the reboot is indeed overkill, then I could switch to a simple PowerOn instead. Though I would have to keep track of the type of extender, as it's undefined before the reboot and possibly while in standby

[Fonceur]

I need a few more volunteers with extenders to test this build. Instead of a full reboot, now it should only do a PowerOn (won't work the first time on the MVP).

[Fonceur]

Originally Posted by brewston

I normally just killall waitpower which starts up miniclient.

That's what version 2.1.8 now uses...

[appelm]

The latest version of this has been giving me a lot of problems. It causes Sage to hang periodically. I have to go to the server and end the SageTV thread and restart. As soon as I uninstall SageTCPServer, my problems go away.

I wasn't having this problem with the last version. I recall when I first installed this version, all my extender names had been wiped out. They defaulted back to the mac addresses.. I tried editing them and it was after that I started having problems.. I've tried clearing all the SageTCPServer lines from my properties files and re-installing but that hasn't helped.. I'm not sure if my editing the extender names has anything to do with this.

[Fonceur]

Originally Posted by appelm

The latest version of this has been giving me a lot of problems.

Version 2.2.0?

It causes Sage to hang periodically. I have to go to the server and end the SageTV thread and restart.

Could you enable the debugging, zip and post the sagetv_0.txt?

I recall when I first installed this version, all my extender names had been wiped out.

It shouldn't overwrite existing ones...


EDIT: Actually, older versions might indeed have been overwriting the names under some conditions.

[appelm]

Originally Posted by Fonceur

Version 2.2.0?


Could you enable the debugging, zip and post the sagetv_0.txt?


It shouldn't overwrite existing ones...


EDIT: Actually, older versions might indeed have been overwriting the names under some conditions.

Well I'm happy to report my problems are no more. Not sure if version 2.2.0 fixed it but all good so far.

[clarenceb5]

Hi, I'm new to this plugin also using version 2.2.0 and am having a similar problem, I did not use a previous version so no experience prior to now.

I am unable to get the plugin to save the names I provide for my extenders, it saves the names when I enter them for the clients anyone have any suggestions for me? Thanks in advance.

[Fonceur]

Worse case, you can shutdown SageTV (and its service) to edit the sage.properties file...

[Fonceur]

The beta should be fine. You have the latest version of the plugins and app installed? Try to enable to debugging and post your sagetv_0.txt log file.

[Fonceur]

Version 2.2.3

- Don't send info about albums without tracks.


Version 2.2.2

- Added support for custom buttons.


Version 2.2.1

- React faster to the Extender going into standby.


Version 2.2.0

- Improved the extender's handling, part 3.


Version 2.1.9

- Added JSON2 as Answer option.


Version 2.1.8

- Improved the extender's handling, part 2.


Version 2.1.7

-Slightly more efficient version...

[Lostinpvr]

Update: I did notice other questions on this subject. I guess this is maybe a BUG?

http://forums.sagetv.com/forums/showthread.php?p=491916&postcount=89

The Fix
Worse case, you can shutdown SageTV (and its service) to edit the sage.properties file...

Fonceur,
I see in the the SageTCPServer Setup that you should be able to change the Extender name shown on TASageTV Device.

It shows the syntax as

The format is Name1:MacID1:Port1:Name2:MacID2:Port2 as in Kitchen:0012345678:9260,Living ...

If I try to change the current syntax
FROM:
0023a500081e:0023a500081e:9260
TO:
Basement Den:0023a500081e:9260

No changes are accecepted. Is this a "Future Feature" or did I make an error?

Thanks, Jeff

[Fonceur]

Originally Posted by Lostinpvr

No changes are accecepted. Is this a "Future Feature" or did I make an error?

No, it's simply a broken feature that I can't figure out why it's not working properly... Thus the suggestion to shutdown SageTV and its service, then edit the SageTV\SageTV\Sage.properties file and replace the:

sagex/uicontexts/0023a500081e/name=0023a500081e

with:

sagex/uicontexts/0023a500081e/name=Basement Den

[Lostinpvr]

Thanks for the input: I have it working. It's actually working great.

Thank You

Originally Posted by Fonceur

No, it's simply a broken feature that I can't figure out why it's not working properly... Thus the suggestion to shutdown SageTV and its service, then edit the SageTV\SageTV\Sage.properties file and replace the:

sagex/uicontexts/0023a500081e/name=0023a500081e

with:

sagex/uicontexts/0023a500081e/name=Basement Den

[Fonceur]

Version 2.2.4

- Modified the Client/Extender configuration of Names and Ports.


Something was not working properly before, and reconfiguring multiple ones was really painful... You can't add new clients/extenders, but they should be auto-detected anyway.

For the custom buttons, here's some new functionality:

Backspace,CMD:Backspace
HD100 On,EXE:C:/sageextctrl.exe 192.168.0.105 on
HD100 Off,EXE:C:\\sageextctrl.exe 192.168.0.105 off

So the CMD:Backspace will act just like the equivalent keyboard key...

You can now use EXE:Command. You will probably need to include the full path, with the folder separator set to either "/" or "\\"...

In principle you can create macros by chaining commands like:

Fav,CMD:Num1\nCMD:Num2\nCMD:Num3

Where the "\n" acts as the glue between 2 commands...

[Fonceur]

Originally Posted by Fonceur

Fav,CMD:Num1\nCMD:Num2\nCMD:Num3

Of course the proper way to do this is with:

Fav,KEY:123

But you get the idea...

[Fonceur]

Version 2.2.5

- Fix: was not reading the proper port for Jetty.


I was not reading the proper key, but jreichen pointed me in the right direction. So for people using a custom port, it should work automatically now.

[Fonceur]

Version 2.2.6

- Removed some extra API instantiations.
- Fixed starting a Playlist.

[IVB]

Just blew away my whole SageTV setup and started from scratch for V7, need to get CQC<-SageTV working again.

I done screwed up something, before I post asking for help i'll do some digging.

Three question though:
1) do I do the entirety of this config via the plugin mgr/configure plugin, or do I need to edit the sage.properties file?

2) (DELETED, I'm an idiot).

3) I have 2 HD200; do I set the name & port in the configure for both? How would I know which is which (or do I just do trial&error)?

[IVB]

sorry one more, i'm not sure i'm understanding the verbiage.

All I should need to do is set the extender(s) ports to #s like 9260, 9261, then refer to those in the CQC add-driver portion right?