Plugin: SageTCPServer

[gianpieroizzo]

Originally Posted by Fonceur

See if it's fixed in 2.0.4.

Ok, thank you, now it works.

one minor bug and one suggestion...

- if the extender is shut down, trying to command it will result in sending the commands to the server UI.

- it would be nice to have the capability of a slideshow view of the pictures in a folder, possibly in typical iPhone style !

Thanks for your work !

Gian Piero

[Fonceur]

Originally Posted by gianpieroizzo

- if the extender is shut down, trying to command it will result in sending the commands to the server UI.

Hmm, I could see why it would do that for the software clients before connection, but it seems odd that it also happens for extenders...

- it would be nice to have the capability of a slideshow view of the pictures in a folder, possibly in typical iPhone style !

That's more a request for the iOS or Android app, not for SageTCPServer itself...

[Fonceur]

Version 2.0.8

- Can now provide the list of scheduling conflicts.


Version 2.0.7

- Fixed the system messages and favorites events handling.


Version 2.0.6

- Set the default VLC port to 554.

[Fonceur]

Version 2.0.9

- Fixed issues with the Server's port.
- Can launch LiveTV on a specific channel.

[Fonceur]

Version 2.1.0

- Capitalize JSON strings.
- Add password protection.
- Limit the system messages sent.


Don't put any password until all the application/plugin/driver that you use to connect to SageTCPServer actually support it... As of now, none do...

[Ericft]

Just happened to come across this being released on App store and I jumped on it...however, now I'm a bit lost on how to configure for access via 3G...i have a win 7 Sagetv server behind a apple airport extreme router at home, with dyndns.org address for external access...What I want is some info about how to include my dyndns.org address in the iphone menu..also, should i just open the 9250/9260 ports on my router and send them to the local IP address of the server, similar to what I do for other placeshifter/IOS streaming Jetty programs?
Any help or direction would be much appreciated.

[Fonceur]

Originally Posted by Ericft

What I want is some info about how to include my dyndns.org address in the iphone menu..

That's more for the TiSageTV thread, but yes, in the iOS device Settings (i.e. not in the app itself), pick TiSageTV, if you scroll down you can define a second server. Then from the Settings you can also define which one is the default server to connect to.

Inside TiSageTV itself, the in-app Settings allows you to switch between your various servers/clients.

also, should i just open the 9250/9260 ports on my router and send them to the local IP address of the server, similar to what I do for other placeshifter/IOS streaming Jetty programs?

Indeed, just replicate what you did for port 8080 (or which ever port you have jetty on).

[Ericft]

Thanks. I did go into the IOS settings to change server 2 information but not sure of the syntax to enter it...so far I have
XXXXX.dyndns.org

do I need to put something else on it such as the port number (even though the next line the in the server setup has the port number already so presumably it logs in with the port number). Also, do the port numbers for server 1 and 2 have to differ?
sorry for posting here...if I need anything further I will send it over to Tisagetv, just figured you already knew the issues.

[Fonceur]

Originally Posted by Ericft

I did go into the IOS settings to change server 2 information but not sure of the syntax to enter it...so far I have XXXXX.dyndns.org

That's fine.

do I need to put something else on it such as the port number (even though the next line the in the server setup has the port number already so presumably it logs in with the port number).

No you put the port in the port field, no need to add it elsewhere...

Also, do the port numbers for server 1 and 2 have to differ?

It's up to you, but I'm pretty sure both have the same 9250 default. Just make sure that internally it does connect to the same port (i.e. you could have a virtual server visible on port 9999 on the outside which actually goes to 9250 internally).

[TechBill]

I saw a update version on SageTCPServer and went to updated it then my TaSageTV could no longer connect to it.

Not sure if it my end or the update broke something but wanted to give you a head up on it.


Bill

[Fonceur]

Originally Posted by TechBill

Not sure if it my end or the update broke something but wanted to give you a head up on it.

There is nothing to affect it... Maybe try to restart SageTV, look at the log or such...

[TechBill]

Originally Posted by Fonceur

There is nothing to affect it... Maybe try to restart SageTV, look at the log or such...

I think I know why, I suspect the SageTV ip address changed when I was doing some adjusting with SageTV server

Sorry about that.

Bill

[Fonceur]

Originally Posted by TechBill

I think I know why, I suspect the SageTV ip address changed when I was doing some adjusting with SageTV server

Yes that would do it.

You might be able to make up an IP with something like machine-name.domain-name, but I'm not sure, and I'm definitely not querying the DNS to get a proper address from just the machine name or such.

[Fonceur]

Nothing major, mostly for upcoming versions of TiSageTV/TaSageTV...


Version 2.1.3

- Enforce the password usage.
- Provide the HTTP port.


Version 2.1.2

- Stop sending Del/Add for a Favorite modification.
- Can send the list of clients.


Version 2.1.1

- Stop capitalizing channel details.
- Retrieve the title from Metadata if present.

[Fonceur]

I need a few volunteers with extenders to test this build for:

- 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...

- Improved reliability: Previously, under some conditions, SageTCPServer might not have been able to re-establish communication with an extender.

- Third party commands The following commands should work:

• XTC:Power = Toggle the StandBy state on an extender, or the full screen mode on a software client.
• XTC:PowerOn = Power on an extender.
• XTC:PowerOff = Put an extender in StandBy.
• XTC:Reboot = Reboot an extender.

You should keep a copy of the SageTV\SageTV\JARs\SageTCPServer.jar, in case of unforeseen issues. Stop the SageTV UI (and its service), extract the SageTCPServer.jar to that folder and restart SageTV.

[Fonceur]

Was a problem with the first attempt, so here's an update...

EDIT: Everything seemed fine, so it's now an official release...

[SomeWhatLost]

just updated...
from a CQC point of view nothing seems broke... well at least nothing I have noticed yet...

[Fonceur]

Well, I'm seeing a problem with Client reconnection on TaSageTV, but maybe it's just my unreleased version...

[batwater]

Originally Posted by Fonceur

Well, I'm seeing a problem with Client reconnection on TaSageTV, but maybe it's just my unreleased version...

Hi Fonceur,

I can confirm this issue with latest SageTCPServer 2.15 and latest taSageTV 1.62 Server connects but no extenders.

-Ben

[Fonceur]

Originally Posted by batwater

I can confirm this issue with latest SageTCPServer 2.15 and latest taSageTV 1.62 Server connects but no extenders.

This should be fixed with the current version:

Version 2.1.6

- The JSON string for multiple clients was malformed.


I was missing some "," between clients, but I think the iOS JSON parser was auto-correcting for it, while the Android one chocked on it.