Stove compatibility

Compatibility depends on the firmware version of the stove's mainboard, not on the model. Each firmware generation speaks its own variant of the protocol, and the bridge finds out by itself which one your stove uses.

By firmware version

The version is shown in the Info menu of the stove screen.

Stove firmware	Status	Read	Control
2.29 e.g. DOMO, DOMO BACK, PRIMO MULTIAIR	Supported	All values and settings	Everything: on/off, mode, power, temperature, schedule, frost protection, room sensor calibration, MultiAir fans, baking oven (DOMO BACK)
2.26 / 2.27 e.g. INDUO	Supported	All values and settings	On/off, mode, power, temperature, schedule, frost protection, room sensor calibration
2.28 e.g. LIVO, INDUO II, SONO	Partial	All values (confirmed on a LIVO)	On/off, mode, power, temperature
2.25 and older	Untested	Nobody has reported a test yet. Feedback welcome.

Firmware 2.28: the link works on a LIVO. On one SONO it does not complete, and the stove shows the code UW29; the cause is still being investigated. RIKA publishes firmware 2.29 for all these models, and on 2.29 a SONO runs the same stick code as a DOMO.

First start

On its first start with a stove, the bridge tries the three protocol variants in turn and keeps the one the stove answers. This takes about six seconds; afterwards it starts with the right one directly. There is nothing to configure.

MultiAir fans

The MultiAir controls appear on the page when the stove reports one of these models:

Model	MultiAir
ROCO MULTIAIR	Fans 1 and 2
DOMO	Fans 1 and 2
PARO	Fans 1 and 2
DOMO BACK	Fans 1 and 2
SUMO MULTIAIR	Fans 1 and 2
PRIMO MULTIAIR	Fans 1 and 2

The board

The firmware is tested on the ESP32-S3. The board must expose the chip's native USB (USB OTG) on a connector: the stove acts as the USB host and the bridge as a USB serial device.

ESP32-S3 with native USB: works.
ESP32-S2: has native USB too and may work, untested.
ESP32, ESP32-C3 and boards with only a UART bridge chip: will not work.

Tell us about your stove

If your stove or firmware version is not listed, or behaves differently, open an issue with the model, the firmware version, the log (CDC Logs tab) and the output of http://open-firenet.local/api/state.