← All work

Queno & Q-Cloud

Firmware on custom PCBs and the cloud platform that manages them. One system, from the bootloader to the device list.


Role

Systems developer, Q-Light AS

Year

2021 – 2024

Firmware

C++, Python, OTA, Modbus, MQTT, OCPP 1.6

Cloud

Next.js, TypeScript


The problem

Hardware in the field cannot be visited. Every device needs to be updatable, configurable and observable from wherever it happens to be installed, and charging hardware has to speak OCPP to whatever back office the customer already runs.


My approach

I wrote the firmware for the Queno PCB prototypes: OTA updates, Modbus, MQTT communication and a fully functional OCPP 1.6 client. Then I built Q-Cloud, the cloud IoT solution around it, with OCPP support, remote control, configuration and administration of Queno devices.

Because I owned both ends, the protocol was designed once. The MQTT topics the firmware publishes are the same ones the platform inspects, which makes debugging a matter of reading the live message stream rather than guessing across a boundary.


Fleet view — devices with live status and firmware version, connectors nested beneath each unit.
Device page — the live MQTT stream, cloud on one side and device on the other, with a publish field at the bottom.

Result

Devices went from prototype PCB to production and are managed remotely. Alongside this I had overall responsibility for IT operations and technology across the organisation, and did the same firmware and testing work on the QUDO smart solution and its Homey app.

White to move