One sender, multiple screens

One P1 meter, several screens: that doesn't scale

Every AutoSockets board queries the HomeWizard P1 meter itself over HTTP — one round trip (request plus response) takes a few tens of milliseconds. With a single screen you never notice. Add a second or third, each with its own poll interval, and they start getting in each other's way at the meter. You'll see that as a board that occasionally skips a reading or briefly shows Conn ERR.

The fix: let only one board query the meter and the sockets, and have that board forward the values to the rest.

One sender, the rest just listen

Only the T-Display S3 scans the network, queries the P1 meter and the sockets, and switches them if configured to. Every second it forwards everything that belongs on a screen to the boards that registered as a client — via a small UDP unicast packet of just over 200 bytes.

The clients scan nothing, switch nothing, and there is nothing to configure. They receive the packet and draw the screen — that's it.

Which boards can act as a client?

Any board that already works as a display for AutoSockets can also run as a receive-only client — same screen, just without pestering the P1 meter itself:

Lilygo T-Display (TTGO)

Waveshare ESP32-S3 1.54"

M5Stack Fire / Basic Core

Waveshare ESP32-S3 4.2" RLCD

Battery client in development — an e-paper-like screen that draws no power while the image doesn't change.

Only one sender per network

Two active senders at the same time is not supported — only one board may actually query and switch the P1 meter and the sockets. Every other board runs the client firmware.