Epoch GC2 Detected, but unable to add

[oldjohngalt]

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.

I have an two Epoch GC batteries in my golf cart and a bluetooth BMS adapter. I have a BLE Proxy device located close to the golf cart and the integration detects the EpochGC2, but is unable to add it. The debug log is below.

Would a capture of the iOS traffic be helpful?

2025-05-26 23:07:24.143 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JTGER9NQNXK2580G9QBR667Q version=1 domain=bms_ble title=EpochGC2-0184
 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=30:55:44:38:C1:6C>
2025-05-26 23:07:24.144 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] initializing Ective Smart BMS, BT address: 30:55:44:38:C1:6C
2025-05-26 23:07:24.144 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for EpochGC2-0184 (30:55:44:38:C1:6C) as Ective Smart BMS
2025-05-26 23:07:24.144 DEBUG (MainThread) [custom_components.bms_ble] EpochGC2-0184: advertisement: {'name': 'EpochGC2-0184', 'address': '30:55:44:38:C1:6C', 'rssi': -83, 'manufacturer_data': {65535: b'0UD8\xc1l'}, 'service_data': {'00003333-0000-1000-8000-00805f9b34fb': b'456'}, 'service_uuids': ['0000ffe0-0000-1000-8000-00805f9b34fb'], 'source': 'A0:A3:B3:79:4E:76', 'advertisement': AdvertisementData(local_name='EpochGC2-0184', manufacturer_data={65535: b'0UD8\xc1l'}, service_data={'00003333-0000-1000-8000-00805f9b34fb': b'456'}, service_uuids=['0000ffe0-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-83), 'device': BLEDevice(30:55:44:38:C1:6C, EpochGC2-0184), 'connectable': True, 'time': 1927299.503065396, 'tx_power': None, 'raw': b'\x02\x01\x05\x03\x02\xe0\xff\t\xff\xff\xff0UD8\xc1l\x0e\tEpochGC2-0184\x06\x1633456'}
2025-05-26 23:07:24.144 DEBUG (MainThread) [custom_components.bms_ble] EpochGC2-0184: BMS data update
2025-05-26 23:07:24.144 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] connecting BMS
2025-05-26 23:07:24.144 DEBUG (MainThread) [bleak_retry_connector] 30:55:44:38:C1:6C - 30:55:44:38:C1:6C: Connection attempt: 1
2025-05-26 23:07:32.997 DEBUG (MainThread) [bleak_retry_connector] 30:55:44:38:C1:6C - 30:55:44:38:C1:6C: Failed to connect: Error ESP_GATT_CONN_TIMEOUT while connecting: Connection failed due to timeout, device_missing: False, backing off: 0.5 (attempt: 1, last rssi: None)
2025-05-26 23:07:33.499 DEBUG (MainThread) [bleak_retry_connector] 30:55:44:38:C1:6C - 30:55:44:38:C1:6C: Connection attempt: 2
2025-05-26 23:07:35.134 DEBUG (MainThread) [bleak_retry_connector] 30:55:44:38:C1:6C - 30:55:44:38:C1:6C: Connected after 2 attempts
2025-05-26 23:07:40.161 DEBUG (MainThread) [custom_components.bms_ble] EpochGC2-0184: BMS communication timed out, check signal strength (-83 dBm)
2025-05-26 23:07:40.161 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching EpochGC2-0184 data in 16.017 seconds (success: False)
2025-05-26 23:07:40.162 DEBUG (MainThread) [custom_components.bms_ble] Shutting down BMS (EpochGC2-0184)
2025-05-26 23:07:40.162 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] disconnecting BMS
2025-05-26 23:07:40.227 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] disconnected from BMS
2025-05-26 23:07:40.227 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] disconnected from BMS
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JTGER9NQNXK2580G9QBR667Q version=1 domain=bms_ble title=EpochGC2-0184
 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=30:55:44:38:C1:6C>
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] initializing Ective Smart BMS, BT address: 30:55:44:38:C1:6C
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for EpochGC2-0184 (30:55:44:38:C1:6C) as Ective Smart BMS
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble] EpochGC2-0184: advertisement: {'name': 'EpochGC2-0184', 'address': '30:55:44:38:C1:6C', 'rssi': -82, 'manufacturer_data': {65535: b'0UD8\xc1l'}, 'service_data': {'00003333-0000-1000-8000-00805f9b34fb': b'456'}, 'service_uuids': ['0000ffe0-0000-1000-8000-00805f9b34fb'], 'source': 'A0:A3:B3:79:4E:76', 'advertisement': AdvertisementData(local_name='EpochGC2-0184', manufacturer_data={65535: b'0UD8\xc1l'}, service_data={'00003333-0000-1000-8000-00805f9b34fb': b'456'}, service_uuids=['0000ffe0-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-82), 'device': BLEDevice(30:55:44:38:C1:6C, EpochGC2-0184), 'connectable': True, 'time': 1927320.576192446, 'tx_power': None, 'raw': b'\x02\x01\x05\x03\x02\xe0\xff\t\xff\xff\xff0UD8\xc1l\x0e\tEpochGC2-0184\x06\x1633456'}
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble] EpochGC2-0184: BMS data update
2025-05-26 23:07:45.275 DEBUG (MainThread) [custom_components.bms_ble.ective_bms::EpochGC2-0184:C16C)] connecting BMS
2025-05-26 23:07:45.275 DEBUG (MainThread) [bleak_retry_connector] 30:55:44:38:C1:6C - 30:55:44:38:C1:6C: Connection attempt: 1

Additional context

Here is a link to the Bluetooth module for the batteries.

[patman15]

Would a capture of the iOS traffic be helpful?

Definitely, but first before you take that effort, I would try to improve your RSSI value. It's pretty low and there are a number of errors that the connection failed. If that does not help, I need the traffic log to check the protocol.

[oldjohngalt]

I moved my BLE Proxy device significantly closer and was still receiving the same error.

I think I captured the traffic log correctly and have attached that to hopefully help. Thanks for taking a look. If I need to do anything else please let me know.

EPoch PacketLogger.zip

[patman15]

Unfortunately, this is again a new protocol that is not yet implemented. It seems that it is not too complicated but still some work. I'd like to finish 3 others first and would then come back if you are still interested?

[oldjohngalt]

That would be great. I completely understand about competing priorities and other devices.

I will be happy to help test anything when the time is right.

[patman15]

@oldjohngalt your device would be next on my list I could start implementing. Are you still interested and willing to do some testing and debug log generation? I unfortunately could not do a mock device on my side that the app accepts, so there will be a number of back and forth tests where I need debug logs. Let me know if this sounds ok for you and if you have the time for it.

[oldjohngalt]

@oldjohngalt your device would be next on my list I could start implementing. Are you still interested and willing to do some testing and debug log generation? I unfortunately could not do a mock device on my side that the app accepts, so there will be a number of back and forth tests where I need debug logs. Let me know if this sounds ok for you and if you have the time for it.

Absolutely. I would be happy to help. I am away for the next week. I can try anything remotely, but if I need to be onsite I won’t be able to until next weekend.

[patman15]

@oldjohngalt if you feel really adventures, you could try the linked branch using manual install. For the moment I found voltage, current, battery_level, temperature. For more, I think I would need another recording an screenshot from the app shortly after each other (so I can map the values). Maybe I find some other also without.

[oldjohngalt]

@patman15 Thanks! I removed/deleted the old instance of the integration and I think I installed it correctly manually.

However when I try to add the integration I get an error "No supported devices found via Bluetooth." Does this mean the integration can't find my Bluetooth Proxy devices or it can't detect the BMS of my golf cart battery?

I am traveling until Sunday, but if it is a range issue I can setup another proxy significantly closer early next week.

[patman15]

Regarding range, you can check the advertisement monitor and check the RSSI value. In addition, I had a small issue in the detection. Please update the code and try again.

[patman15]

@oldjohngalt I completed the development, if you could confirm it works, I can add it to the next release. Thanks!