I have some new-to-me Govee lights for testing.
I haven't ventured into the WiFi world before so these looked interesting.
I would like to use the CT option for standard lighting and RGB for the mood portion.
I tried to added them to my Room Lighting Activator but it seems I have to commit the bulbs to CT or RGB, aka hardcode otherwise I just get logs errors on non-supported commands.
I am assuming I will have to make 2 RL Activator children, one for CT control and one for RBG as I don't see a way to change them programmatically?
The other issue is that RL doesn't seem to extend any of the functionality of these bulbs to WebCore except Set RGB/Level basics.
You can't event set the CT colour temp as the only option is emulated "adjust color temp". This increments/decrements the K which doesn't help fix a constant K number, say, on a Mode change.
The only way I see around this is to manually loop through the devices as a device global in WebCore and leave RL altogether.
Not an issue just not as elegant.
I imagine to get RL to work HE guys would have to mod the app to advertise and handle the other device type attributes and @nh.schottfam would have to do something as well?
This appears to be a driver issue for the bulbs. You should mention what you are using for drivers for issues like this. Did you enable LAN control in the Govee App and you are using a lan driver? Or are you using the cloud and a driver that works with Govee APIs like the one below?
These bubs, H6008, are not LAN supported.
I'm using the Govee V2 stuff and all the commands are there in WebCore if I access them on a device basis.
I was hoping to aggregate them using an app instead of looping through individual devices.
Oh, I must have read your post too quick, I was thinking you were referring to the Room Lighting app, but you mean your own custom app. That makes more sense.
I also use custom apps for room lighting, I call them Scene Executers, and I have three versions of them for different areas of the house.
I didn't think the setting capability for a device wrapper actually gets tied to that capability. I use switch capability for dimmer device inputs, and I have no issues subscribing to level or calling setLevel() on that device. You seem to be saying that these bulbs specifically do not respond to calling command methods that are exposed in the driver, but I'm not clear on how you are "committing" the bulbs to be either CT or RGB, and how that somehow affects your access to the methods in the driver.
A bit more info on what you are doing in your app and how you are doing it would help.
No, indeed you were correct, I was referring to Room Lighting app.
I use it in conjunction with WebCore as it makes cleaner code.
Room Lighting makes you commit to the type of bulb you want to control; you can't switch between types dynamically.
The commands you need exposed are not there in WebCore.
It seems I will have to write my pistons to deal with the devices directly and not through the RL app.
Yes indeed.
I can used the devices individually in WebCore.
It's more of a Room Lighting issue as it doesn't pass or handle/emulate commands like Set CT.
You can't change the bulb assignment either on the fly in RL.
I was hoping to use them in CT mode for day uses by altering the Kelvin but send RGB in other instances.
No problem, just did it the long way in WC; just gets messy with all the Modes/Levels/Ct/RGB and If/Then/Else If ad infinitum.
How is your Room Lighting instance configured? If your devices support it, it should create an activator with both "Set Color" and "Set Color Temperature" commands that will work for either color or CT. Is that what you're looking for but don't have? If so, it's probably something related to your RL configuration. But from your initial post, it's not clear if it's that or just your actual devices missing some comands. Can you share more information about what is missing for you where?
It's really in every facet. RL doesn't let you change the bulb type dynamically and WebCore only shows "emulate CT adjust"; you can't Set CT in WC only inc/dec the existing number.
It's all good, I'm just doing it by Device globals and loops in WC and ignoring the RL Actuator.
RL makes you set an activation type in the activation table, yes, but if you need something more "dynamic," you can use time periods or modes to vary activation settings (including activation type) based on that. But in any case, if you have it create an activator, it should give you full capabilities on that device -- e.g., "Set Color" even if you only have a single activation table and it's set to "CT," for example. These two issues aren't really related.
It sounds like that's where the breakdown is for you. I'm not sure why, but as I suggested above, sharing your RL setup should help figure that out.
Of course, if you're happy with your workaround, that's good, too! Just wanted to point out that it shouldn't be necessary -- something is just a bit unusual with how yours got set up for whatever reason.
Thanks for the reply.
Yeah, I think using WC is the best way for me. I don't use RL for anything except a device aggregator->Activator for my pistons and Dashboards and I find the rule based logic frustrating and a retired programmer.
In WC I enjoy having the extensive trace/debug when things aren't what I expect and good old Variables types.
I tried creating a test activator device in room lighting.
I have no need to do anything with it, but it appears to have the attributes for both RGB and color temp, consistent with what @bertabcd1234 said is expected behavior (and not consistent with what the OP is reporting).
Ok, now I have to go try this again.
I had no Set Color Temperature in WC only Adjust ....
That means my Activator device from RL is exposing itself differently to WC than the device you created.
Hmmm.
I changed my Activator to CT and tried all the Activator device drivers and I don't get what you show.
No Set Color in WC and the states are limited.
What HE Room Lighting Activator driver are you using?
Maybe I have a corrupt RL device or I'm in left field and am doing this wrong.
Ok.
Fresh Activator and I let RL decide on the driver; it picked the one I tested but now I have states like @marktheknife and WC gives me Set Color Temperature.
I have changed RL drivers before when I have gone from a switch to a dimmer and changed Device Control Type.
I guess the CT/RGB thing just doesn't get initialized properly if one does that.
Thanks for killing time with me boys.
