Daikin Onecta (Cloud) Binding [4.0.0.0;5.0.0.0)

Pollegazon · June 7, 2026, 10:58am

Hi uwe,

did you follow the instructions found here https://github.com/adr001db/openhab-addons/releases/download/onecta.4.1.3-OIDC-1/Manual.to.get.the.Onecta.Binding.to.work.pdf

uwe.quelfes · June 8, 2026, 8:08am

Hello Paul, thank you very much. That was exactly what I needed to get it done !!! Just one comment for other users who, like me, don’t do this every day: In the Thing configuration fields, you need to enter the email address and password of your Daikin account, NOT the newly assigned Daikin ID. In hindsight, it seems obvious, but I completely messed up on this during setup and kept looking for the problem elsewhere. Thanks again!

JackyKNX · June 12, 2026, 10:44am

Hi Alexander,

first of all, thank you for creating and maintaining this binding. I have successfully connected my Daikin Altherma 3 heat pump using the latest openHAB 5.0.1 version and the current Onecta binding.

I found what looks like a bug related to ON/OFF control of the heating zone.

Environment

openHAB 5.0.1
Onecta Binding 5.0.0.202510111234
Daikin Altherma 3
Outdoor unit: ERGA06EAV3
Indoor unit: EHVH08S18EJ6V
Gateway: BRP069A78

What works

Reading all values works correctly.
State changes made in the Onecta app are immediately reflected in openHAB.
Writing some parameters works correctly.
For example, changing the Leaving Water Offset Setpoint from openHAB is immediately visible in the Onecta app.

What does not work

Sending:

Daikin_Onecta_climateControl_Pompa_ciepla_Power ON

or

Daikin_Onecta_climateControl_Pompa_ciepla_Power OFF

does not change the heat pump state.

Debug log

The binding sends:

Request:

https://api.onecta.daikineurope.com/v1/gateway-devices/e5ce65e7-cb7f-46a5-873a-06ca94f4399e/management-points/climateControl/characteristics/onOffMode

Body:
{“value”:“on”}

Response:
{“code”:“MANAGEMENT_POINT_MISSING”,“message”:“Could not find management point”}

Interesting observation

The raw API data for my unit contains:

embeddedId = climateControlMainZone

managementPointType = climateControl

and:

onOffMode.settable = true

Therefore it looks like the API supports writing the ON/OFF state, but perhaps the binding uses “climateControl” instead of the actual management point identifier “climateControlMainZone” when sending commands.

This would explain why:

reading works,
onOffMode is reported as settable,
API returns MANAGEMENT_POINT_MISSING during write operations.

I have also opened a GitHub issue with logs and details:

github.com/openhab/openhab-addons

Bug: ON/OFF control does not work for Daikin Altherma main zone (MANAGEMENT_POINT_MISSING)

opened 10:34AM - 12 Jun 26 UTC

JackyKNX

bug

