This may be a dumb question, but is there a way to do transitions with the blues? Usually with HomeAssistant i use the light.turn_on service and add a transition: 5 for a 5 second transition. But this doesn’t seem to work with the Blues as the light just turns on. Been playing with the remote ramp rate setting too without much luck.
Yeah this would be nice to have implemented, right now my logs get spammed with No converter available for 'transition' (10) as adaptive lighting adjusts the brightness of lights. This is a pretty standard feature on most lights so it would be nice to have here as a way to override the remote dimming rate
FWIW, light.turn_on/off works for me with transition times. I did have a problem with turn_off setting the current level to 0, which then caused the light come on fully dimmed if I subsequently used the paddle to turn it on. But the on/off with transition does work. I am using ZHA, so maybe that’s the difference?
For me, the issue only happened when I used light.turn_off with a transition time. If I leave the transition time unset, it works fine. I was fine with the default transition time in my automations, so I just removed the transition time and it worked well enough for my purposes. (It looks like I said the opposite in my original comment above. It’s definitely leaving the transition time unset that works for me.)
@EricM_Inovelli would it be possible to ask the manufacturers to support transition commands in an upcoming FW release? I use Adaptive Lighting as well and my logs are constantly spammed with errors since the blue’s do not support receiving transition commands. I would assume this also means the reds don’t support it either.
The Blue and Red devices definitely support commands with transitions. I don’t know a lot about HA (I use Hubitat migrated over from SmartThings) and if they’re not working for you its more likely to be something specific to the HA environment
I just remembered that earlier versions of WebCore didn’t support transitions and I had to work with the WebCore developer to add it and I’ve been using transitions ever since. (the HE Rule Machine always had it) However that was several years ago and I’m not even sure if WebCore runs on HA or not. But it might be a clue that could be a Node Red limitiation (if you’re using Node Red on HA)
I currently have the problem with ZHA using HA 2023.8.1 where when I use the transition time for dimming and then try to turn on from the paddle it turns on at 0%. I have light switches on both 2.14 and 2.15 that both have this issue. However, I do see that on/off transition times are respected for me and I don’t see any errors
There’s a defaultLocalLevel parameter that you can set to whatever brightness you’d like when you turn the switch back on. That doesn’t solve for being able to default back to the prior brightness (before issuing the transition to off command), but it’s a good solution for most use cases. I should maybe assume you have a use case for that, though, based on you posting it
Changing a param on the switch seems like a weird workaround to me and it’s not exposed directly in ZHA. If there are no reasons why it shouldn’t be exposed I can make the PR to expose them this weekend
I’m also using Adaptive Lighting and have it set to groups with bulbs and switches together (I want the brightness level indicated by the switch’s LED bar). AL’s morning and evening adjustments result in this error spamming the logs. I’m also running zigbee2mqtt v1.33.2.