The HTTP API is wonderful! Just why are some settings only available via the app?

[kolAflash]

At first let me say, that the HTTP API on the go-e Charger is a great feature!!!
I can't say this loud enough. It's the reason why I decided to buy a go-e Charger flex!!!

It's such a good feature, I'm actually thinking about building a nice HTML+JS user interface for the API. If I find time for that I'll publish that it as open source :-)

 

But why are not all settings from the app available in the HTTP API???

For example the country setting and the one phase ampere limit.
And why is the HTTP API not enabled by default and has to be activated via the app?
Are there legal restrictions because of which those settings can't be available via the HTTP API?

I really like to encourage the go-e company to continue this way of openness via customer accessible APIs! It's my experience, that products usually profit from openness. Because users start to develop great additional tools for the product. Those tools can increase the products benefit for everyone. And by this the sales volume of the product will be increased too.
You could even go a step further and publish the firmware itself as open source. It's what WARP2 and openWB already do. Unfortunately the WARP2 and openWB are not available as mobile solutions, because of which I decided for a go-e Charger flex ;-)