They should just open the gates of SmartThings Energy to certified Matter devices with energy monitoring and allow the user to choose which devices to include or not. Otherwise it’s just another form of Matter fragmentation.
After all, for cloud devices there’s a specific integration needed to send the energy report the way SmartThings requires, but with Matter the data comes from standard energy reporting.
Totally agree
OffWithTimedOn would be a much more useful feature. Imagine being able to remotely power-cycle the hub or Internet router…
The OnWithTimedOff feature is designed mostly for binding motion sensors to lights, then it’s quite useful. It even has the option to ignore the command for a while if you manually turn the light off so the motion sensor doesn’t turn on a light you just turned off.
I use it in the plugs as an auto-off that can be restarted. A smart button will turn on the fan for an hour. If later I prefer to keep it on more time I press it again and the timer resets to an hour. With SmartThings routines that can’t be done since delays cannot be reset or canceled, and on top of that the timer runs in the plug so even if the hub dies it will turn off.
Regarding the “auto on” I looked for it when creating the driver but there’s nothing in Matter spec that could be used.
Well… that’s an awesome idea!
Regarding the “auto on” I looked for it when creating the driver but there’s nothing in Matter spec that could be used.
I know, but it should.
I use either Tapo P110M or P304M for this.
Restarting can be made if you use virtual switch standard and Setting Force state change on (default).
I tested it using motion sensor.
Delay ( 5 minutes ) is restarted when motion is detected again. Virtual switch is turned off after 5 minutes from last motion detected.
Thanks for the info, using a virtual switch and some routines would be indeed a workaround.
Halloween day, what a proper date to publish a scary update 
.
There are A LOT of cool new features and internal changes that I wasn’t even sure about making them public since it’s opening Pandora’s box but we are here to play after all, so let’s play.
Will talk about the new stuff later, right now I’m just interested in knowing nothing is breaking for existing users.
───────────────────────────────────────────────────
Driver Id 95a854a8-b110-4cdb-bb9e-82486235c642
Name Matter Playground
Package Key matter-playground
Version 2025-10-31T10:30:27.160800971
───────────────────────────────────────────────────
Just a tease: if you’re curious, try changing the driver of a Nanoleaf or WiZ smart bulb 
That’s a bug in Nanoleaf lights, they don’t follow the spec and use OnLevel to store the last brightness when you turn it off to restore it later, which of course is not its purpose.
WiZ also has its set of bugs with OnLevel though, they rewrite the value when they are powered off, but other than that it’s usable. I use it for the hallway lights so the brightness is different at night since WiZ 1.35.0 firmware broke the custom rhythms (WiZ feature to do basically the same).
For others reading, OnLevel sets the brightness a light will have when you turn it on. It’s in Matter units so instead of 1 to 100% is 1 to 254. The null value which means restore the previous brightness is -1
TIL that smart bulbs don’t have built-in speakers…
Still waiting for a fitting capability…
For compliant lights that don’t mess with On Level you typically just create a Daily routine in SmartThings and use the Write On Level action at different times of the day (sunrise, sunset, midnight, etc.).
Since Nanoleaf currently rewrites the values set by the user, the workaround is creating additional routines with starter the light being Off (and time period conditions as needed) and action Write On Level so it sets the correct value again.
Since the cat’s out of the bag, the driver now supports Matter smart bulbs 
. Some of the features are not available in other smart home platforms by the way, not even Home Assistant!
Perks for smart bulbs (updated Nov 16th, 2025)
Step commands.Move (WithOnOff) and Stop native commands. A button with support for Held / Release is highly recommended. More info in this comment and the next. For lights that flood the hub there’s also an auto-repeat step feature which supports transitions.
On with Timed Off or the native Toggle command that does not depend on SmartThings cache.Tips when using steps with buttons
Tips when using steps and set with Rules API
rate argument if you use the Rules API is the transition time in tenths of a second to match the native unit. It’s called rate to match SmartThings setLevel command, which also supports transitions. The maximum allowed in Matter is 65534 tenths of second which is 109 minutes.stepTemperatureMired(1000, 150) and for coolest use stepTemperatureMired(-1000, 150).Implementation notes
Some of the new actions for smart bulbs
You have defined your own capability panelorange55982.colorMode with values color and white.
ST has its own proposed capability colorMode
Values:
• color - colour
• colorTemperature - colour temperature
Presumably the operation is the same.
That’s a good catch! I forgot I added that feature too, have been playing with drivers for so long 
.
They serve the same purpose indeed, didn’t use it precisely for being proposed instead of a production capability and because no stock driver uses it. Basically out of fear that being subject to change could make the driver crash eventually if they do.
Edit: Funny thing I’ve just realized the configuration capability is deprecated . Well, it was a nice to have but not really needed so I’ll remove it in the next update.
@SeanTek since you were looking for smooth dimming for your Matter LIFX bulbs, you may try this driver. As long as LIFX has a good Matter compliance and doesn’t flood the hub it should work.
It’s super easy to use, install the driver linked in the first post, change the driver of a bulb and create the button automations to map the three Dimming actions (Start brightening, Start dimming and Stop). That’s all.
If you test it and the stop takes too long to stop the dimming, check in the history of events of the bulb if there are a lot of brightness changes. In that case you’ll have to wait for LIFX to update their bulbs to avoid flooding the hub and use steps instead, which this driver also supports.
New version 2025-11-01T16:32:40.978081827. I’ve removed the deprecated configuration capability that had marginal use and updated the driver description to mention smart bulbs and link to this post in the support URL.
Turns out Nanoleaf does the same with the power-on state (StartUpOnOff attribute), instead of setting the attribute to Previous (null in Matter) to restore the last state, they overwrite it to On when the light turns on and overwrite it to Off when the light turns off. Someone didn’t understand the specification .
I tried to report the issues in their subreddit but the post got deleted, twice. It’s been a year since their last firmware update, a Matter 1.4 is way due.
Ah yes, the legendary Nanoleaf subreddit - where in 2025 you still have to remind people that a Thread device actually needs a Thread Border Router if they want to control a lightbulb outside of Bluetooth range.
Apparently, all Nanoleaf lights are “completely unreliable” and “constantly losing connection”… and the rest of the posts are about LED panels falling off the wall - obviously the fault of Nanoleaf, not the wallpaper glue.
So it’s no surprise your post got deleted. Way too technical for a place where you’ll get downvoted just for pointing out that a smart home involves more than one lightbulb and an app - and that maybe, just maybe, the falling panels aren’t a Matter issue but a matter of physics.
Rumor has it someone (Tom?) from Nanoleaf lurks there - might be worth contacting them directly.
That said, the CSA really needs to tighten up the Matter certification process. It’s not enough for the compliance documents to just say “true” or “false”.
