Add Broadlink-wifi climate support

[clementTal]

Description:

The broadlink_thermostat climate platform is a thermostat implemented in Home Assistant. It is used to control wifi thermostat manufactured by broadlink, like Floureon Smart Wi-Fi Programmable Digital Touch Screen Thermostat, Beok TGT70WIFI-EP Smart Wifi Thermostat and SeeSii Programmable Thermostat Heating WiFi

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#8920

previous PR: #15363, #19223

Example entry for configuration.yaml (if applicable):

climate:
  - platform: broadlink
    friendly_name: Thermostat
    mac: "xx:xx:xx:xx:xx"
    host: "xxx.xxx.xxx.xxx"

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

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

• Documentation added/updated in home-assistant.github.io

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

• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

[elupus]

Services should go on broadlink domain as per #21465

[frenck]

The friendly name is required? That is not usual...
I see the library requires it... but it isn't used actually?

In the above image, it shows the only part of the code that uses the entity_id?
The variables seem to be unused, however, they are required?

[tsvi]

We should be careful with the naming here as we already have broadlink RM switch. And since the RM switch can be used as a climate (as I foresee a merge with the smartIr custom component), we might cause problems. Maybe rename the component to broadlink wifi, so we have a clear distinction?

[clementTal]

@tsvi: not sure about naming problem here. This components is made to control thermostat made by broadlink and rebranded. The smartIr custom components you speak about is a components made to control IR climate. It made it simple than using custom climate component, but do the same. I would prefer having this components named broadlink better than a component that provide the same uses cases as another.

If my component should have another name, it will be named by it's brand name, so I'll need to create a least 3 component (breok, floureon, seesii) with the same code inside.

[tsvi]

Definitely was not imagining splitting it up.
But maybe rename to Broadlink Wifi Thermostat, as we have #21465 which might create issues. Otherwise we'll need somehow to merge both although they are completely different components.

[fantognazza]

Fix bugs and mistypes

[fantognazza]

Suggested change

	self._device.set_advanced_config(self, advanced_conf)
	self._device.set_advanced_config(advanced_conf)

[fantognazza]

Suggested change

	def set_advanced_config(self, advanced_conf):
	def set_advanced_conf(self, advanced_conf):

[JakubSch]

Hello guys, I am very sorry for such a dummy question but I am completely new. Could you help me step by step how to install this platform? I am 1 day user of HA :) Shall I create a broadlink/climate.py in custom components or it does not work like that? Thank you very much for help!

[pvizeli]

Please migrate / rebase to https://developers.home-assistant.io/blog/2019/07/03/climate-cleanup.html

[MartinHjelmare]

There hasn't been any movement here for a long time. I'll close now. We're trying to decrease our open PR buffer. Please open a new PR when ready to finish.