This is what I meant by that statement. Still have the devices separate but most people keep the rules connected to its hub on that hub, makes sense for speed and redundancy.
But I does depend on the rule, for example if the rule executes on the main hub and the end product is just a basic ON or set level to one group of light that's not going to make a difference at all. But like in this case when it's more complex AND you want certain commands to flow very fast in a perfect order. By adding the extra layer could cause issues, it shouldn't BTW in a perfect setup they should flow the right time, but for this testing and for redundancy it doesn't make sense not to do it in the same hub.
The Lightify Gardenspots are giving me trouble. Too far and no repeaters on that second hub yet. All Sengled until recently. Need a mesh for them. Any suggestions on what devices they like?
Got four of the buzzing bulbs of theirs, but I don't want those things in my house anymore. What else do they like?
With mine, they repeat through other bulbs (non-buzzing Sylvania RGBWs, my favorite being the recessed version that don’t get blazing hot and die), or the Sylvania plug just fine. My Garden Spots are the newer ones with firmware 102428 FWIW.
PS- I had forgotten that the CT bulbs buzzed, which is why they are still in the DOS (drawer of shame). I don’t hear it with the color bulbs, which are probably cheaper than what you paid for the ct bulbs, unless they were on a clearance sale.
Yep, on clearance. $3.50 CAD per CT bulb No love lost.
Sitting here with the Xbee. Hadn't mapped my second hub before. Forgot that I had put @iharyadi 's Temp/Humidity/Pressure/Light sensor on that hub. The Sengleds love that device for their route, but it's too far from the Gardenspots and is doing a fine job with the Sengleds. Humidity reference values (which is what I primarily use if for) are also good in its location, so I'm not going to move it.
I've never kept my Xbee attached all the time, but the Gardenspots latched onto it almost immediately, so I think I'm going to whip together a case and try it out as their repeater for a while.
Thanks for the response. If this doesn't work out, I've got nothing to lose with a Sylvania outlet. No Xiaomi on this particular hub, so that will be fine to use.
Interesting too that the Gardenspots do not route for each other, even though they're only 10 feet apart.
I have the ugliest of cases I threw together from an old floppy disk case
But it’s behind a short bookcase, so it isn’t noticeable. Only dropped the LQI by 1 being behind the bookcase. Results last night were good, and color control was easier. These are the earlier versions and the Generic RGB driver seems to struggle with them. Works, but getting them to the color you want isn’t a direct line.
There are nice cases on thingiverse if you have a 3d printer.
I find the color is much more accurate if set via Google Home for my sylvania bulbs and gardenspots
Hey That'll work. When it comes to having a well performing mesh, who cares what it looks like.
Is that a 2.4 or 5gHz antenna? I read somewhere they are matched to frequency, and some are dual band
I have a bunch of Osram Lightify A19 Tunable White bulbs. They're model 73674. Can anyone confirm that their (final) firmware version is 01020205? I bought the Lightify hub and it didn't find a firmware update.
Strangely, they didn't seem to identify correctly, and the Lightify app refused to change their color. The color temperature setting is grayed out, but I have been able to change settings in Hubitat using the generic bulb drivers. Thanks!
But, Lightify Sylvania Osram Ledvance Smart+ has put out a lot of variations.
The one thing that's been reliable (knock on wood) for me is the motion sensors.
Dis you try more than one bulb? I have seen bulbs with what I have assumed is bad firmware not identify correctly on the Lightify gateway. I have also used tunable white bulbs with the Lightify gateway before and they identified properly.
I figured it out - your link led me to a FAQ which said to power cycle the Lightify Hub after software updates (which it did when I first powered it up). The app did not suggest this. After rebooting the bulbs identified and updated immediately. The updated firmware version is 01020492.
Thanks also @cwwilson08@Ken_Fraleigh for your inputs. I forgot the one rule in electronics, always turn it off and back on again.
I have the same bulbs. One turns on and off, the other turns up to on and dims to off.
How did you update the firmware? How do I know if my firmware is not updated? It is driving me crazy that I cannot fix this. 73674 model of the bulb. Did you have that problem too? I contacted OSRAM and they told me contact the hub manufacture. Anyway to fix this would be great. I was originally on ST and ST told me to contact OSRAM; the circle of pointing fingers begins.
I'm a little new to Hubitat (came over the ST, and learning quickly) but not new to automation. However, I have a feeling this is going to get more complicated than that. Sorry in advance.
In purchasing 9 of these a couple years ago I literally received 4 different versions of this exact model which is now in my HA drawer of shame. If you look at the bulb, 3 lines down from the model number, you will see the IC version. I would guarantee that your bulbs have different ICs. Some dim to on and off no matter what, some come on instantly with the setlevel command but dim on/off with on or off commands, and some are picky about what CT values they’ll accept. Your best bet is to replace them with the RGBWs (~$10 each), knowing that there is a 2 year warranty that you Will need to take advantage of at least once, or shell out the money for the Sengleds (~$25 each), which don’t operate as smoothly as the Sylvanias, but don’t seem to immediately fill you with regret.
I almost forgot, you also could use Hue lights (~$45 each) if you like setting money on fire. As long as they’re connected to the Hue bridge they’re excellent, but they are sloppy and unreliable connected to anything else.
My understanding (and the answer is in this thread somewhere) that you'll either need the Lightify Hub or other compatible device (Smartthings) to see/update device firmware. Hubitat does not currently allow you to do that.
@benasaur Thank you. I'm assuming that the Lightify Hub will determine if I need an update or do I still need to down load the firmware?
@Ken_Fraleigh Thank you for your input. I may still wind up doing what you had mentioned. The Sengleds aren't as smooth? I'm assuming when dimming and changing the temperature. I was looking at the GE's However, I don't have any experience with them.
Those lights have a very bad reputation for destroying peoples zigbee mesh. I think @april.brandt was pulling out her hair until she discovered they were causing her problems. If you have, or buy a hue bridge, I believe you can put them on the bridge. I personally have around 60 of the Ledvance version Sylvania Smart+ RGBWs and they have been very solid since the last firmware update. They are the ones with “Smart+“ on the side of the bulb. I only recommend the recessed RGBWs (RT5/6) due to their superior color and color temperature reproduction and reliability. I have 12 of these and have never had to rejoin or replace any of them. The A19s work well if they don’t overheat. The ones that have failed have been as hot to the touch as an incandescent light. They also lose their network connection (in my experience) when they overheat. On the plus side, Sylvania have been very good about replacing all of mine that have failed within their 2 year warranty period. None of them are in enclosed fixtures btw.
They do this weird color transition when turning on, and don’t work as well for me as the Sylvanias with Zigbee group messaging. It may be due to them not repeating for each other.
BTW, I don’t believe that Osram has released a firmware update for the CT bulbs in a couple years; at least not since they spun off their consumer lighting division. Any updates should have happened when they were connected to the SmartThings hub.
No love lost.
