After the recent firmware update to 148.something, it is possible to set charge and discharge to 1500 on my Venus A. But when I do so, there’s a short moment of charging/discharging, and then it stops.
I’ve set (dis)charging back on 1200, and that is working a little bit better, but the (dis)charging also stops after a view minutes…
I also have problems after switching to 148. Normally i use self initiated. But now it switches automatically to manual. Also need to enable local api again en switch to 2500w . 147 had no issues before. Pfff
i also have the same problem that it switches back to manual, also daily charge and discharge values are the same as monthly values, after 00:00 hour the values shows zero but ten minutes later it shows again monthly values also the internal clock is not right, when i set charge time e.g. 11:15 it starts at 11:05, a factory reset did not change anything
Same issue here. Upgraded to 148 yesterday evening and the battery reverted to “manual” mode multiple times during the last 12h. Also the API is then disabled in the Marstek app settings. Since this morning I got it stable by changing the polling frequency to 240s. This used to be 120s in the past, without any issue. When lowering the polling to less than 100s, it almost instantly changes the mode to manual and disables API integration. Please share any thoughts or news.
My 0,500 Euro: it looks as the API is changed with the new version. Giving the Homey-app read-only access made things stable - at least for me.
hi @airw0lf , thank you for your reply.
How did you manage to give homey-app read-only access?
What polling interval are you using?
Hi @Elmar Elmar, mine is doing the Same, but It changes the output power to 2500watt instead of 800w, which for my situation isn’t even allowed because the battery isn’t on a separate power circuit.
It looks like the output power is toggled. Yours reverts from 2500 to 800 and mine does the opposite.
I have installed the Marstek app on a Chromebook and created a new user.
I then used the Marstek app on the foon to share the devices with this user in viewer mode.
This user was then used for adding the devices in Homey based on the cloud connection.
When using the cloud connection there is no poll interval.
Hi everyone, I’d like to know of you’re experiencing issues too, using the API integrarion? The flows I had behave unreliable and the battery keeps reverting to manual mode repeatidly. Earlier this week, the battery even appeared to be an a state where WiFi and CT was disconnected and I needed to reset the battery through the Marstek app. Does anyone experience the Same issues? Since few Days I’m using the cloud connector and having No issues. Downside is the lack of commands that control the battery through the flows I like to use.
Many thanks for sharing.
@eniewold@eniewold, any thoughts on What changed in the API?
I notice with v148 when I disable the local API its all working as expected but when enabling the local API it keeps witching to manual mode randomly. even when I disabled all homey cards just to be sure its not homey who is doing this.
Thank you for this test, that saves me a lot of debugging 
As reported by Elmar below, it seems to be an internal issue. I would recommend that you report this issue to Marstek, since they are the only ones that can fix this…
This is an issue with the firmware, they are no longer reporting all data as expected. Report back to Marstek that the ‘ES.GetStatus’ call is no longer reporting data in their local API. Without that data, the Homey app is not able to display anything.
I’ve not seen any API commands to control the LED’s in their documentation…
I’ve noticed a new revision (2.0) of the API documentation. Perhaps it was available a bit longer, but i’ve not found any official channels for these types of announcements. Additionally, I was unable to find details on what model+firmware uses what revision.
Anyway, i’ve done a comparison between two two versions, and none of the currently used calls have changes that should affect the Homey Marstek Connector. Results of compare:
It seems the new version of the API is able to control the led on the device. I don’t know how to check if your firmware has these capabilities…
I’ve release a new TEST version of the Marstek Venus Connector app. I’ve added support for the API v2.0 ‘UPS’ mode and LED control commands. These are new flow cards. The latest SDK and security updates have also been applied.
Let me know if these new flow cards are working and what SDK version you have, so that we can somehow document the API capabilities and firmware versions…
Thnx for the update!
In my situation, the Local API gives the wrong firmware version. I still need to test the new flow cards, but I will do that at a later time.
Question: is it also possible to add all the flow cards to the cloud devices? Because the Local API is still a mess (from Marstek side with a V3)
The Cloud API does not have any control commands that I know of, it seems to be read only. Additionally, there is no official documentation available (at least, at the time of implementation). To be clear; they are two completely different API’s each with a unique set of commands and different implementation in Homey.
Hopefully Marstek is able to get the firmware sorted, but it seems they keep having problems with the Local API communication. I’ve tried to contact them a few times for dialogue, but never get any response… I recommend to keep contacting them individually to keep pressure on their firmware development efforts.
Can I also fully control the battery Venus, via Marstek Cloud and this Homey app, when I have the Venus at my parents house, and I in another house have my Homey setup?