# Bug: ON/OFF control does not work for Daikin Altherma main zone (MANAGEMENT_PO…INT_MISSING) ## Environment * openHAB version: 5.0.1 * Onecta Binding version: 5.0.0.202510111234 * Device type: Daikin Altherma Heat Pump * Outdoor unit: ERGA06EAV3 * Indoor unit: EHVH08S18EJ6V * Gateway: BRP069A78 ## Description The binding successfully discovers and reads all data from my Daikin Altherma system. Read operations work correctly and state updates are reflected in openHAB. Some write operations also work correctly. For example: * Leaving Water Offset Setpoint can be modified from openHAB. * The change is immediately visible in the official Daikin Onecta application. However, ON/OFF control for the climate control zone does not work. ## Observed behavior Sending: ```text Daikin_Onecta_climateControl_Pompa_ciepla_Power ON ``` produces the following API request: ```http PUT /v1/gateway-devices/<device-id>/management-points/climateControl/characteristics/onOffMode ``` with body: ```json {"value":"on"} ``` The API responds with: ```json { "code": "MANAGEMENT_POINT_MISSING", "message": "Could not find management point" } ``` The same happens when sending OFF. ## Debug Log ```text setPowerOnOff : e5ce65e7-cb7f-46a5-873a-06ca94f4399e, climateControl, ON Request : https://api.onecta.daikineurope.com/v1/gateway-devices/e5ce65e7-cb7f-46a5-873a-06ca94f4399e/management-points/climateControl/characteristics/onOffMode Body : {"value":"on"} Response : {"code":"MANAGEMENT_POINT_MISSING","message":"Could not find management point"} ``` ## Device structure returned by Onecta API The API returns the following management point: ```json { "embeddedId": "climateControlMainZone", "managementPointType": "climateControl", "managementPointCategory": "primary", "managementPointSubType": "mainZone", "onOffMode": { "settable": true, "value": "off", "values": ["off", "on"] } } ``` The important detail is that: ```json "embeddedId": "climateControlMainZone" ``` while the binding appears to send commands to: ```text management-points/climateControl ``` ## Possible root cause It looks like the binding uses the management point type: ```text climateControl ``` instead of the actual embedded management point ID: ```text climateControlMainZone ``` for write operations. This would explain why: * reading works correctly, * the device reports `onOffMode.settable=true`, * API returns `MANAGEMENT_POINT_MISSING` when a write is attempted. ## Additional observations The API reports: ```json "operationMode": { "settable": false, "value": "heating" } ``` Therefore operation mode changes not working is expected. However, ON/OFF appears to be supported because: ```json "onOffMode": { "settable": true } ``` and should be writable. ## Expected behavior The ON/OFF command should successfully switch the Altherma main zone on and off, just like in the official Daikin Onecta application. Please let me know if I can provide additional debug logs or API traces.

Could you please have a look and tell me if this theory makes sense?

Thanks again for all your work on the binding.

Mario_S · June 18, 2026, 8:43am

Hello JackyKNX,
I have exactly the same problem as you—have you been able to find a solution?

Thank you in advance.

Best regards

Alexander_Drent · June 18, 2026, 9:12am

Hi, i will look into this

Alexander_Drent · June 27, 2026, 2:04pm

@Mario_S and @JackyKNX,

1,5 week ago I created a test fix and I thought I had informed you about that as well. But I think something went wrong there.

I hope this resolves the issue with the OnOff function. Would you be willing to test this for me? I don’t have a heat pump connected to Onecta myself, so I can’t test it personally.
Once this part is resolved, I’ll need solve this for the other items as well.

https://github.com/adr001db/openhab-addons/releases/download/onecta-5.0.0-snapshot-4-quicktest/org.openhab.binding.onecta-5.0.0-SNAPSHOT.jar

Greetings Alexander

Mario_S · July 1, 2026, 5:51pm

Hi Alex,

I just tested your version, and it works fine. I tested the “POWER” activation on the heater and the water heater, and it works for both.
Let me know if you need me to run any more tests.
Thank you very much for your help.
Best regards

the-ninth · July 5, 2026, 9:28am

Hi,

First of all, thank you very much for all the work you’ve put into this binding!

I’m running openHAB 5.1.4 and installed the SNAPSHOT2 build, but I’m getting the following error:

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

One thing that surprised me is that the Account Thing doesn’t ask for a username or password. Am I correct in assuming that these are supposed to be provided through an OAuth login flow instead?

Do you have any idea what could be missing or misconfigured to cause the error above?

Thanks!

EDIT: I installed openhab-core-auth-oauth2client and restarted openHAB. Both the OAuth2 client bundle and the Onecta binding bundle are shown as active, but the error still persists.

Alexander_Drent · July 5, 2026, 11:00am

Hi Robert,

Did you folow the setup manual at the top of this topic ?

Greetings Alexander

mstormi · July 5, 2026, 11:09am

Sorta off-topic question, I know, but I have been unable so far to figure out a definite answer:

Is there any logically and feature-wise equivalent means to locally control a Daikin device without
dependency on the cloud?

Alexander_Drent · July 5, 2026, 11:45am

Hi Markus,

Well, I would also prefer it if operating Daikin devices were possible without a cloud and everything could be controlled locally. But the problem is that the newer Daikin units are no longer locally accessible. As soon as these units are connected to Wi-Fi, they start communicating via the Onecta service.

