Cumulus Support

mmorris1 wrote:I thought that when the twitter.txt file output went over 140 characters that it used to just cut off the end and would post only the 140 characters.

I do remember some discussion about this, but I seem not to have done it. I'll look into it.

I believe this will be my last update the twitter problem I believe was on my end. As when the cumulus program added in the data to my twitter.txt file that I ended up with over 140 characters and that killed twitter from updating twitter..

Hi

Yep thats the code I'm using at present.

Trying to squeeze everything into 140 chars is a bind!

I am also getting issues with my API Twitter feed from Cumulus. Sometimes it works fine for days and then nothing. My last Tweet from Cumulus was over a day ago. Sometimes restarting Cumulus can fix this, also sometimes changing the Tweet interval, closing Cumulus, then restarting it and setting the interval back gets it going again.

StaffsStormSpotter wrote:I am also getting issues with my API Twitter feed from Cumulus. Sometimes it works fine for days and then nothing. My last Tweet from Cumulus was over a day ago. Sometimes restarting Cumulus can fix this, also sometimes changing the Tweet interval, closing Cumulus, then restarting it and setting the interval back gets it going again.

They have been having problems again: http://status.twitter.com/

I probably need to add some sort of checking to prevent the http component getting stuck waiting for a response from Twitter - it doesn't seem to have any built-in timeouts.

I've added code to truncate the message at 140 chars, but haven't got around to uploading the build yet.

Hi Guys

I have just installed version 1.8.9 and this has resolved the twitter cut off issue. I think the 140 character limit was causing twitter updates to fail as suggested.

I have also installed the Cumulus Toolbox and PHPWebTags and using twittermail I have been able to tweet the rules! Just need the weather to trigger the rules to test it now.

thanks again

Chris
staffsstormspotter

Just to add my penny's worth here.
Both versions 1.88 and 1.89 have been flawless for me using twitter.
I only upload 4 times a day, every 6 hours.
I shortened the content to just the bare facts to get a one liner.
This has always worked fine.
But...........
If I close off Cumulus or reboot then the 6 hours will start from the beginning again.
so, if I reboot at the 5 hour mark, I will have a gap of 11 hours between twits.
But this does not worry me at all
Anyways thanks for this feature, its great

JennyLeez wrote:If I close off Cumulus or reboot then the 6 hours will start from the beginning again.
so, if I reboot at the 5 hour mark, I will have a gap of 11 hours between twits.

Yes, it's the same with all the timers - I went for the easy approach It just starts all of timers when it starts up, so they all start again from then. I'm thinking about a more "calendar" based approach in Cumulus , so you can specify that you want certain things to happen on the hour, or five minutes past the hour, or at 00:00, 02:00, 04:00 etc.

Just wanted to say that Cumulus has been sending to twitter with out any problem at all.
Just thinking it would be nice to have a group of twitter tag that rounded up or down the values to remove the decimal point to just leave the whole number to display, like for the Temp and Wind reading. Ok tell me to stop thinking