Changelog

Every release, firmware and apps.

What changed in each version, newest first. Lamps update over the air from the apps, so you are always one tap from the latest firmware. Binaries for every board and form live on the releases page, or flash straight from your browser on the PlaiiinLightOS page; the apps live on the apps page.

Firmware — the 2.x line

v2.8.0 — AI access keys

An admin can create share keys with the new role ai for AI assistants: instead of a role, each key carries the permissions its owner picks (control, effects, images, scenes, stream, ota, rename, read-only swarm), plus an optional brightness cap and an "only while the lamp is on" switch. Pairing, keys, Wi-Fi and the other owner settings can never be granted. Up to 4 AI keys per lamp, changeable later with PATCH /api/keys/<id>; GET /api/whoami reports a key's permissions. New POST /api/name renames the lamp. Share keys now live in one NVS blob (migrated on first save, up to 20 keys). Hardening: pages no longer embed the admin token or AI provider key for share-key holders, request logs never show ?token=, and a refused swarm join no longer double-frees. API version 2.7.0 (additive).

v2.7.0 — scenes across the swarm

The lamp now remembers which scene it is showing: GET /api/state reports "scene" until another effect, image or an explicit mode pick takes over, so every app (and Home Assistant) shows the same active scene. In a swarm, activating a scene makes every lamp that has a scene of the same name activate its own copy, and tune changes on one lamp follow on the others (new "PLSW" v2 swarm packets, sent next to the v1 state — older lamps keep mirroring as before). An off lamp now follows the effect choice too. Saved images can carry a name (POST /api/images with {"label"}, renamable later). Power is no longer part of a scene, and picking an effect while off only selects it. API version 2.6.0 (additive).

v2.6.0 — scenes

A scene is a named, saved snapshot of the lamp's state (on, mode, effect and its params or a saved image, colour, brightness), stored on the lamp and recalled in one call: POST /api/scenes/<name>/capture saves what the lamp is doing right now, POST /api/scenes/<name>/activate brings it back in the right order with the normal fades, and GET /api/scenes lists them. Every field is optional, so a partial "mood" scene that only sets a colour works too. Up to 32 per lamp; they mirror to the swarm like manual control. API version 2.5.0 (additive).

v2.5.0 — agent-ready API

The whole HTTP contract is served machine-readably at GET /api/openapi.json (OpenAPI 3, unauthenticated, gzipped), so an AI agent or any tool-binding client can discover every operation from the lamp itself. GET /api/js gains an additive effects array with a description, tags and source per effect, so a client can pick an effect by intent ("something cozy") instead of by name; every shipped effect is annotated, and your own scripts self-describe from a // @description / // @tags header or their leading comment. POST /api/color accepts {"color":[r,g,b]} to paint every LED without knowing the LED count. API version 2.4.0 (additive; existing clients unaffected).

v2.4.0 — brown-out-safe boot

Lighting the panel is a lamp's biggest current surge, so boot no longer does it early: the lamp comes up dark but reachable (Wi-Fi + HTTP first), then restores and soft-starts the panel over ~0.8 s, so its inrush never coincides with the Wi-Fi bring-up. A boot-loop breaker counts consecutive boots that fail to stay up (a brown-out is a non-power-on reset); after three it enters safe boot — panel held off, lamp dark but reachable (safeBoot in GET /api/health) — so an under-powered lamp never loops forever. An explicit POST /api/power resumes. See the Powering the LEDs and Brown-out-safe boot sections of SPECS.md. API version unchanged at 2.3.0.

v2.3.0 — model identity

Every lamp now reports modelName + modelVersion (GET /api, BLE device-info), which the apps show as the model (tower8 + v2 = tower8v2); a profile's filename is that model. The lamp name is separate: a freshly burned lamp boots as <name>-<MAC suffix> (tower8-3FA8, the same suffix as its provisioning AP) so several lamps of one model stay distinguishable, and a full factory reset restores that factory name. Lamps that OTA onto 2.3.0 keep their existing name and derive the model from it. API version 2.3.0 (additive; older clients ignore the fields).

