I’m using 3 pcs Marstek V3 with homey Pro TCP/modbus. This works fine.
I’m trying to make a flow to load the batteries at night. It seems to work correctly but i can’t get the Modus back to “ normal” mode. Therefor in de “ manual” mode i get the faillure “wijzen”. Can you give me advise if i’m using the commands in the flow if they correctly used.
B3: VenusE 3.0-uusin, firmware v149, connected via LAN
Commands work fine on B2 and B3 (charge/discharge via Set target power). However I’m seeing these issues on both V3 units:
Firmware shows “xxx” in device info
Stored energy available is always empty
Generic Alarm (yellow) is always active
Test page returns: Error: connect ECONNREFUSED (expected — app already holds the connection)
I suspect these are V3 Modbus register mismatches since commands work but reading certain capabilities fails. Storage capability is set to 5.12 kWh in device settings.
Could you check if registers for firmware version, stored energy and alarm status differ on V3 (v149) vs V2?
I’m planning to connect my VenusE 2.0 (firmware v158.1) via a Chinese RS485-to-Ethernet converter (similar to Waveshare). I know DR134 doesn’t work (RTU/ASCII over TCP).
Does Waveshare work if configured in “Modbus TCP Gateway” mode?
What exact Work Mode setting is needed?
Is Elfin EW11 the safest choice, or does any proper Modbus TCP gateway work?
The modbus registers arn’t document so, checking is a problem. I don’t own a v3 myself so playing with the storm of bad test results on the internet I can not do.
In theory every converter should work as long as they do pure modbus tcp not any wrapper so like http or json or mqtt etc