I have been running my iZone system with these drivers now since early 2019 without issue so I wanted to share to anyone else running this system. I can offer any feedback as required too if you need any guidance from a long term user. If you live in Australia you are probably familiar with iZone here who are located in Perth. Anyways they offer many things now but are well known for their ducted air-conditioning interface.
The 2 drivers that are used to control the iZone AC system can be located on a public GPL V2 license here.
- iZone.groovy - is used for the Master Panel control
- iZone_Zone_Settings.groovy - is used for each zones 1-12 and offers a thermostat for each of them.
Important considerations when implementing Airstream iZone with Hubitat are listed below
Out of the box functionality for Airsteam iZone is that the tablet/controller is configured as “zones” in the admin panel (note default password is wamfud) under controlling options. This should be in “zones” mode previously it was recommended as R/Air but I wouldn’t do that as the R/Air sensor is not as good to use for heating and cooling your home. The reason this was done was due to the setting reverting back when you changed temp to say 25 it would then go back to whatever your tablet had. I got around this by applying the temp to Zone 1 and using NodeRed to update the remaining automatically.
When putting Hubitat rules together in RM and referencing “ACError” under http://iZoneCB/SystemSettings note that there is a JSON tree code error where it should be “OK” it’s actually " OK" (note space).
Another oddness Master Panel will not show temperature when set to R/Air so you need to pull the temp from Zone 1 to show it.
In addition, the iZone.groovy file has presence detailed for the iZone bridge which is handy but I wanted presence detection for the wireless battery controllers in each zone as well so in Nodered i put together the following flow: