inki v0.17.0

Updates

refactor: layer model, webserver split, flash cleanup, NFC improvements

Overview

Full DIY package: enclosure, PCB, and firmware to build inki without a programmer.
Quick-start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; same firmware runs on fully assembled devices and supports OTA via the web UI.

What's Included

• Hardware: 3D-printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi-Fi, web UI, HTTP client, and ePaper rendering; build/flash/UF2 scripts.
• Prebuilt UF2s: single-file images (bootloader + firmware + default config; valid_flag pre-set).

Assets

• inki_seatsurfing.uf2: SeatSurfing room booking display.
• inki_historian.uf2: CCU-Historian time-series visualization.
• inki_homematic.uf2: Homematic home automation display.
• Source code archives (zip, tar.gz).

Quick Start

1. Hold BOOTSEL while plugging in Pico W → RPI-RP2 drive appears.
2. Copy one UF2 (inki_seatsurfing, inki_historian, or inki_homematic) → board reboots automatically.
3. Connect to AP inki-setup (password 12345678) → open http://192.168.4.1.
4. Configure Wi-Fi, use-case settings, and optional logo via the browser.

Hardware For Full Functionality

• RTC: DS3231 (timekeeping and power management).
• ePaper: Waveshare 7.5" V2 or 4.2" V2 (select panel in web UI).
• UF2s run on a bare Pico W to preview the web interface; ePaper rendering and time-based features enable when hardware is present.

inki v0.16.0

Native SeatSurfing HTTPS, NFC booking in DNS mode, refactor

inki v0.14.1

Updates

Web UI: device settings, settings import/export, captive DNS

Logo converter, inki-monitor, pre-commit quality, telemetry

Overview

Full DIY package: enclosure, PCB, and firmware to build inki without a programmer.
Quick-start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; same firmware runs on fully assembled devices and supports OTA via the web UI.

What's Included

• Hardware: 3D-printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi-Fi, web UI, HTTP client, and ePaper rendering; build/flash/UF2 scripts.
• Prebuilt UF2s: single-file images (bootloader + firmware + default config; valid_flag pre-set).

Assets

• inki_seatsurfing.uf2: SeatSurfing room booking display.
• inki_historian.uf2: CCU-Historian time-series visualization.
• inki_homematic.uf2: Homematic home automation display.
• Source code archives (zip, tar.gz).

Quick Start

1. Hold BOOTSEL while plugging in Pico W → RPI-RP2 drive appears.
2. Copy one UF2 (inki_seatsurfing, inki_historian, or inki_homematic) → board reboots automatically.
3. Connect to AP inki-setup (password 12345678) → open http://192.168.4.1.
4. Configure Wi-Fi, use-case settings, and optional logo via the browser.

Hardware For Full Functionality

• RTC: DS3231 (timekeeping and power management).
• ePaper: Waveshare 7.5" V2 or 4.2" V2 (select panel in web UI).
• UF2s run on a bare Pico W to preview the web interface; ePaper rendering and time-based features enable when hardware is present.

inki v0.13 — Improved webinterface

Overview

• Full DIY package: enclosure, PCB, and firmware to build inki without a programmer.
• Quick-start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; same firmware runs on fully
  assembled devices and supports OTA via the web UI.

What’s Included

• Hardware: 3D-printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi-Fi, web UI, HTTP client, XML-RPC for Homematic, and ePaper rendering; build/flash/UF2
  scripts.
• Prebuilt UF2s: single-file images (bootloader + firmware + default config; valid_flag pre-set).

Highlights Since v0.12.2

• OTA use-case guard

  • Firmware headers now include use-case metadata (meta_version, use_case_id, use_case_name).
  • OTA validation checks use-case compatibility before activation.
  • On use-case mismatch, active use-case settings are reset to avoid stale config reuse.

• Status and diagnostics overhaul

  • /device_status layout and readability improved.
  • Better firmware slot/use-case visibility in status/update pages.
  • Extended I²C diagnostics for expected devices (DS3231, BMP581, RV-3028, ST25).

• Web interface improvements

  • SeatSurfing/settings pages refined.

Assets

• inki_seatsurfing.uf2: AP inki-setup, UI at http://192.168.4.1; SeatSurfing pages and OTA included.
• inki_historian.uf2: Same quick start; Historian data view when RTC + ePaper are present.
• inki_homematic.uf2: Same quick start; Homematic reads from CCU (port 2010), units + boolean UI + service footer.
• Source code archives (zip, tar.gz).

Quick Start

1. Hold BOOTSEL while plugging in Pico W -> RPI-RP2 drive appears.
2. Copy one UF2 (inki_seatsurfing, inki_historian, or inki_homematic) -> board reboots automatically.
3. Connect to AP inki-setup (password 12345678) -> open http://192.168.4.1.
4. Setup mode is temporary.

Hardware For Full Functionality

• RTC: DS3231 (timekeeping and power management).
• ePaper: Waveshare 7.5" V2 or 4.2" V2 (select panel in web UI).
• UF2s run on a bare Pico W to preview the web interface; ePaper rendering and time-based features enable when hardware is
  present.

