BinaryPayloadDecoder is deprecated

[mjdebruijn]

The problem

Logger: pymodbus.logging
Bron: custom_components/victron/coordinator.py:117
integratie: victron (documentatie, problemen)
Eerst voorgekomen: 23 februari 2025 om 18:56:22 (347580 gebeurtenissen)
Laatst gelogd: 11:01:46
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"

What version of Home Assistant Core has the issue?

core-2025.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Victron

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

modbus documentation
modbus source

[WillCodeForCats]

This error is for custom_components/victron so it needs to be fixed there.

The victron custom component needs to update its code for pymodbus 3.8.3.

[WillCodeForCats]

sfstar/hass-victron#286

[maddog75]

Looks like the merge request has existed since January

sfstar/hass-victron#281

If i've read the failed checks correctly they are only minor issues with the indentation in custom_components/victron/popBuffer.py

def getItemInBuffer(self, dataType):
    """Get the item in the buffer."""
    match dataType:
        case UINT16:
        # Handle UINT16
        pass
        case UINT32:
        # Handle UINT32
        pass
        case INT16:
        # Handle INT16
        pass
        case INT32:
        # Handle INT32
        pass
        case _:
        raise ValueError(f"Unsupported data type: {dataType}")

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.