Page 1 of 2
AWEKAS
Posted: Sat 31 Dec 2022 3:38 pm
by Mapantz
I just had a notification to say my station is offline..
Code: Select all
2022-12-31 15:30:01.590 AWEKAS: Exception = Type definitions should start with a '{', expecting serialized type 'AwekasResponse', got string starting with: 20221231 02:25:00 20221231 04:29:07
Code: Select all
2022-12-31 15:40:00.483 AWEKAS: Exception = Object reference not set to an instance of an object.
I have no other issues with other networks. Has anyone else got this problem?
Re: AWEKAS
Posted: Sat 31 Dec 2022 4:08 pm
by freddie
Yeah I've had this for a couple of days now - since Thursday evening. I think it may be a problem at their end as you can see the odd 500 response from their servers in MXdiags logs.
Unless they've changed their API and we don't know about the change?
Re: AWEKAS
Posted: Sat 31 Dec 2022 5:09 pm
by PaulMy
I see the same error in my current MXdiags. The oldest file in my MXdiags folder is Dec 23rd and there are no such errors in it, so fairly recent issue. The AWEKAS site seems to have all the data so uploads are ok.
Enjoy,
Paul
Re: AWEKAS
Posted: Sat 31 Dec 2022 6:04 pm
by Mapantz
My data stopped updating on their site about 5 hours ago.
Re: AWEKAS
Posted: Sat 31 Dec 2022 8:21 pm
by Mapantz
I restarted CMX, but still no data going to them. It has to be an issue their end.. oh well, no worries.
Re: AWEKAS
Posted: Sat 31 Dec 2022 8:39 pm
by mcrossley
The error I am getting intermittently is...
Code: Select all
<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h2>Request Timeout</h2>
<p>This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase 'Connection Timeout'.</p>
</body>
</html>
This is being returned instead of the correct JSON response. My data is generally updating though, just some missed updates.
Re: AWEKAS
Posted: Sat 31 Dec 2022 8:43 pm
by Mapantz
Since a restart, the only error I get is this:
Code: Select all
2022-12-31 20:40:00.365 AWEKAS: Exception = Object reference not set to an instance of an object.
Strange how everyone else's data is getting through though, and mine isn't
Re: AWEKAS
Posted: Sat 31 Dec 2022 10:02 pm
by mcrossley
That looks like a bug in that is erroring and not recovering for some reason - I'll take a look at it next year.
Re: AWEKAS
Posted: Sat 31 Dec 2022 10:06 pm
by Mapantz
mcrossley wrote: ↑Sat 31 Dec 2022 10:02 pm
I'll take a look at it next year.
Re: AWEKAS
Posted: Thu 05 Jan 2023 4:11 pm
by Mapantz
Data has stopped again, according to them.
Code: Select all
2023-01-05 15:55:00.311 AWEKAS: Exception = Object reference not set to an instance of an object.
I sent them an email last time out, and I never got a reply back.
I'll probably stop sending data to them altogether. I don't use their site to be honest, and I have found the admin to be very rude in the past.
Re: AWEKAS
Posted: Thu 05 Jan 2023 4:21 pm
by ConligWX
Re: AWEKAS
Posted: Thu 05 Jan 2023 4:33 pm
by mcrossley
I looked at the "Exception = Object reference not set to an instance of an object." - it's a spurious message that should not occur, the previous error should have exited the routine but didn't, hence the code trying access something that had not been initialised.
Fixed in the next release.
Re: AWEKAS
Posted: Fri 06 Jan 2023 12:51 am
by Mapantz
Well, I finally got a reply from the email I sent 7 days ago
Hello
Your transfer string ist corrupt. The & delimeter is missing in sailtemeratures,
Re: AWEKAS
Posted: Fri 06 Jan 2023 9:39 am
by mcrossley
Ok. I'll take a look at that. Have you just started to send soil temperatures? Or is it a new problem in the latest build?
Annoying that it coincided with the awekas server problem.
Re: AWEKAS
Posted: Fri 06 Jan 2023 10:21 am
by freddie
I've got the same problem, it started on 29th December, and they haven't received any data from me since that point. Not related to moving to the latest build. I've not changed anything at my end, apart from updating to the latest build on the 2nd. Same errors in MXdiags in both builds.