Bond strategy from user vs developer perspective

As an eager DIY-er, the Bond platform gives me nearly everything I want to manage my RF (and occasionally IR) devices the way I want.

Would the ability to have additional template creation options and guidance, as well as maybe a way to share among the community, be awesome? Sure!
Can I make any hardware compatible device do what I want? So far, yes.
I do use a mixture of devices and programming to get real world controls and integrations (Harmony remotes, Insteon switches, keypads, and remotes – all controlled through my ISY controller and leveraging Bond’s local API), but it works well for me.

I do have Dyson fans that think they’re ceiling fans, or lamps and monitors that think they’re fireplaces – but it works, and I’m able to make enough changes via local API calls that the Bond app makes decent sense, even though it’s not my default method of controlling Bond-Bridge-associated devices.

Again, I’d love the ability to PATCH or update any properties of any device, support dimming natively, have a list of icons, ability to make my own Actions, etc.
But I’m doing well enough with what there is, and even though the Bond team is small, they do seem very responsive to the community, over time.
With patience on our part as customers, and with clear and specific use case requests being brought to Bond staff, we have a good chance of getting a lot of nice-to-haves added.

Of course, the Bond technology and design being leveraged and licensed by partners to make “Smart by Bond” products with Bond built in (no need for a Bridge) is something that I have begun prioritizing for my home renovation plans. Going to get Smart by Bond ceiling fans, landscape lighting, and will be selecting something compatible for shades/blinds.

1 Like