Here’s a few things, some you’ve probably already tried but just throwing them out there.
First, I would assume you have the latest handler - available here https://github.com/nuttytree/Nutty-SmartThings/blob/master/devicetypes/nuttytree/ge-jasco-zwave-plus-dimmer-switch.src/ge-jasco-zwave-plus-dimmer-switch.groovy
The old one had issues working with the new app
Also, Jasco made a bunch of different switches. The older non-zwave plus swithes don’t support double tap. There were a lot of “in between models” that do through an association on group 3. This DTH works for those. The brand new ones, from what I’ve read on the official Zwave listing page, use central scene control for double tap. I don’t have the brand new ones so don’t know for sure how those work, but assume this DTH would not give you double tap on a new one. If you go in your IDE, and go to the “raw description” under the device, copy that entire line, and paste it into here as a reply I can confirm if the model # works for this DTH.
If this worked before, it probably is a compatible switch though. The way Zwave associations work are when you associate two devices, it sets up direct communication between the devices and bypasses the hub. Multiple devices on association group 2 mirror each other - ie they act in unison. Association group 3 is double tap. When you associate two devices on group 3, they will communicate directly by double tap and bypass the hub. Its a nice feature as these associations still work even if the internet is down or hub is unplugged. However, this will only work with Zwave devices, and not Zigbee or virtual swithes as those are through the hub. So if you try and add a non-zwave device to the association group by entering in its device ID, it definitely will not work.
What the Nuttytree DTH does is take the hub itself and puts it in association group 3, and then create virtual buttons that can be used in various other automations. It’s a bit complicated, and also impressive coding by @nuttytree that he was able to figure that out and make it work. As mentioned above, you need to use the smart lighting app or webcore, as the new automations section of the app won’t let you select different button numbers.
I have a switch that controls a virtual device with Double tap (the virtual devices sends an IFTTT command), and I have one that controls a scene, using the new app and new DTH. I don’t have any Phillips Hue but I can’t see why this wouldn’t work with those.
Another thing to try is create a scene in the new app with your Philips Hue light. From the home page of the new app, click the menu option at the top left. Click “scenes” (it should be a picture of a sun). Create a scene adding your Philips Hue light to do what you want it to do - color, on/off, etc. You can create two scenes - one for button 1 up, another for button 2 down. Then go to your smart lighting app by clicking “smartapps”, then “smart lighting”. Delete out any automations from there that aren’t working. If the automation is corrupt and won’t open, you may need to delete them from the IDE. Click “new lighting automation”. From there it asks what devices you want to control, or activate scenes. Click “activate these scenes”. Click the scene you created in the previous step. Under “select trigger”, select “button”. Under “which button” select your Jasco switch. Button number should then show up - button one is double tap up, button two is double tap down.
Hope this works but if not let me know the model info of your switch from the IDE so I can look into it more.