[Heather Brooks]

@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 working diligently on a fix.

[Heather Brooks]

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

[Heather Brooks]

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!

[Heather Brooks]

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 to MonitorMW, it should be posted in the Mayfly Data Logger forum, but if it’s an issue with the MonitorMW website itself, it should go in the MonitorMW forum. Clear as mud? 🙂

[Heather Brooks]

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

[Heather Brooks]

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.

[Heather Brooks]

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.

[Heather Brooks]

@w3asa @dbressler @movingplaid Jim is correct: comments made in the activity stream on the homepage do not get applied to the forum. This is a flaw in the software that runs the activity stream. I think it is needlessly confusing so I have disabled the display of the Comment link.

[Heather Brooks]

Hi @mbarney, I’m combing through the forum topics with no replies, hoping to get some answers for folks, and found this one you posted last July. I’m sure you already discovered this, but the three example code links you listed no longer return 404s. Perhaps @srgdamiano was reorganizing the examples at the time?

• DRWI_CitSci.ino
• DRWI_LTE.ino
• DRWI_NoCellular.ino

[Heather Brooks]

James, it would be a good idea to search the issues on Monitor My Watershed’s GitHub to see if your problem has been previously reported. If it isn’t, and you are willing to create a new issue to make the development team aware, please do.

[Author]

Posts