-
Notifications
You must be signed in to change notification settings - Fork 152
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
wrong output if jk04 and jkv11 used in config (different proto per section) #496
Comments
I'll have a look. You might need to run a separate instance for each device
though
…On Sun, Jun 16, 2024, 05:19 mfu-mcosys ***@***.***> wrote:
if the config looks like this:
[JKBMS_UNTEN]
type=jkbms
protocol=jk04
port=C8:47:8C:E5:CC:9F
command=getCellData
outputs=screen
[JKBMS_BOX1_UNTEN]
type=jkbms
protocol=jkv11
port=C8:47:80:13:CC:AE
command=getCellData
outputs=screen
the output for the first proto (jk04) is wrong.
If there is just one proto used in the config, it works.
I just upgraded from Python3.9 to Python3.11 to get latest mpp-solar
(version: 0.16.34, python version: 3.11.2) ... but the problem is the same.
Any suggestions?
—
Reply to this email directly, view it on GitHub
<#496>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVKNTNESOOBWG6PAZINVTZHRZSRAVCNFSM6AAAAABJL3BEQSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2TKMBUHE2TKMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thats what i do as workaround. |
You can run 2 daemons just need to call them something different and have 2
service files etc
…On Sun, Jun 16, 2024, 19:50 mfu-mcosys ***@***.***> wrote:
Thats what i do as workaround.
Just dont run as a daemon and use a one line per device in a bash script
which is triggered per cron.
—
Reply to this email directly, view it on GitHub
<#496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVKNW5CLANCHGPXDRBQRTZHU7SZAVCNFSM6AAAAABJL3BEQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGE2TCMBYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Want work (tested it) - because the PI3 BLE-device seems to be blocked if in use by any of the 2 daemons. |
Oh, bummer.
The ble stack and code are pretty rough. I'll see what I can do with it -
though it might be in powermon code instead
…On Sun, Jun 16, 2024, 19:55 mfu-mcosys ***@***.***> wrote:
Want work (tested it) - because the PI3 BLE-device seems to be blocked if
in use by any of the 2 daemons.
—
Reply to this email directly, view it on GitHub
<#496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVKNQS5MSOESOVPGTIXCDZHVAFJAVCNFSM6AAAAABJL3BEQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGE3TCNBSHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I don't want to hijack the post, But Mppsolar run here since 2021 with one Bms (daly wired) one Balancer (JK04 bluetooth) nd one inverter mppsolar wired. So we are in the same boat |
can you post your config file (as this shouldnt happen) |
My config This Required section
|
oh, nvm I missed that both JKBMSs were BLE |
if the config looks like this:
the output for the first proto (jk04) is wrong.
If there is just one proto used in the config, it works.
I just upgraded from Python3.9 to Python3.11 to get latest mpp-solar (version: 0.16.34, python version: 3.11.2) ... but the problem is the same.
Any suggestions?
Output with wrong values for jk04
The text was updated successfully, but these errors were encountered: