Adapter for Schwoererhaus Ventcube system. More information about Ventcube Fresh can be found here.
Disclaimer: This adapter is neither developed nor officially supported by the company Schwoererhaus KG which distributes the Ventcube system. Instructions should be followed with care and at your own risk.
In order to access the network-interface of Ventcube the following (known) preconditions need to be met:
- The Ventcube needs to be connected to your internal network (usually via network-cable)
- Modbus TCP interface needs to be supported (Control-Panel: >= V1.05, VentCube: >= V02.11) and often has to be enabled manually first
- On Control Panel login to "Service" section (use standard password from docs)
- In Basic Settings check that Network Connection is established and "9. Network Interface" and "10. Modbus TCP" are both active.
- If the last two settings are not active, activate them and restart the Ventcube (e.g. by cutting the power temporarily)
Depending on the building-specific Ventcube setup not all parameters that can be retrieved from or changed via the Ventcube interface will be used. Each parameter in the "parameters" folder goes side-by-side with an entry in the "lastUpdate" folder that indicates the last fetch timestamp for each parameter.
All parameters mentioned in the specification referenced below were added to the adapter and can be accessed via Advanced Functions option that is configurable during adapter deployment. Enabling this option will cause the adapter to periodically retrieve data for 100+ parameters, of which most might not be used in common households. Test scope was limited to Basic Functions (enabled by default).
The following default config-values likely will need to be changed during adapter deployment for it to connect to Ventcube properly:
| Parameter | Default Value | Explanation |
|---|---|---|
Server |
HERMES-LT | Usually Ventcube registers itself in network with HERMES-LT but if it does not work, try using the IP address. |
Port |
502 | |
Interval |
30 | After how many seconds should metrics be refreshed from server |
Request Timeout |
5000 | How many milliseconds to wait until requests to Ventcube time out |
Reconnection Attempts |
10 | In case connection is lost to Ventcube, how many times a reconnect should be attempted |
Delay between reconnection attempts |
10000 | How long to wait between reconnection attempts (in milliseconds) |
Advanced Functions |
✓ | While basic functions might be sufficient if Ventcube is just used for air ventilation, advanced functions should be activated if heating/cooling functions, or system metrics (error codes, fan details) are needed. |
- Betriebsart, changeable
- Stoßlüftung (30 minute level 4 air burst), changeable
- Ist Temp Raum 1 (temperature inside house)
- T10 Außentemperatur
The ioBroker adapter was tested sucessfully with:
| Control Panel | Ventcube | Modbus specification |
|---|---|---|
| V01.10 | V02.26 | Parameterliste_Modbus_TCP_03.2020 |
See Changelog for a list of all changes.
- Removed test configuration from default adapter values
- Corrected Modbus address for T6 measurement (Issue #60)[#60], (PR #61)[#61]
- Added scheduling priority Tier 2 (introduced with JS-Controller 3.3.0)
- (Development) added tests for Node.js 16 Support
- Added Admin 5 support
- Added new parameter request timeout
- Added info channel to inform about adapter status
- Redefined state roles to describe available data better
- Improvements to Adapter termination process
- Added missing reconnect behaviour in case Ventcube is not reachable
- Added connection settings for new reconnect-behaviour
- Reworked layout ouf settings page
- (Development) Fixed mock-server connection handling and Windows integration tests
- (Development) Moved integration tests (windows, Linux, OSX) from Travis to Github Actions
MIT License
Copyright (c) 2020-2024 Excodibur
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.