v2.2.0 — stable device ID

Every lamp now advertises its factory MAC as a 12-hex-char id (id in the mDNS TXT record and the BLE device-info characteristic, deviceId in GET /api), so the apps and integrations recognise a lamp after it is renamed instead of treating it as a new device. API version 2.2.0 (additive; older clients ignore the field).

v2.1.2

Swarm join is refused (409) on a lamp with no WiFi connection unless the caller pins a channel, mirroring the apps' rule that only WiFi-reachable lamps can be added to a swarm. Browser flashing returns to plaiiin-light.com: every release now also publishes its flash/effects/manifest set to GitHub Pages for ESP Web Tools.

v2.1.1 — three more SoCs ship prebuilt for every form

ESP32-S3 (-esp32s3), ESP32-C6 (-esp32c6) and, experimentally, ESP32-C5 (-esp32c5, built with IDF v5.5). No on-device changes for the existing esp32 / esp32c3 fleet.

v2.1.0 — saved draw images

  • Image library on the lamp — save up to 30 drawn frames on the lamp itself (/api/images: list, save, show, delete); thumbnails and one-tap show in the apps and the on-device /draw page.
  • Carousel effect — a built-in effect that cycles the saved images as a slideshow, with tunable dwell, crossfade, and shuffle.

v2.0.1

Point release to exercise in-app firmware updates end to end; no on-device changes.

v2.0.0 — the big one

  • Swarm mode — masterless ESP-NOW mesh; change one lamp and the group follows, HMAC-secured, works even with no router.
  • Draw / frame mode — push a still pixel-art frame (POST /api/frame) that survives reboot, plus an on-device /draw pixel editor.
  • Plug factory reset — five fast power cycles recover a buttonless / off-network lamp (a blue flash confirms), keeping its hardware identity and recovery key.
  • In-app Direct OTA — a form-aware /api/ota/info lets the macOS / iOS / Android apps update a lamp wirelessly, form- and chip-checked so the wrong image can't be applied.

Firmware — the 1.9 line

v1.9.14 — smoother onboarding

The WiFi network scan works before the lamp has a connection, slow WiFi at boot no longer costs you mDNS/MQTT or the portal, and the panel and /api/state stay in agreement after setup.

v1.9.13

Prebuilt ESP32-C3 binaries for every lamp form now ship with each release, alongside the classic ESP32 set.

v1.9.12 — ESP32-C3 support lands

Build any form with --chip esp32c3; /api/ota/info now reports the chip target so updaters can't cross-flash; new shrumLight (24-LED strip) profile.

v1.9.11

Web server no longer wedges when clients leave connections half-open: stale sockets are purged (LRU) so the portal and API stay reachable.

v1.9.10 — the factory-reset recovery key is now durable

It survives reset and unpair, so a lost lamp can always be recovered.

v1.9.9 — release-pipeline rebuild; no firmware changes

v1.9.8

Recovery-key endpoints (/api/reset-key); effect next/prev no longer stalls on an uncompilable script; fire effect fixed on pixel-grouped displays.

v1.9.7

MQTT learned mode switching (color/js) and effect next/prev topics; portal root now redirects to /control; knob and switch tunes on the Scripts and Compose pages.

Apps

The macOS and Android builds are published here; the iPhone and iPad app ships through the App Store. The apps share one codebase, so a version number means the same thing on every platform, and the notes below are the ones published with each App Store release.

Apps 2.5.1

Version 2.5.1 is a small fix release.

  • AI access: a new AI share is named "my AI assistant" by default, and the hint names ChatGPT next to Claude.
  • Android: on phones, the tab names in lamp details stay on one line instead of wrapping.

Android · macOS

Apps 2.5.0

