Sara Damiano

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…[Read more]

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 SS…[Read more]

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 us…[Read more]

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:  h…[Read more]

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 usi…[Read more]

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…[Read more]

How and when did you download all of your libraries?

Are you using anything else from the Modular Sensors library? Post your entire sketch as code (use the <> button to post as code)?  Are you setting the host and port for the mqttClient? (mqttClient.setServer(ip, port)) Use your local IP there.  If you do that, I don’t see why you’re not getting a connection even with the bad DL setting in the e…[Read more]

Ooooh.. yup, there’s a bug in DigiXBeeWifi.cpp.  I’ll look into it.

Exactly which version of the library are you using (release, master branch, develop branch)?

For now, you may be able to get it working by commenting out lines ~303-310 in src/modems/DigiXBeeWifi.cpp, the section starting with “set the destination IP to 0”

If that doesn’t compile for you, update your TinyGSM library or just delete lines 87-92 to remove the forceModemBaud command, which needs the version of TinyGSM within the last few weeks.

It it’s working for you, comment out the section that resets the modem to defaults (lines 107-126) and run it one more time to get the modem to 9600. It should…[Read more]

Use 3.3V to power the WiFi bee and make sure that you’re adapter uses 3.3V logic.  The 0.5A most USB ports can provide should be enough for the WiFi bee without browning out.  You are seeing the lights on the bee go on, right?

This script worked for me to force the baud rate on three different WiFi Bee’s.  The script forces the baud rate and th…[Read more]

Once you’ve successfully changed the WiFi bee’s baud rate, it will stay at the slower baud. You should only have to reset the baud rate if you factory reset the bee or update it’s firmware – neither of which you can do by accident.

The WiFi bee should have the AT firmware on it. The problem probably is the baud rate. The default baud rate for the ESP32 (the brain on the WiFi bee) is 115200. That’s too fast for stable communication with the 8MHz Mayfly.  The Mayfly can usually *talk* fairly accurately at 115200, but it can’t listen that fast.  The auto-baud function depends o…[Read more]

Using ModularSensors doesn’t necessarily require the sensors to be directly connected to the Mayfly.  They could be, but they don’t have to be. In the case of a lot of inexpensive sensors sold as breakout boards, the Mayfly connects and talks directly to the sensor, but most of the not-bare-circuit sensors have black-box layers between the raw…[Read more]

I spent some time skimming your GitHub code for your device.  If your logger is using a simple serial protocol to communicate with your GUI controller, it should also be able to communicate with the Mayfly (with or without Modular Sensors) in the same way if you expose the Serial (or AltSoftSerial) pins.

ModularSensors already supports the MS5803…[Read more]

We don’t have any set requirements for connection.  The Mayfly can communicate with almost anything that could communicate with an Arduino-style device.  Many users opt to user our ModularSensors library to run their loggers, but that library supports many protocols.

SDI-12 devices are very common in the environmental sensing field, so we have a…[Read more]

If you’re only running the sketches from Modular Sensors, you should delete all of your libraries and download the bundle from the ModularSensors release page: https://github.com/EnviroDIY/ModularSensors/releases/tag/v0.37.0 (Direct download link:…[Read more]

How is the sensor connected? To disconnect a grove plug, squeeze the lock at the top of the white connector and pull it off.  This is the headphone (stereo) jack: https://www.envirodiy.org/product/envirodiy-grove-to-3-5mm-stereo-jack-pack-of-2/. The stereo/headphone connector is just like the one on wired headphones.

If you’re getting a “could not wake modem” error it means there’s something wrong with the modem power or connection between the modem and your main board.  Are your modem lights turning on? There should be a solid red light and a flashing blue light? Make sure your board is in the socket correctly with the cut corners at the top and all the pins…[Read more]