Wifi thermostat (Beok, Floureon, Beca Energy) component

Maybe it’s not exactly the same model. Mine is different from the originally shown there because it’s not for electric but gas, but it looks the same, with buttons and no touch screen.
I don’t know how to check that there’s the broadlink wifi inside ?

I think you can use the MAC address to determine if its a broadcom/broadlink based one.

@uls169: this device is not a broadlink device, so this component will not work. I made a portscan and found port 6668 open which may point to a tuya cloud based design, maybe try the tuya component:

You are right. Thank you for kicking me. Thermostat paired with Tuya app well (it is similar to Beok app). Home Assistant component loaded, thermostat in climate found. Unfortunately, it is not working well - I can set it on/off and I can set target temperature in whole degrees but temperature reading is strange (doesn’t respond to any temperature). It is step forward but through the time I am beginning to think that I don’t like this thermostat.

Hi
I , just began learn HomeAssistant. And I install it on netbook, linux mint.
I have thermostat BEOK TGT70WIFI and I added it in HI. But in my device has two temperature sensor, internal and external, for warm floor or control the temperature of the heat carrier. And external temperature not displayed.
The device has a setting “choose sensor type”, I need internal`s control and external limit, but setting are reset “only internal”, after work HA with device.
What can be done here?

I’m getting this error: “ModuleNotFoundError: No module named ‘BroadlinkWifiThermostat’”

Error while setting up platform broadlink
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/climate/broadlink.py”, line 132, in setup_platform
import BroadlinkWifiThermostat
ModuleNotFoundError: No module named ‘BroadlinkWifiThermostat’

any idea?

nevermind. deleting the __pycache__ folder fixed it… works great! thanks @clementTal! why is not yet an official component?

The conf can be set on “advance_config” parameter. If you do not set it, default value will be applied.

I’m currently working on it, I’ll submit a new pull request within the week :slight_smile:

That how the component work. I’m currently working on it, I’ll take care of your need :wink:

1 Like

It should work with all broadlink, but not all BECA thermostats are broadlink.
I’ll try to create a script that show if a thermostat will work with it or not.

Work is in progress, I’ll make a new release within the week !

As I said before, thanks a lot @clementTal
Component works great and I’m very happy it is local, fast and with no cloud requirements.

That said, I’m not sure I would have the scheduling part embedded in this component.
It feels ‘wrong’ from a design point of view. The purpose of this component should be to just expose thermostat sensor values and actuation (that is, turning the heater on/off).
To me, any scheduling should be managed in automations, or from some other generic component, but not here. Otherwise you would end up having all climate components implementing their own (different) scheduling logic.

You might say “hey, the component exposes those functionality! why loosing them?”. To me it would be in the name of genericity and not having duplicated/different code to deal with basically the same problem across ha.
Please, take this just as my 2 cents, and feel free to ignore me.

I agree, for most of users, schedule conf is not usefull.
In the next release, I’ve separate it from the config, and made it available through services only (as for advance configuration).
The reason I let it available, is because the thermostat is part of what I call “sensitive” part of my home automation. I do not want it to fail if there is a wifi/HA/network failure.
It do not block the use of HA authomation (by setting the mode to “manual” and set the target temp at distinc times.

1 Like

I have same thermostat, it work with tuya :frowning_face:
I’d like to manage it in local without tuya cloud service

Yes. But it doesn’t work well. I have electric floor heating. Some temperature is showing in HA but I can’t identify what is it. Thermostat target temperature settings in 1deg C steps? Nothing for me.
Problem is in Tuya component, resp. pytuya library. It is not ready for such kind of thermostat. So the reasonable integration is not possible.
But I think the biggest problem is in thermostat firmware! When the floor temperature meets the set limit (for example 35deg C) the thermostat switch the relay 3 to 5 times (it seems it can’t decide to shiwtch or not). The relay will wear out quickly I guess and it is uncomfortable at night.
I recommend don’t buy it even if you see it with good discount. BHT-002-GBLW http://bit.ly/2zscERh
I am using Devireg 550 units in my house, these are “set and forget” devices. I wanted to replace it with something what I can integrate in HA but it seems I will need to write my own component :slight_smile:

PR for the next version is in progress, feel free to try it :slight_smile:
https://github.com/home-assistant/home-assistant/pull/19233

1 Like

Hello
Maybe it’s a silly question, but I’m wondering where can I download the last version of the code for the thermostat

On the PR: https://raw.githubusercontent.com/home-assistant/home-assistant/fe3606bbb8fa94cc7f910b1071a110efbb1c2b86/homeassistant/components/climate/broadlink.py :wink:

1 Like

I’ve downloaded it, but before I break everything…
Can I use it still with 0.83.X or do I have to go to 0.84 before ?
I don’t use the schedules, so I understand I’m safe keeping the same config ?

thanks !