Power values jump to 65535 kW and -65509 kW #398

Doesi · 2025-01-18T15:12:43Z

Issue related to

Sunsynk / mbusd Home Assistant Add-On

Describe the issue/bug

Since the last commit, power sensors randomly jump to 65535 kW and -65509 kW.

Expected behavior
Real values should be shown

Your environment

Home Assistant version: 2025.1.2
Addon:
- Name: sunsynk-multi
- Version: f23619a
Inverter:
- Make: Deye
- Model: SUN 20K-SG01 HP3-EU-AM2
- Firmware: -
Adaptor details:
- solarman

See also #391 (comment)

The text was updated successfully, but these errors were encountered:

JanKraslice · 2025-01-18T22:58:54Z

Hello yes that's right version:f23619a is wrong
I'm attaching pictures, please kellerza

Marow · 2025-01-22T11:00:25Z

I have exactly the same problem with DEYE SG05LP3 20K (the new one).

I am using Sunsynk/Deye Inverter Add-on (edge/dev) with Version: e6c5d80

kellerza · 2025-01-22T11:13:09Z

Can you test with the new edge version that includes #397 ?

proggaras · 2025-01-22T11:51:58Z

Unfortunately I can't update:

maslyankov · 2025-01-22T12:02:33Z

Unfortunately I can't update:

There seem to be some build cicd issues occasionally which I've noticed. They have affected the new version build. I have made a PR that aims to fix this.

maslyankov · 2025-01-22T12:47:44Z

Looks like there no peaks anymore with 02f085f

I will check it again after few hours and will send information here. But first, looks good!

Let's keep this issue open for now. Pls confirm in a day or two if fix is consistent.

Marow · 2025-01-22T12:48:08Z

Its not fixed with the new commit. 02f085f

As you can see on the bottom right. There you can see, it says each phase -65xxx

Marow · 2025-01-22T13:08:24Z

Its not fixed with newest version 02f085f. Thats last 8 minutes.

Up and down 65xxx Watts.

I found that:
StephanJoubert/home_assistant_solarman#329

Looks nearly the same problem on Solarman. Probably you can check how they fixed it.
They have also same Problem with 65xxx Watts up and down

maslyankov · 2025-01-22T13:11:26Z

Yes, I just checked over at https://github.com/davidrapan/ha-solarman/blob/c1e893c1c79e2b969104bf478deca8f2e286f504/custom_components/solarman/inverter_definitions/deye_p3.yaml#L2461-L2485 that they have the same registers are defined here:

sunsynk/src/sunsynk/definitions/three_phase_common.py

Lines 78 to 80 in bbb7a60

    
           Sensor((650, 656), "Load L1 power", WATT, -1), 
        
           Sensor((651, 657), "Load L2 power", WATT, -1), 
        
           Sensor((652, 658), "Load L3 power", WATT, -1),

This appears to be the fix they implemented: StephanJoubert/home_assistant_solarman#270

Marow · 2025-01-22T13:54:02Z

Yes, I just checked over at https://github.com/davidrapan/ha-solarman/blob/c1e893c1c79e2b969104bf478deca8f2e286f504/custom_components/solarman/inverter_definitions/deye_p3.yaml#L2461-L2485 that they have the same registers are defined here:

sunsynk/src/sunsynk/definitions/three_phase_common.py

Lines 78 to 80 in bbb7a60

Sensor((650, 656), "Load L1 power", WATT, -1),
Sensor((651, 657), "Load L2 power", WATT, -1),
Sensor((652, 658), "Load L3 power", WATT, -1),
This appears to be the fix they implemented: StephanJoubert/home_assistant_solarman#270

Yeah, that can be a fix.
Hope for update soon, than i can try again.

Marow · 2025-01-22T16:49:34Z

For your information:

I've found out something else that's very strange! Since the solar has stopped coming in because the sun has gone, there have been no more peaks. From about 4 p.m. onwards, you can't see any more peaks.

Is it somehow related to this?
Maybe too much data being sent together, which is messing things up or something?

maslyankov · 2025-01-22T17:10:30Z

Probably is related, yes. Now that I think of it, I also get spikes when there is solar production. Maybe data gets a bit messed up when many modbus frames come in. For this reason, I also implemented CRC validation as well (in the last PR above), like other projects have.

maslyankov · 2025-01-22T19:22:02Z

Version e37dd6d is up 🙌 Hopefully this does it. 🤞

