Has there been feedback from the Team on the addition of “transition time” control in the Hue Bridge Integration?
I'll add it to the features request.
It's on the list to get added. Don't have a timeline as to completion.
1 Like
Just touching base to see if any progress has been made on adding tranistion time control to hue integration?
Random bit of info... I logged the network traffic between the Hue app on my iPhone and the hub just to see how it was handling status updates. It looks like even Hue's own apps are simply polling the hub. Every 2 seconds the app makes a calls to the /lights and /groups endpoints. Each call returns the status of everything (all the lights or all the groups), so it's a fairly efficient way of getting the state of everything at once.
No success here. Just initialized my Hubitat hub and tried to add the Hue bridge as a start, but it doesn't show up, no matter how long I wait. The browser window was open for half an hour.
Just to make sure the Hue bridge was Ok, I installed Alexa on my phone and added the Hue bridge there (without issue).
Same here, works fine with Alexa, but will not discover with Hubitat...
Installed the Hue Integration app? Also,
Don’t forget to press the button on the Hue Bridge, then do discovery.
Why oh why can I not get the Philips Hue bridge connected to my new Elevation hub??
My setup: In the office room, I have an Amazon Echo Plus and a Philips Hue bridge. Both are 'communicating' with each other. On the Echo Plus, I have the Hue skill installed. They are both using the same router (obviously).
In the same office room, I just added a Hubitat Elevation hub. It is connect to the same router used for both the Echo plus and the Philips Hue bridge.
Over the past days, I have managed to read enough documentation to get the Elevation hub operational - I have even added two Inovelli plugs with their specific drivers. I have added the Alexa Echo app to the Elevation.
I have tried many many times to add the Hue Bridge Integration hoping that it would easily discover the already installed/operational Philips Hue bridge. Unfortunately after many tries, the Elevation hub has not been able to discover the Philips Hue bridge - both the Elevation hub and the Philips Hue bridge are connected to the same router (one beside the other) - I have even pressed the link push button (the one surrounded by the blue ring). I really do not know what to look for anymore - I do not understand why the discovery cannot be accomplished.
I am getting very frustrated with this situation as I feel the Elevation hub needs to 'communicate' with the Philips Hue bridge. 
Any suggestions would be greatly appreciated...
Ray.
I just tried again, not doing anything different of course, and this time the Hue bridge was discovered within a minute or two. @SmartHomePrimer You only need to push the button after the bridge has been discovered. It will put the bridge in some kind of pairing mode for a little while. It will probably work too if you push the button first, but it's definitely not necessary.
It think it's pretty obvious there's something not 100 % right with Hubitat's SSDP implementation, so sometimes it works and sometimes it doesn't.
The big button on the front is how Hue does their local security. It’s for authentication of the Hue and third-party apps. If you can see the bridge and bulbs, but can control them, then it’s because they’re not authorized. Pressing the button and doing a “Refresh bulb discovery” in the Hue Integration app will typically fix the issue.
Might help even if you can find you bridge or devices. In fact, that is what Amazon tells you to do when Hue devices are not immediately discovered. I can’t tell you the number of times I’ve had to push that button more than once to get discovery to work, with many different hubs and apps. The issue of discovery not always working is more likely a Philips issue than a Hubitat one, since I believe they used the official API in developing their App.
It’s never a bad idea to reboot the Hue Bridge and try again from the start.
I'm not trying to blame anyone - just saying that I've tried quite a few smartphone apps for Hue when I first got it - all of which needed to discover the Hue bridge and get authorized by pushing the button - and I never had any problems with that. When I couldn't get Hubitat to discover the Hue bridge, I tried discovery using Amazon's Alexa app (without an Echo) and that worked just fine.
Had you not already paired this bridge with you Amazon account? If so, it’s already authorized. If you bought a new bridge, or opened a new Amazon account, you’d have to press the button again.
No, I hadn't paired it, so yes, I had to push the pairing button after the Alexa app had found the bridge (while Hubitat was also looking for it but couldn't find it). One difference in the process would be that Amazon requires users to do a cloud-based authentication first (log into Hue cloud account inside the Amazon app), then discovers the bridge and after that asks for local authentication - not sure if that makes a difference for discovery.
1 Like
True. Now that there’s a Hue Skill they do discovery differently. When I bought my first Echo in 2015, discovery of Hue, Insteon and Wink was native.
Let's start over with your Hue bridge discovery issue. You have said in this thread, that you don't have any apps installed.
Do you mean other than the Hubitat "Hue bridge integration" app? You need that. Discovery of the bridge isn't the same as a Z-Wave or Zigbee devices in Hubitat. Is that point understood? It's an important difference. If it's not installed, please do the following...
- In your Hubitat UI, click on the word Apps on the left
- Click the +Load New App button at the top right of the Apps page
- Halfway down the list, choose "Hue Bridge Integration"
- Follow the wizard from there. While you're waiting (Up to five minutes for discovery), walk over to your Hue Bridge a press the middle button once, just briefly. No need to hold it).
Let me know if you've been here before. If not, then we're now headed in the right direction. If you have and it didn't work, then let me next hear what devices you have (i.e. Modem/Router and who your ISP is, and connected devices to the ISP modem router).
Look at the layout from the perspective of internet coming into your house and traveling in a straight line from internet to device until you get to the end. I realize it doesn't exactly work like that, but it will help when troubleshooting to think of a logical progression from one, to the next (outside to inside).
It absolutely does. Best not to let frustration get in the way. We will get this working. Logic will prevail, if we take it one step at a time.
2 Likes
The discovery/integration of the Philips Hue bridge with the Hubitat Elevation hub has been tried dozen of times without success - the only results are a screen displaying the following message:
"Hue Bridge Integration - Bridge Discovery Failed!
Failed to discover any Hue Bridges. Please confirm that the Hue Bridge is connected to the same network as your Hubitat Hub, and that it has power."
The problem (as it is in my view a problem) is that the 'Hue Bridge Integration' app has a flaw and for some reasons does not want to recognize the Philips Hue bridge on my network. The Habitat 'Hue Bridge Integration' app is the only application so far that does not want to recognized the Philips Hue bridge - all other Amazon skills, Google Pay apps and Windows software that I have installed have not had that problem.
The Hubitat staff is trying to find out what could cause the problem (I thought I was the only one with the problem but we are now two with the same problem thus my consideration that the Habitat 'Hue Bridge Integration' app has a flaw.
Ray.
The majority of users have been able to pair. I have seen users reporting issues, that were resolved. None of them drew the conclusion to my recolection that the software was "flawed" based on the result of their particular experience. So without knowing what the cause is, I think it more helpful that we take a different mindset, and methodically look at the components of the system.
So you have installed the Hubitat Hue Bridge Integration app and you get a failed discovery message. OK, then let's now please have an understanding of your network. Could you answer a few questions about your network equipment?
- Who is your ISP? Rogers, Bell, Telus, Cogeco or other?
- Do you have a modem only, with your own router connected or do you have a modem/router combination from the ISP?
- If you have a modem/router combination device from your ISP, do you also have your own router connected to that?
- Are there any other routers or network switches connected?
- What is your network IP range (i.e. 192.168.0.x or 192.168.1.x or other)
I am retiring (withdrawing) from the Hubitat Community until the problem between the Hubitat Elevation hub and my Philips Hue bridge has been solved.
All those questions have been answered and no solution has been provided yet...
Obviously the Hubitat Elevation was not designed for my needs - I will remain with my reliable X10 and Insteon devices.
Au revoir, Ray.
Ray, Hate to see you go. But just wanted to follow up and let you know we found the root cause of this rare case and have implemented a fix that will allow Hue bridges to be discovered.
The fix was introduced in version 1.1.1
1 Like
@Patrick Is there any way to access the Hue Bridge device and its child devices in a smart app? Or, alternatively, will refreshing the state of a single Hue bulb cause Hubitat to grab the states of all the hue bulbs (since it seems to be just as efficient as getting the state of a single bulb)? I'd like to implement a heartbeat app to improve the response time of my Hues.
