# Feature Request: Fireplace Lights

**URL:** <https://forum.bondhome.io/t/feature-request-fireplace-lights/699>\
**Category:** Devices\
**Created:** [August 4, 2019, 10:13pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699 "2019-08-04T22:13:43Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dman2306](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dman2306](https://forum.bondhome.io/u/dman2306)\
**Post date:** [August 4, 2019, 10:13pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/1 "2019-08-04T22:13:43Z")

</div>

It’s great that I can control my fireplace’s blower, but many gas fireplaces have an integrated accent light. It’d be nice if there were commands to support this.

---

<div class="post-metadata">

**Author:** ![marcio](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/marcio/32/210_2.png) [@marcio](https://forum.bondhome.io/u/marcio)\
**Post date:** [August 6, 2019, 9:30pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/2 "2019-08-06T21:30:09Z")

</div>

Done!  
If you close and open your app again, you will be able to record Light On/Off and Toggle to your Fireplace

---

<div class="post-metadata">

**Author:** ![dman2306](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dman2306](https://forum.bondhome.io/u/dman2306)\
**Post date:** [August 9, 2019, 11:35pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/3 "2019-08-09T23:35:39Z")

</div>

Works great, thanks!

---

<div class="post-metadata">

**Author:** ![dman2306](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dman2306](https://forum.bondhome.io/u/dman2306)\
**Post date:** [August 12, 2019, 2:09am UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/4 "2019-08-12T02:09:28Z")

</div>

Is adding commands like this an easy thing? I ask because my fireplace has a few other options, for example right now all I can set the fan speed to is low/medium/high, there is no way to turn it off that I can see (though the FpFan documentation doesn’t seem to exist?). The other thing my fireplace has is an “Ambiance burner” - in addition to the flame height for the main flame, this is a secondary flame that has an on/off state. It’d be great if I could control that as well.

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [August 12, 2019, 3:06pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/5 "2019-08-12T15:06:47Z")

</div>

> [@dman2306](#):
>
> The other thing my fireplace has is an “Ambiance burner” […] a secondary flame […]

You could manually add more commands to the device, but the downside is, they would only work within the app. To get support on Alexa + Google Home, we need to add support for specific “features” that are found in many devices.

In this case, I’d recommend adding the “Living Room Ambiance Burner” as a second fireplace, separate from the “Living Room Fireplace”. Then you get the benefit of voice integrations just working.

---

<div class="post-metadata">

**Author:** ![dman2306](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@dman2306](https://forum.bondhome.io/u/dman2306)\
**Post date:** [August 13, 2019, 1:14am UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/6 "2019-08-13T01:14:48Z")

</div>

Hmm if you guys might add support for more commands in the future I think I’d rather just wait. If I make it a separate device that screws up the fact that it is a “child” meaning if I turn off the fireplace, Bond won’t know that the Ambiance burner is off too. That would also help with this, but I don’t think that would help me add an off command to the fireplace fan.

I think it’s just best to wait for you guys to do it so it’s done right.

---

<div class="post-metadata">

**Author:** ![jacob](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/jacob/32/312_2.png) [@jacob](https://forum.bondhome.io/u/jacob)\
**Post date:** [August 13, 2019, 2:32pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/7 "2019-08-13T14:32:40Z")

</div>

> [@dman2306](#):
>
> Is adding commands like this an easy thing? I ask because my fireplace has a few other options, for example right now all I can set the fan speed to is low/medium/high, there is no way to turn it off that I can see (though the FpFan documentation doesn’t seem to exist?)

This one would be easy. Yeah I must have overlooked documenting that feature, I’ll get it in soon. There is a “TurnFpFanOff” action and a “TurnFpFanOn” action, and we’re adding recordable commands with those actions now.

> [@dman2306](#):
>
> Hmm if you guys might add support for more commands in the future I think I’d rather just wait. If I make it a separate device that screws up the fact that it is a “child” meaning if I turn off the fireplace, Bond won’t know that the Ambiance burner is off too. That would also help with this, but I don’t think that would help me add an off command to the fireplace fan.

Something like this is so far not on our roadmap. However, the 2.7.12+ firmware has limited, undocumented support for script-defined devices, and we’ll be rolling out more a more fully-developed version of this feature with accompanying documentation over the next few weeks. Such a device could be defined by a Lua script. However, I think a higher-level integration — Google Home, Alexa, Hubitat, etc. — would be the best fit for defining this sort of parent/child relationship.

---

<div class="post-metadata">

**Author:** ![marcio](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/marcio/32/210_2.png) [@marcio](https://forum.bondhome.io/u/marcio)\
**Post date:** [August 15, 2019, 4:39pm UTC](https://forum.bondhome.io/t/feature-request-fireplace-lights/699/8 "2019-08-15T16:39:08Z")

</div>

Hey guys, you can now record Fan On/Off on fireplaces! Just close and open the app again to fetch the new definitions!
