An HTTP/MQTT bridge for Enervent ventilation units with EDA (and its successor, MD) automation (e.g. Pingvin and Pandion). It provides a REST-ful HTTP interface for interacting with the ventilation unit (reading temperatures and changing certain settings), as well as an MQTT client which can publish readings/settings regularly and be used to control the ventilation unit.
Communication happens over RS-485 (Modbus RTU) by connecting a serial device to the "Freeway" port on the ventilation unit's computer board.
The REST endpoints for enabling/disabling the various modes are designed to be consumed by
https://www.home-assistant.io/integrations/switch.rest/ with minimal effort. See examples in the docs/ directory.
- HTTP API for reading temperatures, modes and settings, as well as changing some settings
- MQTT support (read and write), including Home Assistant MQTT discovery support
- Node.js 12.x or newer
- An Enervent ventilation unit with EDA or MD automation (Pingvin, Pandion and LTR-3 confirmed working)
- An RS-485 device (e.g.
/dev/ttyUSB0) connected to the Enervent unit's Freeway port (see - docs/CONNECTION.md for details on how to connect to the unit)
The following instructions will install the application to /opt/eda-modbus-bridge.
sudo su -
git clone https://github.com/Jalle19/eda-modbus-bridge.git /opt/eda-modbus-bridge
cd /opt/eda-modbus-bridge
npm install --productionThat's it, the application is now installed. You can run it manually with
node /opt/eda-modbus-bridge/eda-modbus-bridge.mjs, or see the next chapter on how to run it as a system service.
The following instructions assume you've installed the application to /opt/eda-modbus-bridge.
sudo cp /opt/eda-modbus-bridge/systemd/eda-modbus-bridge.service /etc/systemd/system/
sudo systemctl enable eda-modbus-bridge
sudo systemctl start eda-modbus-bridgeYou can now check that it is running with sudo systemctl status eda-modbus-bridge.
If you need to change any command-line options (e.g. to configure the MQTT broker URL),
edit /etc/systemd/system/eda-modbus-bridge. After you have edited the file you need to reload systemd and restart
the application:
sudo systemctl daemon-reload
sudo systemctl restart eda-modbus-bridgeSee https://github.com/Jalle19/home-assistant-addon-repository/tree/main/eda-modbus-bridge
node eda-modbus-bridge.mjs [options]
Options:
--help Show help [boolean]
--version Show version number [boolean]
-d, --device The serial device to use, e.g. /dev/ttyUSB0
[required]
-s, --modbusSlave The Modbus slave address [default: 1]
--http Whether to enable the HTTP server or not
[boolean] [default: true]
-a, --httpListenAddress The address to listen (HTTP) [default: "0.0.0.0"]
-p, --httpPort The port to listen on (HTTP) [default: 8080]
-m, --mqttBrokerUrl The URL to the MQTT broker, e.g. tcp://localhost:18
83. Omit to disable MQTT support.
--mqttUsername The username to use when connecting to the MQTT bro
ker. Omit to disable authentication.
--mqttPassword The password to use when connecting to the MQTT bro
ker. Required when mqttUsername is defined. Omit to
disable authentication.
-i, --mqttPublishInterval How often messages should be published over MQTT (i
n seconds) [default: 10]
--mqttDiscovery Whether to enable Home Assistant MQTT discovery sup
port. Only effective when mqttBrokerUrl is defined.
[boolean] [default: true]
There's a Postman collection under docs/.
Returns a JSON object like this:
{
"flags": {
"away": false,
"longAway": false,
"overPressure": false,
"maxHeating": false,
"maxCooling": false,
"manualBoost": false,
"summerNightCooling": false
},
"readings": {
"freshAirTemperature": 7.3,
"supplyAirTemperatureAfterHeatRecovery": 21.7,
"supplyAirTemperature": 21.4,
"wasteAirTemperature": 11.2,
"exhaustAirTemperature": 22.5,
"exhaustAirTemperatureBeforeHeatRecovery": -40.0,
"exhaustAirHumidity": 45,
"heatRecoverySupplySide": 94,
"heatRecoveryExhaustSide": 74,
"heatRecoveryTemperatureDifferenceSupplySide": 14.4,
"heatRecoveryTemperatureDifferenceExhaustSide": 11.3,
"mean48HourExhaustHumidity": 39,
"cascadeSp": 170,
"cascadeP": 0,
"cascadeI": 100,
"overPressureTimeLeft": 0,
"ventilationLevelActual": 60
},
"settings": {
"overPressureDelay": 60,
"awayVentilationLevel": 30,
"awayTemperatureReduction": 2,
"longAwayVentilationLevel": 60,
"longAwayTemperatureReduction": 0,
"temperatureTarget": 17
},
"deviceInformation": {
"fanType": true,
"heatingConfigurationMode": 1,
"familyType": 0,
"serialNumber": 0,
"softwareVersion": 217
},
"alarms": [
{
"name": "ServiceReminder",
"description": "Service reminder",
"state": 1, // 2 = Active, 1 = Dismissed
"date": "2021-10-24T11:28:00.000Z"
},...
]
}Returns the status of the specified mode/flag. The response looks like this:
{"active":false}Returns the active or dismissed alarms. The response looks like this:
{
"alarms": [
{
"name": "ServiceReminder",
"description": "Service reminder",
"state": 1, // 2 = Active, 1 = Dismissed
"date": "2021-10-24T11:28:00.000Z"
},...
]
}Enables/disables the specified mode/flag depending on the boolean value in the following request body:
{"active":false}The response is identical to that of GET /mode/{flag}.
Changes the setting to the specified value. HTTP 400 is thrown if the value specified is out of range or invalid.
Returns the new setting values, like this:
{
"overPressureDelay": 60,
"awayVentilationLevel": 30,
"awayTemperatureReduction": 2,
"longAwayVentilationLevel": 60,
"longAwayTemperatureReduction": 0,
"temperatureTarget": 17
}When an MQTT broker URL is specified, the application connects to the broker and starts to regularly publish data at the configured interval (defaults to every 10 seconds). Device information is published only on startup and retained in the broker.
Every topic is prefixed by eda/, so to subscribe to everything the application sends out, subscribe to eda/#
The following read-only topics are regularly published:
eda/status
eda/mode/away
eda/mode/longAway
eda/mode/overPressure
eda/mode/maxHeating
eda/mode/maxCooling
eda/mode/manualBoost
eda/mode/summerNightCooling
eda/readings/freshAirTemperature
eda/readings/supplyAirTemperatureAfterHeatRecovery
eda/readings/supplyAirTemperature
eda/readings/wasteAirTemperature
eda/readings/exhaustAirTemperature
eda/readings/exhaustAirTemperatureBeforeHeatRecovery
eda/readings/exhaustAirHumidity
eda/readings/heatRecoverySupplySide
eda/readings/heatRecoveryExhaustSide
eda/readings/heatRecoveryTemperatureDifferenceSupplySide
eda/readings/heatRecoveryTemperatureDifferenceExhaustSide
eda/readings/mean48HourExhaustHumidity
eda/readings/cascadeSp
eda/readings/cascadeP
eda/readings/cascadeI
eda/readings/overPressureTimeLeft
eda/readings/ventilationLevelActual
eda/readings/ventilationLevelTarget
eda/settings/overPressureDelay
eda/settings/awayVentilationLevel
eda/settings/awayTemperatureReduction
eda/settings/longAwayVentilationLevel
eda/settings/longAwayTemperatureReduction
eda/settings/temperatureTarget
eda/alarm/TE5InletAfterHeatExchangerCold
eda/alarm/TE10InletAfterHeaterCold
eda/alarm/TE10InletAfterHeaterHot
eda/alarm/TE20RoomHot
eda/alarm/TE30OutletCold
eda/alarm/TE30OutletHot
eda/alarm/HPFault
eda/alarm/HeaterFault
eda/alarm/ReturnWaterCold
eda/alarm/LTOFault
eda/alarm/CoolingFault
eda/alarm/EmergencyStop
eda/alarm/FireRisk
eda/alarm/ServiceReminder
eda/alarm/HeaterPressureSwitch
eda/alarm/InletFilterDirty
eda/alarm/OutletFilterDirty
eda/alarm/InletFanPressureAbnomaly
eda/alarm/OutletFanPressureAbnomaly
eda/deviceState/normal
eda/deviceState/maxCooling
eda/deviceState/maxHeating
eda/deviceState/emergencyStop
eda/deviceState/stop
eda/deviceState/away
eda/deviceState/longAway
eda/deviceState/temperatureBoost
eda/deviceState/co2Boost
eda/deviceState/humidityBoost
eda/deviceState/manualBoost
eda/deviceState/overPressure
eda/deviceState/cookerHood
eda/deviceState/centralVacuumCleaner
eda/deviceState/heaterCooldown
eda/deviceState/summerNightCooling
eda/deviceState/defrosting
Boolean values are expressed as ON or OFF.
The following topics are published to once during application startup:
eda/deviceInformation/fanType
eda/deviceInformation/unitType
eda/deviceInformation/coolingTypeInstalled
eda/deviceInformation/heatingTypeInstalled
eda/deviceInformation/familyType
eda/deviceInformation/modelType
eda/deviceInformation/serialNumber
eda/deviceInformation/softwareVersion
eda/deviceInformation/modelName
The following topics can be written to in order to control the operation of the ventilation unit:
eda/mode/away/set
eda/mode/longAway/set
eda/mode/overPressure/set
eda/mode/maxHeating/set
eda/mode/maxCooling/set
eda/mode/manualBoost/set
eda/mode/summerNightCooling/set
eda/settings/overPressureDelay/set
eda/settings/awayVentilationLevel/set
eda/settings/awayTemperatureReduction/set
eda/settings/longAwayVentilationLevel/set
eda/settings/longAwayTemperatureReduction/set
eda/settings/temperatureTarget/set
eda/mode/topics take the valuesONorOFFeda/settings/topics take integer values
The application supports Home Assistant's MQTT Discovery feature, meaning your ventilation unit will show up as a device in Home Assistant automatically through the MQTT integration. The following entities are available:
- sensors for all readings
- numbers (configurable) for settings
- switches for the ventilation modes
- binary sensors for the alarms
-
Some ventilation units sometimes trip the "TE20 Huoneilma kuuma" alarm when Modbus is used and a room temperature sensor has not been connected to the main board. This can be alleviated by reducing the polling interval from 10 seconds to something like 30 seconds, or fixed permanently by either connecting an NTC10 temperature sensor or a 10 kiloohm resistor to the sensor input terminals (not tested, but confirmed by Enervent).
-
It is not possible to adjust the ventilation level when the unit is operating in normal mode. Enervent has confirmed that this is a limitation in the protocol and there is no direct solution. A workaround is to repurpose one of the modes, e.g. "long away", to be a "manual control" mode, since the ventilation level can be adjusted for all non- normal modes of operation. A slight caveat with this is that the temperature target is also reduced, and the temperature target reduction setting doesn't always seem to accept values below 2 degrees Celsius. Experiment with these values to find something that suits your use case, or trust the built-in automation in the ventilation unit to do its job.
GNU GENERAL PUBLIC LICENSE 3.0
Some documentation under docs/ is proprietary.
Credits to Jaakko Ala-Paavola for creating https://web.archive.org/web/20201020102005/http://ala-paavola.fi/jaakko/doku.php?id=pingvin and self-hosting a copy of the relatively hard to find EDA modbus register PDF document.