Skip to content

Renogy RBT100LFP12-BT #247

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

Closed
4 tasks done
gavrilov opened this issue Apr 3, 2025 · 19 comments · Fixed by #270 or #330
Closed
4 tasks done

Renogy RBT100LFP12-BT #247

gavrilov opened this issue Apr 3, 2025 · 19 comments · Fixed by #270 or #330
Assignees
Labels
more info needed new device Requires a new protocol implementation

Comments

@gavrilov
Copy link

gavrilov commented Apr 3, 2025

Checklist

  • I have filled out the template to the best of my ability.
  • I have understood that this integration is only about battery management systems with Bluetooth Low Energy support.
  • This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
  • This issue is not a duplicate of any previous feature requests.

Please describe the enhancement you would like to have.

Renogy RBT100LFP12-BT

12V 100Ah Lithium Iron Phosphate Battery w/ Bluetooth
link

It would be wonderful if you can add a battery

{
    "name": "BT-TH-66EDFC11",
    "address": "60:98:66:ED:FC:11",
    "rssi": -65,
    "manufacturer_data": {
        "39008": "66edfc11"
    },
    "service_data": {},
    "service_uuids": [
        "0000ffd0-0000-1000-8000-00805f9b34fb"
    ],
    "source": "04:EA:56:EB:B9:54",
    "connectable": true,
    "time": 1743646480.9179232,
    "tx_power": 0
}

Additional context

No response

@gavrilov gavrilov added the enhancement New feature or request label Apr 3, 2025
@patman15
Copy link
Owner

patman15 commented Apr 3, 2025

Hey! I do not know which BMS they are using so

For new BMS types, please provide the output of bluetoothctl info <MAC> and the service explorer script. Please see if you are able to capture the Bluetooth traffic on Android or iOS while using the vendor app with the battery."

Thanks!

@gavrilov
Copy link
Author

gavrilov commented Apr 3, 2025

bluetoothctl info 60:98:66:ED:FC:11

Device 60:98:66:ED:FC:11 (public)
	Name: BT-TH-66EDFC11    
	Alias: BT-TH-66EDFC11    
	Paired: no
	Bonded: no
	Trusted: no
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Unknown                   (0000ffd0-0000-1000-8000-00805f9b34fb)
	ManufacturerData Key: 0x9860 (39008)
	ManufacturerData Value:
  66 ed fc 11                                      f...            
	RSSI: 0xffffffbc (-68)
	TxPower: 0x0000 (0)
	AdvertisingFlags:
  06                                               .               

service explorer

