Invalid value active power after update HA core 2024.12

[Pstart]

Description

PV - HYD 10KTL-3PH-PRO

I had integration Solarman StephanJoubert but update core 2024.12 entered incorrect values many entity. I changed for new integration ha-solarman. Most of the values is ok but active_energe and battery power is incorect for more time. More time returning value is 65kW, like
ActivePower_Output_R 64,526 W
ActivePower_Output_S 910 W
ActivePower_Output_T 64,876 W
ActivePower_Output_Total 64,766 W
ActivePower_PCC_R 64,406 W
ActivePower_PCC_S 64,456 W
ActivePower_PCC_T 64,586 W
ActivePower_PCC_Total 62,356 W
Details is chart in attachment.
My max use energy is about 8kW
My profile is sofar_g3hyd.yaml

Reproduction Steps

I only use integration. Value active power is invalid.

Log

[33m2024-12-11 20:38:15.422 WARNING (MainThread) [py.warnings] /config/custom_components/solarman/parser.py:226: RuntimeWarning: overflow encountered in scalar subtract
value = (value - maxint) if not magnitude else -(value & (maxint >> 1))
[0m
[33m2024-12-11 20:38:15.423 WARNING (MainThread) [py.warnings] /config/custom_components/solarman/parser.py:229: RuntimeWarning: overflow encountered in scalar multiply
value *= scale
[0m
[33m2024-12-11 20:38:41.460 WARNING (MainThread) [py.warnings] /config/custom_components/solarman/parser.py:226: RuntimeWarning: overflow encountered in scalar subtract
value = (value - maxint) if not magnitude else -(value & (maxint >> 1))
[0m
[33m2024-12-11 20:38:41.460 WARNING (MainThread) [py.warnings] /config/custom_components/solarman/parser.py:229: RuntimeWarning: overflow encountered in scalar multiply
value *= scale

Version

24.12.10

Home Assistant Version

2024.12.2

[davidrapan]

Hi @Pstart, you are running containerized home assistant?

[Pstart]

Hi, no i use Assistant OS on x86-64 hardware
Home Assistant

Core
2024.12.2
Supervisor
2024.11.4
Operating System
14.0
Interfejs użytkownika
20241127.7

[davidrapan]

Did you try downgrade of the core (to some known to be working) to see of the problem prevails?

Edit: 2024.12 contains python upgrade to 3.13 and I'm for now not sure what's different there what could cause issues like this but it's the best candidate nevertheless.

[Pstart]

@davidrapan Yes, I downgraded version to 2024.11.3 that's all working good. But when ha-sofarman well work good on 2024.12?

[davidrapan]

Once I figure out what's wrong, because right now I don't have even slight idea... as everything works w/o any issues on my installation w/ 2024.12.2.

[werfpsa]

Same problem with inverter file sofar_g3hyd.yaml

[DawidJan]

I also have the same issue with sofar_g3hyd.yaml file

[davidrapan]

Can someone record 10 minute debug log?

[davidreher]

@davidrapan this is the log from HA:

2024-12-16 20:31:55.636 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Inverter for solarman
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/solarman/__init__.py", line 59, in async_setup_entry
    await async_migrate_entries(hass, config_entry.entry_id, partial(migrate_unique_ids, config.name, config.serial))
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1636, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1179, in async_update_entity
    return self._async_update_entity(
           ~~~~~~~~~~~~~~~~~~~~~~~~~^
        entity_id,
        ^^^^^^^^^^
    ...<21 lines>...
        unit_of_measurement=unit_of_measurement,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1118, in _async_update_entity
    raise ValueError(
    ...<2 lines>...
    )

How can I create the debug log? Happy to provide it ...

[davidrapan]

https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

[davidreher]

Sent it to you via mail (hope that is fine) ...

[mariomurrent-softwaresolutions]

@davidrapan this is the log from HA:

2024-12-16 20:31:55.636 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Inverter for solarman
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/solarman/__init__.py", line 59, in async_setup_entry
    await async_migrate_entries(hass, config_entry.entry_id, partial(migrate_unique_ids, config.name, config.serial))
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1636, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1179, in async_update_entity
    return self._async_update_entity(
           ~~~~~~~~~~~~~~~~~~~~~~~~~^
        entity_id,
        ^^^^^^^^^^
    ...<21 lines>...
        unit_of_measurement=unit_of_measurement,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1118, in _async_update_entity
    raise ValueError(
    ...<2 lines>...
    )

How can I create the debug log? Happy to provide it ...

Having the same issue :(

[davidrapan]

I did not receive any debug logs. Please upload it here in the thread. 😉

[maconly34]

Hello David,
I have similar error with Deye Sun inverter 6k SG03LP1.
Grid Power have a x10 factor shown.
Values is ok on iPhone Solarman App.

See screen copy.

[maconly34]

Hi David,
I've managed to correct the problem by modifying the code in the "deye_hybrid.yaml" file
There are 9 lines (# out of date docs) where the scale function is "scale: [1, 10]" I've replaced it with "scale: 1".

part of the code corrected :

• name: "External CT1 Power"
  l: 2
  class: "power"
  state_class: "measurement"
  uom: "W"
  rule: 2
  scale: 1 # out of date docs
  registers: [0x00AA]
  icon: "mdi:transmission-tower"

  - name: "External CT2 Power"
    l: 2
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    scale: 1 # out of date docs
    registers: [0x00AB]
    icon: "mdi:transmission-tower"
  
  - name: "External Power"
    l: 1
    class: "power"
    state_class: "measurement"
    uom: "W"
    rule: 2
    scale: 1 # out of date docs
    registers: [0x00AC]
    icon: "mdi:transmission-tower"
  

[davidrapan]

@maconly34, it's there for a reason. You proly checked scale modifier in the options. 😉