Changelog: firmware, dashboard, apps and website

Follow along by RSS.

1. 2026-09-19Website19 September 2026

   myperchi.com: the launch site, built from the site plan

   • Product pages for Perchi, Perchi for two and Perchi Matrix, the Phone Nap guide, the app catalogue, comparison and alternatives guides, pricing, the reservation form, security, developers, support, the policy pages and this changelog.
   • Every price, wait estimate, batch label, warranty figure and contact detail on the site is rendered from one configuration file, so a change is one edit and the pages cannot disagree with each other.
   • The site plan (revision 2) fixed one owner per search phrase and per FAQ question, so no two pages answer the same question; the build check fails on a duplicate.
   • The device renders on every page are drawn from the firmware's own face parameters and display font. They stand in for photographs until units exist.
2. 2026-09-19Hardware19 September 2026

   Perchi hardware: firmware complete, bench parts on order, bench pass pending

   • Every Perchi firmware item compiles and passes the host test suites, but nothing has run on a real OLED panel with real electrodes yet. The owner bench pass (B-H1) is waiting for parts.
   • What the bench pass checks: the face appears within 2 seconds of boot and blinks; tap, stroke and 3-second hold gestures; a phone rested on the back starts the focus arc and lifting it pauses the face; pairing over Bluetooth with the dashboard mirror matching the panel frame for frame.
   • Until it passes, the site prints estimated waits only and no ship date. The product PCB, the shell CAD and the first ten sellable units come after it.
3. 2026-09-18Website18 September 2026

   The desk companion is named Perchi

   • Name decided: Perchi, at myperchi.com. Model id mx-perchi, serial prefix MXP; Perchi Matrix keeps mx-ws2812 and MXW. The tap on Perchi's head is a boop.
   • Twelve research notes were written for the launch site: feature inventories for Perchi, Perchi Matrix and the shared platform (with a list of what must not be claimed before the bench pass), competitor notes for desk companions, ambient displays, focus tools and creator counters, an India commerce and legal checklist, a website audit of 13 competitor sites, keyword and question research, and pre-order page practice.
4. 2026-09-18Firmware18 September 2026

   Legacy device protocol retired: Protocol 2 and Perchi OS are the only firmware and protocol

   • Protocol 1, the legacy backend, its import and cutover path and the legacy firmware profiles were removed from the code base rather than carried into launch.
   • Every device now speaks Protocol 2: a key generated on the device and never transmitted, signed envelopes for every command and update offer, WebSocket with an HTTP fallback.
   • Test inventory re-counted the same day: 24 firmware host suites, 8 fuzz targets, and a golden corpus of 107 scenes / 759 frame digests shared by the TypeScript renderer and the C firmware.
5. 2026-09-17Firmware17 September 2026

   Perchi OS for the OLED: display driver, touch, mood and Phone Nap engines

   • SSD1306 128x64 SPI display driver and a monochrome stage with byte-for-byte parity to the dashboard preview: 588 of 588 golden frames match.
   • Touch input: three copper electrodes under the head read as a slider, one electrode behind the phone rest in proximity mode; gestures are tap, double-tap, stroke, and holds of 3, 5 and 10 seconds; phone rest and lift are separate events with hysteresis and a sensitivity slider in the dashboard.
   • Mood engine with ten moods and a Phone Nap engine: blocks of 5 to 120 minutes (25 by default), five visible project stages, a pause grace period, streaks with one earned freeze per 7-day run, and a ring of 64 unsent events so blocks finished offline sync later.
   • 128x64 system screens (pairing code, setup, safe mode) and a burn-in guard: pixel shift every 60 seconds, dimmed clock after 10 idle minutes, sleep in quiet hours.
   • Perchi image 1,681,616 bytes; 134 host tests including fuzzing of the touch gestures and the nap commands.
