Krzysztof Białek

I came across this same problem and solved it by building the binary in a docker container. Here is a gist showing how to do it https://gist.github.com/kbialek/625bfe7c3a285529989374b9febd5ac8

Hi @Hinton Okay, I get the point. In my latest commit I've enhanced `getKey()` method to also accept optional `userId`. WDYT?

@Hinton Thanks for having a look. Could you shortly explain what do you mean by that? > it seems to completely break the desktop application. I built the desktop client...

> Did you use the file below as base for the different parameters? This file I've received from Deye service last time. Yes, exactly

@chfritsch Thank you for this PR. I've added the plugin support to let the users to extend the functionality with code that is not kept in this repo and therefore...

What is your inverter model?

Try out metric group [deye_sg01hp3_battery](https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg01hp3_battery.md) instead of [deye_sg04lp3_battery](https://github.com/kbialek/deye-inverter-mqtt/blob/main/docs/metric_group_deye_sg04lp3_battery.md). SG01HP3 and SG04LP3 have similar register layout.

I found this, maybe it will work. Try to read the registers using the command documented here https://github.com/kbialek/deye-inverter-mqtt?tab=readme-ov-file#reading-and-writing-raw-register-values  

> So I should do "r 600" to get the value for Module Voltage? Yes, exactly In the doc I have, the 1st battery pack address is 600, the 2nd...

Perhaps your batteries are mapped as packs other than 1 and 2? How is the solarman app showing the metrics?