# Add buttons to existing Remotes **URL:** https://forum.bondhome.io/t/add-buttons-to-existing-remotes/3098 **Category:** Devices **Created:** [February 23, 2022, 2:50am UTC](https://forum.bondhome.io/t/add-buttons-to-existing-remotes/3098 "2022-02-23T02:50:28Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![residualimages](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/residualimages/32/74_2.png) [@residualimages](https://forum.bondhome.io/u/residualimages) #### Post date: [February 23, 2022, 11:12pm UTC](https://forum.bondhome.io/t/add-buttons-to-existing-remotes/3098/3 "2022-02-23T23:12:04Z")
A previous Bond team member once shared [this method](https://forum.bondhome.io/t/dummy-devices-w-no-remote/1246/3) of adding templates to your Bond Bridge for devices, without scanning the signals from their OEM remotes. Now, I think the ‘community scripts’ piece he mentioned has been pushed to the back burner with other items on which the team has been focusing, but I remembered that old post today. Wonder if we could pick and choose to add additional templates via this API call strategy, remove buttons / commands that we don’t want (from the Bond app or API), and then name the resulting devices something to distinguish them. Might have 2+ devices listed in Bond for some fan that template #1 works better with the lights and template #2 works better with the fan (maybe discrete command control). Hmmm --- _[View the full topic](https://forum.bondhome.io/t/add-buttons-to-existing-remotes/3098)._