Heather Brooks

@heather, I can confirm the fix is working and add a kudos for the swift fix implementation from LimnoTech. Thanks!

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]

Ah! Thank you @heather! I had already forgotten that notification after a week – yikes!

@heather, I would consider that. I still need to figure out the details on implementation and code.

@heather, Thanks for checking.

Both accounts were set up before the mid-December release. The personal account was around 8/13/19 and the organizational account was around 10/3/19.

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 pinging us.

As @heather mentioned, we released MonitorMW v0.12 yesterday at that time, which has some major under-the-hood improvements to substantially improve reliability, including now being hosted by AWS (zone: us-east-2; Ohio). For details read  our v0.12.0: Update to Python 3.8 & Django 2.2; Migrate to AWS…[Read more]

I was able to add it without issue. Thanks so much, @heather and @srgdamiano!

Hi @heather, Thanks for following up. All looks good to me!

Matt

@heather just FYI. I have attempted to do this on my work computer with the same result.

Is there somewhere I should log MMW problems? We often struggle with the timeseries viewer – it takes a long time to load. Is this a common problem? I thought perhaps it might be caused by our location (New Zealand).

@heather

My bad for starting this post in the wrong category. I should have paid more attention!

@shicks

Forgive my ignorance about the technical details of cellular service but …
As for “any stations currently offline right now are likely using 2G hardware…”, SL168 (Punches Run was upgraded to 4G in 2019 but was still down. If the logger…[Read more]

@heather

Since it’s not a MMW issue should I move my technical questions back to my original post on “infrastructure and equipment” forum?