Anthony Aufdenkampe

@aufdenkampe, any update on this?

Well, I’m back at my desk, with a Mayfly and powered it up, and I’m posting to

Host: monitormywatershed.org

and getting

— Response Code — 301 waited  326 mS Timeout 8000

If I change it to

Host: data.envirodiy.org

— Response Code — 201 waited  577 mS Timeout 8000

From   https://github.com/ODM2/ODM2DataSharingPortal/issues/542

aufdenkampe …

[Read more]

Hi @mbarney, sorry you’re experiencing difficulty after the release. @aufdenkampe, can your team take a look at this issue and this one?

Matt, to answer to your question about notification, an email was sent to all registered Monitor My Watershed users on April 5. I’ll paste in the content below in case others missed it.

Dear Monitor My…

[Read more]

Thanks for asking. The team at LimnoTech is working on a new hierarchical system for organizations that will allow for different levels of editing rights for multiple individuals. This will allow individuals other than the site owner/creator to manage the site. As I understand it, the target is to release this update by the end of the year. As for…[Read more]

@aufdenkampe, do you have any information about why certain sites are having this issue of their map marker being gray even though they’re still sending live data, or the issue of sensors not being able to be deleted from sites?

Hi @ddrummonrtp and @aufdenkampe,

I’m interested in using these mDot modules to connect with the Helium network.

Dale or Anthony, would you mind posting your code to integrate mDot modules with the Mayfly?

Thanks for your help!

Regards,

James

 
<h2 class=”user-nicename”></h2>

This looks like a common database issue that usually gets resolved by a server restart, so maybe @aufdenkampe can comment on it?

@aufdenkampe, could this be related to the recent Monitor My Watershed updates?

@shicks, thanks for your help anyway Shannon.  @aufdenkampe, any insight on the code above would be greatly appreciated.

@neilh20, yes all setups are the same.  Some work fine, others have issues with dropping out.  I have spare Mayflies and a spare CTD, but no spare turbidity sensor.  Did you ever end up producing your Mayfly wings for the 0.5…[Read more]

I am also getting “Server Error (500)” when I use the Forgot Password link in the Monitor My Watershed login form. @aufdenkampe, could it be related to this GitHub issue?

@aufdenkampe, I feel like this question has been answered before but I’m unable to find it in the forums or on GitHub. Can you please help?

Hi @aufdenkampe,

I have followed your advice and I think this is working, i.e., I am no longer having problems with -9999 values for the CTD.

However, the complex loop code is preventing publication of data to MMW.  I’m sure this is something simple, but I can’t seem to figure it out.

I have tracked the issue to the line where the code checks…[Read more]

Unfortunately, there’s currently no way to trim out unwanted datapoints from MMW, but perhaps @aufdenkampe can comment about future changes to the site that might allow this.

@aufdenkampe many thanks. Appreciate this is covering timing issues that are a bit hard to flush out.

I suppose I’m the messenger in checking the system to what appears to be the bar from the Mayfly, but its a pretty hard area to checkout – all I can say is that as the messenger I’ve seen the challenges in other systems and was trying to give…[Read more]

@aufdenkampe – I’ve confirmed that indeed, all stations are now reporting data as expected.

Thanks @aufdenkampe, that sounds like a great plan. I like the idea of the forwarding log too.

We’ll watch for a change in stations’ status once the proxy is in place.

Interesting – we have 1 site with the new LTEbee, and it also weathered the cutover successfully.

@aufdenkampe, As of now, we’re not seeing any of our Digi stations that are able to upload to the new server as a result of the temporary shutdown of your old server, assuming that that indeed took place yesterday.

Matt

We tried the Hologram SIM pause idea on one station, but it had no effect, which isn’t too surprising.

@aufdenkampe, please keep us informed about the timing of the temporary shutdown of the old server. Thanks for your efforts.

Matt

Thanks @heather, and @aufdenkampe, that does makes sense, with the symptoms we’re seeing. Good to know that the data are not being lost in the interim.

Shutting down the old server temporarily sounds like a good idea; all of our devices are on a 15-minute sampling period, so 20+ minutes should cause at least one failed message from the device,…[Read more]

@mbarney, @neilh20, thanks for your posts. The switch from the LimnoTech server to Amazon Web Services happened shortly after 13:00 EST on December 7. LimnoTech’s team is seeing that their production server is still receiving data from devices, which means that data is not going to the new AWS production. @aufdenkampe and his LimnoTech team are…[Read more]