There are controllers for sale at faikin.au, and with these, you could make the units locally accessible. However, from what I have read, you need a fair amount of technical knowledge, with the risk of damaging the unit.

the-ninth · July 5, 2026, 12:02pm

Yes, but I didn’t see anything there about OAuth client dependencies.

Basically, I just copied the SNAPSHOT2 JAR into the addons directory and then created an Account Thing. Is there anything else I need to install or configure, or did I miss a step?

Alexander_Drent · July 5, 2026, 12:08pm

I mean this PDF document

(Installation/connection Guide)

Alexander_Drent · July 5, 2026, 12:24pm

@JackyKNX and @Mario_S.

At the top of this topic you can find “PreRelease Tag onecta.5.0.0-SNAPSHOT-5” this fixes similar issues for heatpump.

greetings alexander

the-ninth · July 5, 2026, 12:44pm

Sorry, I missed that one before. I’ve found it now next to the JAR download link.

I got it working now, thanks a lot!

There were a few hiccups along the way:

The manual shows username/password fields in the Thing configuration, but I don’t see those. This does not seem to matter, though.
The redirect URI was generated as http instead of https in the OAuth dialog.
After successful authentication, it also tried to redirect to the http success link, so I got a 400 Bad Request error. However, that also does not seem to matter, since the authentication worked and the Account Thing is now online.

Thanks again for your help!

the-ninth · July 19, 2026, 3:46am

Hi,

I have been running the binding for sometime now, and the account Thing regularly goes offline with a communication exception. When I restart the binding it comes online again.

COMMUNICATION_ERROR
org.openhab.binding.onecta.internal.exception.DaikinCommunicationException: java.util.concurrent.ExecutionException: java.net.UnknownHostException: api.onecta.daikineurope.com

Are others here experiencing this as well?

@Alexander_Drent would it maybe be an option for a future version of the binding to have some form of auto-reconnect?

stevendp · July 20, 2026, 12:18pm

Yes I have the same. I even created a rule that then automatically disables / enables the account thing to keep it up & running. That works ..

Alexander_Drent · July 20, 2026, 12:25pm

I will take a look at it. But first i try to get the pull request approved

Pollegazon · August 5, 2026, 8:24pm

Continuing the discussion from [Daikin Onecta (Cloud) Binding 4.0.0.0;5.0.0.0):

Hi,

Today I’m experiencing issues with the binding. Not the first time I get (smaller) issues which I can easily solve by disabling and enabling the binding via the guy. Today this is not working. I’m using binding version 5.0.0.202507270959 running on Openhab 5.1. Here are the details

runtimeInfo:
version: 5.1.0
buildString: Release Build
locale: en-US
systemInfo:
configFolder: /openhab/conf
userdataFolder: /openhab/userdata
logFolder: /openhab/userdata/logs
javaVersion: 21.0.9
javaVendor: Debian
osName: Linux
osVersion: 6.6.31+rpt-rpi-v8
osArchitecture: aarch64
availableProcessors: 4
freeMemory: 96884072
totalMemory: 994050048
uptime: 13219857
startLevel: 100
addons:

* automation-jsscripting
* binding-homewizard
* binding-matter
* binding-mqtt
* binding-nest
* binding-network
* binding-somfytahoma
* binding-telegram
* misc-openhabcloud
* persistence-mapdb
* persistence-rrd4j
* transformation-jsonpath
  clientInfo:
  device:
  ios: false
  android: false
  androidChrome: false
  desktop: true
  iphone: false
  ipod: false
  ipad: false
  edge: false
  ie: false
  firefox: false
  macos: true
  windows: false
  cordova: false
  electron: false
  capacitor: false
  nwjs: false
  webView: false
  webview: false
  standalone: false
  os: macos
  pixelRatio: 2
  prefersColorScheme: dark
  isSecureContext: false
  locationbarVisible: true
  menubarVisible: true
  navigator:
  cookieEnabled: true
  deviceMemory: N/A
  hardwareConcurrency: 8
  language: en-BE
  languages:
  * en-BE
  * nl-BE
  * nl
  * fr-BE
  * fr
  * en-GB
  * en-US
  * en
    onLine: true
    platform: MacIntel
    screen:
    width: 1800
    height: 1169
    colorDepth: 30
    support:
    touch: false
    pointerEvents: true
    passiveListener: true
    intersectionObserver: true
    themeOptions:
    dark: dark
    autoDarkMode: true
    bars: light
    homeNavBar: default
    homeBackground: default
    disableExpandableCardAnimation: false
    blocklyRenderer: null
    disablePageTransitionAnimation: false
    hideChatInput: false
    webAudio: false
    visibleBreakpointDisabled: false
    userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36
    (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36
    timestamp: 2026-08-05T20:05:48.427Z

This is the debug from the binding after doing a bundle:nnn restart

2026-08-05 20:51:54.157 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : ServiceFactory.getService()

2026-08-05 20:51:54.159 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Checking constructor public org.openhab.binding.onecta.internal.service.DeviceDiscoveryService()

2026-08-05 20:51:54.159 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Found constructor with 0 arguments : public org.openhab.binding.onecta.internal.service.DeviceDiscoveryService()

2026-08-05 20:51:54.160 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : This thread collected dependencies

2026-08-05 20:51:54.160 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : getService (ServiceFactory) dependencies collected.

2026-08-05 20:51:54.160 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Querying state satisfied

2026-08-05 20:51:54.160 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : For dependency osgi.ds.satisfying.condition, optional: false; to bind: [[RefPair: ref: [{org.osgi.service.condition.Condition}={service.id=6, service.bundleid=0, service.scope=singleton, service.pid=0.org.osgi.service.condition.ConditionImpl, osgi.condition.id=true}] service: [null]]]

2026-08-05 20:51:54.161 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : getting activate: activate

2026-08-05 20:51:54.162 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Locating method activate in class org.openhab.binding.onecta.internal.service.DeviceDiscoveryService

2026-08-05 20:51:54.163 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Declared Method org.openhab.binding.onecta.internal.service.DeviceDiscoveryService.activate([interface org.osgi.service.component.ComponentContext]) not found

2026-08-05 20:51:54.163 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Found activate method: public void org.openhab.binding.onecta.internal.service.DeviceDiscoveryService.activate()

2026-08-05 20:51:54.164 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : invoking activate: activate: parameters []

2026-08-05 20:51:54.164 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : invoked activate: activate

2026-08-05 20:51:54.165 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Changed state from satisfied to active

2026-08-05 20:51:54.168 [DEBUG] [ernal.service.DeviceDiscoveryService] - Starting background discovery

2026-08-05 20:51:54.170 [DEBUG] [ernal.service.DeviceDiscoveryService] - Scanning for devices

2026-08-05 20:51:54.171 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 20:51:54.172 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 20:51:54.172 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 20:51:54.173 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 20:51:54.174 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 20:51:54.175 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 20:51:54.176 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 20:51:54.176 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 20:51:54.177 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 20:51:54.178 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 20:51:54.178 [DEBUG] [internal.handler.OnectaBridgeHandler] - initialize.

2026-08-05 20:51:54.178 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 20:51:54.179 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 20:51:54.180 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 20:51:54.181 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 20:51:54.183 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 20:51:54.202 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 20:51:54.204 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 20:51:54.214 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 20:51:54.215 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 20:51:54.225 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 20:51:54.236 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 20:51:54.238 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 20:51:54.243 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 20:51:54.258 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Jerne Airco

2026-08-05 20:51:54.283 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Uitbreiding

2026-08-05 20:51:54.286 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Ouders Airco

2026-08-05 20:51:54.295 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Birte Airco

2026-08-05 20:51:54.306 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Eetkamer

2026-08-05 20:51:54.315 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 20:51:54.322 [DEBUG] [ta.internal.api.Enums$FanMovementHor] - Unexpected FanMovementHor value of "null"

2026-08-05 20:51:54.326 [DEBUG] [ta.internal.api.Enums$FanMovementHor] - Unexpected FanMovementHor value of "null"

2026-08-05 20:51:54.331 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 20:51:54.483 [ERROR] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://idp.onecta.daikineurope.com/v1/oidc/token failed with error code invalid_grant, description The provided authorization code or refresh token is invalid.

2026-08-05 20:51:54.486 [DEBUG] [uth2.auth.OpenHabOAuthTokenRefresher] - Cannot obtain access token from persistent storage.

org.openhab.core.auth.client.oauth2.OAuthResponseException: null

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.lambda$0(OAuthConnector.java:96) ~[?:?]

at com.google.gson.internal.bind.TreeTypeAdapter.read(TreeTypeAdapter.java:95) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1359) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1260) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1170) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1107) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.doRequest(OAuthConnector.java:368) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.grantTypeRefreshToken(OAuthConnector.java:227) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthClientServiceImpl.refreshTokenInner(OAuthClientServiceImpl.java:338) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthClientServiceImpl.getAccessTokenResponse(OAuthClientServiceImpl.java:379) ~[?:?]

