Yes. Sengled is an independent company not part of the LEDVANCE group that Sylvania and OSRAM are part of.
Yes, but I think problems will persist with the Sylvania bulbs paired to the hub. That is my suspicion of the issue at the moment. @rodney if you try what @Ken_Fraleigh is suggesting and you still have problems, then remove the Sylvania bulbs from the hub and repeat the test.
And you still can. Consider that with the financial threat looming, lost revenue due
to the necessary shutdowns, and the OSRAM announcement, ALL the Sylvania and remaining OSRAM bulbs are going to plummet in price. There are big savings to be had in their bulbs, which will more than make up for the cost of an additional HE hub. Don't expect the price of HE hubs themselves to plummet though. The HE team already works remotely and is prepared for this scenario by nature of their existing structure.
Experts like @mike.maxwell whom is the person that writes the drivers for the HE platform and really understands this, already use a separate hub for Sylvania/OSRAM bulbs to keep them off his main Zigbee network and has perfect results. Connecting HE hubs together is cost effective, efficient and easy. You can have a hub dedicated to affordable Zigbee bulbs, and the rest of your Zigbee devices (non-bulbs) can live on the main hub, unencumbered by bulbs that keep dropping the metaphorical Zigbee ball. 
Hue is certainly a good option, especially if you already own their bridge. The HE Hue Integration is very reliable. Depending on the light types you need, the prices aren't horrible. I have mostly their A19 bulbs in my house which were on average $14 CAD per bulb, and a few deals for much less. Hue BR30 bulbs are outrageously priced. Nice bulbs though, one must admit.
I have never had an issue with the newer bulbs causing problems, unless there arenāt enough of them. Once I ditched the Osrams I havenāt had any problems. My zigbee motion and contact sensors were always reliable though, the problems I had were with bulbs losing connection with the hub.
It may be In this case that the driver isnāt reporting correctly, or the group. Make sure on/off optimization is not enabled, as enabling it prevents on/off commands from being sent if the group thinks the device is already on or off.
Full disclosure: I have all of my bulbs on their own HE hub. Not because of devices dropping, but it fixed my hub slowdowns. I do have some Sylvania plugs and GE in-wall dimmers on that hub as well without any problems since removing all of the Peanuts.
Apparently there is a maximum number of replies allowed in one day and I was cut off . I did replace the Sylvania bulbs with Hue bulbs and they work fine. The problem must be something in the way the Sylvania bulbs work with HE. I found a pretty cheap Lightify gateway and thought I might try that. Is there a interface between HE and Lightify?
They BR30 & A19 sylvania bulbs also update on ST and work well with, so no need for lightify. Plus with ST you can use Hubconnect, which makes HE abou 100X better
Mine are paired to HE and work well, untill the kids flip the switch !
The high output recessed rgbw and Flex XL donāt update on ST btw. According to the LEDvance website, all lights should update to 102428, except garden spots. SmartThings doesnāt have zigbee group messaging afaik, which is one of the reasons I originally switched to HE, but I have a lot of bulbs.
It canāt be the bulbs, something else has to be going on here. I have over 60 Sylvania bulbs connected, some with motion lighting, and have never had an issue like this. Iām starting to wonder if it is the driver, or bulb firmware. Your using dimmable, not color temperature, or RGBW bulbs? If yes, you might try changing the driver to the Sengled Element Classic driver and see if there is a difference.
I'm guessing the problem is not the bulbs. The bulbs will turn on sometimes - usually on the next instance after I use Alexa or manually turn them on from the dashboard. What's interesting is I have them set to turn off after 5 minutes with no motion and that works every time without fail - just getting them to turn on is a problem. Anyway, I just ordered a Lightify bridge (cheap) and found the integration for HE. Hoping that will do the trick.
I'm, sure you'll be pleased once you get this sorted out. I have about 15 of these Sylvania, a mix of BR30 & the recessed type. Both are solid on HE and on ST.
Seeing the fantastic integration for the lightify gateway by @adamkempenich, I'm in the market for a gateway now, just to have something to do while a prisoner in "SuperMax Corona".
I do recall an issue with a lighting rule and these bulbs. The rule when set to turn on & turn off, would often fail to turn on, so I changed my rule to "toggle" and it works perfect over the last few months. I placed a ticket and got 1 response that went nowhere, then discovered the toggle fix on my own. You could try changing logic to toggle and observe
I don't have this problem, but it seems familiar. It may be something that was fixed in a Sylvania firmware update. Currently on 102428 that I think was released June 2019 for nearly all Sylvania Smart+ lights (not Garden Spots). Some groups I have change CT in the background, so I just send an "on' command from a button controller. They respond very fast that way.
I got the lightify gateway as you had suggested, but it shows the RT5/6 as being current with 01020492 -- which is new enough to not have the routing problems, but certainly isn't the 102428 that Ledvance has made available.
I downloaded the images from the Ledvance site, but I can't find any way to push these firmware images using the Lightify gateway. What am I missing?
Iām pretty sure that is an Osram firmware. Even though they kept the model numbers the same, Osram used a different SOC than Ledvance. The firmware isnāt compatible with Osram bulbs, only Sylvania Smart+ made by Ledvance. If the firmware was able to be updated, it would download and install it for you. That would make the lights you have the ones with the issues unfortunately. The old models are still available for purchase today on Amazon. The ones that come with the gateway are the old Lightify bulbs (Osram kept that when they spun off the consumer lighting). I have no idea why after all this time.
In almost all forums the 01020492 was listed as the version that fixed the relay. These are ZHA not ZLL.
I'm sure that the newer firmware has even more fixes, but I've not seen any reports that 0492 had the relay issues.
I didn't get the gateway two-pack. Those were part number 73401. Mine were part number 73858: https://www.amazon.com/gp/product/B01HF2CJUY/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
^ this is from my original order, since it wasn't that long ago.
The link is to the same ones I have, but it now says Lightify where it used to say Sylvania Smart+. Some were sold by Francos Lighting and some directly from Amazon (I have a bunch of them). Mine came with firmware 00102100 that upgraded to 00102428 (102428). They are zha as well. I havenāt seen any zll in the U.S. One easy way I have found to tell the difference between the Lightify and Smart+ recessed lights is that the Smart+ dim on/off over a second, and the Lightify turn on/off like a light switch. If youāre having any issues with them, return them and buy from a different seller.
Just ordered from both Franko & VMInnovations in the last ~6 weeks. They both sent me the newer -ones(FCC ID- LD DZO-AETHER), all updated to 00102428 via ST
Iāve had good luck with vminovations as well in the past.
My go on/off with the 1 second delay, not like a switch. Yet the lightify gateway said 01020492 was the best-est 
My Amazon purchase says Ordered on February 22, 2017. I'm fairly sure that's outside the return window 
Hi Ken - i've got about 55 or so total sylvania bulbs (only recently did I learn of the routing issues on the older OSRAM branded bulbs though luckily all but like 10 bulbs are the newer LEDVANCE brand) My question for you is do you have issues with group command not having the bulbs report proper status afterwards? IE i turn on a group but some of the members will show as OFF despite the bulb being on. I do realize I have some of the OSRAMS on my network so my hope is that once I can swap those out things will 'heal'. Since you have a large network of the same bulbs as me i'd love pointers. For groups you still use group messaging right? Also do you use the 'tamed' driver for your bulbs or the standard generic one. My last question is do you know if these bulbs play nice with ikea signal repeaters.
Thanks so much for your help!
No. I know that when I had issues with devices dropping off the mesh, they would sometimes still be controllable with the group, but not individually. In that case I would expect them to not report status.
Yes, but I have disabled optimization. I think they are a tiny bit more reliable with optimization disabled.
Only with my solitary Osram Lightify under cabinet light at my wifeās desk It would not reliably turn on/off before.
Make sure you update the firmware on the newer bulbs to 00102428. Most of the bulbs come with 00102100, or 00102090, and they donāt behave especially well with the old firmware.
I donāt know about the ikea signal repeaters, outside the fact that they are cheap and lower signal output than their outlets (from the ikea spec sheet I saw somewhere on here). I would recommend the Sylvania plugs or Samsung, as they both seem to get along well with everything and have never dropped off my network. The best thing I ever did was to buy a second Hubitat just for the lights (no repeaters needed).
Download the Hubitat app
