Hue integration stuck spinning in 2.4.0

Looks like I'm stuck in the spinning wheel mode. I've left it for a while but no progress. Anyone else facing this?

1 Like

Anything in Logs?

A bunch if these:

java.lang.RuntimeException: Failed to acquire semaphore for method refreshV1 within 120 seconds on line 1975 (method refreshV1)

Are you on the latest platform version? Existing install or new? (Specifically, is the Hue Bridge child device present with this app as the parent? Trying to think of what might be doing this...)

Yes, just updated to latest platform which is what I believed caused this due to the new Hue features added for the built-in Hue integration. I can see the Hue Bridge device and have sent Initialize, Refresh Connect commands which go through but it seems that there is an issue with the V1 authentication.

Just saw this error pop up in the logs: Parent app is configured not to use EventStream. To reliably use this interface, enable this option in the app.

If you are getting that message (not an error), you ran the command in the bridge child device to connect the eventstream interface without actually enabling it (this being the key component of the V2 API) in the parent app, as the message suggests. This is not a problem per se, but I'd recommend enabling it unless you are familiar with the APIs and think you have a reason not to.

Was this a working integration under a previous platform version or a new install on 2.4.0, and what specific build are you running (check Settings > Hub Details)?

Also curious what device and especially driver are throwing that error. Looks like like the bridge, but the code doesn't go to that high of a line number...

1 Like

Here is what the details say on the Hue hub child device:


Everything was working fine before the update to 2.4.0.
I'll see if I can find that error again, as I think it was the Hue hub child device throwing it because I set a log filter on the Hue hub child device and the Hue integration app only when I noticed it.

Also, getting a lot of these: Device 518 generates excessive hub load. Which I suspect is probably because I am troubleshooting and refreshing the app page every so often to see if other changes (send commands to the Hue device) made a difference.

I'm sure I can just add a new hub and select the existing one, then readd all the child devices and reconfigure all my rules and SharpTools dashboards to fix this but was hoping to avoid that as that will take a lot of time. I'll keep digging and reply if I come across anything just in case anyone else is having this issue.

OK, not sure exactly what happened but I think I am good. The original Hue integration app opens now with the new features/settings. I think I had more than one tab I was trying to open the Hue integration app and when I just noticed that (as it was actually loaded, or eventually loaded and I missed it) I clicked "Done" like others in the linked thread and now the Hue integration app opens as expected each time.

Merry Crimbo everyone.

Unfortunately I'm getting the same issue, also getting hundreds of warnings

Any ideas how to rectify this? I'm running a C8 Pro on platform version 2.4.0.143

Edit; I was able to get into the bridge integration by disabling the app, then re-enabling it while attempting to open it. I wasn't aware of the V2 API update and it wasn't enabled in the integration, but it appears that enabling it has rectified the issue with being able to open the integration.

OK, one clue to look at--thanks!

I don't recommend this option, but it's not enabled by default if you were previously using the integration since it should be a closer match for the old behavior that way.

Quick update, after I enabled the V2 API, I started getting massive error reports from the integration whenever polling of the bridge was executed. I've disabled polling and all seems fine, but thought it was worth posting.

Please provide the actual errors, without which I am unable to even make any guesses.

Also, what hub platform version are you on?

1 Like

Ok, thank you. I've just re-enabled polling and will DM you the error log once it reappears.

I'm running platform version 2.4.0.145

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.