I used to be able to control hue ambient bulbs with the set color temperature function but now this doesn't seem to be available. There is now an adjust color temperature but this isn't working for me. What has changed and how can I set cold and warm lighting?
It seems you cannot set a specific temperature you can only make adjustments. For example if you want to set it to 3000 you would need to know what it is already set too so that you could add or subtract to get to the required value.
Is this by design because if it is it is a very bad design.
It's the same for level, no set only adjust.
Am I missing something or is this broken?
Are your bulbs paired direct to HE, or integrated into HE from your Hue Bridge?
If the former, what driver are you using? If the latter, what integration app are you using?
When you are attempting the CT change how/where are you doing it -- i.e., from the device page, a RM rule, RL rule, etc.
1 Like
This is a webcore question so I am using that. The lights are added directly to hubitat as zigbee lights using the hue white ambient driver. I can control via the device settings but within webcore the 'set ' options are no longer available, only adjust.
Yep, apologies, I missed that webcore tag... I always just view by "Latest", so I'm admittedly sloppy about paying attention to tags.
Hope fully a fellow webore user (I'm not) will be able to chime in here!
1 Like
Any help on this subject?
Still no solutions to this problem?
Seems like it's a webCoRE question, assuming the commands work fine from the device detail page? Tagging @nh.schottfam to see if he wants to chime in.
2 Likes
The question is posted in the webcore section.
Yes, I understand that.
The question is whether you are dealing with an issue that is specific to webCoRE, as it seems, or if there is another issue that might be related to the device or driver.
3 Likes
For webcore issue, it is good to give a reproducer small piston for debugging.
For reporting, please see:
1 Like
Unfortunately an example piston would not help as it is a about functionality that used to be present but seems to be no longer available.
So to clarify, you believe you’ve identified a webcore issue, but are unwilling to participate in resolving the issue. For example, we still don’t know:
- How your hue bulbs are integrated with Hubitat
- Whether setColorTemperature works from the device page
- Whether you’re using the built-in webcore app or the community app
And you’re so convinced that the issue lies with webcore, that you’re unwilling to post a piston so the webcore developer can determine what the issue is.
If those are the conditions that you’re comfortable working with, then the likelihood is high that no one can help you, and this thread is pointless.
Would you like this thread to be closed?
3 Likes
God grief, I'd have thought my description of the problem was quite explanatory. You guys really do take great offence to the slightest notion of critisim. But you know what I have a work around that does work. I thought I'd just report a possible problem so someone can verify or otherwise and maybe help put something right before it became an issue for others. Every time I post on these forums I get flak. So I'm done. Do enjoy yourselves but I'm out of here. Any future problems I'll just work out myself which is the way it's always being anyway because help on here is non existent. Shame, hubitat could be such a good platform if it wasn't left to self righteous egotistical people to provide the support.
If the owners of hubitat are listening my suggestion would be to split the support forums. One powered as is by now which is free and one where the normal expectation of internet trolls can be expected and then another support forum powered by customer focused experts that are actually employed by the company which can be a subscription service which has some kind of service level.
You treat other people as if they’re trolling you even when they’re not.
Then you escalate by trolling them.
And nothing gets accomplished.
Please consider your own role in that cycle.
2 Likes
Hi @darren.rockach
I've just spotted this thread and please correct me if I'm wrong, but just to clarify, are you saying the 'Set color temperature' option is now unavailable.
I have Hue Colour Strips which are connected to a Hue hub and using 'Hue Bridge Integration' to connect them to HE.
I can see that option.
Is there anything you would like me to test for you?
4 Likes
From @bobbles post, it becomes abundantly clear that webcore supports setColorTemperature, when that command is supported by the device.
So if you want your issue resolved, you need to participate in its resolution. There’s either something wrong with your webcore installation, or there’s something wrong with however you’ve integrated your Hue bulbs, or there may be a corrupted database.
Distinguishing between these possibilities requires the provision of information.
If you feel unable to do so, you can request that this thread be closed.
2 Likes
Hi @darren.rockach, I think you are seeing the negative rather than the positive. It's very rare on this community to have people working against you, so it's best to assume that they are actually trying to help and answer the questions they are asking. Only then can they understand you exact situation and setup.
Please remember a few important things:
- almost ALL users on here are here because they enjoy home automation and they enjoy helping others
- No one is paid to help, so please respect that.
- Hubitat is so powerful that the possibility's are massive, that comes with complications that mean we need to break down what your seeing.
- Asking you to check certain things like how it works from you device page is a standard process due to the above.
So in this case you have said your lamps are directly connected using the built in driver, however what you are experiencing is not normal. Otherwise you would see more posts like yours. So if you could test the below on your device that would help to find where your issue is.
If it works then you move on to the app and if you could then show your piston would be the next step.
If it doesn't work then you have something odd happening and we would need to give you different advice at that point.
1 Like
I don't understand your scenario, so it is hard to provide an answer or suggestion
webCoRE has had from ST days built in lifx commands - these are still in webcore. This is not using Hubitat device handler apis, but built-in
Hubitat documentation for color temperature has device commands documented:
see ColorTemperature capability.
It would be good to more clear on what device you are using, or what command the device has that you are trying to use.
So I'm really done on here but logged in one last time to clarify and to also change my notification options as I don't want to get notification from here any longer!
Yes you can change the colour temperature in webcore BUT
you can NOT set it to a specific value you can only add or subtract from it's current setting. So if I wanted to set 3300 I would first need to know what it is currently set too and then either add or subtract to make that number.
For example if I wanted to set 3300 and the current setting is 2900 then I would need to add 400. But that means you have to first discover what it's current setting is. Seemingly you CANNOT just set it directly to the required value, you can only ADJUST the current value by the amount you specify. You used to be able to set the required value directly but now it doesn't seem to be possible as I discovered when I was editing my piston.
Now before you all start on a rant actually take a look as that's all I want to know, is it a bug or is it just me! If it's a bug maybe someone can fix it to help other people out and save them this ridiculous support that is hubitat. If it's just me all is good as I have a work around that works for my requirements.
