Wiznet makers

What the Project Does

Node-REDscape brings multiple puzzle devices in an escape room into a single operating system. Physical devices such as buttons, RFID readers, switches, sensors, and relays are connected to prop controllers, and each controller exchanges messages with the Node-RED server.

The operator can start or stop the game from the Node-RED dashboard, manage the timer, manually mark a specific prop as solved, or reset it. During the game, events generated by props enter the Node-RED flow, and the flow triggers actions such as the next puzzle, hint output, lighting, or sound.

This structure is especially useful for commercial escape rooms. The system is not just a one-time demo; it must support repeated game sessions throughout the day. Prop status monitoring, forced reset, manual intervention, and network status checks directly affect operational quality.

Image source: AI-generated

Image source: https://github.com/playfultechnology/node-redscape

Where WIZnet Fits

The WIZnet product identified in this project is the W5500. The repository includes a wiring document for connecting an ESP32 and W5500 over wired Ethernet, and the ESP32 Ethernet example uses a UDP-based button prop controller structure.

The W5500 sits between the prop controller and the escape room’s internal LAN. The MCU handles button input or puzzle state, while the W5500 handles Ethernet communication over SPI. The Node-RED server receives these network messages and reflects them in the dashboard and game flow.

For commercial installations, wired Ethernet can be a more stable choice than Wi-Fi. Room structure, metal props, visitors’ smartphones, and multiple wireless access points can make Wi-Fi quality inconsistent. The W5500 provides hardware TCP/IP offload, a 32 KB internal buffer, and 8 sockets, making it easier to build reliable networked props even with small MCUs.

Implementation Notes

The example code in this repository does not directly call a low-level W5500 driver. Instead, it uses Arduino-style Ethernet APIs, while the W5500 operates as the hardware layer that provides wired network connectivity.

File path: ESP32/Ethernet/PropControl_UDP_Button/PropControl_UDP_Button.ino
Role: Configures the button prop’s network ID, IP address, UDP server, port, button pin, and Ethernet CS pin.

const char* deviceID = "Button-1";
byte mac[] = {0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED};

const IPAddress localIPAddress(192, 168, 1, 177);
const char* remoteUDPServer = "192.168.0.114";

const int remoteUDPPort = 161;
const int localUDPPort = 161;

const byte buttonPin = 16;
const byte ssPin = 5;

This configuration makes a single button prop identifiable as a network device. deviceID is the name used to distinguish the prop in Node-RED, and remoteUDPServer is the address of the Node-RED server. ssPin is the SPI chip-select pin between the ESP32 and the W5500 Ethernet module.

File path: Node-RED/NodeREDscape_Prop_Button_flow.json
Role: Receives MQTT/UDP messages from the prop and sends RESET or SOLVE commands back to the prop from the operator dashboard.

"topic": "FromDevice/Button-1",
"type": "mqtt in",
"name": "MQTT FromDevice"

"port": "161",
"type": "udp in"

"payload": "{\"command\":\"RESET\"}"
"payload": "{\"command\":\"SOLVE\"}"

This flow shows the basic pattern required for real escape room operation. The prop sends its status to Node-RED, and the operator can reset that prop or manually mark it as solved from the dashboard.

Practical Tips / Pitfalls

For commercial rooms, it is better to use a fixed IP address or DHCP reservation for each prop.

W5500 SPI wiring should be short and simple. Check SCK, MISO, MOSI, CS, 3.3 V, and GND first.

For locks, game-critical buttons, and session reset devices, wired Ethernet should be considered before Wi-Fi.

It is useful to add per-prop online status or heartbeat indicators to the Node-RED dashboard.

UDP is lightweight, but it does not guarantee delivery. For important commands, add ACK or state verification logic.

MQTT is convenient for topic management, but broker failure can affect the entire communication system, so broker status should be monitored.

The W5500 supports 8 sockets, so when building many props, keep the number of connections per device simple.

FAQ

Q: Why is W5500 suitable for Node-REDscape?
A: The W5500 can add stable wired Ethernet to a small MCU. Escape room props must operate repeatedly across many game sessions, so a wired connection that depends less on wireless quality is beneficial for operational reliability.

Q: How does the W5500 connect to an ESP32 or Arduino?
A: It connects over SPI. The basic required signals are SCK, MISO, MOSI, CS, power, and GND. In the ESP32 example, ssPin = 5 is used as the chip-select pin for the Ethernet module.

Q: What exactly does the W5500 do in this project?
A: The W5500 acts as the wired network interface for the prop controller. When the MCU processes button input or puzzle state, the W5500 sends that data to the Node-RED server and receives control commands from the server.

Q: Can beginners follow this project?
A: Yes, starting with a simple button prop is manageable. However, basic knowledge of Node-RED, Arduino or ESP32, IP address configuration, and SPI wiring is required. For commercial installation, power, cable mounting, and failure recovery also need to be considered.

Q: How is this different from a Wi-Fi-based ESP32 prop?
A: Wi-Fi is quick to install and requires less wiring, but it is affected by room structure and wireless interference. W5500-based wired Ethernet requires cabling, but in commercial rooms with repeated operation, it provides better connection stability and easier troubleshooting.