This binding integrates AirZone controlled HVAC systems via connection to the local API offered by the webserver
Please note this binding is unofficial and not endorsed by AirZone in any way.
Supported things
- AirZone bridge to represent the actual AirZone webserver. Only its IP address must be provided, discovery would need DHCP sniffing which is intrusive and not reliable.
- AirZone system to represent the concept of “systems” in the installation. There is generally only one and its most common use is to monitor changes in the Errors channel. If the proper module is installed, it may also report its power consumption.
- AirZone zone to represent a zone controlled by the HVAC system. This is the thing that has the most channels: name, on-off, temperature, humidity, setpoint-temperature (simple or double), operation mode, fan speed, stage kind, auto sleep, air-quality (value and threshold to react), fluid demand (cold, heat, air, floor), slats (swing and position), eco-adapt (target euro label value, a/a+…) and antifreeze.
- AirZone “all zone” to allow controlling all zones at once via write only channels.
Changelog
Version 0.2.4
Changes:
- Introduce support for openHAB 4.2
- openHAB 3.4 is no longer supported
Version 0.2.3
Fixes:
- speeds is not an array but an integer that may be absent
Version 0.2.2
Fixes:
- Older systems do not provide the
master_zoneID
field which prevented the “All zones” thing from working properly
Version 0.2.1
Fixes:
- Prevent dynamic channels from being created more than once which stopped the binding from working properly.
Version 0.2.0
New features:
- Introduced the “All zones” thing that offers channels controlling all zones at once
Fixes:
- Support older API versions that do not offer systems information
- Avoid dancing values by fixing the race condition between auto update and scheduled update
- Do not blindly wait 3 seconds after each HTTP request but rather wait only if needed.
Version 0.1.0
- initial release