I’m unfortunately not sure when it happened, but within the last couple weeks, my Alexa devices have lost the ability to set the brightness level of dimmer Z-Wave switches. Alexa can still turn a light on or off if I say “turn [on|off] (name-of-light)”. But if I say “set (light) to 50%”, it thinks for 5-10 seconds then says it’s not responding. But immediately before and after trying that, on/off commands work just fine as expected.
My hub is a C8-Pro. I noticed it on firmware 2.5.1.172. I updated to .174 and observed it had the same issue. I then rolled back to 2.5.1.143 using advanced options in Diagnostic Tools, but the same issue is still present.
I’m not sure what logs to look for with this one. Any help is greatly appreciated.
I found another user who reported similar, but their solution was to unlink Alexa and start over. I really don’t want to rebuild all my Alexa configuration with my Hubitat devices, so I’m holding out hope for a proper fix. Thanks!
Thanks for your feedback. There are several updates to Alexa Skill coming in the next update that hopefully will resolve the issue you're experiencing.
Does it affect the functionality? The updated Alexa functionality now complains about invalid values instead of silently failing. Without knowing more about what device and driver it is, hard to tell if it's a harmless (if annoying) message or a proper failure.
The only routine I have for it is lights off and that's controlled by a virtual switch on hubitat side, it's only privy to it for direct bulb changes when told to do so (maker api), which is rare for the study. I hit the "play" button for lights off and there was no log.
When i tell it to set to a color it throws:
warn
Skipping Alexa.ColorTemperatureController.colorTemperatureInKelvin for BULBS:study; value is below 1000: 15
"cool white" or any of those colorTemperatures do not trigger it.
Fastest turnaround ever. 