Skip to content

How Does an RP2350 Run an MQTT Broker and Its Dashboard on a W5500 With No PC Behind It?

An RP2350-MINI(ETH) runs an MQTT broker and its live dashboard alone, splitting the W5500's eight hardware sockets into DHCP, web and five MQTT clients.

Grace_Koo

Published October 23, 2026

116 UCC

25 WCC

11 VAR

Original author: Scorch1262Original source (new tab)

How Does an RP2350 Run an MQTT Broker and Its Dashboard on a W5500 With No PC Behind It?

Components

Hardware components
W5500

WIZnet - W5500

x 1

Hardware TCP/IP, all 8 sockets via ioLibrary

WIZnet parts

Project description

📚 Context: Scorch1262/RP2350-MQTT-Dashboard-Broker-Mini-MK1 — firmware that turns a Seengreat RP2350-MINI(ETH) into the LAN's MQTT broker and serves its own live dashboard, with every TCP connection carried by the W5500's hardware sockets. 01 — What the repository builds The board is the broker. Plug in a cable, it takes an address over DHCP and registers with the router as MQTTMON-xxxxxx (the last three bytes of its MAC). MQTT clients connect to port 1883, and a browser pointed at http://<board-ip>/ gets the dashboard. The dashboard is the firmware port of the author's Python/Flask project…

Keep reading with a free account

Guests can read 15 projects per visit. Log in or create a free account to read the full description, open the documents and join the comments.

Similar projects you might like