-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide asyncio interface for homeassistant #59
Comments
I just read https://developers.home-assistant.io/docs/network_discovery/ but it is not 100% clear to me what is needed here. |
@rytilahti Friendly ping! |
Hi @TechHummel, sorry for the delay and thanks for the remainder! Yeah, my understanding is also that the way to handle this would be by passing the I created previously home-assistant/core#74864 to modernize the code base, but I'm currently occupied with other things so I have no time to look into that until very late autumn or so... |
I am looking into this, but I am currently blocked hbldh/bleak#946. Will let you know about any progress. |
Hi! I am hitting the same issue here.... I will start checking out this. Any progress on this? |
Sadly not! Not sure what's causing the issue! |
do you have your implementation working on the latest homeassistant? it seems that they want that you don't use the BleakClient() directly, instead the BLEDevice(). I am quite new with the Bleak library too. It seems that doings so, home assistant can handle multiple BLE python interfaces (what makes sense). I can use your package as an standalone application (without Home assistant), but once that I integrate it I can't use the functionality, and now I am trying to learn how to debug it :) |
No, I don't have a working implementation! I am considering just using a MQTT bridge though! |
mm, could me maybe a easier solution for the moment, but is quite unfortunate that after a home assistant update the things stopped working (my wife is quite piss off :P) |
It's super easy to downgrade HA via the SSH Plugin, worked great for me at least. Tho it's of course only a temporary fix. Make a full backup and download it, before sending this command to your HA.
Hope that helps to make your wife a bit happier again. ;-) cheers, |
I don't have a wife, but thank you very much. I'm happy now. Outside is cold and I need my thermostats working. |
I made the downgrade but then other things stop work as I wanted (specially the new zigbee stuff). I will check more in detail all this but time is limited... (wife again) xD |
I am using Home Assistant now on a downgraded version (2022.6.7) and everything works as it should. However, with every every release I feel the dire consequence of not being able to access the new features and also a bad feeling creeping in due to staying on an outdated version. Our whole apartment works fine with these thermostats and they consume almost no batteries, we recharge once every 18 months. I am more than happy and would love to support any kind of kickstarter request if any of the previous developers would be happy to assigns some valuable time to it. |
This is no solution, but as a temporary fix, I switched to an bt-mqtt bridge, to work with home-assistant. https://github.com/zewelor/bt-mqtt-gateway |
Is there a way to run this on Hassio OS or did you use a separate Pi / PC for hosting this? |
I have the same issue and the same question. |
It is hosted separately. For me it was just another VM, because my HA is also virtualized. It is a bit of a downside, but even if the HA integration is fixed, I will stay at the mqtt bridge. It is much faster, and pops out more usable data, like valve state. Edit: seems like there is a HA addon version: https://github.com/FaserF/hassio-addons/tree/master/bt-mqtt-gateway |
What I really liked about the solution via an integration was that it does not create more dependencies in form of further VM's and addons. It came out of the box and worked. 🥇 |
Btw, I was able to get the valve state from the original integration. Can look it up later if you are interested |
Hello guys! It there any good changes in 2022.9.7? My HACS integration is dead now "You need HA version 2022.8.0 or newer to use this integration". And I understand further will come more and more problems with obsolete HA Core. It's annoying. |
Just realised that one can actually support developers directly via github! |
Hi all, Meanwhile the issue is not resolved I found a temporal solution with a bluetooth to mqtt gateway. I hope it can help someone. I had mqtt configured previously. But if you don't have mqtt configured you should install the Mosquitto add-on previously. Then do the following:
Thanks to @FaserF for the add-on development and to @zewelor for the bluetooth mqtt gateway development. |
I've been using the MQTT gateway and it works great. However, since HomeAssistant introduced Bluetooth Proxies, I would love to have EQ3 over BT Proxy. May want to try to debug myself. |
Here you can find the HACS custom component. https://github.com/dbuezas/eq3btsmart I added some extra stuff like:
My Apologies to @rytilahti for going this way instead of making a PR, I left my reasons in the readme (mostly that the changes I made were too many, and they break the CLI and other backends) |
Hi @dbuezas , Thank you!! I have got 3 of these valves and it's working for two of them but it's not connecting to one of the devices and the following errors are showing:
I know the device is not the cause because it works ok with the bt-mqtt-gateway. |
@r-jordan please raise an issue in the repo to avoid polluting this issue further :) |
Just as a conclusion, the integration works very well, there are a few improvement areas but dbuezas is handling them like a pro !! |
No worries, I have been maintaining this lib just in case someone is using it as I don't. I'm just glad that there's now a working solution for people who are using these devices in their homes! :-) In case you want to make a push to make it into the homeassistant releases, it probably makes sense to create an async fork that removes all the cruft (we did similar for the tplink integration, pyhs100 -> python-kasa) and adjust the integration accordingly. I'm happy to help with the process if needed. edit: just for the ref, although I'm not sure how useful it is, I did some ground work to modernize the integration at home-assistant/core#74864 |
I have strange behavior one of my two thermostats. One of them is paired and working without problems with @dbuezas add-on, but another won't be paired via console. There is no message to input pair PIN. And this one working without problems. Does anybody can help me to solve this problem? |
For me usually worked some restarts:
I'm on a linux server now with a BT Dongle - way more stable, though it's using the same stack (BlueZ based). Also as a quick hint, if it's just not asking for the Pin, try long-pressing the wheel to trigger the pairing mechanism in the Thermostat - maybe due to battery savings it doesn't trigger the pin when RPi asks for it. |
Thanks for fast reply. |
Sorry to hear that, I was expecting you to have tried all the normal stuff...
|
Keep trying to pair, it can take a long time in my experience. What also seemed to help sometimes was toggling the BLE setting in the long press menu settings a couple of times. |
@jhass, @andrei-micu-ro P.S. Just for information. I have bought 2 these used thermostats about 2 years ago for 15€. Now in Germany price is starting from 60€ for one unit. It's insane. |
I bought 7 for 20€ each last year, so I'll pass the thanks to @rytilahti for this repo :) |
that is somehow funny, I never needed to pair anything with codes with the old integration even if I needed the pin on the app. To me the pin requirement appeared rather like a superficial layer of "security" that was not really deep rooted. |
that looks absolutely awesome. are you planning to get it into home assistant's normal releases? that would be great and due to your much improved autodiscovery it will certainly be of more use for less experiences users. |
Thanks! |
That would be really appreciated and also me the easiest option for many other users. Do you have a rough idea when the ESPHome pairing issue might be solved? |
Thank you @dbuezas for providing us with a workaround/solution, and thank you @andrei-micu-ro for the tip with removing the thermostat before pairing it! I have got now all 4 of my thermostats working: One minor issue, however: When I change the temperature through Siri voice command (via HomeKit Bridge), the thermostat switches from OFF to Auto Mode and not to Manual Mode. Is this something you can fix, @dbuezas? |
Yey! |
The custom EQ3 integration https://github.com/dbuezas/eq3btsmart is now a proper device with the entities you missed, and then some more. |
Wow, that looks awesome! Thanks for the great work. Do you know when it will be available via home assistant's own integrations section? |
It may take a while, but eventually I'll do it. I want to add all features and polish it well before I attempt to publish the library and open a PR to the core repo of home assistant. |
@dbuezas David, thank you so much for putting in all the effort to keep this piece of hardware supported by Home Assistant! It is very much appreciated! <3 |
Looks awesome! @dbuezas any news on the proxies? |
Unfortunately no news on the BTProxy. |
It likely doesn't make sense to convert the whole library to use asyncio, but providing a separate homeassistant-friendly interface could be fairly straightforward to implement.
See home-assistant/developers.home-assistant#1412 and home-assistant/developers.home-assistant#1412 (comment) for best practices.
The text was updated successfully, but these errors were encountered: