-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
[Bug]: BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 #1223
Comments
It seems that that the deprecation is no longer the case, but it's strange that it's popping up |
I'll keep track of pyModbus in case we do need to make the change, although there seems to be little examples of the changes required other than the very basic ones. |
Yeah I agree, |
same issue here ..... if you need any logs, let me know ... |
Same here, log is flooded: Logger: 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" |
Hi @wills106
I would prefer option 2 for now, brings the least risk and I don't think we need to maintain it a lot. |
I don't know but maybe this can help you.
will give output link to classmethod |
Same issue:
|
I've created a PR where payload.py is brought to the application and the deprecration message is removed #1232 |
Thanks. |
Dieser Fehler stammt von einer benutzerdefinierten Integration Logger: 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" Sadly its back again after HA Update today...😪 Edit/Update: |
Just released 2025.01.9 with the change.
Edit: It's been abandoned. |
work like a charm ! thanks |
Probably need to look at how many separate reads would be needed with the new method. Unless we can string together the convert calls? Or just stick with payload decoder being in this Integration. |
Calling the separate registers will be a massive overhead, so I think for now we should keep this solution |
I agree and don't fancy going that route unless we have too. |
@wills106 Unfortunately looks like problem appeared again. Or its some issue on my side? |
... and an other one, those spikes at many values from time to time. Now, many stuck at 2025.01.6 Modbus Integration to avoid spikes and misfunction of newer versions sadly 🤷🏼♂️. |
I have noticed you get the warning on restarting HA. But you only get it the once and not 10,000 times. |
Yes, this is right. |
In my case i got 12k times till last restart. So maybe somthing on my side, but what? 2025-02-20 12:07:14.600 WARNING (MainThread) [pymodbus.logging] BinaryPayloadDecoder is deprecated and will be removed in v3.9.0 ! |
What version of the Integration are you using? |
Right now 2025.02.1. |
Reopening it for now, although it's not a major issue. It only writes to the log once per HA restart. |
@wills106 In my case its spaming errors all the time, right now 9k times |
Removed the left overs in all plugins via PR #1274 |
Is there a new Beta or ? out now containing your changes? |
Just released 2025.03.1 with the changes. |
Describe the bug
Warning in log for BinaryPayloadDecoder is deprecated and will be removed in v3.9.0
Integration Version
2025.01.8
Homeassistant core version
2025.1.2
Inverter brand
All
Plugin used
plugin_solax.py
Serial prefix
N/A
Inverter firmware versions
N/A
Connection Method
N/A
Dongle firmware
N/A
Detailed Error Log
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"
Additional context
I have raised this to try and reduce multiple Issues raised for the same warning.
Please don't spam this Issue saying you have the same error, as everyone will have this warning.
The text was updated successfully, but these errors were encountered: