[APP][Pro and Cloud] Daikin ONECTA

This is what Daikin have to say about it.

Users should be mindful of the impact of sending rapid commands to heat pumps, especially those involving the start or stop of the compressor (e.g.onOffMode). To maintain reliability and durability, it’s advisable to avoid initiating compressor start and stop operations more frequently than once every 10 minutes.

It’s essential to consider that the startup behaviour of the compressor consumes more energy than during steady-state operation.

The flows I have developed directly limit this number of on and off cycles. The automation settings change the target temperature of the secondary circuit flow according to the electricity exchange price, and do not allow the heat pump to turn on to obtain the target temperature in only one of the rooms of the building or at high electricity prices.

Hi everydody,
Last week I had this message : Your using a old deprecated driver for your Daikin device PAC - Chauffage. Please upgrade to the universal air_2_water_heatpump driver to benefits the full potential of homey. Just remove the current Daikin device named PAC - Chauffage and add a new one. After upgrade please check al flow for this device! Be aware that in the future the old drivers will be removed!

But air_2_water_heatpump in unavalable when I try to add it.

Thanks a lot.

If your using the latest version you should not get this message anymore.

It is/was pre-work for a next release that shouldn’t be in the 5.1.x release
But you can safely ignore it , and with latest version 5.2.x the message will not be published again.

Thanks for your answer. That is I told to me because with 5.2 it dispears.
Do you know when the 6.x.x will be released ?

I reinstall the Daikin ONECTA app after all connections where lost with the “old” app. The new app can not find any device? I use version 5.2.0. I have the app startup again and even the Homey pro2023 is start up again. Stil no devices are found.

Yes if you use version lower then 5.0.0 you using the “old” Daikin cloud platform and Daikin is decommissioning this platform.

But again if you read this topic probaly the answer is already given.
Best guess based on your info:

After another try, everthing is working again. :slight_smile:

1 Like

Hi
First of all thx for this fantastic app.
Just started to make flows and a dashboard for my home Daikin ftx airco with wifi module.
It is a holiday home so people also use the remotes to control the daikin airco.
Is it possible that when the ir remote has been used that the status of the airco in Homey is not correct?
So there is no feedback from the airco (via Onecta app) to Homey? (For ex onn/off status)

There are 2 methods 2 get the current status from unit.

  1. Every 1/2 hour there will be a API call to get all status from all units.
    This can’t be quiker due to rate-limiting (200 calls the day)
  2. There is a websocket connection that will getting nearly realtime updates.
    This websocket should be a active connection to the Daikin Cloud but i notice its not very
    stable due to some reasons. There is a reconnecting mechanisme in the code but also that
    fails sometimes
    Sometimes it helps to restart the whole daikin app.

Hi Michel
Thx, restarting the app fixed the problem.
Is there any chance that this websocket connection will become stable because this is today for me a missing link. If we rent out our house, we can not check if it works or not…
Thx and good evening! (still great to have this app though!)
Ivan

1 Like

No, for numerous reasons it’s disconnects unexpectedly.
If this happens I trying to reconnect the websocket after a short timeout that increase when no connection can be made.
The increasing timeout is done for not overloading the Daikin cloud

I have trouble with the token being revoked or something. Any clue what it is?

Don’t know the exact reason but simple repair your device(s), you need to reauthorize with you Daikin credentials and a repair triggers this

Thank you for replying quickly. I tried to repair several times, but there seems to be an issue with the authorization website where it shows a blank page. I finally learned on how to «fix» it by going back one page and then go forward again, quickly.

But this did not fix anything, so I had to remove the device from Homey and add it again. So far it works fine.

Dear Mickel,

First of all, thanks a bunch for the app, its a really valuable addition to my home automation (and cost cutting :D). I’m using a few flows to control my heatpump to run in the night when temperatures drop below a certain value. Sometimes however, homey seems to think that the temperatures are no longer changing (see the flat part(s) in the graph below for example). A repair seemed to help two days ago but this night it again got stuck. Is there anything else i could try except the repair and re-login? Thanks!

Hi, after the latest updates, Altherma no longer updates the hot water temperature or the outdoor temperature where the heat pump is located. It only detects the temperatures once when I restart the Homey app, and then they remain stuck at that value. Turning the heat pump on and off works perfectly; only the temperature detection is not working.

I asume that you also send a diagnostic report?
If so , please share the ID of this report so i can match the question and the report.

First of al there is nothing changed in the Altherma drivers in last updates.

See below in and in previous post the methods for updates

In the diagnostic reports i see 2 reasons why.

  1. websocket is disconnect and did try to reconnect 15 times (till now) but fails due to unknow reasons.
    because on every failed reconnect the timer is increased the next connection after 15 fails we be tryed after 5120 sec(83min)

  2. The should be a 30min update by rest api call. but i don’t see this back in the log.
    I will investaged this…

  1. Its a bug, test version with the fix : Daikin ONECTA | Homey
    It’s pending for live by certification by Athom.
2 Likes

I have sent a diagnostic report with the current app version. The report ID is e1dfe9ff-f8f0-4274-9ba0-f2dff23e9fc4.

Now I will update to the test version and check if the issue is resolved. Thanks for your support! :blush: