Projects

One boundary for CoCon

I built the client so application code can work with commands and typed events instead of managing long polling, retries, and reconnections itself. Its async with API handles setup and teardown, while subscriptions and callbacks keep notification handling straightforward.

The notification registry keeps support for new payload types in one place, and restored subscriptions let applications continue after a connection interruption. The same client later became the foundation for CoCon Vote Monitor.

A live view of each vote

I built the monitor as a focused companion to cocon_client. Keeping the current state on the server means a newly connected display immediately receives the full meeting and voting view; existing displays stay current through WebSocket updates instead of polling or refreshing the page.

When voting closes, the standard view can open the browser print flow automatically. /noautoprint keeps the same live view without triggering it.

Integration at conference scale

Across seven conference environments, the project covers nearly 5,000 devices and conference positions: around 1,700 delegate and microphone positions, approximately 2,800 listening units, more than 300 AV-over-IP endpoints, and dozens of controlled cameras.

I work directly with the customer on requirements and possible changes, coordinate the interfaces between systems, and handle the detailed device configuration, testing, and commissioning. Six of the seven planned environments are in operation, with the remaining work still under way.

I work alongside the senior automation developer, who owns the main control-code implementation. My software contribution consists of the smaller changes needed during integration; most of my work is system integration, device configuration, quality checks, and commissioning.

Register-oriented driver model

An MCP9808 instance binds an I2C-compatible object to either an explicit seven-bit address or one assembled from the A0, A1, and A2 pins. The module defines the sensor’s register addresses and configuration masks directly, without depending on concrete machine.I2C classes, and uses one two-byte buffer plus one one-byte buffer for all transfers.

The configuration register is represented as a cached snapshot. refresh() performs one explicit read and updates hysteresis, shutdown, lock, alert, polarity, and mode properties; setters assemble the corresponding bit fields, write the register, and refresh the snapshot. Optional identity verification reads the Microchip manufacturer and device identifiers without making those transactions mandatory for every construction path.

Temperature data follows the sensor’s signed sixteenth-degree register representation, with a Celsius float wrapper for convenience. Alert thresholds likewise have exact signed quarter-degree operations alongside the float API. The same interface covers resolution, low-power state, hysteresis, comparator or interrupt behavior, polarity, threshold selection, and the MCP9808’s power-cycle-reset register locks.

Package and test infrastructure

The repository separates deployment and validation concerns: package.json supports installation through mip, while manifest.py supports freezing the module into MicroPython firmware with line-preserving optimization. Versioned tags and a changelog distinguish the original API from the breaking v2 interface.

Host tests use a dependency-free FakeI2C register map that models identity registers, temperatures, alert flags, configuration locks, the self-clearing interrupt bit, and transaction counts. A separate Pico W suite exercises power cycling and the physical sensor and alert output; an on-device script is retained for repeatable timing and allocation measurements without making a specific benchmark result the project’s main outcome.

Static by default

I chose a static architecture because the site does not need accounts, a database, or an application server. Astro turns the bilingual content into ordinary HTML pages, while the small client-side layer only adds optional controls and effects.

The interface borrows from terminals and text editors without replacing familiar web behaviour. Links remain links, the pages work without JavaScript, motion can be disabled, and the same content adapts to narrow screens and print.

The public repository contains the website source and its verification workflow. Automated checks cover formatting, types, generated routes, publication safety, responsive behaviour, keyboard interaction, and the three browser engines.