inki v0.12.1 — Improved epaper support

Overview

• Full DIY package: enclosure, PCB, and firmware to build inki without a programmer.
• Quick‑start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; same firmware runs on fully assembled devices and supports OTA via the web UI.

What’s Included

• Hardware: 3D‑printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi‑Fi, web UI, HTTP client, XML‑RPC for Homematic, and ePaper rendering; build/flash/UF2 scripts.
• Prebuilt UF2s: single‑file images (bootloader + firmware + default config; valid_flag pre‑set).

Highlights Since v0.12.0

• Improved support for different epaper support for each use case

• weathermap use case: maps are fetched and stored - work in progress

• Assets
  Prebuilt images for USB writing:

  • inki_seatsurfing.uf2
  • inki_historian.uf2
  • inki_homematic.uf2
  • Source code archives (zip, tar.gz)

  Quick Start

  • Hold BOOTSEL while plugging in Pico W → RPI‑RP2 drive appears.
  • Copy one UF2 (inki_seatsurfing, inki_historian, or inki_homematic) → board reboots automatically.
  • Connect to AP “inki‑setup” (password “12345678”) → open http://192.168.4.1. Configuration for respective application can be set via corresponding web interface.

  Hardware For Full Functionality

  • RTC: DS3231 (timekeeping and power management).
  • ePaper: Waveshare 7.5" V2 or 4.2" V2 (select your panel in the web UI).
  • The UF2s run on a bare Pico W to preview the web interface; ePaper rendering and time‑based features enable when hardware is present.

inki v0.12.0 — Three Use Cases (new: Homematic)

Overview

• Full DIY package: enclosure, PCB, and firmware to build inki without a programmer.
• Quick‑start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; same firmware runs on fully assembled devices and supports OTA via the web UI.

What’s Included

• Hardware: 3D‑printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi‑Fi, web UI, HTTP client, XML‑RPC for Homematic, and ePaper rendering; build/flash/UF2 scripts.
• Prebuilt UF2s: single‑file images (bootloader + firmware + default config; valid_flag pre‑set).

Highlights Since v0.11.0

• New use case: Homematic (XML‑RPC, HmIP on port 2010)
  • Reads values via getValue/system.multicall.
  • CCU service messages footer (e.g., UNREACH, LOW_BAT), width‑aware truncation.

Assets

• inki_seatsurfing.uf2: AP “inki‑setup”, UI at http://192.168.4.1; SeatSurfing pages and OTA included.
• inki_historian.uf2: Same quick start; Historian data view when RTC + ePaper present.
• inki_homematic.uf2: Same quick start; Homematic reads from CCU (port 2010), units + boolean UI + service footer.
• Source code archives (zip, tar.gz)

Quick Start

• Hold BOOTSEL while plugging in Pico W → RPI‑RP2 drive appears.
• Copy one UF2 (inki_seatsurfing, inki_historian, or inki_homematic) → board reboots automatically.
• Connect to AP “inki‑setup” (password “12345678”) → open http://192.168.4.1. Setup mode is temporary.

Hardware For Full Functionality

• RTC: DS3231 (timekeeping and power management).
• ePaper: Waveshare 7.5" V2 or 4.2" V2 (select your panel in the web UI).
• The UF2s run on a bare Pico W to preview the web interface; ePaper rendering and time‑based features enable when hardware is present.

inki v0.11.0 — First public release (full DIY package + quick-start UF2s)

Overview

• Full DIY package: this release covers the entire project — enclosure (3D‑print), PCB, and firmware — to build inki without a programmer.
• Quick‑start UF2s: prebuilt images to preview setup and the web interface on a bare Pico W; the same firmware also runs on fully assembled devices and can be configured and updated via the web interface.

What’s included

• Hardware: 3D‑printed enclosure files and custom PCB (RTC, power management, ePaper).
• Firmware: C code for RTC wakeup, Wi‑Fi, web UI, and ePaper; build scripts.
• Prebuilt UF2s: single‑file images (bootloader + firmware + default config; valid_flag pre‑set).

Assets

• inki_historian.uf2: Starts AP “inki‑setup,” web UI at http://192.168.4.1. Ideal to explore the UI; fully supports historian when RTC + ePaper are attached.
• inki_seatsurfing.uf2: Same quick start for the SeatSurfing use case.

Quick start

1. Hold BOOTSEL while plugging in Pico W → RPI‑RP2 drive appears.
2. Copy a UF2 (historian or seatsurfing) → board reboots automatically.
3. Connect to AP “inki‑setup” (password “12345678”) → open http://192.168.4.1. Setup mode is temporary.

Hardware for full functionality

• RTC: DS3231 (timekeeping & power management).
• ePaper: Waveshare 7.5" V2 or 4.2" V2 (select your panel in the web UI).
• The UF2s run on a bare Pico W (EPAPER_NONE by default) to preview the web interface; ePaper rendering and time‑based features activate when hardware is present.