-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
How to use this as standalone? #34
Comments
Hello! The first thing that comes to mind is to use a device with ESPHome firmware, which also uses a passive method and has a native api for integration into HA. At the moment, it supports: LYWSDCGQ, LYWSD02, CGG1, HHCCJCY01. The second option is a custom component remote_homeassistant. I have not tried it, but the description is exactly what you need. Quote: |
But I’ll consider the idea of implementing our component as a separate executable or library. |
A standalone library would be great! |
+1 |
thanks for your efforts so far. |
Hi, It would be indeed nice to get a standalone version. I'll have a look to ESPHome, is it able to make it working? I mean, can we use ESPHome to get those sensor data to a custom app (and not Home Assistant)? Thanks |
On the basis of the errors I have seen with Multiple BT devices, It would be great if there was a 'wrapper' that enabled this component to be used as a standalone system on any Linux device. |
Guys, the topic is dead? |
No, it's not dead, but it isn't high on the priority list. Last months, I've moved the parser towards a separate folder, which allows it to be moved to an external pypi package in the future, if we want. But it still depends on BLE monitor configuration options, like |
Okay, great, thanks for your answer! Of course, having stand-alone mode, one could get more user experience. Since the dongle is not always convenient to use. For example, when your server is outside the coverage area of the required territory. |
I also wish a standalone version of this to feed my HA through MQTT or something similar. The reason I don't use ESPhome for this is the lousy BT signal of ESP32. Raspberry PI has so much better BT hardware. |
Perhaps consider a feature enhancement to specify and read data from an MQTT topic, e.g. messages with a “MAC” and “data” JSON fields, and parse the data as if it were scanned from the local hci. As a start, this would enable third-party scanner code to have an interface to which they can send encapsulated raw ble frames and know they’ll get parsed without having to replicate this integration’s intelligence. At some point, this integration could release official “satellite scanner” code that runs on other platforms (python, esp32, android, etc). Would this work? |
Ok guys, I've started to work on this. I'll keep track on the process in this post
The aim is that we create a pypi package that does the parsing, so it only will convert an advertisement to a dictionary with readable data. The data collecting should be done with other packages, like |
So, the first release is online (0.1.0). You can install it with @Magalex2x14 @Thrilleratplay, I will add you both to the repository as editors. I will wait a couple of weeks before switching with BLE monitor to use https://github.com/Ernst79/bleparser |
@Ernst79 thanks for the separate library! For what its worth, to anyone interested in a bare minimum ble2mqtt python script based on |
@freol35241 I've added your mqtt example to the bleparser repository in the examples folder. Thanks. I'm closing this issue, as it is resolved with |
First thing is first, so thank you for this project, it really improves the current status of the sensors in home assistant.
My question is more related on how to use as standalone or as a library to be integrated in something like this https://github.com/algirdasc/xiaomi-ble-mqtt
The use case is to be able to use a simple device such as rpi to gather the data and send it to home assistant via mqtt for those sensors that the home assistant bluetooth device cannot reach.
See algirdasc/xiaomi-ble-mqtt#17 for the 'reverse' issue.
Thanks!
The text was updated successfully, but these errors were encountered: