# Matter Lights - "during xx sec" missing
**URL:** https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090
**Category:** Questions & Help
**Tags:** matter, lights
**Created:** [October 27, 2024, 11:52am UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090 "2024-10-27T11:52:16Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Jumpingtrees](https://community.homey.app/u/Jumpingtrees)
#### Post date: [October 27, 2024, 11:52am UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/1 "2024-10-27T11:52:16Z")
Hello,
while playing around with Circadian Lightning I noticed that a dim level or temperature cannot be set during a distinct time period. While it is possible when using the flow card provided by the Hue app, the native Matter flow card does not have this feature.
Am I missing something? Is this a missing feature in the Matter protocol or does it need to be implemented by Athom? Does somebody may have a workaround for the Matter device? I dont like to have the same device twice in my list of devices.
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [October 27, 2024, 1:51pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/2 "2024-10-27T13:51:27Z")
> [@Jumpingtrees](#):
>
> Is this a missing feature in the Matter protocol or does it need to be implemented by Athom?
Transition time is a mandatory field for MoveToLevel commands in the Matter 1.2 standard, which Athom says Homey supports:
In other words: Athom needs to implement this.
---
### Author:  [@staeff](https://community.homey.app/u/staeff)
#### Post date: [October 27, 2024, 1:51pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/3 "2024-10-27T13:51:58Z")
The matter standard does support a duration for brightness/color transitions. So either Hue does not expose that through their bridge or Homey can’t handle it. But I don’t have a Matter certified light bulb to check myself.
---
### Author:  [@staeff](https://community.homey.app/u/staeff)
#### Post date: [October 27, 2024, 1:53pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/4 "2024-10-27T13:53:10Z")
Could still be that Hue simply does not expose it through their bridge as their Matter support is a bit shaky
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [October 27, 2024, 1:59pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/5 "2024-10-27T13:59:04Z")
This is Homey’s “dim” implementation for Matter:
```auto
export const genericOnDim = ({ virtualDevice }) => ({ capabilityId, value, }) => {
if (typeof value !== 'number') {
throw new TypeError(`Invalid value for capability ${capabilityId}: ${String(value)}. Expected number`);
}
const level = 1 + Math.round(value * 253);
return virtualDevice.sendClusterCommand({
endpointId: virtualDevice.store.capabilities[capabilityId].endpointId,
command: MatterClusters.LevelControlCluster.commands.moveToLevel,
commandArguments: {
transitionTime: 0,
level,
optionsMask: {
executeIfOff: true,
coupleColorTempToLevel: false,
},
optionsOverride: {
executeIfOff: true,
coupleColorTempToLevel: false,
},
},
});
};
```
Notice the transition time 😉
---
### Author:  [@staeff](https://community.homey.app/u/staeff)
#### Post date: [October 27, 2024, 2:01pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/6 "2024-10-27T14:01:55Z")
Well ok in this case fully Homeys fault and a huge L since they support it for zigbee etc… I guess only option is to message support and wait for a few months…
**EDIT:** Just checked the specs and transitionTime has been part of the standard since 1.0
---
### Author:  [@Jumpingtrees](https://community.homey.app/u/Jumpingtrees)
#### Post date: [October 27, 2024, 4:58pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/7 "2024-10-27T16:58:18Z")
Thanks for the clarification! I will write to the support and request this feature according to the Matter standard. The more people will do that the higher the chance that we do not need to wait months. 😉
---
### Author:  [@Bence\_Molnar](https://community.homey.app/u/Bence_Molnar)
#### Post date: [December 16, 2024, 7:54pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/8 "2024-12-16T19:54:29Z")
I wrote 2 times because Nanoleaf light bulbs (matter over thread) has the same issue…no duration…
My old inner bulbs was that so that was very disappointing with an update I have less functions 😕
---
### Author:  [@staeff](https://community.homey.app/u/staeff)
#### Post date: [October 12, 2025, 8:41pm UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/9 "2025-10-12T20:41:40Z")
@robertklep just out of curiosity does homey still use the code this way with “coupleColorTempToLevel: false” in the current firmware? Because I’m running into an issue with my new Hue Essential bulbs that dimming them changes the color temperature (from bright/cold to dark/warm) and wrong usage of this property seems like a strong contender.
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [October 13, 2025, 4:51am UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/10 "2025-10-13T04:51:56Z")
Yes, still there (at least in 12.7.0):
```auto
export const LevelControlClusterMethods = ClusterMethodFactory.begin()
.withMethod('setLevel', async (ctx, level, transitionTimeMs) => {
const transitionTime = durationToTransitionTime(transitionTimeMs);
await ctx.cluster().sendCommand('moveToLevel', {
level,
transitionTime: transitionTime,
optionsMask: {
executeIfOff: true,
coupleColorTempToLevel: true,
},
optionsOverride: {
executeIfOff: true,
coupleColorTempToLevel: true,
},
});
})
```
Every description I read for that option explains exactly what you’re describing, no idea why this option is enabled by default.
---
### Author:  [@staeff](https://community.homey.app/u/staeff)
#### Post date: [October 13, 2025, 5:08am UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/11 "2025-10-13T05:08:45Z")
Thanks for looking it up. Seems like they changed the value to true since the last time you posted the code which would explain the behaviour.
---
### Author:  [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [October 13, 2025, 5:14am UTC](https://community.homey.app/t/matter-lights-during-xx-sec-missing/119090/12 "2025-10-13T05:14:12Z")
Oh yeah sorry, I misread. It has indeed been changed to `true` for whatever silly reason.