Can you post the output of your http://192.168.1.xx/skyfi/aircon/get_control_info please?
My output: ret=OK,pow=0,mode=1,stemp=23,dt1=23,dt2=23,dt3=23,f_rate=3,dfr0=1,dfr1=3,dfr2=1,dfr3=1,f_airside=0,airside0=0,airside1=0,airside2=0,airside3=0,f_auto=0,auto0=0,auto1=0,auto2=0,auto3=0,f_dir=0,dfd0=0,dfd1=0,dfd2=0,dfd3=0,dfd7=0,filter_sign_info=0,cent=0,en_cent=0,remo=2
I do wonder what would happen if I send the f_airside=1 command - I assume I’d get a NOK response code…
From http://192.168.1.xx/skyfi/aircon/get_model_info:
....,en_airside=1,....
I presume this means “enable airside” ? What does yours say?
Mine says …,en_airside=0,…
So we should be able to parse the get_model_info string to know if this is supported or not. If not supported, if the Airside mode is selected, the code should not get run, so the fan speed won’t change.
Hi @Paul_Smedley,
I’ve managed to get my development environment set up on my laptop, and was able to build the daikin binding. I’ll work on the airbasefanspeed but I might rehash some of the info classes a bit first. I wish I could just work off your PR since I noticed you’ve had some work on Refresh as well as that homekitmode.
While looking through the binding’s code, I noticed that there’s no channel name called “setpoint” as mentioned in the doc’s example. Both airbase and non airbase use “settemp”. Upon closer inspection, the documentation also stated that “settemp” is the channel name for both non airbase and airbase. So the Doc’s example is wrong about the non airbase being “setpoint”. I’ll submit another PR for the doc.
Good work - should I give you access to my github? I’ll fix up the homekitmode commit hopefully tonight - no idea how the PW2 stuff got mixed up in there - I have to admit git isn’t my friend 
On your system, assuming it does have the en_airside=0, could you please test setting f_airside=1? I’m curious to know what will happen. Please post the before and after output from get_control_info. My guess is that nothing will change, which means we won’t need to implement any special checks and just let the binding user either use Airside or not. Making design decisions isn’t easy. The alternative to this model is to introduce yet another channel to toggle f_airside, but that will complicate things in a different way.
I’m new to git myself. I think it would be easier / less complicated if I waited for your latest PR to be merged, then I’ll work off that directly to the main openhab repository.
In the mean time I’ll just work on it on my private repository until then. That way I am not disturbing anyone.
@Paul_Smedley, I’ve got my implementation of airside / auto levels working now. I will wait until your PR is accepted, then I’ll merge your changes and do another PR for the Airside code. How long does it normally take for a PR to be accepted?
Hi Jim,
I’ll try and test f_airside tonight - I assume it will fail - which is OK. I still wonder if there is a way to ‘build’ the options for fan mode based on the capability of the AC unit - so that we wouldn’t show airside unless en_airside was set to 1 - but that’s a nice to have. Using an items file, people can choose not to show the Airside option anyway.
In terms of my last PR - I suspect the delay is due to them trying to release 2.5 ASAP - so I suspect that as my PR is an improvement, not a fix, it will need to wait until 2.5 is released.
Cheers,
Paul.
That indeed would be nice, but afaik, the list of options is static, and defined in thing-types.xml ?
The other approach would be to have “Airside” as a separate On/Off channel. I wouldn’t mind this, as I think I can just tweak my items / rules / sitemap to show a unified fan speed setting that would include Airside. What do you think?
The Airbase Fan speed would still need to change: - There is no “AUTO” setting - does yours have it? Instead, mine has Auto level 1, auto level 2, and auto level 3 in addition to non-auto level 1-3.
Yep - best I can tell, that’s the case.
Does Airside on still show a fan speed? or does this disappear then? What does the Daikin app do when you press fan? toggle Airside/Low/Medium/High/Auto Low/Auto medium/Auto High ?
Agree - mine is as you describe above - I think this comes down to me mis-understanding how things worked with the Airbase vs the Euro Daikin controllers.
Cheers,
Paul
When it’s “Airside” the wall controller just says “Auto” with zero “bars” for the fan speed, only the fan logo shows up. As I press the “Fan” button on the wall, it will cycle through this “Auto with no bars”/Low/Medium/High/Auto Low/Auto Med/Auto High
The app on the phone does the same, except instead of “Auto” it actually says “Airside”.
This is why I implemented Airside into fanspeed instead of a separate channel. However I do see your point about those without Airside support. My implementation would simply switch the fan to Low / level1 when Airside is not supported, if the controller is fine with it, otherwise, it probably just doesn’t change the fan setting- I’d like to know exactly which will happen but it needs you to test it on your system. To test it:
- Set your fan to medium or high
send set_control_info with …,f_airside=1,f_rate=1… and see whether your fan setting changes to low or remain unchanged.
Either way I think it’s an acceptable behaviour, and those who don’t support Airside can just omit it in their sitemap.
I don’t know enough about this stuff to have any idea if this might be relevant -
1 Like
That appears to be the ticket! One question, as a binding user, where can I find the list of state options other than from the documentation? Answer: PaperUI
@Paul_Smedley, what do you think about splitting the ac_unit and airbase_ac_unit into two separate classes, perhaps create an airbase handler which derives from the acunithandler? I know it will be quite a big job but it would also reduce some duplications in the code and it should make things cleaner. I’ll be happy to take on this task. Something to think about, not for the immediate future. Right now I’ll just add my fan code onto the existing structure.
1 Like
I asked Kai on Twitter, he suggested “Sure, should work out of the box when using a ChannelOptionProvider in the binding. Best if you ask in the forum for help: https://t.co/tfJPSaXzm0”
https://www.openhab.org/docs/developer/bindings/thing-xml.html has more details on this - this is cool 
Sounds good, but this is way beyond my knowledge of java
If you guys need any output from the airbase units on a multizone unit with the multi speeds (i too have auto with 3 difference speeds, plus auto and the 3 manual speeds) i’m happy to give you what debug you may need. Just sing out! love this binding.
1 Like
Hi @dastrix80, it sounds like you have the controller that supports “airside” (auto) like mine. I’ve added this fan mode on my forked version, which I will submit soon. If you’d like to try it out I can post a 2.5 jar somewhere for you in the mean time.
Could you please paste the output of:
http://192.168.1.xx/skyfi/common/basic_info
http://192.168.1.xx/skyfi/aircon/get_model_info
http://192.168.1.xx/skyfi/aircon/get_zone_setting
http://192.168.1.xx/skyfi/aircon/get_sensor_info
http://192.168.1.xx/skyfi/aircon/get_control_info
Thanks!
1 Like
Sure Jim, Ill do that this afternoon. I’m in no rush , happy to wait.
To be honest, having it on low is more than enough for me right now!