2025-04-03 16:19:01,259 __main__ INFO: starting scan...
2025-04-03 16:19:01,366 __main__ INFO: connecting to device...
2025-04-03 16:19:04,261 __main__ INFO: connected
2025-04-03 16:19:04,261 __main__ INFO: [Service] 0000ffd0-0000-1000-8000-00805f9b34fb (Handle: 27): Vendor specific
2025-04-03 16:19:04,584 __main__ INFO:   [Characteristic] 0000ffd4-0000-1000-8000-00805f9b34fb (Handle: 38): Vendor specific (read), Value: bytearray(b'')
2025-04-03 16:19:04,981 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 40): Characteristic User Description, Value: bytearray(b'REG_READ')
2025-04-03 16:19:05,380 __main__ INFO:   [Characteristic] 0000ffd2-0000-1000-8000-00805f9b34fb (Handle: 31): Vendor specific (read,notify), Value: bytearray(b'')
2025-04-03 16:19:05,776 __main__ INFO:     [Descriptor] 00002902-0000-1000-8000-00805f9b34fb (Handle: 33): Client Characteristic Configuration, Value: bytearray(b'\x00\x00')
2025-04-03 16:19:06,173 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 34): Characteristic User Description, Value: bytearray(b'nc')
2025-04-03 16:19:06,572 __main__ INFO:   [Characteristic] 0000ffd5-0000-1000-8000-00805f9b34fb (Handle: 41): Vendor specific (read,write), Value: bytearray(b'')
2025-04-03 16:19:06,969 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 43): Characteristic User Description, Value: bytearray(b'REG')
2025-04-03 16:19:07,367 __main__ INFO:   [Characteristic] 0000ffd1-0000-1000-8000-00805f9b34fb (Handle: 28): Vendor specific (read,write-without-response,write), Value: bytearray(b''), Max write w/o rsp size: 20
2025-04-03 16:19:07,764 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 30): Characteristic User Description, Value: bytearray(b'RX')
2025-04-03 16:19:07,764 __main__ INFO:   [Characteristic] 0000ffd3-0000-1000-8000-00805f9b34fb (Handle: 35): Vendor specific (write)
2025-04-03 16:19:08,162 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 37): Characteristic User Description, Value: bytearray(b'REG_WRITE')
2025-04-03 16:19:08,162 __main__ INFO: [Service] f000ffd0-0451-4000-b000-000000000000 (Handle: 49): Unknown
2025-04-03 16:19:08,162 __main__ INFO:   [Characteristic] f000ffd1-0451-4000-b000-000000000000 (Handle: 50): Unknown (write-without-response,write), Max write w/o rsp size: 20
2025-04-03 16:19:08,560 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 52): Characteristic User Description, Value: bytearray(b'Reset')
2025-04-03 16:19:08,560 __main__ INFO: [Service] 0000180a-0000-1000-8000-00805f9b34fb (Handle: 8): Device Information
2025-04-03 16:19:08,957 __main__ INFO:   [Characteristic] 00002a24-0000-1000-8000-00805f9b34fb (Handle: 11): Model Number String (read), Value: bytearray(b'TC,R2#4,1,248,S')
2025-04-03 16:19:09,354 __main__ INFO:   [Characteristic] 00002a26-0000-1000-8000-00805f9b34fb (Handle: 15): Firmware Revision String (read), Value: bytearray(b'V1.1')
2025-04-03 16:19:09,752 __main__ INFO:   [Characteristic] 00002a25-0000-1000-8000-00805f9b34fb (Handle: 13): Serial Number String (read), Value: bytearray(b'2019-11-5')
2025-04-03 16:19:10,348 __main__ INFO:   [Characteristic] 00002a29-0000-1000-8000-00805f9b34fb (Handle: 21): Manufacturer Name String (read), Value: bytearray(b'www.tuner168.com')
2025-04-03 16:19:10,746 __main__ INFO:   [Characteristic] 00002a2a-0000-1000-8000-00805f9b34fb (Handle: 23): IEEE 11073-20601 Regulatory Cert. Data List (read), Value: bytearray(b'\xfe\x00experimental')
2025-04-03 16:19:11,143 __main__ INFO:   [Characteristic] 00002a50-0000-1000-8000-00805f9b34fb (Handle: 25): PnP ID (read), Value: bytearray(b'\x01\r\x00\x00\x00\x10\x01')
2025-04-03 16:19:11,540 __main__ INFO:   [Characteristic] 00002a28-0000-1000-8000-00805f9b34fb (Handle: 19): Software Revision String (read), Value: bytearray(b'V1.1')
2025-04-03 16:19:11,938 __main__ INFO:   [Characteristic] 00002a27-0000-1000-8000-00805f9b34fb (Handle: 17): Hardware Revision String (read), Value: bytearray(b'609866EDFC11')
2025-04-03 16:19:12,335 __main__ INFO:   [Characteristic] 00002a23-0000-1000-8000-00805f9b34fb (Handle: 9): System ID (read,write-without-response,write), Value: bytearray(b'\x00\x00\x00\x00\x00\x00\x00\x00'), Max write w/o rsp size: 20
2025-04-03 16:19:12,335 __main__ INFO: [Service] 0000fff0-0000-1000-8000-00805f9b34fb (Handle: 44): Vendor specific
2025-04-03 16:19:12,733 __main__ INFO:   [Characteristic] 0000fff1-0000-1000-8000-00805f9b34fb (Handle: 45): Vendor specific (read,notify), Error: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0a (Attribute Not Found)
2025-04-03 16:19:13,130 __main__ INFO:     [Descriptor] 00002901-0000-1000-8000-00805f9b34fb (Handle: 48): Characteristic User Description, Value: bytearray(b'TX')
2025-04-03 16:19:13,528 __main__ INFO:     [Descriptor] 00002902-0000-1000-8000-00805f9b34fb (Handle: 47): Client Characteristic Configuration, Value: bytearray(b'\x00\x00')
2025-04-03 16:19:13,528 __main__ INFO: disconnecting...
2025-04-03 16:19:16,110 __main__ INFO: disconnected

