Lutron Caseta Switches not processing commands consistently

#1

1) Give a description of the problem
Lutron Caseta Switches not responding to commands from webCoRE consistently
2) What is the expected behavior?
Turn on/off when with command

3) What is happening/not happening?
Sporadically switches don’t change with command.

4) Post a Green Snapshot of the pistonimage
(UPLOAD YOUR IMAGE HERE)

5) Attach any logs (From ST IDE and by turning logging level to Full)
Logging shows that command was skipped because it would not change the state of switch

REMOVE BELOW AFTER READING
My theory is that the API is receiving incorrect “switch state” from Lutron Switch which is causing the switch to not set as expected. Is this something I can alleviate by changing “command optimizations” to “no” or is there a different solution?

#2

After much troubleshooting I’m convinced this is an issue with Smartthings/Lutron Caseta API not webCoRE, so I am going to contact smartthigs/lutron tech support. Thanks in advance if anyone has any experience with this.

#3

Thanks @halfrican , I’m only 2 days into webcore and was banging my head trying to understand why my Casetas were sporadic. Is it against community protocols to ask if you’d mind updating this thread with any new info you find?

#4

Well after some more experimentation I do not believe the problem I’m experiencing has anything to do specifically with Lutron.

The problem seems to be that occasionally smartthings doesn’t know what the state of the light is as I first concluded.

In the logs I can see where smartthings is saying that: Skipped execution of physical command [Front Foyer Ceiling].setLevel([40]) because it would make no change to the device

Any assistance on how to work-around this would be greatly appreciated.