Docs
Documentation
Plynx connects a board to your iPhone. You put a widget on a canvas, bind it to a pin, and the two talk: a tap on a Button writes to a pin, a reading your sketch sends moves a Gauge. Everything here is a variation on that.
Start here
| Page | What it covers |
|---|---|
| Getting started | From nothing to a working dashboard: install the library, flash a sketch, add a widget |
| Auto setup | Flash once with no token and no WiFi credentials in the code, and let the app configure the board |
| How it works | Virtual pins, the connection, and what the server does while your phone is closed |
Widgets
Every widget has its own page, with what it sends or shows, its settings in the app, a working ESP32 sketch, and the cases that catch people out.
The widget index groups them by direction: what sends from the phone to the board, what displays what the board sends back, and what runs on the server without your sketch being involved.
The two rules worth knowing before you start
Direction decides your code. A widget that sends needs a PLYNX_WRITE(Vn)
handler in your sketch. A widget that displays needs your sketch to call
Plynx.virtualWrite(Vn, …). Nothing moves by itself in either direction.
Plynx.run() lives in loop(). Without it, nothing is sent and nothing is
received, and the board looks connected while doing nothing.
Compatibility
Plynx speaks the classic Blynk Legacy protocol, so existing legacy servers and dashboards work with it. A sketch written against the classic library needs its identifiers renamed first, since the Plynx library carries no legacy aliases: see the FAQ for the list.
Plynx is an independent project, not affiliated with Blynk Inc.