Salda Recuperator — Fibaro HC3 QuickApp

Control and monitor a Salda RIS P EKO 3.0 heat-recovery ventilator from the Fibaro Home Center 3. Talks Modbus TCP directly to a Modbus gateway on your LAN — no external bridge service required.

What it does

• Fan speed: 4 stages (Off / Low / Med / High), active stage marked ▶ ◀
• Boost: one-click toggle with live countdown to auto-off
• Sensors: supply + outdoor air temperature, humidity, bypass damper position, motor speeds
• Alarms: filter, antifrost, fire, fan — shown in header when active
• Three child devices automatically created:
  • Salda Supply Temp (com.fibaro.temperatureSensor)
  • Salda Outdoor Temp (com.fibaro.temperatureSensor)
  • Salda Humidity (com.fibaro.humiditySensor) Each updates its value every poll — usable in scenes, graphs, and notifications independent of the parent QuickApp.

Requirements

• A Salda recuperator with Modbus access. Either:
  • Built-in Modbus TCP (some EKO 3.0 firmwares), or
  • An external Modbus TCP ↔ RS-485 gateway (MBGW) bridging the unit's bus
• HC3 firmware 5.x. Tested on 5.200.8.

Install

1. Download salda-recuperator-v1.0.0.fqa.
2. In the HC3 web UI: Settings → Devices → + Add → Other Device → Upload file and pick the .fqa.
3. Open the new "Salda Recuperator" device.
4. Go to the Variables tab and set:
   • mbgw_host — IP of your Modbus gateway (required)
   • mbgw_port — TCP port (default 502)
   • mbgw_slave — Modbus unit ID (default 1)
   • poll_interval_s — seconds between reads (default 30)
5. The QuickApp starts polling automatically. The header shows ▶ Speed 1 (Low) etc. as soon as it has live data.

If the header keeps showing "Configure 'mbgw_host'" you haven't set the gateway IP yet — go back to the Variables tab.

Scene / automation API

Methods on the parent QuickApp, callable from any scene or REST request:

Method	Arg	Effect
setSpeedN(stage)	0..3	Set fan stage
setSpeed0/setSpeed1/setSpeed2/setSpeed3	—	Same, no arg
boostOn / boostOff / boostToggle	—	Boost coil
tempChanged(N)	0..30	Supply air setpoint, °C

Example: fibaro.call(<id>, "setSpeed2") from a Lua scene.

Known limitations

• Boost countdown is accurate to the poll interval (default 30 s). Setting poll_interval_s lower makes the countdown smoother at the cost of more network traffic to the gateway.
• The boost countdown timer is tracked locally by the QuickApp. If you trigger boost from the unit's control panel or the Salda mobile app instead of from HC3, the QuickApp shows the configured duration but can't show "X minutes left" — it doesn't know when boost started.

License

MIT.