Thank you for your feedback, Duane. As the php versions increase, the installation procedure may require installing a new one because Grocy has strict requirements. I hope the developer will include a docker version in the near future, as a docker container also solves the version issues

Installing PHP 8.5 on Debian 13 (Trixie)
To install PHP 8.5 on Debian 13, follow these steps:

Prerequisites
Ensure you have root access or a user with sudo privileges.
Update your system packages.
Step-by-Step Installation
Update Package Index Run the following command to update your package index:
sudo apt update

Install Required Dependencies Install necessary packages for adding external repositories:
sudo apt install lsb-release ca-certificates curl apt-transport-https -y

Add the Sury PHP Repository This repository contains the latest PHP versions. Execute the following commands:
curl -fsSL https://packages.sury.org/php/apt.gpg -o /usr/share/keyrings/sury-php.gpg

echo "deb [signed-by=/usr/share/keyrings/sury-php.gpg] https://packages.sury.org/php/ $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/php.list

Update Package Index Again After adding the repository, update the package index again:
sudo apt update

Install PHP 8.5 Now, install PHP 8.5 with the following command:
sudo apt install php8.5 -y

Install Common PHP Extensions If you need common extensions, you can install them using:
sudo apt install php8.5-{cli,common,curl,mbstring,xml,zip,gd,intl,mysql,opcache} -y

Verify PHP Installation Check the installed PHP version to confirm the installation:
php -v

Optional: Install PHP-FPM
If you are using Nginx or Apache with PHP-FPM, install it with:
sudo apt install php8.5-fpm -y

Enable and start the service:
sudo systemctl enable php8.5-fpm
sudo systemctl start php8.5-fpm

You have now successfully installed PHP 8.5 on Debian 13 (Trixie). Configure your web server to use PHP and start deploying your applications.

thank you for your feedback!

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

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: . 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’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.

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 (https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/).
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.
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’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

I’ve been working on a door access control system using the PICO and WIZNET Ethernet hat, I really like both devices. However, I can’t get the Ethernet have to connect at 100Mb/s, ( it’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’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’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