Add support for fireplaces to bond integration

[prystupa]

Proposed change

Add Bond-controlled fireplaces to bond integration, exposing them as lights (on/off) with brightness (flame level)

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[ctalkington]

im wondering if any other fireplaces have been implemented as this feels a bit hacky to me.

[prystupa]

im wondering if any other fireplaces have been implemented as this feels a bit hacky to me.

I search through HA for 'fireplace' and there is no patterns at all I can find. Surprisingly, there is no 'FireplaceEntity' either. Though the 'light' domain with fireplace icon approach looks reasonable to me (fireplace works a lot like dimmer), I am open to suggestions...

[ctalkington]

totally get it where you are coming from.

Out of curiousity, reading the docs it says:

For Fireplaces, it refers to the state of the flame. Note that many fireplaces have separate light or fan functions, which are not governed by the Power feature.

Do the fans/lights get handled by prior code or would they have to be added after this?

[prystupa]

totally get it where you are coming from.

Out of curiousity, reading the docs it says:

For Fireplaces, it refers to the state of the flame. Note that many fireplaces have separate light or fan functions, which are not governed by the Power feature.

Do the fans/lights get handled by prior code or would they have to be added after this?

They would have to be added after this as they all use special Bond commands - I just started with 'main' fireplace device first - fire, as I expect that is what people are mostly interested in automating...

[ctalkington]

im going to approve this as i dont really see a better way to represent a fireplace with flame intensity with current platforms. Flames (fire) are a type of light in a broad sense so its not so far fetched.

[ctalkington]

I do have one concern since fireplaces can have lights and fans per docs. itll be important to set names such as "{device name} Light" or "{device name} Fan" if they dont come from bond as such if/when you extend the support.