Activity

OK, looks like I still get 504 errors intermittently, even when all UUIDs are specified properly.

ending data to [ 0 ] data.envirodiy.org
POST /api/data-stream/ HTTP/1.1
Host: data.envirodiy.org
TOKEN: 
Content-Length: 274
Content-Type:…

[Read more]

I just found issue #303 on the ODM2DataSharingPortal site that may be related to my issue: I have a blank UUID in my example request, posted above. I’ll retest and report back.

Looks like it will still happen when posting to monitormywatershed.org. It’s intermittent, as before. Log file attached.

To do this test, I modified line 21 in EnviroDIYPublisher.cpp as follows:

// const char *EnviroDIYPublisher::enviroDIYHost = "data.envirodiy.org";
const char *EnviroDIYPublisher::enviroDIYHost = "monitormywatershed.org";

Matt

Hmm. I wonder if it is somehow connected to our last release on Thu. Jan. 23. As Sara mentioned, we didn’t touch the code related to the HTTP post request, but at that time we did make some changes to our virtual machine host OS and our router.

Does it make a difference if you post to monitormywatershed.org, which is now our primary hostname,…[Read more]

@aufdenkampe – any thoughts?

Postman automatically tacks on more standard http headers than I include in the post from ModularSensors.  I wonder if one of them is making a difference. In PostMan after making a request you can click the “Headers” tab and you’ll see 8 or 9 “temporary” headers that it used in addition to your token header.  M…[Read more]

I think the Hydros 21 takes half a second or so to warm up and take a sample, so it’s probably fine.  It’s turbidity sensors, sondes, and anything Yosemitech that are really the slow-pokes.

If you’re not worried about the small amount of extra data consumed on your cellular plan by those few extra characters, you could also just include the…[Read more]

In my case, any time I get a 504 response, the corresponding data do not show up on MMW. Pasting the same JSON message body into Postman and sending it always succeeds with a 201.

Hi Sara, Thanks very much for those details. I will set the updateValue flag to true for values calculated from sensor readings where we’re not also sending the non-calculated reading of the same variable. I’m doing this on the DS3231 temp as well as the Hydros-21 depth, which I’m converting from mm to inches. If you anticipate this causing any…[Read more]

I’m seeing it as well. It starts of as 201, and then after 10~2 POST starts printing 504. It has been happening from late last week – but is being recorded on MMW. I wasn’t monitoring anything early last week,

Huh.  I’m not aware of any particular reason today would be worse than any other day.  There was an update to MonitorMW released on Thursday (1/23), but it mostly dealt with Leaf Pack data and shouldn’t be affecting anything today.

The loop that requests values from sensors only queries sensors that have an associated variable in the variable list.  So if you don’t put the ds3231Temp in your variable list, the program will never actually ask the DS32321 for the temperature.  In that case, the value returned by ds3231Temp->getValue() in your calculation equation will just b…[Read more]

I’m converting the temp value coming from the DS3231 from C to F and reporting the F value to MMW. However, unless I also add the C value to the variableList array, the F value being reported is -17966.2, which doesn’t make any sense. What am I missing?

// Create a DS3231 sensor object
MaximDS3231 ds3231(1);

// Create a temperature variable…

[Read more]

We’re eagerly awaiting the new Campbell turbidity sensors which should be available in late spring or early summer.  In the meantime, there aren’t any other low cost, high quality turbidity sensors that easily interface with the Mayfly except for the Yosemitech ones, which we’re still evaluating for long term performance reliability and…[Read more]