<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for peppe8o	</title>
	<atom:link href="https://peppe8o.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://peppe8o.com/</link>
	<description>Raspberry PI, Arduino and Electronics made simple</description>
	<lastBuildDate>Fri, 15 May 2026 13:18:09 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		Comment on How to Use a Photoresistor From Raspberry PI To Detect Light with Python by peppe8o		</title>
		<link>https://peppe8o.com/using-photoresistor-from-raspberry-pi-to-detect-light/#comment-82818</link>

		<dc:creator><![CDATA[peppe8o]]></dc:creator>
		<pubDate>Fri, 15 May 2026 13:18:09 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=1998#comment-82818</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://peppe8o.com/using-photoresistor-from-raspberry-pi-to-detect-light/#comment-82813&quot;&gt;Hunter&lt;/a&gt;.

thank you for your feedback!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://peppe8o.com/using-photoresistor-from-raspberry-pi-to-detect-light/#comment-82813">Hunter</a>.</p>
<p>thank you for your feedback!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on How to Use a Photoresistor From Raspberry PI To Detect Light with Python by Hunter		</title>
		<link>https://peppe8o.com/using-photoresistor-from-raspberry-pi-to-detect-light/#comment-82813</link>

		<dc:creator><![CDATA[Hunter]]></dc:creator>
		<pubDate>Fri, 15 May 2026 12:38:37 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=1998#comment-82813</guid>

					<description><![CDATA[Thanks for the tip on pin_factory. My red/green led and photoresistor test was dead at 0.0 until that fix]]></description>
			<content:encoded><![CDATA[<p>Thanks for the tip on pin_factory. My red/green led and photoresistor test was dead at 0.0 until that fix</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Manage Raspberry PI GPU Memory Split by peppe8o		</title>
		<link>https://peppe8o.com/manage-raspberry-pi-gpu-memory-split/#comment-82189</link>

		<dc:creator><![CDATA[peppe8o]]></dc:creator>
		<pubDate>Sun, 03 May 2026 16:50:01 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=3394#comment-82189</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://peppe8o.com/manage-raspberry-pi-gpu-memory-split/#comment-82123&quot;&gt;Pinocchio&lt;/a&gt;.

Hi. A common GPU resize need is when you want to reduce GPU memory (not increasing it). So, I tested it (with Raspberry PI up to 4 models) to set GPU memory to 16 or 32 MB]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://peppe8o.com/manage-raspberry-pi-gpu-memory-split/#comment-82123">Pinocchio</a>.</p>
<p>Hi. A common GPU resize need is when you want to reduce GPU memory (not increasing it). So, I tested it (with Raspberry PI up to 4 models) to set GPU memory to 16 or 32 MB</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Manage Raspberry PI GPU Memory Split by Pinocchio		</title>
		<link>https://peppe8o.com/manage-raspberry-pi-gpu-memory-split/#comment-82123</link>

		<dc:creator><![CDATA[Pinocchio]]></dc:creator>
		<pubDate>Sat, 02 May 2026 09:52:36 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=3394#comment-82123</guid>

					<description><![CDATA[What system memory size did you test this with? The gpu_mem_### parameters behave like conditional overrides depending on the total RAM (e.g., 256/512/1024 MB), and each requires an explicit value that defines the amount of memory reserved for the GPU.&quot;]]></description>
			<content:encoded><![CDATA[<p>What system memory size did you test this with? The gpu_mem_### parameters behave like conditional overrides depending on the total RAM (e.g., 256/512/1024 MB), and each requires an explicit value that defines the amount of memory reserved for the GPU.&#8221;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Use Ecoflow API from Raspberry PI with N8N: Monitor and Control your Photovoltaic System by peppe8o		</title>
		<link>https://peppe8o.com/ecoflow-api-raspberry-pi-n8n/#comment-79377</link>

		<dc:creator><![CDATA[peppe8o]]></dc:creator>
		<pubDate>Tue, 17 Mar 2026 19:55:50 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=15961#comment-79377</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://peppe8o.com/ecoflow-api-raspberry-pi-n8n/#comment-79219&quot;&gt;Björn&lt;/a&gt;.

Hi Björn,
I got it working with some tests (at least to change the backup value). You can get my workflow from my download area at this link: &lt;a href=&quot;https://peppe8o.com/download/docker/n8n/ecoflow_stream_command_test.json&quot; rel=&quot;ugc&quot;&gt;&lt;/a&gt;. From the resulting script, you must change the following values with your one:
my_access_key
my_secret_key
my_serial_number
Soc_backup_value (this value is included 2 times)

Then you can import the resulting JSON file in your N8N and try it. It isn&#039;t still in the best version, but it can be a start point.
In a few words, you must change the URL string and include the same query both in the secret and the HTTP PUT body.

Hope this helps you.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://peppe8o.com/ecoflow-api-raspberry-pi-n8n/#comment-79219">Björn</a>.</p>
<p>Hi Björn,<br />
I got it working with some tests (at least to change the backup value). You can get my workflow from my download area at this link: <a href="https://peppe8o.com/download/docker/n8n/ecoflow_stream_command_test.json" rel="ugc"></a>. From the resulting script, you must change the following values with your one:<br />
my_access_key<br />
my_secret_key<br />
my_serial_number<br />
Soc_backup_value (this value is included 2 times)</p>
<p>Then you can import the resulting JSON file in your N8N and try it. It isn&#8217;t still in the best version, but it can be a start point.<br />
In a few words, you must change the URL string and include the same query both in the secret and the HTTP PUT body.</p>
<p>Hope this helps you.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Use Ecoflow API from Raspberry PI with N8N: Monitor and Control your Photovoltaic System by Björn		</title>
		<link>https://peppe8o.com/ecoflow-api-raspberry-pi-n8n/#comment-79219</link>

		<dc:creator><![CDATA[Björn]]></dc:creator>
		<pubDate>Sun, 15 Mar 2026 14:54:57 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=15961#comment-79219</guid>

					<description><![CDATA[Hello! Thank you for the great instructions. I have an Ecoflow Stream AC Pro and Ultimate. So far, I&#039;ve only been able to query the device list and the device itself. Have you found a way to change the state of charge or the SOC limit? I can&#039;t find any information on how to do this. All my attempts fail with an error message about an incorrect string.]]></description>
			<content:encoded><![CDATA[<p>Hello! Thank you for the great instructions. I have an Ecoflow Stream AC Pro and Ultimate. So far, I&#8217;ve only been able to query the device list and the device itself. Have you found a way to change the state of charge or the SOC limit? I can&#8217;t find any information on how to do this. All my attempts fail with an error message about an incorrect string.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Raspberry PI Pico Ethernet Port: adding the WIZNET Ethernet HAT by peppe8o		</title>
		<link>https://peppe8o.com/raspberry-pi-pico-ethernet-port-adding-the-wiznet-ethernet-hat/#comment-79205</link>

		<dc:creator><![CDATA[peppe8o]]></dc:creator>
		<pubDate>Sun, 15 Mar 2026 11:25:33 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=5331#comment-79205</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://peppe8o.com/raspberry-pi-pico-ethernet-port-adding-the-wiznet-ethernet-hat/#comment-79203&quot;&gt;APL&lt;/a&gt;.

Hi Paul. I think the speed you achieved is already a good number and it is similar to a test from another user on the Wiznet blog (&lt;a href=&quot;https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/&quot; target=&quot;_blank&quot; rel=&quot;nofollow ugc&quot;&gt;https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/&lt;/a&gt;).
On the theory side, the Pico runs at 125MHz (125Mbps), but the SPI clock divides this by 2 (to get a clean signal border) -&gt; now around 60Mbps. On top of this, internal buffers (shared between the CPU sockets) gives you another limitation.
Another limitation comes from the MicroPython framework, which takes a number of cycles to send a bit on the wire. For example, if you would transmit data from a C firmware I think it would give you a some speed improvements, but you would lose the MicroPython simplicity and you wouldn&#039;t get so big speed improvements.

At the end, i think thath reaching 8-10 Mbps is a great result for Raspberry Pi Pico with the WIZnet Ethernet HAT]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://peppe8o.com/raspberry-pi-pico-ethernet-port-adding-the-wiznet-ethernet-hat/#comment-79203">APL</a>.</p>
<p>Hi Paul. I think the speed you achieved is already a good number and it is similar to a test from another user on the Wiznet blog (<a href="https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/" target="_blank" rel="nofollow ugc">https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/</a>).<br />
On the theory side, the Pico runs at 125MHz (125Mbps), but the SPI clock divides this by 2 (to get a clean signal border) -> now around 60Mbps. On top of this, internal buffers (shared between the CPU sockets) gives you another limitation.<br />
Another limitation comes from the MicroPython framework, which takes a number of cycles to send a bit on the wire. For example, if you would transmit data from a C firmware I think it would give you a some speed improvements, but you would lose the MicroPython simplicity and you wouldn&#8217;t get so big speed improvements.</p>
<p>At the end, i think thath reaching 8-10 Mbps is a great result for Raspberry Pi Pico with the WIZnet Ethernet HAT</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Raspberry PI Pico Ethernet Port: adding the WIZNET Ethernet HAT by APL		</title>
		<link>https://peppe8o.com/raspberry-pi-pico-ethernet-port-adding-the-wiznet-ethernet-hat/#comment-79203</link>

		<dc:creator><![CDATA[APL]]></dc:creator>
		<pubDate>Sun, 15 Mar 2026 09:55:13 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.com/?p=5331#comment-79203</guid>

					<description><![CDATA[Hello Peppe80,

I&#039;ve been working on a door access control system using the PICO and WIZNET Ethernet hat, I really like both devices. However, I can&#039;t get the Ethernet have to connect at 100Mb/s, ( it&#039;s fine at 10Mb/s ) and this is not a problem for my application using MQTT, but the system is up and running, but the 10Mb/s connection speed is an itch I&#039;d like to scratch. Have you noticed the same behaviour ? Or is it just a problem between my Wiznet and TPLink swich ?

About my project: I have a Pico 2 with a Wiznet hat managing a cheap ( from Amazon ) RFID card reader over the Weigand protocol. The PICO sends MQTT requests when a Card is presented to a back-end system that interfaces with a MySQL db that provides user authorisation, and card validity. Once the credentials are authorised, the Acknowledge  is sent back to the card reader, but also to another PICO and WIznet device to manage the electronic door lock. This is because the external card reader is physically distant from the internal door lock. 

Next thing, I&#039;d like to try is audio, since the PICO 2 is idle 99% of the time, I think it could handle digitised speech too.

Anyway, interested to hear your feedback on the WIZnet 10/100 Mb/s issue]]></description>
			<content:encoded><![CDATA[<p>Hello Peppe80,</p>
<p>I&#8217;ve been working on a door access control system using the PICO and WIZNET Ethernet hat, I really like both devices. However, I can&#8217;t get the Ethernet have to connect at 100Mb/s, ( it&#8217;s fine at 10Mb/s ) and this is not a problem for my application using MQTT, but the system is up and running, but the 10Mb/s connection speed is an itch I&#8217;d like to scratch. Have you noticed the same behaviour ? Or is it just a problem between my Wiznet and TPLink swich ?</p>
<p>About my project: I have a Pico 2 with a Wiznet hat managing a cheap ( from Amazon ) RFID card reader over the Weigand protocol. The PICO sends MQTT requests when a Card is presented to a back-end system that interfaces with a MySQL db that provides user authorisation, and card validity. Once the credentials are authorised, the Acknowledge  is sent back to the card reader, but also to another PICO and WIznet device to manage the electronic door lock. This is because the external card reader is physically distant from the internal door lock. </p>
<p>Next thing, I&#8217;d like to try is audio, since the PICO 2 is idle 99% of the time, I think it could handle digitised speech too.</p>
<p>Anyway, interested to hear your feedback on the WIZnet 10/100 Mb/s issue</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Security Camera with Raspberry Pi Using Motioneye by peppe8o		</title>
		<link>https://peppe8o.com/raspberry-pi-motioneye/#comment-77035</link>

		<dc:creator><![CDATA[peppe8o]]></dc:creator>
		<pubDate>Wed, 28 Jan 2026 22:16:58 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.ddns.net/?p=388#comment-77035</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://peppe8o.com/raspberry-pi-motioneye/#comment-77034&quot;&gt;Andy&lt;/a&gt;.

Glad it helped you too, Andy. Thank you for your feedback!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://peppe8o.com/raspberry-pi-motioneye/#comment-77034">Andy</a>.</p>
<p>Glad it helped you too, Andy. Thank you for your feedback!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Security Camera with Raspberry Pi Using Motioneye by Andy		</title>
		<link>https://peppe8o.com/raspberry-pi-motioneye/#comment-77034</link>

		<dc:creator><![CDATA[Andy]]></dc:creator>
		<pubDate>Wed, 28 Jan 2026 21:03:42 +0000</pubDate>
		<guid isPermaLink="false">https://peppe8o.ddns.net/?p=388#comment-77034</guid>

					<description><![CDATA[Worked perfectly on Pi 3b , Bookworm Lite 64bit , Official raspberry pi camera 3. Thank you!]]></description>
			<content:encoded><![CDATA[<p>Worked perfectly on Pi 3b , Bookworm Lite 64bit , Official raspberry pi camera 3. Thank you!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