Doesi · 2025-01-22T21:56:08Z

Now it's completely broken. In the logs I get continously:

Error reading: PySolarmanV5Async.read_holding_registers() got an unexpected keyword argument 'sequence_number'

Marow · 2025-01-23T04:28:17Z

Now it's completely broken. In the logs I get continously:

Error reading: PySolarmanV5Async.read_holding_registers() got an unexpected keyword argument 'sequence_number'

Not for me. I didnt have that error.

Version e37dd6d is up 🙌 Hopefully this does it. 🤞

Will check it later, when Solar Power comes in. Without solar, i didnt have that peaks

maslyankov · 2025-01-23T07:20:03Z

Now it's completely broken. In the logs I get continously:

Error reading: PySolarmanV5Async.read_holding_registers() got an unexpected keyword argument 'sequence_number'

Not for me. I didnt have that error.

Version e37dd6d is up 🙌 Hopefully this does it. 🤞

Will check it later, when Solar Power comes in. Without solar, i didnt have that peaks

Are you using solarman connection? I am guessing not (tcp to modbus?)

Doesi · 2025-01-23T07:33:53Z

Yes, solarman with the original wifi dongle.

Marow · 2025-01-23T07:40:37Z

Now it's completely broken. In the logs I get continously:
Error reading: PySolarmanV5Async.read_holding_registers() got an unexpected keyword argument 'sequence_number'

Not for me. I didnt have that error.

Version e37dd6d is up 🙌 Hopefully this does it. 🤞

Will check it later, when Solar Power comes in. Without solar, i didnt have that peaks

Are you using solarman connection? I am guessing not (tcp to modbus?)

No, i am using cable from modbus with Waveshare RS485 to USB (USB into my Home Assistant mini PC)
And pymodbus config

martinarva · 2025-01-23T07:50:44Z

I'm running the latest and still have issue with power jumps. Connection is direct modbus to PC.

maslyankov · 2025-01-23T08:14:10Z

Just found that there is a related issue from a long time ago: #184

This is strange, as when using the pysolarman driver, under the hood we had already been doing these checks I added, yet the issue is there.

Looking through the code, I am starting to think that my validations were not implemented on the right place... This does not change my confusion with why the issue persists when using the pysolarman driver, as they should be already there in the recent versions...

@kellerza any ideas here?

Marow · 2025-01-23T08:56:45Z

My Solar Power starts now, lets see... right now, on low solar power there are no peaks with newest version. Hope that also doesnt comes with more power soon

maslyankov · 2025-01-23T09:01:15Z

My Solar Power starts now, lets see... right now, on low solar power there are no peaks with newest version. Hope that also doesnt comes with more power soon

I am skeptical. #408 I think we need to revert this PR, as it only affects solarman (pysolarmanv5) driver usage (and overlaps with validations inside it).

proggaras · 2025-01-23T09:15:05Z

Mine is working just some spikes are there from time to time...

Your environment

Home Assistant version: 2025.1.3
Addon:
- Name: edge/dev
- Version: e37dd6d
Inverter:
- Make: Deye
- Model: SUN-25K-SG01HP3-EU-AM2
- Firmware: HMI: Ver 2001-C030 MAIN: Ver 3002-1066-1E08
Adaptor details:
- RS485
- Waveshare RS485_TO_POE_ETH

maslyankov · 2025-01-23T09:29:47Z

I will do another PR with revert of solarman breaking changes, also will add more validation to reading of data and more debug logs, so it it continues to happen we can hopefully see why.

Marow · 2025-01-23T10:06:24Z