Version 2.5 lets you share a lamp with an AI assistant.

  • AI access: the Share tab can now create a key for an AI assistant such as Claude, next to the User and Creator shares.
  • You choose what the assistant may do on that lamp: control, scripts, drawings, scenes, live streaming, firmware updates, renaming — each one is a separate switch.
  • Limits: set a brightness cap, and let the assistant act only while the lamp is switched on.
  • Change the permissions later or revoke the key at any time; an AI key can't be used by apps.
  • Needs lamp firmware 2.8 or newer.

Android · macOS

Apps 2.4.0

Version 2.4 brings scenes: save what a lamp shows and bring it back with one tap.

  • Scenes: save a lamp's effect and tunes, a drawing, colour and brightness as a named scene. The dashboard tile gets a Scene mode to step through them, and a Scenes tab lets you edit them and keep a library on your device.
  • The tile follows the lamp: a scene started from another app, from Home Assistant or from another lamp in the swarm shows up as the active scene (firmware 2.7).
  • Swarm sync: copy a scene, script or drawing from your library or from one lamp to the other lamps in a swarm — a scene brings its effect, tunes and drawing along.
  • Drawings get names: name a drawing when you save it, and rename it later.
  • Scripts: download a script from a lamp into your local library.

macOS

Apps 2.3.1

Version 2.3.1 brings a new app icon and the model-identity changes from 2.3.

  • New icon: a disco mirror ball, because running light effects is what the app is about.
  • Model: the Devices list and lamp settings now show the lamp's model (for example tower8v2) separately from its name.
  • Stable identity: lamps are recognised by a permanent device ID, so renaming a lamp no longer makes it appear as a new device.
  • New lamps come up with a unique name (model plus a short suffix) so several lamps of the same model are easy to tell apart; rename them freely afterwards.

Android · macOS

Apps 2.3.0

Version 2.3 shows each lamp's model and keeps lamps apart after renaming.

  • Model: the Devices list and lamp settings now show the lamp's model (for example tower8v2) separately from its name.
  • Stable identity: lamps are recognised by a permanent device ID, so renaming a lamp no longer makes it appear as a new device.
  • New lamps come up with a unique name (model plus a short suffix) so several lamps of the same model are easy to tell apart; rename them freely afterwards.

Android · macOS

Apps 2.0.0

Version 2.0 brings Swarm, Draw, and in‑app firmware updates.

  • Swarm: group lamps so they play the same effect in sync. Create a swarm, rename it, add or remove members, re‑key it, and optionally show the whole swarm as one dashboard tile. Claiming a new lamp offers to add it to a swarm.
  • Draw: paint pixels straight onto the lamp with paint, brush, spray and fill tools, stream live while you draw, import an image, and save images on the lamp to recall later.
  • Firmware updates from the app: an update badge on the Devices tab and one‑tap install with progress.
  • Dashboard: drag tiles to reorder them.
  • Share tab redesigned as per‑lamp tiles.
  • Fixes: brightness slider no longer stalls the lamp, firmware upload timeout, clearer unpair/reset texts.

Android · macOS

Apps 1.0.0

First release. Control your ESP32 LED lamps, compose effects with AI from a plain‑language description, preview them live, onboard over Bluetooth, and share lamps by key, QR, or Bluetooth. Universal for iPhone and iPad.

Android

Every app build

Point releases and platform catch-ups. Each links its signed download and checksums.

  • 2.3.4 — Android
  • 2.3.3 — Android
  • 2.3.2 — Android · macOS
  • 2.2.0 — Android · macOS
  • 2.1.2 — macOS
  • 2.1.1 — macOS
  • 2.1.0 — macOS
  • 1.0.13 — macOS
  • 1.0.12 — macOS
  • 1.0.11 — macOS
  • 1.0.10 — macOS
  • 1.0.9 — macOS
  • 1.0.8 — macOS
  • 1.0.7 — macOS
  • 1.0.6 — macOS
  • 1.0.5 — macOS
  • 1.0.4 — macOS
  • 1.0.1 — Android

Disclaimer

The software and the information on this page are provided as is, without warranty of any kind. You install, flash and use them at your own risk.

As far as the law allows, plaiiin is not liable for damage to devices, data or property that results from using them.