The reset process for a Hue bulb isn't easy: you either need it still connected to a Hue Bridge (in which case removing it from the app when the device is powered on and the bulb is otherwise "healthy" should reset it), or you need a Zigbee remote like the Hue Dimmer, Eria Dimmer, RGBTGenie remote, or Lutron Connected Bulb Remote (the latter of which used to be the only thing people recommended for this purpose and has certainly been around the longest of the three, but don't pay insane prices on eBay for one if anyone still thinks this is the only way).
But adding Hue bulbs directly to Hubitat is generally a bad idea. If they're the only kinds of Zigbee devices you have on that Zigbee network on that hub, then it's OK; the issue is that they are poor repeaters and may eventually cause problems for anything besides other Zigbee bulbs. Hubitat's Zigbee documentation summarizes this problem, which is generally applicable to most Zigbee bulbs, not just Hue: How to Build a Solid Zigbee Mesh - Hubitat Documentation.
That being said, I'm not sure why your Hue Bridge Integration app wouldn't be working. Hubitat's appears to use SSDP to discover the Bridge. Wink might use the same, though there is a cloud-based discovery option it might use instead, so who knows. I wrote an integration that allows bypassing discovery (which I actually haven't even released in the public version yet), so you can just manually use an IP address (static required, but I'd recommend one for both Hue and Hubitat anyway), if you feel like using a third-party workaround: [RELEASE] CoCoHue: Hue Bridge Integration (including scenes!). If that doesn't work, I'd at least know what the logs the app might generate would mean to help troubleshoot. 
