Skip to content
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

High SOC and Wattage number #305

Open
enduring78 opened this issue Mar 1, 2025 · 2 comments
Open

High SOC and Wattage number #305

enduring78 opened this issue Mar 1, 2025 · 2 comments
Labels
bugfix Inconsistencies or issues which will cause a problem for users or implementors.

Comments

@enduring78
Copy link

enduring78 commented Mar 1, 2025

The problem

Hello, since a few weeks, the Victron integration on my Home Assistant had been reporting percentages above 100% for the batteries, and unreal numbers for the power Watts. This issue started with the update to Home Assistant 2.0. I have reverted a earlier backup of my Home Assistant (which now has version 1.4) be be able to keep using the integration in the meantime.

Environment

I am having this issue with Home Assistant 2.0 and up. I converted back from Remcom's repo to this one since this one seems to be active again, and I'm using the latest release 0.4.2.

  • Home Assistant Core release with the issue: 2025.2.0 and up
  • Last working Home Assistant Core release (if known): 2025.1.4
  • Integration version causing this issue: Not sure. After seeing the message in the 0.4.2 release that said I need to install it before installing HA Core 2025.2.0, I migrated first before upgrading. Version 0.3.5 from Remcom worked fine on 2025.1.4 and still continues to do so IF I don't update HA Core.

Problem-relevant configuration dialog

Not sure where to get this info, but this is in the configuration box if I click configure next to the device:

Image

Traceback/Error logs

These are logs form the exact time a extremely high value appeared on Home Assistant. Nothing changed physically, and HA Core 1.4 with integration version 0.3.5 from Remcom is not reporting any anomalies during that period.

2025-03-01 15:27:46.944 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.946 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.948 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.950 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.951 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.952 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 !
Please use "client.convert_from_registers()" or "client.convert_to_registers"
See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers"
2025-03-01 15:27:46.954 ERROR (SyncWorker_26) [pymodbus.logging] Exception response 131 / 0
2025-03-01 15:27:46.954 WARNING (MainThread) [custom_components.victron.coordinator] no valid data returned for entities of slave: 230 (if the device continues to no longer update) check if the device was physically removed. Before opening an issue please force a rescan to attempt to resolve this issue
2025-03-01 15:27:46.956 ERROR (SyncWorker_30) [pymodbus.logging] Exception response 131 / 0
2025-03-01 15:27:46.956 WARNING (MainThread) [custom_components.victron.coordinator] no valid data returned for entities of slave: 230 (if the device continues to no longer update) check if the device was physically removed. Before opening an issue please force a rescan to attempt to resolve this issue

In case of unit ID issue, missing devices or non-updating devices

Additional information

Here's a screenshot of the issue:

Image

@enduring78 enduring78 added the bugfix Inconsistencies or issues which will cause a problem for users or implementors. label Mar 1, 2025
@sfstar
Copy link
Owner

sfstar commented Mar 5, 2025

Hello and thank you for opening this issue.
Can you see/confirm if the
2025-03-01 15:27:46.956 ERROR (SyncWorker_30) [pymodbus.logging] Exception response 131 / 0
is reported at the same time there is an percentage spike?

@enduring78
Copy link
Author

Hi,

The 2025-03-01 15:27:46.956 ERROR (SyncWorker_30) [pymodbus.logging] Exception response 131 / 0 line does not appear to be related, since that one shows up on my working instance (running 2025.1.4) as well.

On my test instance, which is a clone of my working instance since I didn't want to mess up my data, there is a spike today 17:24:58.

At 17:24:57, I see this error in the log:
2025-03-05 17:24:57.453 ERROR (MainThread) [custom_components.victron.coordinator] Unexpected error fetching victron data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/victron/coordinator.py", line 96, in _async_update_data self.parse_register_data( ~~~~~~~~~~~~~~~~~~~~~~~~^ data, register_info_dict[name], unit ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ).items() ^ File "/config/custom_components/victron/coordinator.py", line 129, in parse_register_data decoder.decode_16bit_int(), value.scale, value.unit ~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/pymodbus/payload.py", line 447, in decode_16bit_int return unpack(fstring, handle)[0] ~~~~~~^^^^^^^^^^^^^^^^^ struct.error: unpack requires a buffer of 2 bytes

Then, at 17:24:58, I see this:

2025-03-05 17:24:58.449 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 ! Please use "client.convert_from_registers()" or "client.convert_to_registers" See documentation: "https://pymodbus.readthedocs.io/en/latest/source/client.html#pymodbus.client.mixin.ModbusClientMixin.convert_from_registers" 2025-03-05 17:24:58.449 ERROR (MainThread) [custom_components.victron.coordinator] Unexpected error fetching victron data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 380, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/victron/coordinator.py", line 96, in _async_update_data self.parse_register_data( ~~~~~~~~~~~~~~~~~~~~~~~~^ data, register_info_dict[name], unit ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ).items() ^ File "/config/custom_components/victron/coordinator.py", line 143, in parse_register_data .decode() ~~~~~~^^ UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte

I'm also seeing some logs from other integrations about the network going down briefly, but I believe this is due to a saturated Ethernet connection while my backup is running. My test HA instance and the working instance are on the same Proxmox host and I am getting the same errors on the working instance, but on that one the readings stay normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Inconsistencies or issues which will cause a problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants