Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
An error has occurred - please zip up the MXdiags folder and post it in the forum
Moderator: mcrossley
-
- Posts: 41
- Joined: Tue 21 Jun 2011 7:50 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Tiverton, UK
An error has occurred - please zip up the MXdiags folder and post it in the forum
Well, I made the switch to Cumulus MX about a month back. All worked well and seems to be running happily on a standalone machine under Windows 10. I have MX build 3043.
This week I decided to set up some FTP space on my personal website and get CumulusMX to drive that. All seemed to go OK apart from the gauges page. A bit of investigation revealed that realtimesettings.txt was not being copied over. I did this manually and suddenly that seems to be working permanently.
So my last tweak was to set up a feed to Twitter. This has been unsuccessful.
I took another look at the command console and discovered several pages of error message ending in the line:
An error has occurred - please zip up the MXdiags folder and post it in the forum
Reading the messages I suspect that there is a problem with the Twitter stuff although I cannot be certain. I did remove all the Twitter settings, stopped CumulusMX, edited the Cumulus.ini file to remove the OAuth and OAuthSecret tokens. Reset my Twitter password. Re-entered the Twitter settings in MX and restarted. In due course the errors reappeared.
So I've done what the program requested and zipped up the MXdiags folder and it is attached along with a capture of the error text from the console.
Being only slightly competent to read these files it seems to suggest that Twitter is refusing a connection from CumulusMX with an error 87 - 'Client is not permitted to perform this action'.
I've disabled Twitter posting for now and the errors have not been seen so far.
Anyone with insight able to help me diagnose this?
Andrew
This week I decided to set up some FTP space on my personal website and get CumulusMX to drive that. All seemed to go OK apart from the gauges page. A bit of investigation revealed that realtimesettings.txt was not being copied over. I did this manually and suddenly that seems to be working permanently.
So my last tweak was to set up a feed to Twitter. This has been unsuccessful.
I took another look at the command console and discovered several pages of error message ending in the line:
An error has occurred - please zip up the MXdiags folder and post it in the forum
Reading the messages I suspect that there is a problem with the Twitter stuff although I cannot be certain. I did remove all the Twitter settings, stopped CumulusMX, edited the Cumulus.ini file to remove the OAuth and OAuthSecret tokens. Reset my Twitter password. Re-entered the Twitter settings in MX and restarted. In due course the errors reappeared.
So I've done what the program requested and zipped up the MXdiags folder and it is attached along with a capture of the error text from the console.
Being only slightly competent to read these files it seems to suggest that Twitter is refusing a connection from CumulusMX with an error 87 - 'Client is not permitted to perform this action'.
I've disabled Twitter posting for now and the errors have not been seen so far.
Anyone with insight able to help me diagnose this?
Andrew
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
It could be that Twitter have changed their API (again) and Cumulus breaks the new rules. I'll see if I can find anything about this. It would be useful if someone using MX and Twitter could reply to say whether it still works for them.
Has MX managed to get the tokens again?
Has MX managed to get the tokens again?
Steve
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Found it. As of June 30th they have withdrawn support for xAuth, which is the mechanism Cumulus uses for authentication. The problem is that they really don't cater properly for applications which do Twitter updates automatically like Cumulus. They do have an alternative mechanism called 'PIN based authorization' which would require Cumulus to display a URL to the user which they would then put in a browser, receive a PIN, and then enter that PIN into Cumulus.
Steve
-
- Posts: 2547
- Joined: Wed 08 Jun 2011 11:19 am
- Weather Station: Davis Vantage Pro 2 + Ecowitt
- Operating System: GNU/Linux Ubuntu 22.04 LXC
- Location: Alcaston, Shropshire, UK
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
It works for me - hourly updates. https://twitter.com/FishpoolFarmWxsteve wrote:It could be that Twitter have changed their API (again) and Cumulus breaks the new rules. I'll see if I can find anything about this. It would be useful if someone using MX and Twitter could reply to say whether it still works for them.
Last edited by freddie on Sun 09 Jul 2017 9:04 pm, edited 1 time in total.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Thanks - I think it's the initial setup that's affected, obtaining the tokens. But I can't remember the full details of how it works, it was stupidly complicated even before this latest change.
Steve
- PaulMy
- Posts: 3907
- Joined: Sun 28 Sep 2008 11:54 pm
- Weather Station: Davis VP2 Plus 24-Hour FARS
- Operating System: Windows8 and Windows10
- Location: Komoka, ON Canada
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
VP2+
C1 www.komokaweather.com/komokaweather-ca
MX https://komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX https://komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX https:// komokaweather.com/cumulusmx4/index.htm
C1 www.komokaweather.com/komokaweather-ca
MX https://komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX https://komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX https:// komokaweather.com/cumulusmx4/index.htm
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Cumulus 1 should have the same problem. I'll do some experimenting tomorrow to see what happens if I delete my tokens. I strongly advise that no-one else tries this! If it's working for you, leave it well alone.
Steve
-
- Posts: 41
- Joined: Tue 21 Jun 2011 7:50 am
- Weather Station: Davis Vantage Vue
- Operating System: Windows 10
- Location: Tiverton, UK
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Thanks Steve. I'm pleased that I was reading the errors correctly but sorry that you have more work again
OAuthToken/OAuthSecretToken=unknown
Andrew
OAuthToken/OAuthSecretToken=unknown
Andrew
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
I can confirm that it's the initial obtaining of the tokens which no longer works. If you already have tokens, updates still work OK.
Steve
-
- Posts: 214
- Joined: Tue 24 Nov 2015 11:30 pm
- Weather Station: Fine Offset & Davis Vantage Vue
- Operating System: Windows 10; Raspbian Buster
- Location: Switzerland
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
My tweets were working fine until I broke the SD card and had to reinstall. Now, even though I have a note of the previously-working tokens, I can't get it to restart. Any suggestions?
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Perhaps the tokens encode some information about the installation, I don’t really know.
Steve
-
- Posts: 214
- Joined: Tue 24 Nov 2015 11:30 pm
- Weather Station: Fine Offset & Davis Vantage Vue
- Operating System: Windows 10; Raspbian Buster
- Location: Switzerland
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Thanks for trying. The tokens - as I understand it - give your twitter app "Sandaysoft Cumulus" permission to access (ie write to) my twitter account, but without me telling you my username and password. I'm guessing that Cumulus uses the username and password when trying to get tokens (the feature known to not work), but then does not need them any more (which is why if we change either username or password we were told to delete the tokens and let them be regenerated).
Further information. When I run with no OAuth tokens, I get as follows (red added by me):
pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:02:09
Type Ctrl-C to terminate
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Error: SendFailure (Error writing headers) ---> System.Net.WebException: Error writing headers ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (IAsyncResult result) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult, System.Net.TransportContext& context) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback (IAsyncResult ar) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+<UpdateTwitter>d__479.MoveNext () [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate
The file in MXdiags has exactly the same information, no more or less.
But if I run with my previously working OAuth tokens, I get no error messages here; but there are errors noted in MXdiags
pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:04:49
Type Ctrl-C to terminate
From MXdiags:
2018-05-06 23:04:51.649 End of PWS archive upload
2018-05-06 23:05:02.263 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:06:00.346 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:07:00.486 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:08:00.345 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:09:00.316 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:10:00.110 Writing log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.114 Written log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.128 Writing today.ini, LastUpdateTime = 06/05/2018 23:10:00 raindaystart = 3126 rain counter = 3126
2018-05-06 23:10:00.138 Latest reading: 7960: 04 27 EB 00 55 B2 00 A0 24 00 0A 00 00 B4 28 00
2018-05-06 23:10:00.408 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:11:00.334 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:12:00.376 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:13:00.385 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:14:00.394 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:15:00.370 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:16:00.534 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:17:00.424 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:18:00.529 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:19:00.452 UpdateTwitter: An error occurred while sending the request.
Maybe the problem is that (following earlier suggestions) I revoked access to my Twitter account by your app "Sandaysoft Cumulus"; it now no longer appears on my list of apps. Any ideas how reinstate access? I don't remember ever giving access permission
Further information. When I run with no OAuth tokens, I get as follows (red added by me):
pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:02:09
Type Ctrl-C to terminate
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Error: SendFailure (Error writing headers) ---> System.Net.WebException: Error writing headers ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (IAsyncResult result) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult, System.Net.TransportContext& context) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback (IAsyncResult ar) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+<UpdateTwitter>d__479.MoveNext () [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate
The file in MXdiags has exactly the same information, no more or less.
But if I run with my previously working OAuth tokens, I get no error messages here; but there are errors noted in MXdiags
pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:04:49
Type Ctrl-C to terminate
From MXdiags:
2018-05-06 23:04:51.649 End of PWS archive upload
2018-05-06 23:05:02.263 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:06:00.346 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:07:00.486 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:08:00.345 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:09:00.316 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:10:00.110 Writing log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.114 Written log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.128 Writing today.ini, LastUpdateTime = 06/05/2018 23:10:00 raindaystart = 3126 rain counter = 3126
2018-05-06 23:10:00.138 Latest reading: 7960: 04 27 EB 00 55 B2 00 A0 24 00 0A 00 00 B4 28 00
2018-05-06 23:10:00.408 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:11:00.334 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:12:00.376 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:13:00.385 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:14:00.394 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:15:00.370 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:16:00.534 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:17:00.424 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:18:00.529 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:19:00.452 UpdateTwitter: An error occurred while sending the request.
Maybe the problem is that (following earlier suggestions) I revoked access to my Twitter account by your app "Sandaysoft Cumulus"; it now no longer appears on my list of apps. Any ideas how reinstate access? I don't remember ever giving access permission
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
That may be the problem, but I don’t know how you would reinstate it, sorry.
Steve
- mcrossley
- Posts: 12966
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
Qualifier: I have no idea what I am talking about! But...
There is a twitter apps page https://apps.twitter.com/ where you can register your own apps - is that of any use?
There is a twitter apps page https://apps.twitter.com/ where you can register your own apps - is that of any use?
-
- Posts: 214
- Joined: Tue 24 Nov 2015 11:30 pm
- Weather Station: Fine Offset & Davis Vantage Vue
- Operating System: Windows 10; Raspbian Buster
- Location: Switzerland
Re: An error has occurred - please zip up the MXdiags folder and post it in the forum
I accidentally thought that too and made one. But no, that's not what's wanted. Cumulus needs to access the "Sandaysoft Cumulus" app not one I made myself. Tough luck .mcrossley wrote:There is a twitter apps page https://apps.twitter.com/ where you can register your own apps - is that of any use?
Nice web page you have btw - I plan copying bits of it when I get time.
How's Macc? I used to work at AstraZeneca !