Issue connecting to several modbus masters

[janwadebock]

Describe the bug
I keep receiving errors when trying to connect and pull holding registers from eg Huawei and Solaredge It works from node red, but not from the iobroker/modbus adapter (I am moving all my logic to IObroker) I can connect to the ananas test modbus and retrieve values in iobroker/modbus

To Reproduce
Steps to reproduce the behavior: 0. Connect to the IOBroker instance which is running on docker (with host network)

1. Go to the modbus instance
2. Configure it with the right IP address, port, instance
3. go to holding registers TAB and add 1 register eg 32080, length 2, signed integer
4. Set to instance in debug mode

Expected behavior
I expect the correct value to be returned in objects, as I do see it in node-red

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:
Modbus adapter: 6.3.2

Docker instance on synology. Platformoperating system:linux Architecture:x64 CPUs:4 Speed:1501 MHz Model:Intel(R) Celeron(R) CPU J3455 @ 1.50GHz RAM:3.6 GB System uptime:06:46:30 Node.js:v18.20.4 time:1732863993991 timeOffset:-60 NPM:10.8.2 adapters count:547 Disk size:5352.2 GB Disk free:4748.8 GB Active instances:11 Path:/opt/iobroker/ Uptime:06:35:32 alive:true _nodeCurrent:18.20.4 _nodeNewest:18.20.5 _nodeNewestNext:20.18.1 _npmCurrent:10.8.2 _npmNewest:10.7.0 _npmNewestNext:10.8.2

Additional context
same configuration works on node red also in docker on same system

[janwadebock]

Note the example given was for Huawei converter

[GermanBluefox]

Normally in 99.9% the slave is closing the connection as it cannot process the request. In 99.9% of the use cases you can adjust ioBroker instance to work with this device. Try to change FC commands, smaller read sizes