When dimmer switches are configured as physical turn ons/offs for a motion lighting rule and they are the only switches being acted on in that rule, their brightness level is skipped over since they are seen to already be on.
- Preset the brightness of a dimmer to 100 while dimmer is off, when according to the mode and the motion lighting rule it should be 1.
- When the dimmer is physically, or digitally triggered, i.e. not by the motion, the motion lighting rule responds with "Not turning on, already on" since that dimmer is the only device in that rule and it is seen to be on since it was just physically or digitally pressed.
- This then does not change the brightness level of the dimmer to the intended level of 1 even though it is at the "incorrect" level of 100.
Add a second endpoint device to that motion lighting rule, real or virtual. If there is a second device in the rule to act on, it seems to send a request to all devices being acted on, thus resetting the brightness to the correct level regardless of what level it was when physically or digitally turned on. This, in my opinion, is the intended effect of the rule.
Has anyone else experienced this issue or is my assessment of how the app should be functioning incorrect?