I have a relatively small apartment, so connectivity is no problem for me
Please, tell me how I cant get it to work.
Hassio, Pi, config with mac address but I get Unavailable.
what am I doing wrong. Please help.
witch version of raspberry pi are you using? Can you share your config? What distance do you have between the thermostat and your pi?
Hello, I wanted to connect the eQ-3 bluetooth thermostat (CC-RT-BLE-EQ) to the HA according to these instructions.
First, I installed “VMware Workstation 16 Player” on my laptop running “Windows 10”. Then on “VMware Workstation” I created a virtual machine (in the options for USB I checked “Share Bluetooth device with the virtual machine”, I installed “Debian GNU / Linux 10 (buster)” on it and installed “Home Assistant 0.115.6” on it in docker. Everything works fine.
In the next step I installed python3-pip, bluetooth, bluez, bluez-tools, rfkill on the “Debian” OS and “python-eq3bt” on docker HA.
By issuing the following commands:
bluetoothctl
agent on
scan on
I can see different bluetooth devices but I do not see the “EQ3” thermostat and I can’t pair it by issuing commands:
trust MAC_ADDRESS
pair MAC_ADDRRESS
connect MAC_ADDRES
receives the message:
Device 00: 1A: 22: 0A: 0E: A4 not available
but if I give the command:
hcitool -i hci0 info 00: 1A: 22: 0A: 0E: A4
it gets information from the thermostat.
Requesting information …
BD Address: 00: 1A: 22: 0A: 0E: A4
OUI Company: eQ-3 Entwicklung GmbH (00-1A-22 )
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Do you know how I can pair this thermostat and add the thermostat correctly to the HA?
Added to config:
climate:
- platform: eq3btsmart
devices:
living_room:
mac: 'XX:XX:XX:XX:XX:XX'
But the new entity is “unavailable”.
I have first found mac address via one of the android apps which allow to do so, and afterwards I have confirmed it by pairing thermostat with my phone via official app.
- Does HASS also need some kind of pairing procedure?
- Anything else which could cause trouble?
- probably my next step will be to check that the server bluetooth is even working
UPD: after a few days (and also update of HASS), it just worked. Cannot say for sure what was the reason it didn’t in the first place.
I had the same issue. In my case the distance of the thermostat was to far to my raspberry pi (HASS installed).
An alternative would be to use an ESP32 to control the valves over MQTT. We’re currently testing an implementation using Tasmota 9.2.0.2 (Not released yet).
This will possibly resolve connectivity issues as you can easily position multiple EP32 around the house and they will act as a bridge between the EQ3 and MQTT.
More info:
Or just ask…
2 Likes
Hi all,
i’m a newbee in Homeassistent an now I got the information from EQ3BTSmart.
How can I put these information in a sensor for displaying in lovelance?
hvac_modes:
- heat
- 'off'
- auto
min_temp: 5
max_temp: 29.5
preset_modes:
- boost
- away
current_temperature: 20.5
temperature: 20.5
preset_mode: null
away_end: null
is_locked: false
low_battery: false
valve: 0
window_open: false
friendly_name: Arbeitszimmer
supported_features: 17
Will be great if you cann support me
Hi
Follow @CichY link above to add your eq3 device to your configuration file. Where it says room1 you put the name arbeitszimmer. For mac you will need to find the code for your device. Getting that code will be the fun bit (search the forum on how to do that). People in the community will tend to ignore your request for very basic things and expect you to search for the answer yourself. When you’ve done that restart your device and then pick the lovelace card thermostat and pick climate.arbeitszimmer. The fun is finding out for yourself.
Good luck.
@Spiro in this way you cannot get the informations that @AgentP38 need. Using https://www.home-assistant.io/integrations/eq3btsmart/ you can only set the temperature but you cannot check any of parameters set on the thermostat like % of valve open, actual mode ect. I also looking for a way how to control it using only HA. Now I have an algoritm in Node Red which sends these info using MQQT to HA.
Ah @Piotr_Kowalski you are right. I thought AgentP38 was just looking to setup a thermostat for the eq3. So if you put this yaml below in your configuration.yaml you will get a new sensor.temperature with friendly name arbeitszimmer current temp as an example. Sorry for the misunderstanding AgentP38 . Tried it out on my eq3s and it worked.
sensor:
- platform: template
sensors:
temperature:
friendly_name: "Arbeitszimmer current temp"
unit_of_measurement: '°c'
value_template: "{{ state_attr('climate.arbeitszimmer', 'current_temperature') }}"
1 Like
Hi @Spiro @Piotr_Kowalski
Thanks a lot. I will try… sorry that I don’t communicate well in English…
BR Meik
for info:
On Tasmota, we’re working on an EQ3 driver - basically so you can have some ESP32 around the house to talk to the EQ3s, and send the info to HA.
We’re only just starting to think about how best to integrate with HA for information and control…
s
3 Likes
Hi @YJB/ @btsimonh I would be very interested in something like this (using ESP32 to talk with EQ3). I have been trying in the last months with different USB dongles but I haven’t found one with enough range. If you need a tester, just let me know.
I tried ESP32 and they had very poor range. I ended up using Raspberry PI zeroW with home assistant running on it and remote home assistant from HACS on my main Home assistant. Runs very well on RPIZeroW as it only runs 4 EQ3 on it.
Hi,
The current version is here:
EQ3-2021-04-08
Preliminary documentation (needs an update as things have developed, but should get you going:
EQ3 Documentation
It’s still not released, but its working pretty good.
You can alias your trv’s as well, so that you do not have to use the mac addresses:
BLEAlias 001A2228C457=room1
(hint use the new autoexec.bat in Tasmota to set them all at boot time)
MQTT topics:
There is one generic topic across all ESP32 for the EQ3 trv’s. This means you can have multiple ESP32 around the house without worrying which ESP32 is actually talking to your trv:
stat/EQ3/room1
In the same way you can define a regular group topic that includes all the ESP32 which are controlling your trv’s to send commands.
Anyways, give it a try and let us know how it’s going
I’m running 9 * EQ3 right now across 2 * ESP32
- 2 floors
- Total coverage (each floor) 2 * 18 m.
As my second floor is not made of concrete, I can cover both floors with a single ESP32 for 50% of the house. So you might need extra, but then the cost of an ESP32 is around USD4 (compared to USD 15-20 for the Raspberry PI zeroW).
Yeah, I have concrete floors. You also have the price of the SD card to add and I use an ethernet to USB connection. I find the WIFI on ESP32 great , just not the Bluetooth. It was ok if good line of site in a room on an opposite wall but poor if even 2m away on the same wall. Turning the ESP 90 degrees didn’t fit with the case. Response to changing target temp is faster on the RPI I found.
Hello everyone,
is it possible to show the schedule and adjust it via Home Assistant?
I set everything up and have the normal default UI integration, but I do not see any options to adjust the scheduling. 
I use scheduler-component and the scheduler card from HACS to control the programming of the EQ3s.
I’m using 2.0.5 of scheduler card as 2.1.1(perhaps it was 2.1.0) didn’t work. This doesn’t change the built in schedule in the device memory but works very well except when you lose connection to the bluetooth.