You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2024. It is now read-only.
As in the past few months I understood the HCI capture format there is are no more obstacles to receive a bthome package and on the receiver node (ble or more likely beethowen/esp-now) create a BLE HCI package and proxy it directly to the blemonitor integration.
As it requires no additional component, just a service call the receiving node can be an ESP8266 as well.
Next step would be proxy it directly to the BLE stack of HA - yet I lack this knowledge yet and were not able to get info from the forums yet.
The text was updated successfully, but these errors were encountered:
I'm keen to see this happen at some point, and when I get some time to dedicate to this part of a project I have on the back burner, I hope I might be able to chip in a little.
I really like the approach you've taken, and I feel it's the "right" way to bring ESPNow to esphome/ha. Integrating the BTHome protocol is a perfect fit, imo - and being able to then inject the received BTHome packets as if they were BLE adverts is chef's kiss 👨🏼🍳 💋
I've got a number of Lenovo battery-powered PIR sensors that I want to reflash to make them a better product. They use the TuyaMCU (low-power variant) and an esp8266 to send motion events via wifi, via the cloud. It's no wonder they ran a fire sale on the things, between wifi and cloud they would provide a terrible user experience :-)
My plan is to:
Put esphome on the devices
have it talk TuyaMCU low-power mode to the mcu
send motion and battery events/data with BTHome over espnow using your beethowen-transmitter component
Deploy several esp8266 or esp32 espnow-proxy's running esphome
receive BTHome over espnow using your beethowen-receiver component
forward those BTHome packets as pseudo-ble adverts to HA using the bluetooth_proxy api.
I have esphome running on the device, but the tuya mcu component doesn't talk the low-power variant of the protocol (yet), so that's where my available time will go for now - although I've other projects that are getting priority currently.
Anyway, I know all this is rather off-topic for this feature request, but I wanted to ping you and let you know about at least one potential use-case, and some moral support :-) Hopefully it will inspire some more collaborators to jump in, if nothing else :-) If I get further along with the other parts of the project I'll see if I can help out with this part of things, too.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As in the past few months I understood the HCI capture format there is are no more obstacles to receive a bthome package and on the receiver node (ble or more likely beethowen/esp-now) create a BLE HCI package and proxy it directly to the blemonitor integration.
As it requires no additional component, just a service call the receiving node can be an ESP8266 as well.
Next step would be proxy it directly to the BLE stack of HA - yet I lack this knowledge yet and were not able to get info from the forums yet.
The text was updated successfully, but these errors were encountered: