I’m using OH 2.4.0 Stable, the previous binding was working OK on that.
Ahh… ok this one was built for 2.5 and afaik, there was a big change in the internals of 2.5 compared to 2.4. Sorry you’ll have to wait until you’ve upgraded to 2.5.
To revert simply delete the jar from the addons folder and reinstall the daikin binding from paperui.
I’ll try and test this week - the airbase controller should be installed at the holiday house tomorrow, then I need to find somewhere secure to install the Pi 
No worries, 2.5 is not stable enough for my liking.
2.5 final should be out today… I’m running rc1 at-home and it’s been very stable
Far too many issues in the threads I see
AFAIK, only from people who pulled the trigger too soon before it was officially announced. These people were upgrading from 2.5RC1 too.
Hi Gents,
Does anyone know why this occurs on boot?
21:05:01.446 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'daikin:airbase_ac_unit:DaikinAP65279' changed from INITIALIZING to ONLINE
21:05:01.759 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'daikin:airbase_ac_unit:ducted_ac' changed from INITIALIZING to ONLINE
21:05:01.760 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel settemp
21:05:01.759 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel power
21:05:01.761 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel indoortemp
21:05:01.762 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel airbasefanspeed
21:05:01.761 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel mode
21:05:01.768 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Power changed from NULL to OFF
21:05:01.782 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_SetPoint changed from NULL to 23.0 °C
21:05:01.786 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Mode changed from NULL to COLD
21:05:01.789 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Fan changed from NULL to LEVEL_1
21:05:01.895 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_IndoorTemp changed from NULL to 26.0 °C
21:05:02.008 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Zone1 changed from NULL to OFF
21:05:02.009 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Zone2 changed from NULL to OFF
21:05:02.011 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Zone3 changed from NULL to OFF
21:05:02.013 [INFO ] [smarthome.event.ItemStateChangedEvent] - DaikinACUnit_Zone4 changed from NULL to ON
21:05:02.341 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel zone1
21:05:02.687 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel zone2
21:05:03.021 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel zone3
21:05:03.360 [WARN ] [.internal.handler.DaikinAcUnitHandler] - Received command of wrong type for thing 'daikin:airbase_ac_unit:ducted_ac' on channel zone4
Stil works fine though!
These are fixed in git code - probably in the 2.5 release…
Ah, fair enough. Guess I’ll ignore then 
Has anyone actually even tried this (the latest binding) on 2.4? 2.5 looks like a disaster. All I see are issues, I’ve got a perfectly stable 2.4 system so the last thing I want to do is update to fix an issue to have 100 new problems!
I don’t think it will work on 2.4. There have been many many changes in the package references due to the move away from ESH, afaik. You could quickly try it out yourself, it’s very simple. Delete the daikin binding from your openhab, and drop the jar into the addons folder. To revert, simply delete the jar and reinstall the 2.4 binding from paperui.
I know you’re been saying how 2.5 is full of problems. I really don’t understand what the problems are. I haven’t encountered any issues in 2.5. I’ve been using it since about 2.5M2 and I’ve just upgraded to 2.5.1 two days ago, it has been very very stable and bug free for me. Perhaps it’s to do with specific bindings that I am not using?
On the contrary, I had problems with MQTT in 2.4 particularly the outgoingtransformation and the transformation chain that didn’t work.
A search of the forum on 2.5 upgrades yields many many posts my 2.5 upgrade experience etc etc.
Guess I’ll do the test like you suggest, thanks Jim.
I’m running 2.5 at my house, and my holiday house. Rock solid at both sites.
Hi Guys
What is the supported FAN command for AUTO? LEVEL_1, LEVEL_2, LEVEL_3 works just fine, but no auto setting I can find?
Thanks!
I think @jimtng did some work on this, but the code hasn’t been approved yet, so isn’t in any releases yet…
Yep, in my version, the fan speed options are AIRSIDE (if supported), LEVEL_1, LEVEL_2, LEVEL_3, LEVEL_4, LEVEL_5, AUTO_LEVEL_1, AUTO_LEVEL_2, AUTO_LEVEL_3, AUTO_LEVEL_4, AUTO_LEVEL_5. The AUTO_LEVEL_X isn’t supported by all controllers, so when it’s not supported, it won’t work.
I discovered you can set 5 different levels of fan speed, and I believe the fan speed does has 5 different speeds, even though on the physical controller you can only set to 3, that being level 1, level 3 and level 5. There are even physical controllers only allowing level 1 (low) and level 5 (high)
@dastrix80 have you upgraded to 2.5 yet?
Hi Jim,
No , it’s not stable enough. I’m still reading all sorts of issues related to 2.5.1 and 2.5.2 so I’ve no desire to be going to something less stable. Ill just sit where I am until such time as its stable.
Cheers
My PR has been merged!
1 Like
How do I detect if AirBase goes offline?
A few times the device is not online and I have to reboot A/C