Damn, I think you are right… good but not good 
Via the remote it does give the error, via ONECTA andriod app it does not show any errors. Now I have to call someone to diagnose issue.
Thanks for your quick reply and implementation of the feature, at least I am aware of the issue now.
1 Like
Oh, I was wrong, after checking the error codes PDF it became clear that error U0 did not show up via the remote control, the only long beep was on 00. So the issue is only visible with the data the homey app comes up with. The units are also still working and only 1,5 years old. Any thought on how to check if the error show up for an invalid reason?
Can your restart the Homey Daikin ONECTA app and the hit the diagnostic report.
Let’s see what I can find in the total data object from Daikin cloud from your units.
Did you receive my message?
Yes, will look on to it asap
Hi !
I have the same issue.
Error U0-00 in Homey, nothing in Onecta and nothing on the remote controls.
Brand new AirPump (< 6 mois) so unlikely to have a leak issue (but not impossible) !
1 Like
While truly appreciating the extension in flow cards available, I have run into some problems. After the update to the latest version, I am currently unable to set target temperature at .5-degree intervals using flows. Any value ending with .5 sent to my Daikin Origo ii appears to be rounded to integer values as they appear in Homey and the Onecta app. Is this by design or unintended?
Installation: Origo ii + Homey Pro 2023
Best, Kranis
Same here - when looking at the Home Assistant integration, which I also use, I can see that the error code is there, but neither indoor nor outdoor units are in any error state. So I wonder if the error code doesn’t get cleared when the error state ends, and only has meaning in combination with an error state…
Could also be an error on the API - since there is nothing in the Onecta app, but I do see caution states on some of the indoor units over the last days, also on a pretty much brand new unit. Interestingly, not on all indoor units, but starting at the exact same time on those that do report it.
No, in the API there are separated object for the caution, warning and error state wich can be true or false.
Just checking every 30 min if these items are true or false and when true generate a notification.
Not much I can do about it just relaying on the data from Daikin.
After removing one of my air-2-air’s I cannot add it again. Permission is given, it is present in the Daikin app, restarted Homey (pro). It now keeps telling me there is no new device found.
Please advise…
Update: Tried it again after an hour or 2 on a different computer and both units show up to be added. Apparently I have been too impatient :o)
1 Like
I keep getting the warning i am using the deprecated air-to-air driver, but its really not clear how to fix this? I as indicated in this post removed and re-aded the units. However there is no air-to-air2 thing i can select anywhere whilst re-adding, and the error on please change driver keeps being there every so many hours.
I am really struggling with the not so clear instructions, and how do i resolve this? The app was already updated 5.0.7 version. Any clue how to resolve this?
It’s happens a lot that, when I go to the operationmode in the Homey app, it displays another mode than the mode it’s actually in. Resulting in the unit being changed to that other mode. For example these day the operationmode is always on Heating. But when I randomly go to the operation mode in the Homey app it sometimes says another mode and then the unit switches to that mode while it shouldn’t switch anything. Maybe it’s an idea to fetch the operationmode data everytime that tab is being used (if possible)?
Or am I the only one facing this? I have 2 Daikin FDXM units.
Should not be possible, the API call is only be generated I’d there is manual interaction.
But it could also be a bug, let me see if I can reproduce it, or maybe you can send me a video with the homey (web)app and ONECTA app
This part of de code it not changed old drivers vs AIr-2-Air driver.
I have installed the new driver and am using the air-to-air pump. This also works fine. However, when I try to trigger “air conditioning is on” in advanced flows, it doesn’t do anything. In the flow “air conditioning is off,” the follow-up trigger does work. Anyone else experiencing this issue?
1 Like
Here the same. I thought I was doing something wrong in my flows 
Let me see if I can reproduce this…
Could be a bug …
It is a bug…will create a fix version later this day.
1 Like
Thank you so much for your quick work!
