Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of 
@srgdamiano
Active 4 days, 8 hours agoForum Replies Created
-
AuthorPosts
-
2026-10-01 at 12:38 PM in reply to: logger stops uploading to Monitor My Watershed at a set duration #19977
If you want the updated library, start from the examples for the updated library. It shouldn’t be too hard to update if you’ve mostly stuck to the example. A side-by-side difference viewer would help to check what you need to change. That being said, if everything was working well for you using the old version of the library, you don’t necessarily have to update. Do make sure that all of your other libraries are the expected versions for whichever version of ModularSensors you’re using.
For data you have on the SD card, you can upload it so that it appears online following these instructions: https://wikiwatershed.org/wp-content/uploads/monitor-my-watershed-quick-guide-uploading-data.pdf. NOTE: The instructions mention that there’s a file size limitation. That limitation no longer exists.
Sadly, though, if your data isn’t on the SD card and wasn’t posted online, there is no way to recover it. There is no other place the data would be stored. The SD card is the only local data storage on the Mayfly. If something happened that made the whole station go down and stop writing to the SD card, there’s nowhere to recover any data from.
For me to help fix the station so it will record and publish data again, I’ll need to know more about its current condition. Are you sure the battery is good? Have you tried turning the station back on to watch what it does on your desktop? Do the lights blink when you turn it on? Which lights? Can you connect it to a computer and share the serial monitor output?
Yes, those are because of the old firmware. If you’ve got it working, it may not be worth updating, but it should eliminate those work-around.
If you want to use custom SSL certificates, upgrade. The only way to push custom certificates with the old firmware (or with an ESP8266) is to use a python script to write the memory blocks with the new certificate data. And getting that working is much harder than upgrading the firmware. AWS IoT core requires custom certificates.
Are you using the original TinyGSM or the EnviroDIY fork? The EnviroDIY fork is far ahead of the original right now. (It’s on my to-do list to have a proper PR.)
I’d (strongly) recommend updating your AT firmware. The current version of TinyGSM on the EnivroDIY fork expects firmware >= 3.2.0.0. Because of changes in the memory mapping for SSL certificates (and other stuff) around version 3.2, you’ll need to completely re-flash the board with esptools/ESP flash download tools instead of using the AT+CIUPDATE function.
Were you able to connect to your MQTT broker?
It looks like you’re working from the modem component within Modular Sensors. That component wraps TinyGSM and adds physical pin support for power management. But the wrapping makes it a bit confusing because you have to access objects with pointers and creator functions. And if you’re trying to use the ModularSensors master branch as of 8/4/26, it’s broken. (The last release is fine, just not the current master branch.) Until you have your communication set, I would work directly from the TinyGSM example set which is more direct. After you’ve got your communication set, figure out power.
Ah. That example is written for the current “master” branch of the library, not the latest polished release. I’m way overdue for a new release, but there are some bugs I still need to fix.
Try starting from this example instead, which is matched to library release 0.37.0: https://github.com/EnviroDIY/ModularSensors/blob/v0.37.0/examples/DRWI_Mayfly1/DRWI_Mayfly1.ino
**DO NOT** use the current master branch as of 8/4/2026. There’s definitely a bug in for the SIM7080/EnviroDIY LTE module. Usually I keep the master branch functional and try to keep not-actually-working stuff in other branches, but as of today master is broken.
The ESP32 does. It’s also a currently supported product and very widely available. You can get very cheap ESP32 breakout boards in a variety of shapes and sizes. There are several flavors depending on how much power you need, but they can all do a basic secure post request. You could even use the older, even cheaper ESP8266.
If you’re using something else as the “brain” and only want to use the ESP32 (or ESP8266) as a blind modem, flash it with AT firmware and use TinyGSM. Check out the Web Client example for a hand-made post request. This is probably similar to what you were doing with the S6B. If all you need is sever certificate verification, that example should be all you need. If you need client certificate or mutual verification, I wrote up an example here of uploading new certificates to the module. You only need to upload the certificates once.
You can get a lovely ESP32 in Bee format with AT firmware pre-flashed here: https://www.envirodiy.org/product/envirodiy-esp32-bee-wifi-bluetooth/
If you don’t want to use a second board as the brain, there are zillions of examples on the web of people using ESP32’s to do all kinds of cool things. They’re very heavily used in home automation and are quite powerful. Buy any breakout format you want.
No. The S6B (wifi) does not support secure clients.
From your error messages, it looked like you have mismatched versions of libraries. I’m not sure how permissions are set up on your PC, but typically the Arduino libraries would be stored in a personal user folder that you could change at will.
How and when did you download all of your libraries?
-
AuthorPosts