Peaks starting again :(

Marow · 2025-02-04T14:23:08Z

I have commit f044dd2 running on my home assistant over 24 hours now and no peaks. There must be a commit after that, which brings the problems

JanKraslice · 2025-02-09T17:07:55Z

Hello and please.
Is there really no other solution but to go back to 92dd837 ?
In the future we will never use updates again ?
I have version 174e080 since its release on 3.2.2025 and the 65XXX spikes are still every day.
There used to be patching and new releases quite often now nothing :-(
I'm just a mere user apart from the test and report I can't help with the code so sorry.
Thank you

kellerza · 2025-02-10T06:09:52Z

Did you try the custom sensors mentioned above?

JanKraslice · 2025-02-10T08:25:15Z

I have tried 2 times before to create a custom sensor and never succeeded.
I'm seeing the aforementioned 65xxx on the default
sensor.ss_grid_l1_power
sensor.ss_grid_l2_power
sensor.ss_grid_l3_power
sensor.ss_grid_power
a
sensor.ss_grid_ct_l1_power
sensor.ss_grid_ct_l2_power
sensor.ss_grid_ct_l3_power
sensor.ss_grid_ct_power

proggaras · 2025-02-10T09:39:07Z

For now I added the following definitions to: /share/hass-addon-sunsync/mysensors.py
The changes from: e3af430 seem to be reverted.

SENSORS += (
    Sensor(616, "Grid CT L1 power", WATT, -1),  # aPower
    Sensor(617, "Grid CT L2 power", WATT, -1),  # bPower
    Sensor(618, "Grid CT L3 power", WATT, -1),  # cPower
    Sensor(619, "Grid CT power", WATT, -1),  # totalPower

    Sensor(625, "Grid power", WATT, -1),  # gridTotalPac
    Sensor(622, "Grid L1 power", WATT, -1),  # aPower
    Sensor(623, "Grid L2 power", WATT, -1),  # bPower
    Sensor(624, "Grid L3 power", WATT, -1),  # cPower

    Sensor(636, "Inverter power", WATT, -1),
    Sensor(633, "Inverter L1 power", WATT, -1),
    Sensor(634, "Inverter L2 power", WATT, -1),
    Sensor(635, "Inverter L3 power", WATT, -1),

    Sensor(653, "Load power", WATT, -1),
    Sensor(650, "Load L1 power", WATT, -1),
    Sensor(651, "Load L2 power", WATT, -1),
    Sensor(652, "Load L3 power", WATT, -1),

    Sensor(636, "Inverter power", WATT, -1),
    Sensor(633, "Inverter L1 power", WATT, -1),
    Sensor(634, "Inverter L2 power", WATT, -1),
    Sensor(635, "Inverter L3 power", WATT, -1),
)

JanKraslice · 2025-02-10T13:48:54Z

For now I added the following definitions to: /share/hass-addon-sunsync/mysensors.py The changes from: e3af430 seem to be reverted.

SENSORS += (
    Sensor(616, "Grid CT L1 power", WATT, -1),  # aPower
    Sensor(617, "Grid CT L2 power", WATT, -1),  # bPower
    Sensor(618, "Grid CT L3 power", WATT, -1),  # cPower
    Sensor(619, "Grid CT power", WATT, -1),  # totalPower

    Sensor(625, "Grid power", WATT, -1),  # gridTotalPac
    Sensor(622, "Grid L1 power", WATT, -1),  # aPower
    Sensor(623, "Grid L2 power", WATT, -1),  # bPower
    Sensor(624, "Grid L3 power", WATT, -1),  # cPower

    Sensor(636, "Inverter power", WATT, -1),
    Sensor(633, "Inverter L1 power", WATT, -1),
    Sensor(634, "Inverter L2 power", WATT, -1),
    Sensor(635, "Inverter L3 power", WATT, -1),

    Sensor(653, "Load power", WATT, -1),
    Sensor(650, "Load L1 power", WATT, -1),
    Sensor(651, "Load L2 power", WATT, -1),
    Sensor(652, "Load L3 power", WATT, -1),

    Sensor(636, "Inverter power", WATT, -1),
    Sensor(633, "Inverter L1 power", WATT, -1),
    Sensor(634, "Inverter L2 power", WATT, -1),
    Sensor(635, "Inverter L3 power", WATT, -1),
)

If you use 6xx sensors like that, don't you already have 65xxx,-kW peaks?

JanKraslice · 2025-02-11T18:02:35Z

Sorry, I couldn't add my own sensors.
Can I now use the sensors a,b,c you mentioned?

proggaras · 2025-02-11T19:11:16Z

Sorry, I couldn't add my own sensors. Can I now use the sensors a,b,c you mentioned?

Did you add mysensors in the addon configuration?

...
SENSORS:
   ...
   - mysensors
   ...

JanKraslice · 2025-02-12T16:15:16Z

Hello, I have a problem already with the creation of the folder
/share/
Where should I please create it directly in the main one like this ?
/homeassistant/share/hass-addon-sunsync/mysensors.py
So in this folder there will be a file called mysensors.py ( which I will create as a text file where I will copy the above from you and then change the ending to .py ?
Then in the addon I will add the text mysensors to the sensor entry?

Then I will have new sensors ( the original ones ) ?

Does this work for you and you no longer have spikes after this solution ?

schein-heilig · 2025-02-13T07:09:50Z

I have the same issues with the Battery Charge (sensor.deye_day_battery_charge) .

JanKraslice · 2025-02-15T14:05:29Z

Zkoušel jsi výše zmíněné vlastní senzory?

I confirm both the 92dd837 version and the custom sensors solve the 65xxx peak problem

Will there be a permanent solution in the next release? Can we try it please.

martinarva · 2025-02-16T11:54:24Z

Can confirm the mysensors workaround works. After f932d4c commit i can see the errors is log:

11:50:41 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:50:41 WARNING High value total_grid_import=179677 (#522=0xbddd, #523=0x2)
11:50:41 WARNING High value total_pv_energy=86258 (#534=0x50f2, #535=0x1)
11:50:46 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:50:50 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:50:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:01 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:05 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:10 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:16 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:20 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:25 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:31 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:35 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:40 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:46 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:50 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:51:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:01 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:05 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:10 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:16 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:20 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:25 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:31 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:35 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:40 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:46 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:50 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:52:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:01 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:05 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:10 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:16 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:20 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:25 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:31 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:35 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:40 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:46 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:50 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
11:53:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)

EDIT: would it be possible to turn off this logging, as this probably chrashed my sunsynk this night.

kellerza · 2025-02-16T13:41:00Z

11:53:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
EDIT: would it be possible to turn off this logging, as this probably chrashed my sunsynk this night.

If this crashed your addon, you probably need to update your HA OS system 😉

Anyway, I've removed the logging and implemented a possible fix based on a new Sensor16 class
5ae3b76#diff-975965ed99ea476ca9badb6a59ccdc1867f1570d8d136ae22458627a812bc456R64

Please try it without the custom sensors and let me know.

nicopret1 · 2025-02-16T17:30:46Z

Tried 5ae3b76 but unfortunately the spikes are back when I remove custom sensors.

kellerza · 2025-02-16T17:37:08Z

Did you see anything in your log?
What inverter do you have?

nicopret1 · 2025-02-16T18:30:25Z

I see regular entries like these:
18:26:30 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffe', '0xffff']
18:26:31 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfff6', '0xffff']
18:26:35 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfff9', '0xffff']
18:26:35 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfff9', '0xffff']
18:26:40 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfff6', '0xffff']
18:26:40 INFO Sensor Grid power reported a 32-bit value: ['0xffff', '0xffff']
18:26:40 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffa', '0xffff']
18:26:45 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffc', '0xffff']
18:26:45 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffa', '0xffff']
18:26:55 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffb', '0xffff']
18:26:55 INFO Sensor Grid L2 power reported a 32-bit value: ['0xfffe', '0xffff']
18:27:00 INFO Sensor Grid L2 power reported a 32-bit value: ['0xffff', '0xffff']

I experience the problem on the following inverters:

Sunsynk Three phase HV Hybrid 50kW
Sunsynk Three phase LV Hybrid 12kW

kellerza · 2025-02-17T03:44:36Z

Hi @nicopret1 - the latest version should log the first 50 readings with more detail (including rated_power). Please post the log for both inverters.

With a 1-register sensor (old behavior) - any value between 32768-65535 would have been reported as a (small) negative value - so it might be that this happened on your 50kW inverter, but you never noticed it.

For an inverter<32k, a 1-register sensor should be enough - maybe the solution is just to use 1 register when rated_power is low.

With a 2-register sensor you might get:

a big positive spike if the 2nd register is zero
a big negative spike if the first register is 0

nicopret1 · 2025-02-17T06:24:16Z

Hi @kellerza thank you for the detailed information. What I've experienced, now makes more sense. I've attached the logs files for both installations:

The 2x12kW installation uses very little grid power and that was the site where I first noticed the spikes.
The 4x50kW inverter installation was not that obvious initially. I've also included some log history for this install.

4x50kW-4bb530c7_hass-addon-sunsynk-edge_2025-02-17T06-02-39.364Z.log
2x12kW-4bb530c7_hass-addon-sunsynk-edge_2025-02-17T05-52-31.308Z.log

martinarva · 2025-02-17T07:33:11Z

T

11:53:55 WARNING High value rated_power=120000 (#20=0xd4c0, #21=0x1)
EDIT: would it be possible to turn off this logging, as this probably chrashed my sunsynk this night.
If this crashed your addon, you probably need to update your HA OS system 😉

Anyway, I've removed the logging and implemented a possible fix based on a new Sensor16 class 5ae3b76#diff-975965ed99ea476ca9badb6a59ccdc1867f1570d8d136ae22458627a812bc456R64

Please try it without the custom sensors and let me know.

The latest version now works and my grid entity is clean. Only CT Grid has errorrs, but currently my CT clamps are not on thle wires as I moved my load to inverter backup.

Here is a log>

sunsynk-multi.log

EDIT: still peaks in grid_power as well unfortunately.

JanKraslice · 2025-03-05T10:39:30Z

Hello, I am sending a comparison version
(174e080)
and the latest available version installed today
(0337510)

THE 65XXX PEAK PROBLEM PERSISTS

I attach pictures and LOG

NOTE THE PROBLEM ONLY MANIFESTS ITSELF WHEN THE INVERTER IS NOT DRAWING FROM THE GRID OR FEEDING INTO THE GRID

4bb530c7_hass-addon-sunsynk-edge_2025-03-05T10-32-57.298Z.log

JanKraslice · 2025-03-09T13:44:52Z

Does that really bother anyone?
It happens over and over and over again.
I don't know what happened here, before when there was a bug in the addon it was fixed in the next version, now everyone doesn't care. That's a shame.

schein-heilig · 2025-03-10T06:08:55Z

Im on edge 0337510 and had no PV Power Spikes since 25.02.

But Battery Charge is still off with regular spike :-(

schein-heilig · 2025-03-10T06:12:31Z

same here with Grid spikes

JanKraslice · 2025-03-10T10:17:10Z

Yes the spikes are still there and only on GRID from the beginning
CT L1
CT L2
CT L3

Please is there really no solution to use only one register as before?

JanKraslice · 2025-03-10T10:18:25Z

Ahoj@nicopret1- nejnovější verze by měla zaznamenávat prvních 50 odečtů s podrobnějšími údaji (včetně jmenovitého výkonu). Zašlete prosím protokol pro oba střídače.

U senzoru s 1 registrem (staré chování) - jakákoli hodnota mezi 32768-65535 by byla hlášena jako (malá) záporná hodnota - takže se to mohlo stát na vašem 50kW měniči, ale nikdy jste si toho nevšimli.

Pro invertor<32k by mělo stačit čidlo s 1 registrem - možná je řešením jen použít 1 registr, když je rating_power nízký.

S 2registrovým senzorem můžete získat:

velký kladný hrot, pokud je 2. registr nulový

velký záporný vrchol, pokud je první registr 0

Please is there really no solution to use only one register as before?
Currently there are still spikes on GRID CT L1, CT L2, CT L3

kellerza · 2025-03-10T10:52:12Z

Upgrade your firmware or use a custom definition with the single register for grid and battery

JanKraslice · 2025-03-10T12:13:52Z

Upgradujte svůj firmware nebo použijte vlastní definici s jediným registrem pro síť a baterii

Hello, according to the inverter support I have the latest version see picture it is an inverter
SUN-30K-SG01HP3-EU-BM3
30kW - 3 phase, high voltage batteries
The current version used by you is see picture

I ASSUMED IT WAS A BUG with yours, as it only started from version f23619a before that there was no problem. So I waited for a fix and did not use my own sensors.
If this is a permanent condition and desired and is the correct behavior then it is pointless to keep this topic open.

kellerza · 2025-03-10T12:36:26Z

I doubt this is a bug.

Different inverters seem to behave differently

We use the latest available modbus definitions. Read my explanation above. I’m not sure we can improve this and still support 2 registers.

Best would be to use a custom definition and if someone with ons of these inverters wants to document this, even better

JanKraslice · 2025-03-10T16:01:22Z

Pochybuji, že se jedná o chybu.

Zdá se, že různé měniče se chovají odlišně

Používáme nejnovější dostupné definice modbus. Přečtěte si mé vysvětlení výše. Nejsem si jistý, zda to dokážeme zlepšit a stále podporovat 2 registry.

Nejlepší by bylo použít vlastní definici a pokud to někdo s těmito měniči chce zdokumentovat, ještě lépe

I totally agree I would stick with the original definition of version 92dd837 where the default is read only one register.
Simply as it was before.

If some versions of inverters need to read both registers, let the option be via mysensor.
Personally I think most don't need to read the value of both registers I don't see any advantage in that.

Do you agree?

JanKraslice · 2025-03-15T00:31:24Z

If anyone needs help with setting up mysensors.py which solves the mentioned spikes just write.
I can help, I managed to

maslyankov mentioned this issue Jan 18, 2025

Enhance helper functions for register value conversions #397

Merged

maslyankov mentioned this issue Jan 22, 2025

Improvement/build cicd #406

Merged

Marow mentioned this issue Jan 22, 2025

Error Updating edge/dev Version to a664930 #407

Closed

maslyankov mentioned this issue Jan 22, 2025

Bugfix/values spikes #408

Merged

Doesi mentioned this issue Jan 23, 2025

Doesn't read any data anymore (PySolarmanV5Async.read_holding_registers() got an unexpected keyword argument) #409

Closed

Power values jump to 65535 kW and -65509 kW #398

Power values jump to 65535 kW and -65509 kW #398

Comments

Doesi commented Jan 18, 2025 • edited Loading

Issue related to

Describe the issue/bug

Your environment

JanKraslice commented Jan 18, 2025

Marow commented Jan 22, 2025

kellerza commented Jan 22, 2025

proggaras commented Jan 22, 2025

maslyankov commented Jan 22, 2025

maslyankov commented Jan 22, 2025

Marow commented Jan 22, 2025 • edited Loading

Marow commented Jan 22, 2025 • edited Loading

maslyankov commented Jan 22, 2025 • edited Loading

Marow commented Jan 22, 2025 • edited Loading

Marow commented Jan 22, 2025

maslyankov commented Jan 22, 2025 • edited Loading

maslyankov commented Jan 22, 2025 • edited Loading

Doesi commented Jan 22, 2025

Marow commented Jan 23, 2025

maslyankov commented Jan 23, 2025 • edited Loading

Doesi commented Jan 23, 2025

Marow commented Jan 23, 2025 • edited Loading

martinarva commented Jan 23, 2025 • edited Loading

maslyankov commented Jan 23, 2025 • edited Loading

Marow commented Jan 23, 2025

maslyankov commented Jan 23, 2025

proggaras commented Jan 23, 2025

Your environment

maslyankov commented Jan 23, 2025

Marow commented Jan 23, 2025

Marow commented Feb 4, 2025

JanKraslice commented Feb 9, 2025

kellerza commented Feb 10, 2025

JanKraslice commented Feb 10, 2025

proggaras commented Feb 10, 2025 • edited Loading

JanKraslice commented Feb 10, 2025

JanKraslice commented Feb 11, 2025

proggaras commented Feb 11, 2025

JanKraslice commented Feb 12, 2025

schein-heilig commented Feb 13, 2025

JanKraslice commented Feb 15, 2025

martinarva commented Feb 16, 2025 • edited Loading

kellerza commented Feb 16, 2025

nicopret1 commented Feb 16, 2025

kellerza commented Feb 16, 2025

nicopret1 commented Feb 16, 2025 • edited Loading

kellerza commented Feb 17, 2025

nicopret1 commented Feb 17, 2025

martinarva commented Feb 17, 2025 • edited Loading

JanKraslice commented Mar 5, 2025

JanKraslice commented Mar 9, 2025

schein-heilig commented Mar 10, 2025

schein-heilig commented Mar 10, 2025

JanKraslice commented Mar 10, 2025

JanKraslice commented Mar 10, 2025

kellerza commented Mar 10, 2025

JanKraslice commented Mar 10, 2025

kellerza commented Mar 10, 2025

JanKraslice commented Mar 10, 2025

JanKraslice commented Mar 15, 2025

Doesi commented Jan 18, 2025 •

edited

Loading

Marow commented Jan 22, 2025 •

edited

Loading

Marow commented Jan 22, 2025 •

edited

Loading

maslyankov commented Jan 22, 2025 •

edited

Loading

Marow commented Jan 22, 2025 •

edited

Loading

maslyankov commented Jan 22, 2025 •

edited

Loading

maslyankov commented Jan 22, 2025 •

edited

Loading

maslyankov commented Jan 23, 2025 •

edited

Loading

Marow commented Jan 23, 2025 •

edited

Loading

martinarva commented Jan 23, 2025 •

edited

Loading

maslyankov commented Jan 23, 2025 •

edited

Loading

proggaras commented Feb 10, 2025 •

edited

Loading

martinarva commented Feb 16, 2025 •

edited

Loading

nicopret1 commented Feb 16, 2025 •

edited

Loading

martinarva commented Feb 17, 2025 •

edited

Loading