Daikin Onecta (Cloud) Binding [4.0.0.0;5.0.0.0)

Great,

Then I will delete the Target temperature channel

thanks a lot.

Can confirm that Target Temperatur (and Target Temperatur Min Value, Target Temperatur Max Value, and Target Temperature Value Step) as UNDEF. I use the SetPoint without any issues.

Hello everyone I need some input.

In the pull request, where my code for the binding is being reviewed by other developers, the question arose whether the number of channels regarding energy consumption is actually useful. Onecta provides this data in a strange way: per day, per hour, and per month. I simply send this data through the binding. But I think this is pointless and, above all, inaccurate.

I also created a yearly total in the binding, in which I calculate the consumption myself based on all the separate data per month. Every year, this channel also correctly resets to 0.

From this data, you can also calculate the consumption on a specific date.

My idea is to remove this strange consumption data from the binding and only pass on the calculated annual totals.

Am I missing something in this reasoning?

Greetings Alexander

I think it’s worth knowing the monthly totals.

Would agree that the monthly totals are useful.

Hi Alexander,

Is there a technical reason to remove channels? Users can choose to use or ignore channels according to their personal needs. If there is a valid reason, then yes, channels can be removed. For power consumption, the current year is sufficient. If you keep the raw data, everyone can add whatever they want. But if there is no real reason to remove channels, then leave them as they are, since they map 100% to the Onecta GUI.

Hi @HenMus
The RawData had to be removed due to pullrequest comments.

My approach was also, “I’ll put everything in there so everyone can choose for themselves.”
But:
The problem with the energy items is that I can’t get the naming to conform to the desired standard.

The labels can consist of a maximum of 3 words and a maximum of 23 characters.
This doesn’t work with the following labels:

  • Energy Heating Last Year, January
  • Energy Heating Current Year, January
  • Energy Cooling Last Year, January
  • Energy Cooling Current Year, January

These are 4 different channels. And I really don’t know how to shorten this while keeping it unique and meaningful.
Mayby naming :

  • Energy Heating Last Year, January → Energy Heating Jan-1
  • Energy Heating Current Year, January –> Energy Heating Jan
  • Energy Cooling Last Year, January –> Energy Cooling Jan-1
  • Energy Cooling Current Year, January –> Energy Cooling Jan

I can ask to the reviewer if this is ok ?

On the otherhand if the yearly power is stored the data can be selected with an simple sql

This gives me a headache :frowning:

Hi,

The totals for current day and current year are enough.

I remember that way back I tried using those “strange” values to track daily consumption but they didn’t work as you would expect. I didn’t have time or interest to start debugging what the issue was so I switched to current day counter which works well when combined with timescaledb time_buckets.

So I’d suggest to double check if the values make any sense before deciding to keep them.

Hi @Tommo ,

I agree with that.

I added the yearly totals myself by adding the monthly totals for the current year. This gives a much better picture of energy consumption over time when you store this in a database.

I am not happy with any other fields either. But the code reviewer approved the naming suggestion so all the fields are renamed so the users of the binding can decide for themselves if they want to use it.

Perfect naming.

Will the official release still require Openhab cloud? I hope not.

If you mean Onecta Cloud. Yes this the only way to connect to the units

@Alexander_Drent Good evening! On a Pi3 with OH5 I had a working binding, many thanks for developing the binding! Today I changed hardware from Pi3 to Pi5, what do I have to do to get the binding working again on the new hardware, I restored a backup from Pi3 on the new Pi5, but on the Pi5 the bridge won’t come online. When I reconnect my “old Pi3” to ethernet, the Onecta bridge comes online (on the Pi3). Many thanks for your answer.

I think you need to re-login to Daikin on the Pi5. https://ip-of-pi5/onecta. Keep in mind that if the new Pi has a different IP address, this also needs to be set on the Daikin developer site.