6. 2026-09-17Dashboard17 September 2026

   Perchi in the dashboard: device page, calibration, wardrobe, focus rooms, Record my Perchi

   • An OLED preview panel, store chips that show which apps fit a 128x64 monochrome screen, and the app builder working at 128x64.
   • The Perchi device page: mode, current block, streak, resting screen, gestures, sleep and burn-in settings; the pairing wizard gained calibration steps (boop three times, rest and lift your phone once).
   • Wardrobe and Focus pages: every finished scarf, sprout and tower with its date and block length, daily and weekly report cards, focus rooms and Perchi links.
   • Record my Perchi: a 540x960 GIF of the last 10 seconds of the face, reconstructed from events the server already knows (300 frames, about 1.5 MB), with a public link that lasts 30 days.
   • 787 unit tests and 216 Playwright specs on chromium and mobile-chrome.
7. 2026-09-17Apps17 September 2026

   Server focus module, links and rooms, and the shared app library on Perchi

   • A focus module on the server: blocks, streaks, wardrobe and settings over 17 routes, report ingest from the device, and daily and weekly report jobs.
   • A tall monochrome template tier and a face-card template, so every catalogue app renders beside the face with one big number.
   • Links and rooms: a tap on one Perchi makes the linked Perchi blush and wave, a finished block sends a well done, and rooms of up to four Perchis share presence dots and a daily tally, never app content.
   • The factory image is now pinned per device type, because Perchi and Perchi Matrix share the same ESP32-S3 board. Server test count: 2,521.
8. 2026-09-16Platform16 September 2026

   Factory flasher: USB provisioning with per-unit serial numbers

   • The factory page in the admin dashboard flashes a pinned, signed stable release over USB from the browser, erase-first, plus a per-unit factory partition that carries the display geometry and the serial. One firmware image serves every geometry.
   • Serial format MXW-000042-I for Perchi Matrix and MXP-000007-A for Perchi, with a check character so support can catch typos. Serials are never reused, even for scrapped units; every attempt, retry and scrap is audited.
   • A boot check over Improv serial records the version, serial and short id after flashing. The factory partition holds no secrets: the device key is generated by the device on first boot.
   • Hardware acceptance of the flasher on real boards (F-09) is pending.
9. 2026-09-15Platform15 September 2026

   Pre-beta fix pass and the engineering handbook

   • The one launch-blocking code defect from the review (an app using a connected account never recovered after that account was re-authorised) was fixed, together with eight smaller findings.
   • The security, end-to-end and release-guard test suites became required CI steps. Production boot guards now refuse test Turnstile keys, plain-http origins and development keys by name.
   • The engineering handbook: 13 chapters written from the source, every claim cited to a file and line, each chapter ending with gotchas and a table of where the design and the code disagree.
   • As-built status recorded: 45 of 45 platform work packages complete.
10. 2026-09-14Platform14 September 2026

    Final acceptance run and launch-readiness review of the platform

    • 14 steps, 24 commands, every one exiting 0 on the first run: 4,271 unit and integration tests (contracts 615, renderer 630, SDK 67, server 2,324, dashboard 635), smoke 67 of 67, security and contract 393 of 393, dashboard end-to-end 502, accessibility 181 of 181.
    • Load: 300 simulated devices for 120 seconds with 0 errors and a notification p95 of 243 ms; an earlier run held 1,000 devices for 600 seconds at p95 242 ms.
    • Plugin registry validated: 63 integration modules, 0 errors, 0 warnings.
    • Review verdict: ready for a private beta after one code fix and owner configuration; not ready for public launch until production alerting, the policy pages, the hosted device domain and the hardware release gates are done.
11. 2026-09-13Platform13 September 2026

    Platform v2 design finalised (revision 2)

    • The merged design set: architecture, data model, API contract, device protocol, plugin SDK and catalogue, display and app builder, pairing and security, dashboard, firmware, distribution and the 45-package build plan, with every review critique and its disposition recorded.
    • Package versions, ESP-IDF components and Docker image tags were checked against their registries on the day.
    • The 24x8 WS2812B matrix on the bench was dark that day; the cause was a power-supply fault, so firmware deliverables were verified by builds and host tests.

Hardware lines here match the batch log in the Shipping Policy. Units are designed and assembled in Bengaluru, India, and every one is bench-tested before it leaves; the current estimate for new reservations is on the reservation page. What each release changes for the API, webhooks and the local API is on the developer page; how updates are signed and rolled out is on the security page. Journalists will find the fact sheet in the press kit.