WARNING:root:on_data_received: unknown operation=131 #88
-
Hello hello, After having been turned on to this as a possibility to pull data from my renogy rego charge/inverter (built in BT not from a BT-1 or BT-2 RJ module), I was able to connect to the rego's BT but I am now at a loss: WARNING:root:on_data_received: unknown operation=131 Running off of a op5+/ubuntu 24.10.
this doesn't happen every time, but it locks the script when it does. Thanks a million ahead of time. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 21 replies
-
If you can add |
Beta Was this translation helpful? Give feedback.
-
*Here ya go, *
[image: l63.png]
[image: logafterl63.png]
*-TXT-*
INFO:root:Init InverterClient: BTRIC134000035 => D8:B6:73:BF:4F:75
INFO:root:Adapter status - Powered: True
INFO:root:Starting discovery...
INFO:root:Devices found: 10
INFO:root:Found matching device BTRIC134000035 => [d8:b6:73:bf:4f:75]
INFO:root:[D8:B6:73:BF:4F:75] Resolved services
INFO:root:subscribed to notification 0000fff1-0000-1000-8000-00805f9b34fb
INFO:root:found write characteristic 0000ffd1-0000-1000-8000-00805f9b34fb
INFO:root:resolved services
DEBUG:root:create_request_payload 4000 => [255, 3, 15, 160, 0, 8, 82, 228]
INFO:root:characteristic_enable_notifications_succeeded
INFO:root:characteristic_write_value_succeeded
ff031004cf034104cf01971773008800e600006a9e
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_stats ff031004cf034104cf01971773008800e600006a9e
DEBUG:root:create_request_payload 4311 => [255, 3, 16, 215, 0, 8, 229, 42]
INFO:root:characteristic_write_value_succeeded
ff0310524956313233305243482d53505300009ff7
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_model ff0310524956313233305243482d53505300009ff7
DEBUG:root:create_request_payload 4329 => [255, 3, 16, 233, 0, 5, 69, 35]
INFO:root:characteristic_write_value_succeeded
ff030a000000000000000101f6a2df
INFO:root:on_data_received: response for read operation
INFO:root:parse_solar_charging ff030a000000000000000101f6a2df
DEBUG:root:create_request_payload 4410 => [255, 3, 17, 58, 0, 2, 244, 228]
INFO:root:characteristic_write_value_succeeded
ff030401fa0000c431
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_load ff030401fa0000c431
DEBUG:root:create_request_payload 57348 => [255, 3, 224, 4, 0, 1, 231, 213]
INFO:root:characteristic_write_value_succeeded
ff8302a101
WARNING:root:on_data_received: unknown operation=131
*Hope this helps and let me know how else I can be of assistance. *
*G*
…On Mon, Nov 18, 2024 at 8:46 PM Cyril Sebastian ***@***.***> wrote:
If you can add print(response.hex()) into BaseClient.py#L63 and share the
logs here that will help me figure out the issue.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2TQHU4YU4OK6KYJQ54RNWT2BKYCJAVCNFSM6AAAAABR6YS7GOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRZHE4TKMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Garrett Hazlett
|
Beta Was this translation helpful? Give feedback.
-
Can you try https://github.com/cyrils/renogy-bt/tree/inverter-battery ? |
Beta Was this translation helpful? Give feedback.
-
I did a quick file comparison and dropped the modified as of yesterday into
the pi. Ran with existing config comes up with this:
INFO:root:Init InverterClient: BTRIC134000035 => D8:B6:73:BF:4F:75
INFO:root:Adapter status - Powered: True
INFO:root:Starting discovery...
INFO:root:Devices found: 12
INFO:root:Found matching device BTRIC134000035 => [d8:b6:73:bf:4f:75]
ERROR:root:Connection failed: le-connection-abort-by-local
ERROR:root:on_error: le-connection-abort-by-local
Now this is on a pi zero w (not 2w) i'd like to use for this, but i fear
it's bt 4.1 controller might be an issue. i'm going to switch back to the
pi4 fresh when i get a moment and i'll report back to you this evening...
…On Wed, Nov 20, 2024 at 10:47 AM Cyril Sebastian ***@***.***> wrote:
Can you try https://github.com/cyrils/renogy-bt/tree/inverter-battery ?
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2TQHU4L67F6YZPG66EUEL32BTDMBAVCNFSM6AAAAABR6YS7GOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZSGY3DQNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Garrett Hazlett
|
Beta Was this translation helpful? Give feedback.
-
Yep, that was on me.
*Working a treat:*
INFO:root:Init InverterClient: BTRIC134000035 => D8:B6:73:BF:4F:75
INFO:root:Adapter status - Powered: True
INFO:root:Starting discovery...
INFO:root:Devices found: 9
INFO:root:Found matching device BTRIC134000035 => [d8:b6:73:bf:4f:75]
INFO:root:[D8:B6:73:BF:4F:75] Connected
INFO:root:[D8:B6:73:BF:4F:75] Resolved services
INFO:root:subscribed to notification 0000fff1-0000-1000-8000-00805f9b34fb
INFO:root:found write characteristic 0000ffd1-0000-1000-8000-00805f9b34fb
INFO:root:resolved services
DEBUG:root:create_request_payload 4000 => [255, 3, 15, 160, 0, 8, 82, 228]
INFO:root:characteristic_enable_notifications_succeeded
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_stats ff03100000000004b002231770008300e000000356
DEBUG:root:create_request_payload 4311 => [255, 3, 16, 215, 0, 8, 229, 42]
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_model ff0310524956313233305243482d53505300009ff7
DEBUG:root:create_request_payload 4329 => [255, 3, 16, 233, 0, 5, 69, 35]
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
INFO:root:parse_solar_charging ff030a0000000000000000000072c9
DEBUG:root:create_request_payload 4410 => [255, 3, 17, 58, 0, 2, 244, 228]
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
INFO:root:parse_inverter_load ff030402900000e469
DEBUG:root:create_request_payload 57348 => [255, 3, 224, 4, 0, 1, 231, 213]
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
DEBUG:root:create_request_payload 256 => [255, 3, 1, 0, 0, 8, 80, 46]
INFO:root:characteristic_write_value_succeeded
INFO:root:on_data_received: response for read operation
INFO:root:on_read_operation_complete
DEBUG:root:BTRIC134000035 => {'function': 'READ', 'uei_voltage': 0.0,
'uei_current': 0.0, 'voltage': 120.0, 'load_current': 547, 'frequency':
60.0, 'temperature': 13.1, 'model': 'RIV1230RCH-S', 'solar_voltage': 0.0,
'solar_current': 0.0, 'solar_power': 0, 'solar_charging_state':
'deactivated', 'solar_charging_power': 0, 'load_power': 656,
'charging_current': 0.0, '__device': 'BTRIC134000035', '__client':
'InverterClient'}
INFO:root:mqtt logging
DEBUG:paho.mqtt.client:Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60)
client_id=b'renogy-bt'
DEBUG:paho.mqtt.client:Received CONNACK (0, 0)
DEBUG:paho.mqtt.client:Sending PUBLISH (d0, q0, r0, m1), 'b'barnbatt'', ...
(396 bytes)
DEBUG:paho.mqtt.client:Sending DISCONNECT
INFO:root:Exit: Disconnecting device: BTRIC134000035 [D8:B6:73:BF:4F:75]
*Confirmed working on: Orange pi 5+ running ubu24.10 w' realtek 5.3 dongle,
rpi4 and the logs above were pulled from a rpi zero w. Pending package
installation fun with python it's solid. I do suggest pipx where possible. *
*You are awesome to have worked with me on this, thanks again,*
*G*
…On Thu, Nov 21, 2024 at 1:57 PM Garrett Hazlett ***@***.***> wrote:
I did a quick file comparison and dropped the modified as of yesterday
into the pi. Ran with existing config comes up with this:
INFO:root:Init InverterClient: BTRIC134000035 => D8:B6:73:BF:4F:75
INFO:root:Adapter status - Powered: True
INFO:root:Starting discovery...
INFO:root:Devices found: 12
INFO:root:Found matching device BTRIC134000035 => [d8:b6:73:bf:4f:75]
ERROR:root:Connection failed: le-connection-abort-by-local
ERROR:root:on_error: le-connection-abort-by-local
Now this is on a pi zero w (not 2w) i'd like to use for this, but i fear
it's bt 4.1 controller might be an issue. i'm going to switch back to the
pi4 fresh when i get a moment and i'll report back to you this evening...
On Wed, Nov 20, 2024 at 10:47 AM Cyril Sebastian ***@***.***>
wrote:
> Can you try https://github.com/cyrils/renogy-bt/tree/inverter-battery ?
>
> —
> Reply to this email directly, view it on GitHub
> <#88 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A2TQHU4L67F6YZPG66EUEL32BTDMBAVCNFSM6AAAAABR6YS7GOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZSGY3DQNQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
Garrett Hazlett
--
Garrett Hazlett
|
Beta Was this translation helpful? Give feedback.
-
oh? I was certain I loaded from the main branch... my bad, I'll load again.
…On Fri, Nov 29, 2024 at 7:42 PM Cyril Sebastian ***@***.***> wrote:
Okay thanks. Looks like you don't use the latest code yet.
—
Reply to this email directly, view it on GitHub
<#88 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2TQHU3FJTVQ5C3EISDFUZD2DEQ2XAVCNFSM6AAAAABR6YS7GOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBRHE4TINA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Garrett Hazlett
|
Beta Was this translation helpful? Give feedback.
-
yeah and batt percentage! I was going to build a calc for my
percentage tracker, this will save a LOT of time. Do you know how the
percentage is calculated? Or is it just what the inverter spits out?
this is an awesome amount of data to play with, cant thank you enough
(again)
…On Sun, Dec 1, 2024 at 8:56 AM Cyril Sebastian ***@***.***> wrote:
You can see many more fields here. Especially related to load.
—
Reply to this email directly, view it on GitHub
<#88 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2TQHU23747TOQ5KWDG6LS32DMWTJAVCNFSM6AAAAABR6YS7GOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBSHA4DKNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Garrett Hazlett
|
Beta Was this translation helpful? Give feedback.
I've updated main branch. It should work better.