D'oh. Ok, fixed now. If you grab the latest version of the group driver it should work.
Yep, that fixed it! BTW, I really like the flashNotify command, looking forward to the update to the white ambiance code so I can use it system side.
Well, it just so happens... 
Watch this space
1 Like
OK, I've updated the Ambiance Bulb and Ambiance Group drivers. But I haven't got these type of bulbs yet so I haven't been able to test the changes, you'll have to let me know if there are any issues. If you do try them please can you keep an eye out in the logs for "Unhandled parameter: ..." as that will indicate I've removed bits related to color which I don't think are needed but I may be wrong.
Running some errands, will give it a try in a couple hours. Thanks.
@xap ok, just installed and yes, I'm seeing the error you mentioned on the group:
dev:30102018-11-13 04:16:41.913 pm traceHue B Smart Ambience Bulb: setColorTemperature ( 6500 )
dev:30102018-11-13 04:16:39.668 pm debugUnhandled parameter: colormode. Value: ct
dev:30102018-11-13 04:16:39.666 pm traceHue B Ambience Group: updateStatus ( colormode:ct )
dev:30102018-11-13 04:16:39.657 pm debugUnhandled parameter: hue. Value: null
dev:30102018-11-13 04:16:39.655 pm traceHue B Ambience Group: updateStatus ( hue:null )
dev:30102018-11-13 04:16:39.643 pm debugUnhandled parameter: effect. Value: null
dev:30102018-11-13 04:16:39.641 pm traceHue B Ambience Group: updateStatus ( effect:null )
dev:30102018-11-13 04:16:39.629 pm debugUnhandled parameter: xy. Value: null
dev:30102018-11-13 04:16:39.627 pm traceHue B Ambience Group: updateStatus ( xy:null )
dev:30102018-11-13 04:16:39.614 pm traceHue B Ambience Group: updateStatus ( ct:343 )
dev:30102018-11-13 04:16:39.567 pm debugUnhandled parameter: sat. Value: null
dev:30102018-11-13 04:16:39.565 pm traceHue B Ambience Group: updateStatus ( sat:null )
dev:30102018-11-13 04:16:39.547 pm debugUpdate Needed: Current Value of level = 40 & newValue = 100
dev:30102018-11-13 04:16:39.543 pm traceHue B Ambience Group: updateStatus ( bri:254 )
dev:30102018-11-13 04:16:39.524 pm debugUpdate Needed: Current Value of switch = false & newValue = true
dev:30102018-11-13 04:16:39.520 pm traceHue B Ambience Group: updateStatus ( on:true )
dev:30102018-11-13 04:16:15.199 pm traceHue B Smart Ambience Group: refresh():
dev:30102018-11-13 04:16:14.034 pm traceHue B Smart Ambience Group: setLevel ( 100 ):
dev:30102018-11-13 04:15:43.056 pm debugUnhandled parameter: colormode. Value: ct
dev:30102018-11-13 04:15:43.054 pm traceHue B Ambience Group: updateStatus ( colormode:ct )
dev:30102018-11-13 04:15:43.042 pm debugUnhandled parameter: hue. Value: null
dev:30102018-11-13 04:15:43.040 pm traceHue B Ambience Group: updateStatus ( hue:null )
dev:30102018-11-13 04:15:43.028 pm debugUnhandled parameter: effect. Value: null
dev:30102018-11-13 04:15:43.026 pm traceHue B Ambience Group: updateStatus ( effect:null )
dev:30102018-11-13 04:15:43.014 pm debugUnhandled parameter: xy. Value: null
dev:30102018-11-13 04:15:43.012 pm traceHue B Ambience Group: updateStatus ( xy:null )
dev:30102018-11-13 04:15:42.999 pm traceHue B Ambience Group: updateStatus ( ct:343 )
dev:30102018-11-13 04:15:42.989 pm debugUnhandled parameter: sat. Value: null
dev:30102018-11-13 04:15:42.987 pm traceHue B Ambience Group: updateStatus ( sat:null )
dev:30102018-11-13 04:15:42.975 pm traceHue B Ambience Group: updateStatus ( bri:102 )
dev:30102018-11-13 04:15:42.959 pm traceHue B Ambience Group: updateStatus ( on:false )
dev:30102018-11-13 04:15:30.041 pm traceHue B Smart Ambiance Group: flashOff():
dev:30102018-11-13 04:15:24.856 pm traceHue B Smart Ambiance Group: flashOn():
dev:30102018-11-13 04:15:24.850 pm traceHue B Smart Ambiance Group: flashNotify():
dev:30102018-11-13 04:15:15.688 pm debugUnhandled parameter: colormode. Value: ct
dev:30102018-11-13 04:15:15.684 pm traceHue B Ambience Group: updateStatus ( colormode:ct )
dev:30102018-11-13 04:15:15.664 pm debugUnhandled parameter: hue. Value: null
dev:30102018-11-13 04:15:15.659 pm traceHue B Ambience Group: updateStatus ( hue:null )
dev:30102018-11-13 04:15:15.634 pm debugUnhandled parameter: effect. Value: null
dev:30102018-11-13 04:15:15.629 pm traceHue B Ambience Group: updateStatus ( effect:null )
dev:30102018-11-13 04:15:15.598 pm debugUnhandled parameter: xy. Value: null
dev:30102018-11-13 04:15:15.593 pm traceHue B Ambience Group: updateStatus ( xy:null )
dev:30102018-11-13 04:15:15.527 pm traceHue B Ambience Group: updateStatus ( ct:343 )
dev:30102018-11-13 04:15:15.497 pm debugUnhandled parameter: sat. Value: null
dev:30102018-11-13 04:15:15.491 pm traceHue B Ambience Group: updateStatus ( sat:null )
dev:30102018-11-13 04:15:15.424 pm traceHue B Ambience Group: updateStatus ( bri:102 )
dev:30102018-11-13 04:15:15.355 pm traceHue B Ambience Group: updateStatus ( on:false )
If I adjust the white ambiance bulb individually all commands appear to work fine without errors. The errors in last post don't appear to cause the commands to fail, though.
Another thing I noticed is that the device settings show an extra "set level" option with no input boxes right next to the normal one.
My ambiance bulbs are arriving tomorrow so I'll be able to correct and test the drivers properly this weekend.
1 Like
Sounds good, I did have some issues with HE system performance after adding the incomplete drivers. Fortunately I kept a copy of original driver. I also noticed the system events log seems to be getting spammed with SSDP entries with the Hue B Smart app installed, I believe the official integration used to have an issue with this before some modifications were made but I don't know what they were.
1 Like
I have adjusted the app code to remove the regular ssdp polling so that it only performs this when searching for bridges during setup.
Everything still works for me with this change but my Hue bridges have assigned IP addresses in the router, i.e. they always have the same IP on the network. I don't know if removing the ssdp polling may cause the system to be more brittle if a bridge IP address changes (or if that may have broken the system anyway).
Anway, this change stops all the ssdp events but use it at your own risk (of darkness, if the lights stop working - shouldn't happen though )
This is actually the HE recommended way of using ssdp discovery. Any devices relying on ssdp should have a static or reserved IP address to avoid issues with Hubitat.
2 Likes
@halfrican.ak I've finished updating the drivers for now, it all seems to work nicely with my new ambiance bulbs. Have a go, let me know if you have problems.
1 Like
Sorry if this has been asked. Do these drivers work with ramp rate?
That's alright, it has been asked... by you 
If you mean the transition time setting that's in the ST original version of these drivers, then yes, that still works in this port. I've also added support for the setLevel duration parameter.
1 Like
Thank you. Apologies for the forgetfulness. I am going to have to give this a shot I think.
Was hoping it would be added to the official driver however it does not seem to be high on the list at this time, lol or even on the list at all.
Now to read up on this.
No need to apologise. Feel free to message me if you have any issues getting it to work.
Since there were so many changes in this version and I also added a bunch of new lights, I decided to reinstall from scratch. I got some errors during the discovery setup as seen below:
app:49362018-11-18 09:20:21.880 am errorjava.lang.NullPointerException: Cannot get property 'value' on null object on line 983 (linkButton)
app:49362018-11-18 09:20:21.871 am debug>>> linkButton(null)
app:49362018-11-18 09:20:10.911 am errorjava.lang.NullPointerException: Cannot get property 'value' on null object on line 983 (linkButton)
app:49362018-11-18 09:20:10.881 am debug>>> linkButton(null)
app:49362018-11-18 09:20:05.007 am debug>>> linkButton(null)
app:49362018-11-18 09:20:01.929 am debug>>> linkButton(null)
app:49362018-11-18 09:19:27.425 am debug>>> linkButton(null)
app:49362018-11-18 09:19:24.272 am debug>>> linkButton([ip:192.168.1.193, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-00178849d586,
Did the errors stop you from completing setup?
Ok, I've updated the app. Should stop the NullPointerException. Let me know if that works better for you.
At first it was, but I just kept re-installing and it finally installed but with some additional errors in log. I'll install the latest version, but all seems good as of now.
1 Like
