No worries, we’ve all been there every now and then.
Haven’t updated to 2022.7 but the prospect of losing my EQ3’s has nudged me in the direction of trying the EQ3 on ESP32.
Previously had poor result with ESP32 before ( about 3 feet range) but this time I used an ESP32 nodemcu devkitc U with an a pigtail to a sma connection. Used an old 2.4Ghz antenna from a router I bricked.
Have to say so far I am impressed. Have already removed one of my RPI zeros that I was using to connect to distant EQ3 ( these would not be affected by the update to 2022.7 as they stopped being supported last year)
I ask myself, will it never be possible again?
Yes, of course someone will fix it. I think it might stimulate more interest if more people on analytics selected to show their integrations. Only 36 active integrations. Come on there must be more HA users with EQ3! There are several alternative ways of making it work if HA itself doesn’t fix it.
2 Likes
Yes I will not update to 2022.7 because of the eq3 itegration not working.
1 Like
teprrrTeemu RGreat contributor
FurMachinery
Moi, the fix for eq3btsmart is already in the 2022.8 beta, so if you have a chance please try it out to see if it works for you now 
Yes i have test it now with update to 2022.8.2 but just 1 of 3 works the other 2 aren‘t available.
Is anyone of you is still using zewelor/bt-mqtt-gateway for EQ3 thermostats? I was using it until HA 07.2022. Was working very stable. Now since update to HA 08.2022 is not working anymore. I’m getting always:
raspberrypi service.sh[6000]: 07:34:44 Error during update of thermostat device 'wohnzimmer_terrasse' (00:1A:22:xx:xx:xx): BTLEDisconnect
Can it be is related to the new bluetooth integration provided in HA 08.2022? I downgraded already for test to HA 07.2022. The devices are working again … Anyone made similar experience?
Seems thats the cause. I disabled in HA now bluetooth integration. Now the zewelor/bt-mqtt-gateway is working again. Probably noth accessing the same BT adapter and creating a conflict …
Can you use capital letters in device name. Should it be bad not Bad?
But the „Bad“ thermostat is working
Perhaps it just reading the first mac. Try it and see renaming them all in lower case. Process of elimination.
Ok i will test it later
Same result. I delete now the lines in the configuration.yaml and look in the dev tools and see that the climate entitys are verry confused, its named room1 and room2 and bad. But i cant find a way to „reconfigure“ the climate entitys.
Can you delete the 3 entities and restart HA.
How delete? You mean in the configuration.yaml?
In settings → Devices & Services–>Entities.
No the delete button is grey. Weird is the name is still climate.bad but i rename it all in the configuration.yaml in room 1,2and 3
can you add a e.g. unique_id: Bad then you should be able to delete. As you say they may have gotten confused.
climate:
- platform: eq3btsmart
devices:
bad:
unique_id: Bad
mac: '00:1A:22:11:F4:AB'
Then restart HA and try to delete all 3 and then restart again.