Hi all,
I’ve been working about 8 months on this and it’s finally time to release this beast.
Below is a link to the custom_component which support Daikin Skyzone.
Note: This very different to the Daikin SkyFi component.
Supported Skyzone controllers: BRC230TZ4, BRC230TZ8, BRC24TZ4 and BRC24TZ8
Supported Daikin Models: Any FDYQ & FDYQN unit fitted with a Skyzone controller (Single or 3 phase)
Drop it into your custom_components folder and just simply add the ‘skyzone:’ tag into your config and done.
Full discovery supported. It will add in the climate module, temperature sensors and zones.
I’ll update the documentation over the next few days to with some of the features, but pretty much it’s all there.
Here my setup.
https://github.com/BenNeumeister/daikinSkyzone
I’ve already created a pypi package so it installs the API in the background nicely.
Incase you want a peek at the API see here;
https://github.com/BenNeumeister/daikinPyZone
There probably aren’t alot of other users out there with this system, but this is what got me into the whole HA thing as the factory control tablet is really really limited.
Cool things I can do now;
- Multiple temperature zones
- Usual cool HA stuff with temps etc.
- Ditch clunky APP and also get rid of the daikin server for remote access.
So yeah, hit me up if you find any bugs, or have any suggestions, but I tried to do as much as possible with the API I managed to reverse engineer 
configuration.yaml
99% of users all you will need is;
skyzone:
The other 1%;
skyzone:
name: 'Daikin Climate Control' (optional)
password: 1234 (optional)
host: 192.168.1.101 (optional)
scan_interval: 60 (optional)
debuglevel: 2 (optional)
pollextsensors: 0 (optional)
name: Give the Climate instance a specific name for HA/Google Home/Alexa. Default is ‘Daikin Skyzone’
password: Adapter password as configured in the Daikin Tablet. API will show an error if this is wrong or needed.
host: Set the Daikin AP IP address if you want to bypass discovery. Might save 2-3 seconds during init
scan_interval: Set how often the API is polled. 60 seconds is default. I wouldn’t go any lower than 30seconds as you risk much overlapping. Any higher and you risk loosing refrigerant temp data, especially when it goes into de-ice or a lubrication cycle.
debuglevel:
- 0 - Disabled (default)
- 1 - See information updated as it comes in and polling flags
- 2 - See raw info received from unit. Only really useful if somethings not working right.
For debugging, you will need to configure the logging component and monitor for ‘debug’.
pollextsensor:
- 0 - Disabled (default)
- 1 - Enabled. Will trigger the API to switch between external sensors every 3minutes instead of showing ‘Unknown’. Has some side-affects as the Daikin unit itself will use this value for ~3mins. So if your zones have very different temperatures, don’t use it.
