Great new,
after intensive testing by @rb44 ( again, thanks Rocky 
), the integration of IntesisBox devices has been merged into openHAB 3.0 and will be available with the next SNAPSHOT, probably tomorrow morning.
@rb44 If you are going to test it, the structure has changed, so please check the README 
@hmerk, Great news indeed. Just the excuse I needed to get myself an instance of openHAB 3.0 running. Binding installed smoothly and went online immediately, properties display as expected.The binging receives updates from the AC Control Panel and likewise sends commands to the AC unit as expected.
Removing the binding is also effortless and immediate.
These are the properties:
The only issue I had was in regards to the display of the Error Status, Error Code and Ambient Temperature, but this is most likely di to myself not having found the right README
The ambient temperature starts with the correct value then goes to null, the other two read-only values are always null (though they show correctly within the properties screen). Will have to study a bit more, in the meantime this is what it looks like.
Also need to learn how to configure/change the Target Temperature.
Note this is from a clean install no items file etc.
Will play some more later if I get more time.
Thanks, R.
Thanks for posting Rocky,
I will check later, as there seem to be something wrong, still seeing properties for eerorCode and errorstatus.
Will dive into it and come back later…
Best
Hans-Jörg
Fixed and patch provided as PR…
Fix got merged, should be available with next SNAPSHOT tonight.
Figured thanks. Just updated to S1986, removed pages, items, things etc and re-created Intesis thing.
Target temperature is looking better but Error Status and Code are still null.
From memory they were channels in the original version of the binding but in the unified binding they became properties.
I suspect something went lost in translation and 3.0 has now Errors show as properties and channels.
Personally happy for them to be channels so the error status can be trapped programmatically i.e. to generate alerts… but no big deal.
Basically i suspect the ERR channels are not updated because they were no longer meant to be there, but… might be wrong.
Additionally seems we’ve lost the half degree on the Target Temperature, the 23.0 below should read 23.5
Thanks
R.
My latest fix will be available tomorrow,
errorCode and errorStatus have been refactored to be channels again, but the updates had been missing. Fixed now.
I will check the targetTemp half degree issue again…
Have you followed my examples in the readme and set step=1 ?
After tonights update, please try again with step=0,5 …
Yep you right, operator error. I think temperatures comes through ok, more a matter of item / UI setup.
Will try a classic setup with items and sitemap files
Build #1990 did it for me.
Error code and status come through correctly.
Ambient Temperature is now back to displaying Err, think due to default format of the auto generated item being incorrect. When format overridden (eg %.1f) in sitemap or State Description or anywhere else then displays correctly.
Strangely Target_Temperature never suffered from this formatting issue, maybe something to do with the attributes of the channel? In any case once format is set everything is looking good and behaving as expected.
Binding is fully functional, @hmerk thanks a lot! 
Thanks for testing @rb44 
That’s strange, as I did not change anything on the ambientTemperature channel and as I understood, Build 1986 was showing up correct. I will check if I can optimize this.
Both channels are build with the same attributes.
Best
Hans-Jörg
Pull Request to set default pattern to %.1f created…
Fix should be available with SNAPSHOT-1992…
It is indeed, best version yet. Used wizard to create Equipment, Items and Page Cells. All populated well formatted automatically including all lookups on Unit Mode, Fan Speed and Vane Swing Mode which is really great thanks!
Translated well to HABPanel also by using server provided format and item options.
great…
Does this procedure still work? I do not get it to work. When cloning the AirCon repo, there is no query_cli.py
Does the intesis binding also work with the FGLAir app (Fujitsu) WIFI modules?
I know the IP’s of my devices but password field does not correspond with the pincodes on the stickers, at least In get communication error.
No, not supported by the binding. AFAIK, these devices are cloud only, no local access.
Does this binding work with all intesis box adapters? I just realized, that the Mitsubishi adapter INWMPMIT001I000 will be compatible with my AC.
@jensflorian Yes. Tested extensively against a Fujitsu but no reason for it to not work with a Mitsubishi or any other WMP gateway from Intesis. If you do go ahead let us know how it worked for you.
