CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water. 
Community Activity See all activity
Elliot Ma replied to the topic Could not wake modem for clock sync in the forum Mayfly Data Logger 1 year, 11 months ago
Also double checked hologram.io to check to see if the sim is active, it is. I’ve also tried swapping the battery out, taking the sd card in/out, and have messed around with
const int8_t modemVccPin = 18;
and have swapped it from 18 to -1 as per the commented code, but it has not worked.
Elliot Ma started the topic Could not wake modem for clock sync in the forum Mayfly Data Logger 1 year, 11 months ago
Hi,
Continuing to run into a problem connecting our Mayfly to LTE, getting an error: “Could not wake modem for clock sync”.
I’ve seen this posted a lot but I still can’t find any concrete reasons as to why I’m getting this error. I’m using the “DRWI_SIM7080LTE” sample sketch and using a HYDROS 21 to connect.
I’ve generated, formatted, and…[Read more]
Heather Brooks replied to the topic Changes coming January 1, 2024 for Monitor My Watershed users in the forum Monitor My Watershed 1 year, 11 months ago
Hi Paul! Thanks for suggesting a biennial subscription. I’ve added it as an option for each of the plan levels.
You have the ability to modify your subscription, so if you need to change to an annual plan after two years, you can do that from your Monitor My Watershed Shop account.
Elliot Ma replied to the topic Buying new batteries + sim card problems in the forum Mayfly Data Logger 1 year, 11 months ago
Nevermind! We’ll just buy the 6600 mAh battery
Elliot Ma started the topic Buying new batteries + sim card problems in the forum Mayfly Data Logger 1 year, 11 months ago
Hi,
We’re looking to buy new 3.7 V 4400 mAh batteries for our Mayfly 1.1 and it seems that both the Adafruit and the Digikey vendors on the parts list table are both sold out. Any recommendations on replacement batteries that we could look for or are we okay with buying any general 3.7 V 4400 mAh batteries we can find that have similar…[Read more]
Paul Wilson replied to the topic Changes coming January 1, 2024 for Monitor My Watershed users in the forum Monitor My Watershed 1 year, 11 months ago
I’m thinking ahead to 2025 and beyond. I have funds available until early next year (2025) that I can use to pay for EnviroDIY web hosting. My question is can I pay a year in advance? For example in December 2024 can I pay for both 2025 and 2026 (Medium annual plan) OR is it only possible to pay for 2025 at that time. Thanks. Paul
pkbellamy became a registered member 1 year, 11 months ago
pkbellamy
@pkbellamy
D_Manning replied to the topic Artifactual troughs and flickers in recorded stream depth in the forum Monitor My Watershed 1 year, 11 months ago
No luck. I disconnected the solar panel, but am still seeing artifactual troughs. It’s reminiscent of the much more extreme variations in reported stream depth for the Pine Creek station, which calmed with a new sensor. The latter might have been related to a frayed wire from the sensor, I’m not sure.
KKMaier became a registered member 1 year, 11 months ago
KKMaier
@kkmaier
neilh20 replied to the topic New Xbee Modem: XB3-C-GM1-UT-001 in the forum Mayfly Data Logger 1 year, 11 months ago
Oh interesting, Thanks for sharing, Sounds like it connected some of the time, showing that it was possible to connect. I’ve found there are four source of failure – setup to cell tower, TCP/IP setup, POST ack, MMW timeout,
I found this hardware data sheet – but it turns out there is a GM1 and GM2 – GM1 is the low power. I wonder which o…[Read more]