If needed, I'll try to capture Bluetooth traffic on Android next week. Thank you so much!

@patman15
Copy link
Owner

patman15 commented Apr 4, 2025

Looks good, but I can't guess the BMS from that information yet, so I would really need the Bluetooth traffic to proceed.

@gavrilov
Copy link
Author

gavrilov commented Apr 10, 2025

Battery device is TexasInstrum_ed:fc:11 (BT-TH-66EDFC11)
EDIT: deleted log due to private data contained

@patman15 patman15 self-assigned this Apr 11, 2025
@patman15
Copy link
Owner

@gavrilov thanks, perfect input, I will have a look as soon as I have covered the other requests. I will keep you posted.

@patman15
Copy link
Owner

@gavrilov are you using this app https://play.google.com/store/apps/details?id=com.renogy.dchome ? Or which is the correct one for Android? I would soon start the development ...

@gavrilov
Copy link
Author

Yes, I use this app

@patman15
Copy link
Owner

@gavrilov the app needs registration. 😞 I pushed a first version that shows the BMS responses. Could you please install the linked branch via manual install, enable debug logging, and then send me the log including some timely related screenshots from the app with all the values you can see there, so I can compare?

@gavrilov
Copy link
Author

@patman15
Copy link
Owner

Hi @gavrilov, that was very helpfull. Can you update and see if it works?
Open items:

  • I could not find a cycle counter? Does the app show something, somewhere?
  • I could not test current, as it is 0. Maybe you can check that the value is correct, positive, negative, value.
  • I do not know where the errors are, so those are not mapped. Are you able to trigger some and do a log?

@patman15 patman15 linked a pull request Apr 19, 2025 that will close this issue
@gavrilov
Copy link
Author

gavrilov commented Apr 21, 2025

I see the battery in bluetooth advertisement monitor, but not in homeassistant. BLE Battery Management: "No supported devices found via Bluetooth." I use last commit of 247-renogy-rbt100lfp12-bt branch

{"name":"BT-TH-66EDFC11 ","address":"60:98:66:ED:FC:11","rssi":-69,"manufacturer_data":{"39008":"66edfc11"},"service_data":{},"service_uuids":["0000ffd0-0000-1000-8000-00805f9b34fb"],"source":"04:EA:56:EB:B9:54","connectable":true,"time":1745274734.457435,"tx_power":null}

@patman15
Copy link
Owner

I checked it again, it should work, my tests run against your advertisement and do pass.
Did you replace all files? In this case especially manifest.json? Did you reboot HA?

@patman15
Copy link
Owner

@gavrilov any news on that topic? I'd like to include the code in the next release, but only if you can confirm it works ... Thanks!

@patman15 patman15 assigned gavrilov and unassigned patman15 May 5, 2025
@patman15 patman15 added new device Requires a new protocol implementation and removed enhancement New feature or request labels May 16, 2025
@gavrilov
Copy link
Author

I'm very sorry, I couldn't answer earlier

Everything works fine, except for the current indicator - it is 10 times greater. Here I connected a 4.57A load (measured with multimeter)

Image

error_log.log

@patman15 patman15 reopened this May 23, 2025
@patman15 patman15 linked a pull request May 23, 2025 that will close this issue
@patman15
Copy link
Owner

@gavrilov can you check this branch? Unfortunately, I had no test data as you current is always 0. Even the new log shows no current ...

@gavrilov
Copy link
Author

I checked 247-fix-renogy-current - the same thing, the current is 10 times higher than it should be.

Image

@patman15
Copy link
Owner

I checked 247-fix-renogy-current - the same thing, the current is 10 times higher than it should be.

Did you restart HA after changing the files? Can you send me a debug log?
I did change it, so I'm a bit puzzled:

Image

@gavrilov
Copy link
Author

Most likely I made a mistake - I updated the files again and now everything looks fine.

Image

home-assistant_bms_ble_2025-05-28T20-00-43.105Z.log

@patman15
Copy link
Owner

No worries, thanks for the feedback, I will include it into the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more info needed new device Requires a new protocol implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants