After several weeks of real-world testing across a handful of Marstek installations, I’m happy to share the first community-ready release of the Marstek Local API integration for Home Assistant.
Try it out
Grab the integration, wire it up to your batteries, and let me know how it runs in your setup. Please report issues or requests on GitHub so we can track them properly.
Looking forward to hearing how you put the “Marstek System” in action!
Good evening, the Marstek local API integration is causing disconnections between the Marstek Venus E battery and the CT002. How can this problem be resolved? Thank you.
This is a known issue. I had this happen when i polled the batteries too often. But the default of 60s seem to work fine. My batteries no rarely loose their connection. If they do a reset of my CT003 usually solves it. Not perfect. Hope Marstek comes with a solution.
Hi
When I look at the BLE Monitor it seems that Local API was eabled by default on Port 28417. But when I run the command to Disable it or Enable it with another Port nothing is changing. Did a Update from stock V122 to V139 today and have the same behaviour. Do you know what I can try?
I have the Venus E V3
Greetings
Update: Contacted support yesterday and got a response today that they activated it. I have an option in the app now to activate it and set the port and it works.
Most of the sensors are Unknown or incorrect for me. Battery % is correct. It says charging while discharging. Remaining capacity is also incorrect. Really pleased with the development but something is going wrong for me. The FW of the Marstek V3 is V139
It seems to have the same purpose. So maybe it would be a good idea to see how they can benefit from each other or maybe merge them with the best from both?
My Marstek Venus A will hopefully arrive in one or two weeks and I am really looking forward to integrate it into HA!
im kinda lost with using the services described in the git. only service visable for me is the request data. and im missing some statistics.
I copied and pasted an automation example that the developer provided (to set the system into passive mode)
However, when I go to create or edit the automation in Home Assistant, the action part (the service call or action entity) doesn’t appear in the list of available services
If I manually paste the YAML, the automation “runs” — but then the system (via Spook) complains that the action/service does not exist
Is something broken? I have just reinstalled it from HACS after two days of no connection. My battery connects okay to the CT, and to the (okay, not always accurate) app but HA cannot even see it anymore.
Same here - even after total reboot of HA and Marstek, no luck to get it installed and working again. (did work before - a bit).
Not sure what we can do …
I’m waiting for some updates. From the moment I enabled the API, my batteries continually lost connection to my CT002 3-phase meter, causing them to go into standby mode. This was a constant problem at first, but it finally resolved itself after the latest software update. Anyone else experiencing this problem?
Yes, I had this for a bit, but with a new app (Marstek, not HA) update it got fixed. At least, it’s more stable. I have 2 batteries, and one has the port open, the other not (so I can compare) and the issue actually was with both batteries, at first, then the one with the port open, then neither. So, something was fixed at Marstek HQ!
I continue to compare and contrast.
However, right now, post-re-install of the Marstek Local API, it doesn’t see the battery with the port open at all, and cannot connect via the (static) IP set by the router for that battery.
Me thinks the same, no (more) UDP connection possible after latest HA update.
Tested it, and the UDP 30000 port is adressable/open form outside (other test app), but within HA no more connection possible (’ device not found’ )
Hope this can be fixed (?)
Yes, that would be great, but if they insist on building it based on HAOS UDP then future HAOS updates will break it. Looking around the internet, it seems that HA UDP support is somewhat flaky. Like the Bluetooth implementation (not BLE, 't other Bluetooth).
So…
Maybe a UDP-WiFi bridge as an ESPHome device that uses MQTT to get/set Venus attributes/commands by delivering full-on JSON as payload in the same kind of way that the ESPHome Bluetooth Bridge Ready-Made Project works?
Leaves the logic in HA where it belongs, but removes the UDP dependency, which seems to break other implementations?
EDIT: Where I say “based on UDP” why not use Bluetooth for API access? It’s more stable and I think even used by app when it’s in range and I get much better results using the app locally than remotely. So, maybe there’s a general issue?
I dont know anything about python, but they are using classes like MarstekUDPClient, which looks like its a custom non-default-haos udp lib configured in py-marstek (py-marstek · PyPI).
Dont know if this helps or make things even more confusing
Really looking forward to get this running. I am receiving my three Venus E V3 soon. Will run them on three phases with the CT002. Lets see how that goes with your integration
