@eniewold the cloud connection looks more stable but is it possible to create some new flow Cards to Change the State of the battery is dit possible with the Cloud connection
The Marstek Cloud API does not have any mode change commands, so currently not possible…
But… I’m currently testing a new update that allows you to configure the local API polling for battery status. This allows you to read the status from the cloud device and send commands to the battery with much less change in breaking the local API. If you turn off polling on all battery devices; local API communication is basically stopped, until you send a command.
1 Like
This is the most common problem reported! Unfortunately this can only be fixed by Marstek…
I’m working on a new version with more configuration for polling, like interval (seconds wait between messages). Perhaps it will help a little. The new version also allows you to turn polling of altogether.
@eniewold that sounds great because the ai implementation of Marstek is currently broken after changing to 15 min prices (by Nordpool) by dynamic tariff. With your implementation, I can change the status of the battery with the dynamic tariff of Homey itself.
I’ve released a new TEST version that allows you to enable/disable polling for devices and set the poll interval. Please try and disable polling for all devices to minimize UDP communication. Then use flows to set the mode of the battery.
2 Likes
Het is me 1 keer gelukt de Marstek toe te voegen via scannen, daarna nooit meer. En had hem helaas gewist… Aangezien je enkel via de API manier de sturing kan regelen wil ik die graag terug werkende 
Nu merk ik op dat als ik mijn wifi netwerk ga scannen met een IP scanner ik hem ook niet zie. Echter kan ik via de BLE tool wel alle info opvragen en het IP achterhalen. Dit is ook te pingen.
concreet: is er een manier waarop ik hem manueel door het IP in te geven kan toevoegen?
Unfortunately if the battery is not responding to the discovery requests, it will also not respond to any other data request, so manually adding it does not help. Additionally, if the battery IP address is resolved through DHCP, manually configured addresses will break when a new lease is given.
But when you ‘System Reset’ the battery using the BLE tool, both discovery and data polling will start working again (see troubleshooting). This reset will take no longer than a minute and does not disrupt the battery configuration, only the power delivery will be stopped for a few seconds (also on backup port).
Hi @eniewold, where can I find the test version?
I keep links to the latest TEST and latest PRODUCTION versions up-to-date in the topic start post, at the end of the read-me. In case you missed it, the latest TEST version can be found here: Marstek Connector TEST.
1 Like
“Maybe I’m doing something wrong, but has anyone here managed to control the batteries via a flow?! I do see the correct flow cards and when manually executed it runs, but the battery mode is not changed.”
I’m very interested in exploring the possibilities of the app to control my Marstek V3. I’ve activated the local API and added it to Homey, but no data is coming through. I understand that others are experiencing the same issue. I’m using a VenusE 3.0 v122. Thanks in advance for the developer’s work!
If resetting the battery does not help (see troubleshooting) can you enable debugging (settings of battery device) and send a diagnostics report through Homey please? Perhaps the logs can explain somehting for VenusE v3…
1 Like
I performed a reset using the BLE tool. However, no data is coming through. I have enabled the debugging checkbox. 1467db49-8cbd-465f-a66e-1d2dcfe17f5b
There is a bug in the cloud part of the app: If the email address you used for subscribing to Marstek includes a + sign (like used for aliases on your gmail account) it will fail to login.
However, when i used ‘%2B’ instead of ‘+’ it worked, so it seems to be an escaping issue.
Hi Eniewold, currently added 3 Marstek Venus E 3.0. This went ok but I can’t get any data out of it. Not sure if its related to the UDP3000 port (which I set in the BLE tool) API is enabled but stays on 28418 also after changing. Diagnostics report: 686b5d0a-86cd-4b37-aabe-35467708be64.
I did some additional checks, seems when playing with the flows I can switch between states (ie Manual or AI mode) so connection in that sense seems to work.
same thing here!
Thank you for the report, it seems the Venus E 3.0 does not react well to the broadcast messages from the Homey App. I have not tested on Venus E 3.0 since I don’t own this version of the device. I can’t find any difference in the API documentation, so I will try to investigate other local API software solution to see if there are differences.
I’m not sure how to test changes, but perhaps I will add some debugging. If I have a TEST version of the Homey App, can I ask you to install that and send a diagsnostics report again?
1 Like
Thank you for the details; I will try and fix the escaping!
Sure sounds 
. Thanks a lot for the effort!
