I uses only local communication, no cloud. So you have to enable local API on your batteries through the app. Every device can auto-discover on your network if all is configured right.
It supports reading data from the batter and meter and also setting the charge mode and depth of discharge through flows.
I’m using V153. It just keeps polling for a succesful state within your set timeframe. If it can’t get it, it will retry every 2 seconds and fail gracefully. For ‘set’ commands I use an exponential back-off strategy: retry up to 5 times with exponential backoff (2s, 5s, 10s, 30s) before giving up.
For a few days now it’s running very stable. The only thing that’s variable is when you get data, the battery is in charge of that because either it fails or succeeds. Which in my case results in fresh data every sub 1-minute, almost every time within 30 seconds, which I have set my polling interval to.
I’m sorry I had to pull my app from the official store. They don’t think it’s unique enough and encourage me to implement the CT003 into the existing app.
I personally don’t like the existing app(s) because of the mentioned unstability, and I don’t really have the time to work together with somebody to get this done. So I pulled my app, you can installed it custom through my Github page: https://github.com/b03tz/HomeyMarstek but Homey doesn’t want me to publish it here in the store.