FlyingDiver wrote:Ok, I was able to replicate the behaviors based on the payloads Cesar posted. Here's what's going on, as best I can tell. I'm using some shorthand for the commands.
When turning on the device using ON/100, all works as expected, and the status reply from the bridge also reports ON/100.
When turning off the device using OFF/(any), the device turns off, but the status replay from the bridge is OFF/(previous brightness level). The bridge ignores the brightness when it gets an OFF.
When turning off the device using ON/0, the bridge (or actual device) interprets this correctly and the status reply is OFF/0.
The problem is that Indigo uses the brightness value to override the on/off state. When I set the (Indigo) device's state to OFF/100, the non-zero brightness causes the state to be ON. I set both states in the same update.
I can understand why the bridge retains the brightness level, so going ON->OFF->ON would go back to the original brightness.
I think the best thing here is for the plugin to only update the brightness level if the state is ON.
Try this pre-release:
https://github.com/FlyingDiver/Indigo-S ... /tag/0.3.8
Hello everyone, hope you are all safe and enjoying some family time.
Joe, I'm not sure, but maybe a similar rationale applies to the dimmer type of shim device, as the Indigo GUI Icon stays off.
TIA
Cesar