Developer Challenge: Make SageTV "Tweet"?

[Slugger]

Originally Posted by darcilicious

Perhaps I'm too dense for this this morning ;-) First, SageClient.properties is a file, yes? How do I install Jetty in a file when the Jetty instructions say:



So on the local client then I'm thinking I just need to do this step:

Edit the SageClient.properties file and add
sagex.jetty.starter.Main to load_at_startup_runnable_classes

Okay fine. But now, I don't understand where the "new jetty installation" is...

Not sure, but you'll definitely have a problem. You will need to change the port that each copy of the plugin runs on so they are different. Not sure how that can be done for the local client vs. the server service. You'll want to head over to the Jetty plugin thread and see if anyone's tried it (I do not author the Jetty plugin - my plugins just run on top of it).

At this point, I really need step by step instructions, something akin to http://tools.assembla.com/sageplugins/wiki/JettyInstall because as someone really new SageTV I don't understand how to follow the relatively abbreviated instructions above.

It's summer time - won't be any new docs coming from me anytime soon. However, I strongly encourage you to write up some supplemental docs - and I'll be happy to add them to the wiki area of the project site - after you're up and running.

(Also, in poking around on my SageTV installed on my laptop/remote client, there aren't ANY applicable .properties files so I wouldn't even now how to complete the Jetty installation server there to have it startup).



Perhaps the way Jetty works isn't really compatible with non-extender "clients". Or more likely, I'm missing some key piece of information...

Thanks again for all your help!

http://forums.sagetv.com/forums/show...402#post237402

As you're learning, setting up these kinds of plugins and customizations aren't straightforward and do require/assume some level of knowledge about how SageTV works. I encourage you to ask questions, but you'll notice a lot of my answers end up quoting some post somewhere on these boards - most of the answers to most of the problems/questions you're having are on the boards - you're just going to have to go looking for them. If you want to continue adding plugins, etc. to your Sage install then you're going to want to become rather familiar with these boards and how to best search for the answers you seek.

[darcilicious]

Not sure, but you'll definitely have a problem. You will need to change the port that each copy of the plugin runs on so they are different. Not sure how that can be done for the local client vs. the server service. You'll want to head over to the Jetty plugin thread and see if anyone's tried it (I do not author the Jetty plugin - my plugins just run on top of it).

Thanks, will do!

[Slugger]

As I get ready to make a v1.0.0 release of SageTweet, I'm looking for a few testers to give it a final run through. Please grab the latest 0.0.2 beta build and install. Key feature changes that I'm looking for feedback on:

* Each type of tweet can now be tweeted to their own Twitter account

Motivation: I've created two separate Twitter accounts for my Sage box. One where I tweet general info (what's recording, UI connections, etc.). I don't want SMS alerts for these tweets so I direct them to a twitter account that I don't receive SMS for. The important messages (System messages, conflicts, low space) are directed to a second twitter account for which I do receive SMS alerts. This way I get immediate SMS notification of important things while not having my txt msg inbox being cluttered with informational tweets that aren't important (but perhaps still nice to be able to read up on)

* Twitter accounts are now managed on a separate tab

Motivation: Register your twitter id/pwd once and use that id everywhere (you'll see what I mean when you test it)

NOTE: The settings format file has changed to accommodate these changes. Therefore, I've renamed the settings file, which will force you to reconfigure your settings from scratch (trust me when I say trying to use and massage the old settings file is more headache than it's worth).

[darcilicious]

Originally Posted by Slugger

If you want clients to tweet then you must also install the plugin on the clients and then configure each one separately. The server (in service mode) can only tweet for media extenders. To tweet for your clients you will have to install the plugin in the SageClients.properties for both systems. If you do that then the client id is SAGE_LOCAL_UI (or something like that). If you upgrade to build 493 and visit (on your client installation of the plugin):

http://jetty_srv/sagetweet/ShowConnectedClients

then it will show you the exact string that is required for the client id.

First, thanks again for all your help in this and other posts. Finally had a chance to play with this some more this weekend and have the Windows remote client running Jetty and SageTweet just fine

The client id for a Windows-based client is: SAGETV_PROCESS_LOCAL_UI. Just saw the first remote client tweet for 'currently watching'.

Also, nice improvements to the SageTweet software -- it's working out great!

Currently working with the Jetty developer testing a new version that will install Jetty on a local client as well. Will keep you posted if you like

Cheers!

[nethead]

Quick question;

been using sagetweet for about 2months now, worked great.

this past friday I installed the SageWebApp, now sagetweet doesn't tweet and not able to access via the web page, appears not to be running now.

http://localhost:8080/sagetweet/ <-- use to work, now 404 error

any tips?

oh, checked and the sagetweet.properties file exist/shows last tweet at 20:40pm last friday / and the sagewebapp is working great.

TIA

[Slugger]

Sounds like the web server and Jetty are trying to use the same port. Check C:\Program Files\SageTV\SageTV\JettyStarter.properties if that file is configured to also use port 8080 then stop SageTV, edit that file, change the port, restart SageTV and then everything should play nice together. Just remember that all your Jetty apps (such as SageTweet) will have moved to the new port.

[jreichen]

By "SageWebApp" I think he means the mobile web interface. That's what I named the zip file - not the best name in retrospect.

Maybe he should try deleting the directory where the sagetweet war was extracted, then "touching" the context file to extract the war file again. Or perhaps try restarting the SageTV server.

[Slugger]

In preparation for the official v1.0.0 release of SageTweet, I've thrown together an installation/configuration wiki doc. Nothing too extravagant, but I think it suffices. But do let me know if it's missing something.

[Slugger]

Originally Posted by jreichen

By "SageWebApp" I think he means the mobile web interface. That's what I named the zip file - not the best name in retrospect.

