Hi @ninjaltd
I’m starting a new thread to announce the availability of the latest version of the binding.
This release has versions of the plugin working with Airtouch4 tested against OH 3.4.0 and OH 4.1.3
The underlying library (airtouch-utils) does support Airtouch5 as well, so if there is demand I can look at adding support for Airtouch5 to this binding.
What about openHAB 4.2 ?
Actual developments should be at this version…
Oh thanks! I’ll look at building against that version and update the post when I get it built.
Many thanks mate, tested and working on my 4.1.3 install.
Great. Thanks for the confirmation.
Hey @netwolfuk I’m sure many of us are looking to move to v5 soon. Are you still maintaining this and able to provide a build for v5?
I’ll have a look tonight. It feels familiar, but maybe I am getting airtouch5 and openhab5 confused.
If I do have a build for oh5, it will be quite old and will need some love. I won’t get to look at it until at least next month.
Sorry. The latest build I have is against OH4.2
I’m still running 4.3.2 on my OH server.
Is there a guide somewhere outlining what devs need to do to upgrade their add-ons to OH5?
I’m still on 4.3.5 too and using your 4.1 build without too much issue. I’m sure it’s possible it may just work. I guess I’ll be the guinea pig and find out tonight … 
I spent an hour on it tonight and managed to:
Auto discovery didn’t work because my docker instance is not on the iot vlan where the airtouch4 is.
I don’t have CI working on the new branch, so can’t do a release, and there looks to be some changes I should do to support yaml configuration.
Also some items have poor defaults now that oh5 seems to have lots more dimensions for values.
I don’t think I’ll get back to this until next week at least though sorry.
That’s impressive work for only an hour. Sounds like it’s mostly functional.
@netwolfuk Let us know if you make any progress on a release for v5.
Not much testing, but you can try this jar
I’ve not looked at what I need to do to support YAML or anything. This is simply the same code as last time but compiled against OH 5, and Java 21.
hi, I’m looking to upgrade my HVAC with this unit, so interested if this will this be rolled into prod release ?
Do you mean a PR raised against the main OpenHAB repo?
I have a lot of tidy up for that. I looked a few months ago and found a bunch of boiler plate code that I had never updated, so I guess I’m saying not to hold your breath
Are you looking at Airtouch4 or Airtouch5?
Are you looking at OH4 or OH5?
thanks for the reply , I now have AirTouch 5 installed with OH5.
ok. I have not written the code for Airtouch5 in OpenHAB yet. I’ll try to see what I can get done over the next week. I already have the code running for Airtouch4, and have builds for OH3, OH4 and OH5 . I’ll run a build on on OH 5.1 over the weekend. However, you’re not running AT4, so that won’t help you yet, since the protocol is very different
The good news is that one of my neighbours has an AT5, so the library and console are tested. They just don’t run OH, so that part was never finished off.
In the mean time, you could try the console app I wrote to test the library. Assuming you can control your AT5 from that console, you should be good when I get the OH code running.
Support for AirTouch5 added. Please see:
I ran the console app today here is the output after a long wait…
Found 'AIRTOUCH5' at '192.168.0.15' with id #####(removed)###
Exception in thread "Airtouch5ConnectorThread" java.lang.IllegalArgumentException: Unable to resolve Address from supplied bytes. Supplied bytes are: 'FF90'
at airtouch.v5.constant.MessageConstants$Address.getFromBytes(MessageConstants.java:56)
at airtouch.v5.connector.Airtouch5ConnectorThread.messageStarted(Airtouch5ConnectorThread.java:153)
at airtouch.v5.connector.Airtouch5ConnectorThread.run(Airtouch5ConnectorThread.java:85)
after this nothing…
posted log on Github
Does A/C need to be ON?
No. AC can be off. Just as long as the the AirTouch is alive on the network, it should work.
From what I can tell from your post, the UDP broadcast is successful, and the AirTouch is responding on the network. Yey!
I don’t have the code in front of me at the moment, but it looks like the discovery code is not passing the address correctly to the connector.
You could try manually setting the address of the airtouch before running the console app.
It’s documented on the console github page, but it’s just an environment variable.