search

tjhowse / modbus4mqtt

Modbus TCP <-> MQTT glue. YAML configuration. Robust.
Other
75 stars 33 forks source link

Unit ID = device_address not working? #52

Open TeslaV1 opened 4 months ago

TeslaV1 commented 4 months ago

Huawei inverters use a dongle as bridge to accept modbus tcp requests and map them to modbus rtu. With this more than one inverter can be connected to the dongle.

When wanting to read registers from one or the other inverter, the unit ID is needed to identify the correct inverter.

Please add support for that, many thanks in advance.

TeslaV1 commented 4 months ago

Dammit, is already implemented, sorry for that.

TeslaV1 commented 4 months ago

Sorry I have to reopen that.

This is my config:

ip: 192.168.0.157 #your inverter ip address port: 502 update_rate: 15 device_address: 2 (tested with different addresses) address_offset: 0 variant: tcp (tested with rtu-over-tcp) word_order: highlow scan_batching: 1 registers:

Device Address is 2. If I look at the packets in wireshark I see: Unit Identifier 1

Unit Identifier does not change if I change the device_address in the config.

Any tips? Error is: ValueError: Failed to read 1 holding table registers starting from 32107: Modbus Error: [Input/Output] No Response received from the remote unit/Unable to decode response