There's a package manager? Found it ...
I'm a fan of package managers so will give this a try.
I've been a bit confused on what this new functionality is/does from your guys' conversation leading up to this official release. What is an example that you'd want to use an external program to set the bulb's IP address?
Will it effect a current setup where you had to manually enter the IP address?
Please don't remove HPM support! 
It's convenient to have all the drivers/app in one consolidated place.
And that it automatically notifies you when a developer pushes an an update is super nice too!
I agree -- I didn't know about HPM when I asked about the URL at the top. HPM is indeed a better solution.
@gamerkingfaiz, don't worry -- nothing in the new driver affects existing features or setup
at all, and HPM support is not going anywhere!
What @Bob.ma asked for was the addition of a comment with the repository information to the driver code's header. It just makes it really easy to find out where the project lives by looking at the first screen of driver code. (as it is, you have to scroll a bit to find it.) It's convenient if you're manually updating, or just want a look at the code in the repository.
The new features let a network manager run a program to query a router or DNS server for the IP address associated with a bulb, and change it automatically on the Hub if it has changed on the network for any reason. This way, if a router gets restarted or replaced, a network segment is reconfigured, or a device loses its DNS lease for some other reason, you can automatically keep all your light bulbs working.
(btw, @Bob.ma, you actually can use these features to set the IP address completely from scratch now -- if you know which bulb you want to associate with which Hub device, you can leave the address field in the device blank, and call setIPAddress to configure your bulbs.)
When a DNS server hands out an address to a new device, that address is "leased" for a period of time. It's not guaranteed to be permanent unless you explicitly go to the trouble to make it so. On most small networks, the leases are renewed automatically, but it is still possible for a device to be assigned a different IP address occasionally. For a small number of devices, this is easily manageable by hand.
On networks with hundreds or thousands of devices, you really need management tools to keep up. The new features are the plumbing for these management tools. I added them because I'm interested in how home automation scales to large numbers of devices, and @Bob.ma had a good use case and had already built the tools to make it work.
2 Likes
I haven't seen anything about using the Wiz Color Light Driver with the Wiz Dimmer Switch. I've only seen them available from Costco in the US so they're a little hard to get. But I wanted to report that the Wiz Color Light Driver by @zranger1 works great to control the Wiz Dimmer Switch, both on/off and Level to dim. I'm using the switch to control a basement full of recessed dumb LED lights. 
1 Like
What is the purpose of pauseExecution(100) ? -- in my group of 12 lights it sequentially delays them instead of turning them on at the same time.
@thefastlane, it just gives the bulbs time to stabilize after being turned on. I saw several cases of the bulbs dropping commands that were sent immediately after "on" - this is actually the root cause of the "stuck at 10%" problem - a few milliseconds of delay, and everything's ok again.
I've seen this done in other bulb drivers, some of which give you the option to adjust the delay from the UI, and if there's a need, I can add that as well. I didn't do much testing to find out what the minimum timing threshold actually is, but reducing it is safe -- you'll know it's too low when moving a dimmer rapidly up from the off position doesn't produce the level you expect.
Glad to hear this works, @seth.ma! It's nice to know they've kept the same basic protocol for multiple devices. I'll see if I can get a few different bulbs and one of these switches and come up with individual drivers for them so your switches and CT bulbs don't have to carry all that extra color code around.
1 Like
As an FYI I found that https://www.taolight.com/ is the company behind Wiz.
As an FYI -- got some additional bulbs and this time instead of the laborious onboarding the app itself popped up saying some bulbs are available and found them via Bluetooth! This is a vast improvement. I wonder why it didn't work on other bulbs. I also noticed that one of the bulbs is in a new MAC address range 6c:29:90:..
Which brings up another general request - a comment field for all devices. Even better would be a JSON field for additional comments and notice like this. Of course both get-able and set-able (or marked readonly). Perhaps I should post this as a general request if other would join me in supporting it.
Just posted an update that has smarter packet rate throttling, which should speed up group switching. It also includes a few other other performance improvements and minor bug fixes.
Anybody seeing slowdown in group on/off switching, take a look and see if this helps.
I don't expect it to be truly simultaneous though, particularly if you're sliding a dimmer up to turn the group on. Without going into detail, it's a Hub issue, tied to the legacy Smartthings architecture, which mostly predates the current wave of wifi based IoT devices.
2 Likes
for some reason only 1 bulb will link to app or hubitat at a time...
I only have 2 but when one is set up the other stops working.
any ideas ?
SB
don't know why but working OK again.
Has anyone had any trouble getting the 4lite GU10's to work with this driver.
They use the 'Wiz Connected' app and the process for installing them and finding their IP is all pretty straight forward however I can't get HE to find my bulb at all.
The HE Wiz driver uses local UDP communication only -- it does not talk to bulbs via their MQTT<->Cloud path, which the Wiz app uses. I do not know if these bulbs support the local-only protocol. However...
In the Wiz app settings under "Security Settings", check that "Allow Local Communication" is enabled. If it's not, enable it and see if it fixes the problem.
Just as an FYI -- the WIz strips work fine with the Driver
1 Like
Ah, so they're not actually the correct bulbs then!
(I did check the local connection in the app and it is set)
So that's a lesson for me then, "Wiz bulbs" NOT "Wiz Connected" bulbs.
Now, how do I send these ones back....
The Hubitat doesn't "find" the bulbs. You need to explicitly enter the IP address into the device settings. (or use an app to do it).
So I must still be doing something wrong..
I now have 'Wiz Colour' GU10's (not wiz connected as before)
I have connected them to the wiz app.
I have found them on my network and given them a static ip
I have installed the HE wiz colour driver
I have created a virtual device
I have saved that device as 'wiz color light'
I have input the ip address of the light into said virtual device.
And that, as far as I'm aware, should be it.
I should have a working bulb but I've not no reaction from the bulb when I use any of the buttons on the virtual device.
Obviously the wiz app works fine.
I wonder what I'm doing wrong.?
Are the bulbs setup to allow local control, or is that turned off. For the driver to work local control needs to be enabled.
In the app go to the Security Settings section and make sure "Allow Local Communications" is turned on.
