-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add support Redodo battery BMS #78
Comments
Hi! The information you already provided is helpful! Next, details about the used protocol, e.g. specification, would be needed. If you do not have that and can't find it, a BT debug trace from an Android/iOS app communicating with the BMS and the link to the app itself are necessary. |
Hello, here is the link to the program: https://play.google.com/store/apps/details?id=com.redodopower.ble |
Hmm, hope for bad weather in my area, so I'm bored. 😆 |
@azisto is it really the case that I need to register with Redodo in order to use the app?! 😞 |
@patman15 Yes, you need to create an account to use the app. I couldn't find any information about the Bluetooth protocol. |
Maybe I could write to the manufacturer, but I don't know how to write a proper request (what exactly do I need from them and why) |
Well the ask would be a specification of the protocol between the battery and the app via Bluetooth, especially the frame format being used. |
@azisto ok, I had a look into the data that you provided and could come up with a first version that should work partially. Can you check the version from the linked branch in this ticket? Please follow the steps for manual installation in the README. What I could not identify (but I think must be there) is SoC, remaining capacity, cycles, temperature. In you message you linked a btsnoop_hci.log that was extremely helpful to progress. Could you do this again, but also note down the time and the values from the app? Basically I would need the log and something like If you could provide that as a .zip attached (especially if you have a number of screenshots) that would be great, I think we can solve that together! |
@patman15 Here you go. Now I will try the first version and give you my feedback soon. |
@azisto wow, that was a super set of information! I think I found the missing values, pushed a new commit, you can run a test. Let me know if the values are plausible. Be aware that you most likely cannot connect HA and the app in parallel, but you can simply disable it in HA and then have a look at the app. |
@patman15, I just tried to add the previous version from this test branch to HA manually (according to your readme instructions). This is the problem I'm having. I must be doing something wrong. |
Update: I've uploaded the latest version. Everything is working now (commit 2e47676).
|
Except for one useless debug message, it looks good to me. Let me know if you are happy or spot some strange or implausible values. I'll release it with 1.9.0 with you confirm it's good. |
I am very happy, thank you very much! According to my observations, all indicators are correct. The only thing that doesn't work is the runtime, maybe it should be the remaining time? |
Good catch! I actually mixed up cycle charge (Ah) and cycle capacity (Wh). It showed the number of the first as the second which also lead to missing runtime value. Fixed in newest commit. Thanks! |
Checklist
Is your feature request related to a problem? Please describe.
Hi, is it possible to add Redodo Smart BMS support to your integration ?
Describe the solution you'd like
What information should I provide to do this?
Additional context
I try add to manifest.json
{ "local_name": "R-24*" },
and
In Debug:
DEBUG (MainThread) [custom_components.bms_ble] Bluetooth device detected: <BluetoothServiceInfoBleak name=R-24100BNN160-A00643 address=C8:47:80:15:D8:34 rssi=-88 manufacturer_data={22618: b'\xc8G\x80\x15\xd84'} service_data={} service_uuids=['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '0000180a-0000-1000-8000-00805f9b34fb', '0000180f-0000-1000-8000-00805f9b34fb', '0000ffe0-0000-1000-8000-00805f9b34fb', 'f000ffc0-0451-4000-b000-000000000000'] source=BC:2B:02:10:E2:B4 connectable=True time=19205.862500036 tx_power=None>
The text was updated successfully, but these errors were encountered: