Can't connect new Hue Bridge Pro to openhab

  • Platform information:
    • Hardware: Proxmox
    • OS: openhabian on Linux openhabdeb 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux
    • Java Runtime Environment:
      openjdk version “21.0.8” 2025-07-15 LTS
      OpenJDK Runtime Environment Temurin-21.0.8+9 (build 21.0.8+9-LTS)
      OpenJDK 64-Bit Server VM Temurin-21.0.8+9 (build 21.0.8+9-LTS, mixed mode, sharing)
    • openHAB version: 5.0.1 (Build)

I have just migrated my square white Hue bridge to a new square black Hue Bridge Pro. I used the migration feature in the Hue app (replace an existing Bridge). Hoping I could retain my openhab setup. All the lights and setup have been transferred to the new Hue Bridge Pro.

I changed the ip-address in the Hue API v2 Bridge, I also created a new Application key, using the api debug tool of the bridge directly ( needed to press the button :slight_smile: ).

Using the ip-address and application-key, from the command line of my openhab system this works just fine,

curl command and response
openhabian@openhabdeb:~$ curl -s --insecure --location http://192.168.3.87/api/$SECRET/lights| jq | head -30
{
  "1": {
    "state": {
      "on": false,
      "bri": 1,
      "hue": 33090,
      "sat": 61,
      "effect": "none",
      "xy": [
        0.3669,
        0.3706
      ],
      "ct": 230,
      "alert": "none",
      "colormode": "ct",
      "mode": "homeautomation",
      "reachable": true
    },
    "swupdate": {
      "state": "noupdates",
      "lastinstall": "2025-09-11T10:05:49"
    },
    "type": "Extended color light",
    "name": "Keuken Plafond",
    "modelid": "LCT001",
    "manufacturername": "Signify Netherlands B.V.",
    "productname": "Hue color lamp",
    "capabilities": {
      "certified": true,
      "control": {

If I use the same ip-address and applicationkey in openhab I get the following error:

COMMUNICATION_ERROR
An unexpected exception occurred: java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

This is the definition of the Bridge:

UID: hue:bridge-api2:5c29b86073
label: Hue API v2 Bridge
thingTypeUID: hue:bridge-api2
configuration:
  applicationKey: <removed>
  ipAddress: 192.168.3.87
  checkMinutes: 60
  useSelfSignedCertificate: true

Forgot to mention: same issue in Openhab4, upgrade to OH5 did not change anything
Has anyone connected the new Hue Bridge Pro to openhab yet?

I have the same problem.
Can’t connect it. But it’s not the only thing I can’t connect anymore.
Direct linking in Homematic for example also wont work anymore.

Signify seems to have changed something from V2 to the Pro Bridge…

That really hampers my setup.
Even tried linking it as a matter device, instead through the Hue binding, but that still doesn’t work at all because I can’t seem to get it working in Docker because of ipv6…


EDIT:
I finagled with my ipv6 settings one last time before giving up and lo and behold.
It worked all of a sudden.
Could now add OH as a matter bridge to Homekit AND for this purpose here also add the Hue Bridge Pro as a matter device to OH via the Matter Binding and generating a Matter Controller as thing and adding the Hue bridge via Matter Code.

That is done via the App.
Settings > Smart Home > + > Other Apps > Generate Code

And Voila. I could add the Bridge and it immediately started working. Painful is, that you have to add everything again with all those channels and delete all those old things from the hue binding.

No Idea, if the Hue binding can be updated to natively support the new bridge.
But thanks to standardization via Matter at least it works for now.

I am working on it…

This doesn’t look like an API v2 request..

Just out of interest, has anyone already tried if there is some kind of legacy / partial API v1 support in the Hue Bridge Pro?

I am extensively using CLIP sensors which cannot be replaced by API v2 to my knowledge…

You are right, but to make sure it also works, this is:

openhabian@openhabdeb:~$ curl -s --insecure --location 'https://192.168.3.87/clip/v2/resource/light' --header 'Accept: application/json' --header "hue-application-key: $SECRET" | jq | head -30
{
  "errors": [],
  "data": [
    {
      "id": "06606574-7acf-4882-bcb8-3189ce8dd028",
      "id_v1": "/lights/35",
      "owner": {
        "rid": "5802dbae-fb67-4edc-b509-86b31b22272c",
        "rtype": "device"
      },
      "metadata": {
        "name": "Hue Being Mika",
        "archetype": "ceiling_round",
        "function": "functional"
      },
      "product_data": {
        "function": "functional"
      },
      "identify": {},
      "service_id": 0,
      "on": {
        "on": false
      },
      "dimming": {
        "brightness": 100,
        "min_dim_level": 0.1
      },
      "dimming_delta": {},
      "color_temperature": {
        "mirek": 366,

:slight_smile:

Could you please turn on log:set TRACE org.openahab.binding.hue and then disable and reenable the thing?

I have set the log level and disabled/enabled the brisge thing but nothing is added to openhab.log.
(I have added part of the event log that shows bridge goes offline / online. And the lines around same timestamp in the openhab.log).

What am I missing here?

Logger                                             │ Level
───────────────────────────────────────────────────┼──────
ROOT                                               │ WARN
com.zsmartsystems.zigbee                           │ ERROR
com.zsmartsystems.zigbee.dongle.ember.internal.ash │ ERROR
javax.jmdns                                        │ ERROR
javax.mail                                         │ ERROR
martsystems.zigbee                                 │ ERROR
openhab.event                                      │ INFO
openhab.event.AddonEvent                           │ ERROR
openhab.event.ChannelDescriptionChangedEvent       │ ERROR
openhab.event.GroupStateUpdatedEvent               │ ERROR
openhab.event.InboxUpdatedEvent                    │ ERROR
openhab.event.ItemAddedEvent                       │ ERROR
openhab.event.ItemChannelLinkAddedEvent            │ ERROR
openhab.event.ItemChannelLinkRemovedEvent          │ ERROR
openhab.event.ItemRemovedEvent                     │ ERROR
openhab.event.ItemStateEvent                       │ ERROR
openhab.event.ItemStateUpdatedEvent                │ ERROR
openhab.event.RuleAddedEvent                       │ ERROR
openhab.event.RuleRemovedEvent                     │ ERROR
openhab.event.RuleStatusInfoEvent                  │ ERROR
openhab.event.StartlevelEvent                      │ ERROR
openhab.event.ThingAddedEvent                      │ ERROR
openhab.event.ThingRemovedEvent                    │ ERROR
openhab.event.ThingStatusInfoEvent                 │ ERROR
openhab.event.ThingUpdatedEvent                    │ ERROR
org.apache.cxf.jaxrs.sse.SseEventSinkImpl          │ ERROR
org.apache.cxf.phase.PhaseInterceptorChain         │ ERROR
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.ssh.SshUtils                │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.apache.sshd                                    │ WARN
org.eclipse.lsp4j                                  │ OFF
org.jupnp                                          │ ERROR
org.openahab.binding.hue                           │ TRACE
org.openhab                                        │ INFO
org.openhab.binding.zigbee                         │ ERROR
org.openhab.persistence.influxdb                   │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
smartsystems.zigbee.dongle.ember.internal.ash      │ ERROR
su.litvak.chromecast.api.v2.Channel                │ ERROR

Event log (snippet)

2025-09-15 20:24:30.367 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:bridge-api2:5c29b8607
3' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): An unexpected exception occurred: java.util.con
current.ExecutionException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.
provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested targe
t -> javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCe
rtPathBuilderException: unable to find valid certification path to requested target
2025-09-15 20:24:30.370 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:678
089f1-705b-4cb3-8c4c-5f18911ff428' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.372 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:16c
9cb21-d7ae-4b3e-8cf6-c078c238a243' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.372 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:room:5c29b86073:6575a
4a3-b71c-483d-9c60-ca836ec6ab0f' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.372 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:dd8
118b5-9d4e-431d-960f-8c8352d2e954' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.372 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:a3c
14870-f17d-4ca8-a0fa-59709eb07ab4' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.373 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:zone:5c29b86073:9b6f2
60a-db95-4d66-bdf1-f8c1c8c07b25' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.373 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:ba7
c4c34-3868-4201-9452-0d16d36ae6c2' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.373 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:227
daebb-4dac-4d7a-8c29-323aadc2e9eb' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.373 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:95e
d4058-2cd0-4d78-b0ec-a3d4ee820f78' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.373 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:a28
a9374-280d-45cb-91b3-8088b7b745ce' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.374 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:room:5c29b86073:0ea67
bf6-7852-43a2-bfa1-c88fc2cf06c1' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.374 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:device:5c29b86073:bb0
942a2-d32d-4fbf-aaca-cd59e563dd65' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.374 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:room:5c29b86073:42c03
d86-2ea6-4b42-af00-3ea72db51be3' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2025-09-15 20:24:30.375 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:room:5c29b86073:bd0d0
308-fb66-4011-b43d-49df37ef5160' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)

openhab.log (snippet)

2025-09-15 20:23:29.206 [WARN ] [o.internal.handler.SystemInfoHandler] - No information for channel batter
y#remainingTime with device index: 0
2025-09-15 20:23:29.215 [WARN ] [o.internal.handler.SystemInfoHandler] - No information for channel batter
y#remainingCapacity with device index: 0
2025-09-15 20:23:29.507 [WARN ] [o.internal.handler.SystemInfoHandler] - No information for channel batter
y#name with device index: 0
2025-09-15 20:23:30.106 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection t
o 'localhost' with clientid 334850e9-d7b0-4187-99c6-b2b327568f44
2025-09-15 20:23:31.314 [INFO ] [nding.http.internal.HttpThingHandler] - Using the secure client for thing
 'http:url:Toon_Thermostaat'.
2025-09-15 20:23:31.815 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2025-09-15 20:23:33.946 [INFO ] [o.internal.handler.AstroThingHandler] - Scheduled Positional job astro:su
n:local every 300 seconds
2025-09-15 20:24:10.832 [ERROR] [converter.ZigBeeConverterSwitchLevel] - 001788010D2AA652: Error 0xffff setting client binding
2025-09-15 20:24:20.459 [ERROR] [converter.ZigBeeConverterSwitchLevel] - 001788010D2AA652: Error 0xffff setting client binding
2025-09-15 20:24:49.207 [WARN ] [o.internal.handler.SystemInfoHandler] - No information for channel battery#remainingTime with device index: 0
2025-09-15 20:24:49.209 [WARN ] [o.internal.handler.SystemInfoHandler] - No information for channel battery#remainingCapacity with device index: 0
2025-09-15 20:24:50.104 [ERROR] [verter.ZigBeeConverterBatteryPercent] - 001788010D2AA652: Error 0xffff setting server binding
2025-09-15 20:25:34.414 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Zone_2' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2025-09-15 20:25:34.416 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Zone_2': {thing/channel=Type description yamahareceiver:availableinputZone_2 for yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Zone_2:zone_channels#input not found, although we checked the presence before.}
2025-09-15 20:25:34.545 [WARN ] [core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Main_Zone' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
2025-09-15 20:25:34.546 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing 'yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Main_Zone': {thing/channel=Type description yamahareceiver:availableinputMain_Zone for yamahareceiver:zone:9ab0c000_f668_11de_9976_f086206cf828:Main_Zone:zone_channels#input not found, although we checked the presence before.}
2025-09-15 20:25:49.347 [ERROR] [nverter.ZigBeeConverterGenericButton] - 001788010D2AA652: Error 0xffff setting client binding for cluster 6
2025-09-15 20:25:58.984 [ERROR] [nverter.ZigBeeConverterGenericButton] - 001788010D2AA652: Error 0xffff setting client binding for cluster 6
2025-09-15 20:26:08.600 [ERROR] [nverter.ZigBeeConverterGenericButton] - 001788010D2AA652: Error 0xffff setting client binding for cluster 8
2025-09-15 20:26:18.215 [ERROR] [nverter.ZigBeeConverterGenericButton] - 001788010D2AA652: Error 0xffff setting client binding for cluster 8

It looks like some issue with the validation of the SSL certificate over the HTTP v2 connection. I guess the new bridges have a different certificate than the prior ones. This occurs before there is even anything for OH to start logging. And without some details of the transactions it will be hard to find out. Do you know Wireshark? And if so can you send a capture of when you try to enable the bridge?

Yeah. I looked it up. It has a self signed certificate which OH does not trust. We had a way to trust the prior bridge server certificate, but not yet the new bridge.

https://github.com/openhab/openhab-addons/issues/19337

I actually tried to add the 2 CA certificates mentioned in the Hue documentation to my debian trusted store, but hit a bump in dns and connecting to the bridge and then realized that it would be of little use as the binding uses an ip-address anyway, so I did not pursue that

Would you still want the wireshark trace?

@dries_dokter / @Hundertvolt1 / @tylerstyle I made a new PR which should (in theory) allow the binding to support the certificate of the new black v3 bridge natively at OH binding level without requiring the certificate to be installed at operating system level. However as I do not yet have such a bridge, it needs people like yourselves to kindly test it.

https://github.com/openhab/openhab-addons/pull/19401

Hm, actually I don’t even have a Hue Bridge Pro :wink: I was more like observing how others have a go with it and looking if the most crucial features don’t break.

The transfer process of actually moving configurations from the old bridge to the new one is scary and gruesome, with no possible way back and without a real backup and restore functionality. If something goes wrong, I’m literally sitting in the dark.

Signify should really arrive in reality concerning this instead of throwing new products on the market allover. Their stuff is good but not unbreakable.

Yeah well, this is why I want to be really sure, but don’t have a real device yet…

Hey thanks for your work! I have a hue bridge pro and tried to use the jar file from github.

I am running openhabian v 5.0.1.

I just moved the .jar file to usr/share/openhab/addons and restarted the system.

I checked the version number in the binding settings and it was correct.

I started the device search and nothing was found.

Is there any help i can provide to make it work? If you need somenlogs just tell me how to get them.

You need to uninstall the official Hue binding via the OH UI first before you copy the new Jar to your addons folder (otherwise probably the original version will continue to be used).

Set the binding logging settings to TRACE and post the results during a disable/enable of the binding..

I will of course gladly test your update.

I do need to make sure that I can do the correct test. As I used the workaround steps described in Hue Bridge Pro support.

So I assume I have to:

  • Remove the certificate from keystore /etc/ssl/certs/adoptium/cacerts
  • Remove my bridge pro hostname from the hosts file
  • Remove the current hue binding
  • Download and use the jar file
  • Use the ip address, not the hostname in the bridge thing

Right?

Yes, but remember to restart openhab, so:

  • Remove the certificate from keystore /etc/ssl/certs/adoptium/cacerts
  • Remove my bridge pro hostname from the hosts file
  • Remove the current hue binding
  • Restart Openhab service or whole machine
  • Download and use the jar file
  • Use the ip address, not the hostname in the bridge thing

Today i have set up a fresh installation of openhab 5 on a raspberry cm5. I will trie to install the binding and send you the logs this weekend.

If it helps i could give you remote access to this system or we could meet on discord and you could trie some things remotely.

edit:

i did a first trie and wasnt able to install the binding. it looks like the binding needs gson-2.13 and gson-2.11 is installed. when i install 2.13 i get a cvonflict because both are installed.

I will trie a few more things later…

Where I can find new jar with fix for Hue Bridge Pro binding?