at org.openhab.binding.onecta.internal.oauth2.auth.OpenHabOAuthTokenRefresher.getAccessTokenFromStorage(OpenHabOAuthTokenRefresher.java:121) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaSignInClient.getToken(OnectaSignInClient.java:66) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaSignInClient.isOnline(OnectaSignInClient.java:74) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaConnectionClient.isOnline(OnectaConnectionClient.java:89) ~[?:?]

at org.openhab.binding.onecta.internal.handler.OnectaBridgeHandler.initialize(OnectaBridgeHandler.java:84) ~[?:?]

at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:580) ~[?:?]

at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:149) ~[?:?]

at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) ~[?:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]

at java.lang.Thread.run(Thread.java:1583) [?:?]

2026-08-05 20:51:54.495 [DEBUG] [internal.handler.OnectaBridgeHandler] - pollDevices.

When I perform an disable enable using the things gui I get this error

2026-08-05 21:21:43.187 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : ServiceFactory.getService()

2026-08-05 21:21:43.187 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : This thread collected dependencies

2026-08-05 21:21:43.188 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : getService (ServiceFactory) dependencies collected.

2026-08-05 21:21:43.188 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Querying state satisfied

2026-08-05 21:21:43.188 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : For dependency osgi.ds.satisfying.condition, optional: false; to bind: [[RefPair: ref: [{org.osgi.service.condition.Condition}={service.id=6, service.bundleid=0, service.scope=singleton, service.pid=0.org.osgi.service.condition.ConditionImpl, osgi.condition.id=true}] service: [null]]]

2026-08-05 21:21:43.189 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : invoking activate: activate: parameters []

2026-08-05 21:21:43.189 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : invoked activate: activate

2026-08-05 21:21:43.189 [DEBUG] [ernal.service.DeviceDiscoveryService] - bundle org.openhab.binding.onecta:5.0.0.202507270959 (249)[org.openhab.binding.onecta.internal.service.DeviceDiscoveryService(426)] : Changed state from satisfied to active

2026-08-05 21:21:43.192 [DEBUG] [ernal.service.DeviceDiscoveryService] - Starting background discovery

2026-08-05 21:21:43.192 [DEBUG] [ernal.service.DeviceDiscoveryService] - Scanning for devices

2026-08-05 21:21:43.194 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 21:21:43.194 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 21:21:43.195 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Eetkamer' with ID '35fab2c8-c92c-4893-9181-bf20bda5058d'

2026-08-05 21:21:43.195 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 21:21:43.196 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 21:21:43.196 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Jerne Airco' with ID '5c14aa82-c164-4aeb-a195-4c44170e7bc2'

2026-08-05 21:21:43.197 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 21:21:43.197 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 21:21:43.198 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Birte Airco' with ID '645cc908-7723-462e-9e97-59136841bec5'

2026-08-05 21:21:43.198 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 21:21:43.199 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 21:21:43.199 [DEBUG] [internal.handler.OnectaBridgeHandler] - initialize.

2026-08-05 21:21:43.204 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Uitbreiding' with ID '85766d6e-2ddc-427c-9e35-8bf6b7b51dfd'

