Hi Developer,
Re: SetBrightness: note that for most legacy r/c ceiling fans in the market, there’s a single “hold to dim” button. There’s just a “start/stop” dimming capability, not a “set brightness” capability at the level of the RF signals. This means that the Bridge has no idea what the true brightness level is. Consequently, we are able to emulate the hand-held remote experience within the Bond Home app, but we cannot export a SetBrightness action to integrations in any meaningful way. (Fanciful possibilities of dead reckoning aside).
Our consumers told me their app has up, down and stop control that do work to adjust their light brightness.
Not sure what stop means here (could be mixed up with Up/Down/Stop UI for Somfy shades?).
But there are a very small number of ceiling fan remotes with separate Up and Down dim buttons, which suffer from the same problem described above.
Note that there are some remote controls which support SetBrightness at the RF level (these are remotes with LCD screens typically). But then the physical remote control must not be used to avoid conflicts.
Re: TurnLightOn: what @residualimages said.
I’ll just add instruction and screenshot to see this option:
Bond Home app > Device > Settings > Trust Tracked State
Read the grey text for another explanation:
If you want to use TurnLightOn/Off in the integration, user will want to enable that Trust Tracked State switch in the app, and then discontinue using the factory remote.
If you instead opt to put just a ToggleLight control in the integration, user can leave this option disabled and continue to the use the factory remote.
This option can also be PATCHed via the API.