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:
Thanks very much. This is my setting at the moment. But Iām getting this error for master panel and zones everytime it refreshes. Not sure if itās related to the R/Air setting or is there something else Iām missing.
dev:6502021-01-13 09:44:37.099 am errorsomething went wrong: java.lang.IllegalArgumentException: Response does not have a content-type header
dev:6502021-01-13 09:44:37.061 am errorsomething went wrong: java.lang.IllegalArgumentException: Response does not have a content-type header
dev:6502021-01-13 09:44:37.051 am infoPulling Zone 5_8 Settings
dev:6502021-01-13 09:44:37.048 am inforefresh 5-8
Update all: We are working with @bendarklighter via PMās in an attempt to resolve his issues. Once I know more I will update here. It seems an iZone update has occurred causing issues on newer firmware units.
Iām also about to setup a new iZone with the added bonus of Irrigation and potentially some lights and garage door controllers. I also have a copy of the iZone network protocol json header files so hopefully I can fix any issues with the current drivers and code.
I paid Scott to write this code for me in early 2020. You can find the original driver code in my original post (although it seems his gitlab is down atm).
Iāve found a few errors in the code and fixed it for a current iZone system and currently having it working for me in a HE system. I think Iāll probably re-write the entire driver stack and use the child component thermostats etc
Excellent, yes I have an edited version with the fixes too. Sorry I should have passed that over sooner. If you do end up rewriting it with the child components definitely share that for all that would be great. I am sure @markus would be keen to see that too.
Nice. The only thing Iād have done if I was just starting out and it was within my control not my builders Iād have gone wired sensors per zone not the battery RF ones. The batteries do last a long time but I have had to replace some and or had to press the pair button because they have dropped off a a couple of times since 2019.
Otherwise itās a great system and these drivers integrate it well. I have built on it more with NodeRed but these drivers easily allow that to happen.
Thatās true @bendarklighter and while I donāt have any issues myself due to only 6 theromstats but bigger systems most definitely so simply polling the once for all would make a lot of sense. Anyways I am looking forward to what @gslender puts together
Another question from the new guy (so close to purchasing air conā¦ )
Iām definitely getting wired sensors!
Is the WiFi Bridge the only way to connect to the controller. Or can the controller itself be cabled back to a switch?
The iZone CB (control bridge) uses RF to talk to the CPU (green router) in ceiling including RF sensors if you have them too. My CB is connected to ethernet (100Mbps). My tablet on wall in loungeroom is ethernet back to the CPU. So no WiFi is used at all.
@Beeble1983 I saw you are expecting to use the Nexus tablet as an android device to run your Hubitat dashboard. Fyi it cannot do that itās completely locked down for iZone only it does act as a zone sensor for that area though which is handy.
)