2026-08-05 21:21:43.205 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta indoorUnit unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 21:21:43.206 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta climateControl unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 21:21:43.206 [DEBUG] [ernal.service.DeviceDiscoveryService] - Discovered a onecta gateway unit 'Ouders Airco' with ID '972c732b-9c69-4a82-a4ab-a7bb47cb4445'

2026-08-05 21:21:43.218 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 21:21:43.220 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 21:21:43.222 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 21:21:43.237 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 21:21:43.237 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 21:21:43.241 [DEBUG] [nternal.handler.OnectaGatewayHandler] - refreshDevice : GATEWAY,

2026-08-05 21:21:43.244 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 21:21:43.252 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Jerne Airco

2026-08-05 21:21:43.257 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 21:21:43.273 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Uitbreiding

2026-08-05 21:21:43.295 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Ouders Airco

2026-08-05 21:21:43.304 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Eetkamer

2026-08-05 21:21:43.317 [DEBUG] [ta.internal.api.Enums$FanMovementHor] - Unexpected FanMovementHor value of "null"

2026-08-05 21:21:43.319 [DEBUG] [internal.handler.OnectaDeviceHandler] - refreshDevice : CLIMATECONTROL, Birte Airco

2026-08-05 21:21:43.319 [DEBUG] [ta.internal.api.Enums$FanMovementHor] - Unexpected FanMovementHor value of "null"

2026-08-05 21:21:43.323 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 21:21:43.327 [DEBUG] [rnal.handler.OnectaIndoorUnitHandler] - refreshDevice : INDOORUNIT,

2026-08-05 21:21:43.486 [ERROR] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://idp.onecta.daikineurope.com/v1/oidc/token failed with error code invalid_grant, description The provided authorization code or refresh token is invalid.

2026-08-05 21:21:43.490 [DEBUG] [uth2.auth.OpenHabOAuthTokenRefresher] - Cannot obtain access token from persistent storage.

org.openhab.core.auth.client.oauth2.OAuthResponseException: null

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.lambda$0(OAuthConnector.java:96) ~[?:?]

at com.google.gson.internal.bind.TreeTypeAdapter.read(TreeTypeAdapter.java:95) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1359) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1260) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1170) ~[?:?]

at com.google.gson.Gson.fromJson(Gson.java:1107) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.doRequest(OAuthConnector.java:368) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthConnector.grantTypeRefreshToken(OAuthConnector.java:227) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthClientServiceImpl.refreshTokenInner(OAuthClientServiceImpl.java:338) ~[?:?]

at org.openhab.core.auth.oauth2client.internal.OAuthClientServiceImpl.getAccessTokenResponse(OAuthClientServiceImpl.java:379) ~[?:?]

at org.openhab.binding.onecta.internal.oauth2.auth.OpenHabOAuthTokenRefresher.getAccessTokenFromStorage(OpenHabOAuthTokenRefresher.java:121) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaSignInClient.getToken(OnectaSignInClient.java:66) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaSignInClient.isOnline(OnectaSignInClient.java:74) ~[?:?]

at org.openhab.binding.onecta.internal.api.OnectaConnectionClient.isOnline(OnectaConnectionClient.java:89) ~[?:?]

at org.openhab.binding.onecta.internal.handler.OnectaBridgeHandler.initialize(OnectaBridgeHandler.java:84) ~[?:?]

at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?]

at java.lang.reflect.Method.invoke(Method.java:580) ~[?:?]

at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:149) ~[?:?]

at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) ~[?:?]

at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]

at java.lang.Thread.run(Thread.java:1583) [?:?]

2026-08-05 21:21:43.498 [DEBUG] [internal.handler.OnectaBridgeHandler] - pollDevices

.

I’ll probably remove the bundle and try to set it up once more unless there is something else I can try?

Pollegazon · August 7, 2026, 6:35am

I’ve upgraded to 5.2. Onecta binding version is 5.0.0.202507270959 but still get the following error;

grant type refresh_token to URL https://idp.onecta.daikineurope.com/v1/oidc/token failed with error code invalid_grant, description The provided authorization code or refresh token is invalid.

I’ll reinitialize the binding. Probably something got invalidated over time and is not refreshing