Ok, so this seems not related to my Venus E v2 setup ...

investigating goes on

Sure,
I ran nmap against the IP of the battery and checked port 30000 ... As network person I call this UDP/30000 ...
nmap -sU-sV 192.168.0.155 -p 30000
Starting Nmap 7.98 ( https://nmap.org ) at 2026-02-18 22:10 +0100
Nmap scan report for marstek-bat (192.168.0.155)
Host is up (0.024s latency ...

yes, I did a full scan

I finally had time to fully reboot my Venus v2 battery ... (need to disconnect RS485 connection because that one keeps the battery ON ...)
1 disconnected rs485
2 tested on udp/30000, still timeouts, no luck
3 tried to disable API thru the ap, no luck, gives a configuration error.
4 power down the ...

Meanwhile I updated my plugin to 1.0.4

I tried to power down my Venus E v2 but after holding the powerbutton for about 10sec it powersdown and immediatly powers up again ...

Still no luck

Need more time for this.
I tried to disable local api and that gives an error ...
still no ears on 30000/udp

Is it neccesary to reboot the Venus after enabling local api ?
I did enable it a while ago but perhaps it did not reboot after that

- yes I can ping it ...
Venus E (MST_ACCP_3393)
V153
Local API enabled
I can read it with https://rweijnen.github.io/marstek-venus-monitor/latest/
⚡ Runtime Information [19:53:54]
Backup Power: 0 W
Battery Power: 0 W
Work Mode: 1 (Standby)
Status Flags B/C/D: 1/1/1 (0x01/0x01/0x01)
📡 Connections ...

Yes,
I am pretty sure I entered the corrext IP ...

The test code gives me the same results ...
Timeouts

Although I enabled local API on port 30000 I get timeouts ....

Timeout waiting for response from 192.168.0.155:30000

Alle devices are created, none is updated ...

Should work for the Venus E since it is the same API. I already had a MQTT broker running so I slightly adapted the bridge installation to use the existing broker. But I think the plugin will not use the MQTT broker, it will just use the API functions. I will publish on github once available ...

@willemd I am interested and would like to see if this also works on a Marstek Venus E, as we are able to enable that api port there to ...
I looked at that github page but I dont like the idea of the api poller and the mqtt in one container ...

I hope someone will create a domoticz plugin for this, I am not a python programmer...
If someone does, I would be happy to test

Marstek released a new version of there App which allows us the enable OpenAPI
in the App there is a link to the documentation,

see https://resource.marstekenergy.com/ems/ ... penApi.pdf

Anyone tested this and was able to get this into domoticz ?

Can you please post de DR134.json and the mqttmapper.json you used ?

tnx Walter, I will look into the battery communication for a counter ...
Until now I did not find a "inc/decreasing" counter ...

I actually want just a device graph with real time updates (every minute or every 5 min is fine)

I tried the calculations but none of them work

newEnergy = P1.actualWatt - P1.usageDelivered + solarEnergy.actualWatt + battery.actualWatt
updateEnergy(usageReal, newEnergy )
newElectricity = P1 ...

Hi,

I am trying to create a graph over the total "real" energy used in my house.
The energy dashboard allready displays this but I can not get it to work in a separate device.
So, I want to have a "device" that contains history of the "home" circle in this graph, is that possible as addition ?
OR ...

the above compose.yaml for dockge works on rpi5

I am using the modbus-proxy.yml below to test
devices:
- modbus:
url: 192.168.0.10:1502
listen:
bind: 0:1502
logging:
version: 1
formatters:
standard:
format: "%(asctime)s %(levelname)8s %(name)s: %(message)s"
handlers:
console:
class ...

needed to modify the compose.yaml a bit to run in dockge on my rpi5

services:
modbusproxy:
build: https://github.com/tiagocoutinho/modbus-proxy.git
container_name: modbusproxy
restart: unless-stopped
ports:
- 1502:1502
volumes:
- /opt/stacks/modbusproxy/:/config/
networks: {}

seems to ...