Cumulus Support

This time the OauthToken seem OK. Twitter is enabled.

[Twitter]
User=xxxxxxxxxxxxxxxx
Password=xxxxxxxxxxx
Enabled=1
Interval=12
OauthToken=xxxxxxxx
OauthTokenSecret=xxxxxxxx

It's updating OK for me, and no-one else has a problem, so it's nothing to do with 1.9.1.

Look in the latest diags file to see if there are any Twitter error messages; turn on the debug log, and see if there are any Twitter error messages in there. You could also try deleting the OauthToken and OauthTokenSecret lines from cumulus.ini (with Cumulus stopped) to make it fetch new ones, to see if that helps.

in cumulus.009:

after
30/04/11 09:46:39.437 : Station settings done

30/04/11 09:47:17.750 : HTTP/1.1 401 Unauthorized
30/04/11 09:48:15.640 : HTTP/1.1 401 Unauthorized
30/04/11 09:49:14.781 : HTTP/1.1 401 Unauthorized
30/04/11 09:50:16.453 : HTTP/1.1 401 Unauthorized
etc...

Web site, PWS, APRS and WU are OK

Twitter ID and password rechecked and OK

[Twitter]
User=xxxxxxxxxxxxxxxx
Password=xxxxxxxxxxxx
Enabled=1
Interval=1
OauthToken=xxxxxxxx
OauthTokenSecret=xxxxxxxx

Twitter is saying that your login details are invalid. Have you changed your Twitter user or password? Did deleting the OAuth tokens not help?

ID and password checked OK and the same; OAuth tokens are new.

So you haven't changed your Twitter user or password recently? Have you tried deleting the OAuth token lines from cumulus.ini - with Cumulus stopped? If your Twitter user or password change, the OAuth tokens are no longer valid and a new set have to be created.

The problem must be something specific to your Twitter account, because I don't have the problem and no-one else seems to be reporting a problem.

By the way, there is a Twitter limit of 1000 status updates per day (with corresponding limits per half hour, i.e approx 20 per half hour). You have an interval of one minute, so you will be exceeding these limits.

I set it up to 1 minute for testing only; I use to update at 12 minutes intervals. I can send you my twitter.txt content and a temporary password if you want to give a try!

Angile wrote:I set it up to 1 minute for testing only; I use to update at 12 minutes intervals. I can send you my twitter.txt content and a temporary password if you want to give a try!

Yes, that's a good idea.

Something new (strange)

I changed my "twitter.txt" content to "TEST 123" only and the message went good.

My usual "twitter.txt" content use to hold some word with french accent. Could this be the problem? This file was use with the previous version with issue.

Angile wrote:My usual "twitter.txt" content use to hold some word with french accent. Could this be the problem?

Almost certainly. Version 1.9.1 is fully unicode, so it's possible that non-ansi characters are causing the encoding to go wrong.

Well Steve, we found the problem, the message is going OK if I remove the french accents in my twitter.txt file. Something must have been change in your new code; the new 1.9.1 version doesn't like "accents" as prior version did recongnize them.

Also, the <#currcond> variable do recongnize the accents and show them on Twitter. Only the text included in twitter.txt does not any more.


Temperature actuelle : 18.5 ºC, Humidite : 31 %, Vent : 3.6 km/hre ENE, Pluie tombee : 0.0 mm, Ciel : ensoleillé 14:11 H.A.E.

Angile wrote:Also, the <#currcond> variable do recongnize the accents and show them on Twitter. Only the text included in twitter.txt does not any more.

Can you explain what you mean by this? Do you mean that if you put <#currcond> which has accented characters into a twitter.txt, it works OK, but accented characters directly in the twitter.txt file do not?

Could you zip up your original twitter.txt and attach it, please?

Have you receive my PM?