<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EnviroDIY | Mark E. | Activity</title>
	<link>https://www.envirodiy.org/members/meliot/activity/</link>
	<atom:link href="https://www.envirodiy.org/members/meliot/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Mark E..</description>
	<lastBuildDate>Thu, 16 Apr 2026 08:36:11 -0400</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">4c5b11e4d29afe3c9f4cafb9793fc0fd</guid>
				<title>Mark E. started the topic LTE module and ArduinoHttpClient in the forum Miscellaneous</title>
				<link>https://www.envirodiy.org/topic/lte-module-and-arduinohttpclient/</link>
				<pubDate>Mon, 11 Dec 2023 23:44:45 -0500</pubDate>

									<content:encoded><![CDATA[<p>I&#8217;m connecting to the internet with the LTE Bee module and using the ArduinoHttpClient library to download a configuration file for my logger. The download works fine exactly once. After the first download, it seems like the LTE module &#8220;resets&#8221; in the sense that prior to the second download reading the signal strength returns 0% and the modem no&hellip;<span class="activity-read-more" id="activity-read-more-10010"><a href="https://www.envirodiy.org/topic/lte-module-and-arduinohttpclient/" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">09c5a627d6b59561adafcc7ef2b0d1a4</guid>
				<title>Mark E. replied to the topic Communication hardware selection advice for development in the forum Infrastructure and Equipment</title>
				<link>https://www.envirodiy.org/topic/communication-hardware-selection-advice-for-development/#post-18067</link>
				<pubDate>Mon, 18 Sep 2023 19:01:47 -0400</pubDate>

									<content:encoded><![CDATA[<p>Great! Thanks for the quick reply.</p>
<p>One followup question: I think I saw a reference in some of the documentation about the LTE module having restricted source and destination IP addresses i.e. once configured it will only work with a single destination address. Is that correct? And if so, does the WiFi Bee have a similar restriction?  (Or maybe&hellip;<span class="activity-read-more" id="activity-read-more-8883"><a href="https://www.envirodiy.org/topic/communication-hardware-selection-advice-for-development/#post-18067" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">a377cbb9df035abfdaaee55fcbe459cf</guid>
				<title>Mark E. started the topic Communication hardware selection advice for development in the forum Infrastructure and Equipment</title>
				<link>https://www.envirodiy.org/topic/communication-hardware-selection-advice-for-development/</link>
				<pubDate>Mon, 18 Sep 2023 18:47:37 -0400</pubDate>

									<content:encoded><![CDATA[<p>I may be helping a friend with some software development on a Mayfly logger. He uses an LTE Bee module in the field when his loggers are deployed, but I don&#8217;t anticipate being in the field myself. Communications in the field require IP service. Instead of using an LTE Bee module while I&#8217;m developing, I&#8217;m considering an EnviroDIY WiFi Bee module or&hellip;<span class="activity-read-more" id="activity-read-more-8881"><a href="https://www.envirodiy.org/topic/communication-hardware-selection-advice-for-development/" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">128e2c7a64da5295662b7e16d7d40968</guid>
				<title>Mark E. became a registered member</title>
				<link>https://www.envirodiy.org/activity/p/8879/</link>
				<pubDate>Mon, 18 Sep 2023 18:19:49 -0400</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>