If you're not using your MAC address in the current implementation—that's fine. It's only assigning it as the DNI. If you have two gateways, they just can't be the same.
In a future version, the app (might) scan your network for the MAC of a gateway, and make a connection. That way, it won't need a static IP. If a gateway becomes disconnected, it would auto-scan, and find it again. This is pretty low-priority, though. Maybe a month or two away.
Quick update:
I wanted to get groups out tonight. The good news is that they're implemented—but.. well, maybe I should just explain how groups work, and then I'll explain what I'm doing.
Groups on the Gateway itself are stored in the following format:
[ID] [00] [GROUP NAME] [00]
So, you might have a device with the following ASCII name:
3LivingRoomLights
Wait ... what happens when you delete group 2? Does the ID for group 3 stay the same? Nope, it becomes:
2LivingRoomLights
And that also means if you use multiple gateways, multiple groups can have the same IDs
And then the device would lose its ID in Hubitat... Which means each of the groups must have a unique ID in Lightify.
On the Hubitat side, I needed a way to manage relations between group names and their IDs.
I figured, while I'm doing this, I may as well explore creating a device discovery system.
So, I've got this going:
And I'm going to try to get it all put together by tomorrow 
Thank you for your patience.
Too many.... That gateway has more than 30 devices already. I have extras that are unused and may try to migrate over to a "clean slate".
I was going to say you're a BEAST for developing this so fast, but now I'll say you're the @Kings!
> Removes sword from scabbard
> I dub thee sir Michael Nelson
Edit: Oh dang! What the heck! There's actually a king icon next to my bow tie. Wow---thanks!
@Bobby -- is this some kind of sweet sweet Valentine's day gift? Who is my Valentine? 
BTW, I found a webpage that lists all of the firmware for the lights with download links. OTA Firmwares - Ledvance Firmware. One thing I have noticed is that the Lightify gateway doesn't control large groups of lights as well as my HE hub does. I moved a 9 light group to the gateway and ended up moving it back because it was faster and more reliable on HE. Nothing to do with this integration, I was controlling it from the lightify app. I will qualify this by saying I have a HE hub just for lights.
Something I've noticed is that using Groups in the Lightify hub has helped me locate bad bulbs --- there are two or three of them that will simply kill my mesh.
I suppose this is a mileage-may-vary deal 
There were a couple I had to remove and pair again to the lightify gateway. I didn't have that issue when I paired them back to HE. I can't tell what channel the lightify gateway is on and may be suffering from interference.
@adamkempenich I finally got this to work and I'm sure that it was something that I was doing but anyhow after I reinstalled your app it works. I added a couple of bulbs and they are working and now are showing up in Hubitat. Thanks
Just in time for me to push an update later today 
I’m glad you got it working!! Hopefully the next version has those kinks worked out.
Really appreciate your work @adamkempenich. I have several PAR16 (GU10) CCT lightify bulbs that didn't work 100 % reliably when connected to Hubitat.
I just migrated them over to the Lightify Gateway I still had to do updates on occasion and installed your code - works great so far
I just noticed something odd: I have Hubitat Groups (v2.1) set up to group my bulbs (3 per group) and these groups are controlled by Motion Lighting apps - basically one dimmer per ML app. This worked fine (most of the time) with the bulbs connected to Hubitat, but via the Lightify gateway, it's hit or miss if just, 1, 2 or all 3 bulbs per group will turn on. Same when turning the group on via Google Assistant. However, it seems to work every time when pushing the web UI On button.
Any idea what might be the issue?
Thanks,
Jan
Suck up LOL
You know im joking right ?
Hey! Has anyone commended @anon61068208 for @Kings? 
I’m not sure if this is because packets get dropped, or if commands get missed. Actual groups are coming later today, so it’ll be fixed in a different way until I can see why your issue occurs—I’ve noticed it too.
That's how that works ? Never knew that LOL
I assume it’s because when the bulbs were on HE you could use group messaging to control the lights all at once. Once Adam releases the groups update, it should work comparably well by using group messaging on the Lightify gateway.
Alright. Just put the final touches on 0.22. I will finish testing this evening and publish it.
I left some debug stuff in this release. This is a huge departure from the way things were handled in prior versions, and I'm still putting a lot of time into getting this polished.
Ok, I've updated and added the drivers and app. I open the App and see the Manage Groups option. When I open it my group isn't showing up. Is there a manual step I'm missing?
Download the Hubitat app