Maybe he should try deleting the directory where the sagetweet war was extracted, then "touching" the context file to extract the war file again. Or perhaps try restarting the SageTV server.

I've seen cases of the war magically disappearing from the webapps dir and then on a Sage restart the app obviously doesn't deploy. If it's a 404 `NOT_FOUND` error then I'm guessing the war has just magically vanished. Download the zip again and reinstall it. (Doing so would be about the same as what jreichen has suggested above, but might be easier for you).

[wayner]

Would there be a way to create aliases rather than using MAC IDs or IP addresses for your Sage extenders, etc.

So rather than getting a mesage that says: "Remote UI(s) Connected: '001d6a4bfeca'; #SageTweet" it could say something like: "Remote UI(s) Connected: 'Kitchen _HD200'; #SageTweet

and "Remote UI(s) Connected: '/192.168.1.96:54680'; '/127.0.0.1:1104'; '001d6a4bfb37"'; #SageTweet it would say: Remote UI(s) Connected: 'Kitchen'; 'SageServer'; 'Bedroom'; #SageTweet

[Slugger]

Originally Posted by wayner

Would there be a way to create aliases rather than using MAC IDs or IP addresses for your Sage extenders, etc.

So rather than getting a mesage that says: "Remote UI(s) Connected: '001d6a4bfeca'; #SageTweet" it could say something like: "Remote UI(s) Connected: 'Kitchen _HD200'; #SageTweet

and "Remote UI(s) Connected: '/192.168.1.96:54680'; '/127.0.0.1:1104'; '001d6a4bfb37"'; #SageTweet it would say: Remote UI(s) Connected: 'Kitchen'; 'SageServer'; 'Bedroom'; #SageTweet

Someone beat you to it. Issue 81 was opened the other day for this exact request. I've already accepted the ticket and will add the functionality before the official v1.0.0 release (which I hope to make in the next week or two). If you want to be notified when a snapshot containing this feature is made available, click on that issue ticket above and star the issue.

[Brent]

Originally Posted by wayner

Would there be a way to create aliases rather than using MAC IDs or IP addresses for your Sage extenders, etc.

So rather than getting a mesage that says: "Remote UI(s) Connected: '001d6a4bfeca'; #SageTweet" it could say something like: "Remote UI(s) Connected: 'Kitchen _HD200'; #SageTweet

and "Remote UI(s) Connected: '/192.168.1.96:54680'; '/127.0.0.1:1104'; '001d6a4bfb37"'; #SageTweet it would say: Remote UI(s) Connected: 'Kitchen'; 'SageServer'; 'Bedroom'; #SageTweet

Brilliant idea! Funny that we're thinking alike Wayne. As Slugger mentioned above, I just added Issue 81 a few days ago!

I love this addon - really useful for me and this addition would make it even better for those of us with many TVs in the house.

[wayner]

For the "Be Sociable" tweet - does it make sense to be able to do this to multiple Tweet IDs?

I don't know if this is exactly a job for this application but it might be interesting to get summary information every week or so.

For example:
SageServer recorded 68 shows for a total of 38 hours of content and used 125GB.
LivingRm_HD200 watched 28 shows in the last week and was active for 112 hours.

[Slugger]

Originally Posted by wayner

For the "Be Sociable" tweet - does it make sense to be able to do this to multiple Tweet IDs?

It does, if the option were to stick around. I've been thinking of removing it. I mostly put it in there as a way to test things at the beginning and just never got around to removing it once all the other tweet types were tested and working. Is the sociable tweet something that others actually use/find useful/aren't annoyed by?

I don't know if this is exactly a job for this application but it might be interesting to get summary information every week or so.

For example:
SageServer recorded 68 shows for a total of 38 hours of content and used 125GB.
LivingRm_HD200 watched 28 shows in the last week and was active for 112 hours.

If such stats could be easily extracted from the Sage API then I'd consider adding it, but they aren't and the plugin itself definitely won't be tracking these kinds (or any kind) of usage stats.

[wayner]

I think the Be Sociable is useful as a test mechanism. It also tells you that your system is still alive - if this tweet stops then it could be an indication that your Sage Server is having problems. That may not be as useful if you are at home but if you are travelling and your family depends on your Sage being up then it could be useful.

[wayner]

It looks like many of your make your Tweets public. Is this a good idea? Do you want other people to know what you are watching and/or recording?

[darcilicious]

Two quick comments:

I hope that Windows-based clients will be able to make use of the 'aliases' as well

Yes, my tweets are public but they're also relatively anonymous ;-) I'm totally into social tv, I'm a big fan of Boxee, which is like a narrower version of twitter -- I can see what my Boxee friends have been watching / listening to and they can see "me"

[Brent]

Originally Posted by wayner

It looks like many of your make your Tweets public. Is this a good idea? Do you want other people to know what you are watching and/or recording?

I left mine public so others could see how it works. I'll eventually make it private though. I'm only embarrased by all of the soaps my wife watches and the fact that my daughter is a CSI (anything edition) and NCIS addict.

The worst thing about keeping it public is all of the twitter spammers it picks up. My SageTwitter account seriously has 72 Followers! Now that's a popular machine right there

If anyone wants to see how many public SageTwitterers there are out there do a search for #SageTweet There's definitely a few of us.

[wayner]

You may not want the MPAA to see what your watching, ie. Currently watching 'Movies/Torrents/Inglourious.Basterds.Telecine.avi' or even worse, 'Movies/Adult/Torrents/Deep.Throat.DVDrip.avi'

[Slugger]

Snapshot 513 contains the addition of client/extender aliases. I've tested it, but the more the better. A screen shot from my server's twitter feed included. I'm gone for the day now, but if others can download, test, and provide feedback by tomorrow evening then I should have a couple hours to clean up any issues found.