on and off this week Ive been trying to see what might be going wrong, including re-installing Cumulus.
It seems to me that if I use the default twitter message it does seem to work fine, but if I use a custom message by creating a twitter.txt then I get the unreliable behavior, specifically it tweets a few times then flips upside down and falls to the bottom of the cage (or stops). Various restarts, reboots, etc can prod it back into life, but its unreliable. When Cumulus is unreliably, or not at all, tweeting (with a custom message) I can tweet from the same PC using any other Tweet tool or command line (via CURL) - so my conclusion is that I think the Cumulus custom twitter message is the problem. Hardly evidence to prove guilt (but men have done life for less)
Right now 60redwood is set to tweet the standard message every 10 minutes, lets see if it runs ok for the next hour. The I'll stop it, put the custom message back and set it off again.
Update#1
Ok between 19:51 and 20:51 the standard message was tweeted every 10 minutes - Working great. Now lets swap to the custom message
This is the twitter.txt message format
#Weather #Woodley <#hour>:<#minute> <#forecast> <#temp>°C <#temptrendtext> <#rfall>mm Rain <#press>hPa <#presstrend> Humidity <#hum>% Wind <#wspeed>mph <#wdir> (<#beaufort> <#beaudesc>)
lets set it running and see... Cumulus started 20:58ish
Update#2
ok custom message has been running since 20:58 and so far hasn't tweeted at all, turning the default back on now and first tweet pops up at 22:01, I'm guessing it will now run fine again
So it could be MY custom message is the problem (likely) or it could be Cumulus as some issue with custom messages (possibly), any ideas anyone?
My custom message (twitter.txt)
Code: Select all
#Weather #Woodley <#hour>:<#minute> <#forecast> <#temp>°C <#temptrendtext> <#rfall>mm Rain <#press>hPa <#presstrend> Humidity <#hum>% Wind <#wspeed>mph <#wdir> (<#beaufort> <#beaudesc>)
