Heather Brooks

Reminder: we’re limiting this forum topic to non-technical questions related to the production status and availability of EnviroDIY products like the Mayfly Data Logger or its accessories.

Please post other Mayfly-related discussions separately on the Mayfly forum. We’ll move off-topic replies posted here to their own threads to preserve the…[Read more]

@brianjastram, our partners at LimnoTech believe they have resolved the affiliation issue for you. I’m adding an excerpt here for the record; please see GitHub issue #562 for the full explanation.

This site’s affiliation should be resolved. […] The short term fix is to make sure the user is affiliated with an organization, then edit the site…

[Read more]

@craig607, thank you for posting this! Would you consider expanding on it as a guest blogger here on EnviroDIY?

Thanks for the details. I’ve created a GitHub issue for this.

Thanks for that information. Next question: was the site that’s not displaying your affiliation (SAVPW-RG) created after mid-December? If it was created before the release, did the affiliation used to appear correctly and is now defaulting to “currently unaffiliated”?

@brianjastram, I want to make sure I’m understanding the problem before I post this as an issue on GitHub. Did you set up your personal account and the organizational account on Monitor My Watershed at roughly the same time? What I’m really asking is: did both accounts get created after the mid-December release that moved Monitor My Watershed to…[Read more]

I’ve opened a GitHub issue for this.

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

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 @mbarney and @w3asa, LimnoTech’s team is working hard on a fix. Please see my reply on Matt’s other post for a bit more detail.

@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]

@ayalavinay, @james-dareboprc-govt-nz: Just a heads up that a new version (v0.12) of Monitor My Watershed has just been pushed from staging to production (at ~13:15 EST today). Please look for a release post here on EnviroDIY.org in the next day or two from @aufdenkampe outlining improvements to the data portal.

Hi Fiona. We thought these were already in MonitorMW but Sara (@srgdamiano) was going to check. If they’re not, she’ll be able to add them for you. Thanks for your patience!

No worries (and you’re not alone!). If you’re uncertain about where to post, you can check the main Forums page and you’ll see the list of forums with brief descriptions. Admittedly, there is a bit of overlap for Monitor My Watershed. Others can weigh in if I’m getting this wrong, but I think if you have a Mayfly-related problem pushing your data…[Read more]

P.S. I’ve moved this topic from the Mayfly Data Logger forum to the Monitor My Watershed forum, in case other look there for this issue.

Hi Cheryl, thanks for posting. This issue was reported to the Monitor My Watershed development team yesterday. They have identified the cause and will be working to fix it today.

I believe this is the same issue that was reported here? If so, it should mostly be resolved. The browse sites feature is now working; the sparkline plots (panels) are not working but should be soon. Note that only data display was affected; Monitor My Watershed continued to collect the data. Here is the GitHub issue if you’d like more details.