Thanks for the fast response! (Dankjewel ;)). the IP of the Pi5 is the old IP of the Pi3, it had a fixed IP in my router which was MAC based, I have changed the MAC in my router. All other bindings/Node Red/MQTT, which were on the Pi3 now work on the Pi5. When I connect my Pi3 to my router it gets a new IP, that is why I can see that my Pi3, even on another IP address gets the Onecta bridge online. I can’t login on the address you give me with the Pi5 IP. My “local” Pi IP is a basic 192.168.1.x address. Many thanks for your efforts to help me :slight_smile:

Alexander PM-ed me yesterday, problem was solved, many thanks @Alexander_Drent !!!

Account went offline and would not come back on - However – I have managed to go through and rebind the account, and all appears to now be working again.

I suppose this is not the correct thread, but where do I get basic information about:

  1. Where I can dowload the latest Daikin Onecta (Cloud) Binding?
  2. How to install this Binding in openHAB?

These are some basic stuff, maybe you can send me some useful links. Thanks for understanding.

Jan

See the first post in this thread :grinning_face:

Hi guys,

I have just set a new instance of OH 5 and the only thing I cant get working is the Onecta.
I cant get the redirect to be https - it always reverts to http with :443 in the address :frowning: Manually I can change it, and I get success and Online on the next page.
However also in the Thing - I dont have username /pass section to enter details like what is in the PDF.
I have the onecta Thing online - but what I am missing? Can I change the code to enter this?

Oh - EDIT::: I should have mentioned,
I’m running OpenHAB 5.1.3 in docker, on my QNAP453
My default page is http://qnap453:8085 / secure is https://qnap8445
i’m not sure if this makes any difference? I’m assuming not, being this bridge is setup via the myopenhab cloud setup?
Sorry - I know enough to be dangerous - I might need educating a little here

Update for my situation in Australia. I’m using a BRP072A42 wifi adapter too.

Turns out the OneCTA App is NOT available in Australia. This above process is for only those (which was also missed in the first topic, and might be useful) - dont bother with this unless you’ve migrated to ONECTA app for control of your Daikin unit.
If you can still use the Daikin Mobile Controller app on your phone, then you can use the original Daikin Binding. As soon as I installed this, it found my unit and IP. I just had to enter the key that is on the side of the adapter itself. Then everything was discovered and controllable.

Hope that helps someone else :slight_smile:

Hi Alexander,

I’m trying to use the latest Onecta binding with openHAB 5.1.0 on openHABian (Raspberry Pi) and BRP069C4x WiFi adapters (6 indoor units).

Binding installed:

org.openhab.binding.onecta-5.0.0-SNAPSHOT.jar

from:

onecta-5.0.0-Snapshot-2

The binding loads correctly and appears in the UI. The Account Thing can be created, but immediately goes to:

OFFLINE - COMMUNICATION_ERROR

openhab.log shows:

Error in OnectaConnectionClient

org.openhab.binding.onecta.internal.exception.DaikinCommunicationException:
org.openhab.binding.onecta.internal.oauth2.auth.OAuthException:
OAuth client service is not available.

Stack trace:

Caused by:
org.openhab.binding.onecta.internal.oauth2.auth.OAuthException:
OAuth client service is not available.

at OpenHabOAuthTokenRefresher.getOAuthClientService(...)

What I already verified:

  • openHAB 5.1.0

  • OAuth2 feature installed

  • OAuth2 bundle active

Karaf:

feature:list | grep oauth

openhab-core-auth-oauth2client
Started

bundle:list | grep -i oauth

openHAB Core :: Bundles :: OAuth2
Active

I also:

  • restarted openHAB

  • cleaned cache/tmp

  • reinstalled the binding JAR

  • restarted the bundle

The error remains unchanged.

Questions:

  1. Is Snapshot-2 actually compatible with openHAB 5.1?

  2. Has anyone successfully used this version with OH5?

  3. Is there a newer build than Snapshot-2 for OH5?

  4. Could the binding still be compiled against OH4 services only? The Marketplace entry still states:

Daikin Onecta (Cloud) Binding [4.0.0.0;5.0.0.0)

Any hints would be appreciated.

Thanks!