Set sensor values via API

[CommandoThanatos]

Would be great if it there would be a possibility to set the energy value of a sensor via the api.
Why? I own a smart home system which measures the production of a mini photovoltaic system via a "Fritz Schaltsteckdose" and there are also other devices which i would like to be recognized by the go-e controller anzeigen and to add them to kategories (like solar with valiues of the big pv and the mini pv) to show the real production for all systems and to add the mini pv to the overall consumption of the house.

[SIMULATAN]

Yes, absolutely.

As someone with the go-e controller and a DC battery, this is an absolute necessity.
(only AC batteries can be read, there is no possibility of reading DC ones - see the go-e magazine)
Without the ability to ingest power consumption and battery state from arbitrary sources, the controller unfortunately is useless in a lot of cases when it comes to excess charging.

A note regarding the implementation: it'd be great to implement the setters in the "PATCH"-style, as in, you can choose to update only a subset of the values. This would allow multiple sources writing data concurrently leading to further flexibility.
I'd personally choose MQTT as the leading protocol for these high frequency values as it's made for exactly this use case. Something similar to the go-e charger would be perfectly applicable.

Thanks for the otherwise great products!

[tom-mi]

So are there any updates on this @0xFEEDC0DE64 @erxbout ?
I currently have one charger in place which I feed via Homeassistant with realtime battery & power readings (which I get from my inverter). I bought a controller for load balancing, as I will install a second charger soon. I expected to be able to just point my automation to publishing to the controller, but as this doesn't seem to work, I'm quite disappointed now that

1. I actually would have to connect the sensors of the controller (even though my inverter already provides all the values collected via it's own sensors)
2. I would miss the battery data

So using the controller in its current state would be a downgrade regarding data quality, but seems necessary to get some sort of proper load balancing working (?)

[tom-mi]

Ok ich nehme alles zurück und behaupte das Gegenteil - I think I got it working (not tested with real car yet) using the instructions in this comment
#14 (comment)
and publishing that 16-element array via MQTT to .../ecp/set.
There is this caveat though
#14 (comment)

Please note that this might break if the position of the battery power changes because of a firmware update or other changing settings so fetching the index before via 'ccn' would be better practice as stated in my clarification

That would be much more complex than just using the builtin mqtt publish action in Homeassistant. I'd love to see

• this to be documented somewhere :)
• an API similar to the one for the charger (sending a dict / object instead of a "magic" array)

[SvenAbels]

I totally agree with this suggestion. - Especially for DC battery status delivery

[norcon]

It would be great to set pGrid, pSolar, pAkku, … via MQTT or other APIs like in Charger API

[0xFEEDC0DE64]

The next firmware release will have the energy counters writable on the go-e controller

[norcon]

Not available in 1.0.8 Beta right?
Tested with Mqtt:
unknown api key: ids

[mi-hol]

The next firmware release

With missing documentation for MQTT as noted in #3 how can the advertised MQTT feature be used/tested?

[erxbout]

Protocoll for using mqtt is the same as https://github.com/goecharger/go-eCharger-API-v2/blob/main/mqtt-en.md
The api keys for the controller are here https://github.com/goecharger/go-eController-API/blob/main/apikeys-en.md

I´ll update the documentation as soon as possible and also add mqtt docs to controller repo

[mi-hol]

I´ll update the documentation as soon as possible

Just to be sure, by above do you mean to resolve "TODO for go-e: Document the topics for reading/writing."?

[JaroRobo3000]

It would also be very good if, instead of the sensor inputs for measuring the individual phases, it were possible to make these values writable via the API, for example, to make them "isv" writable. I have a Victron system with an energy meter, but it is connected to the GX device via USB. So I would have to transfer the values via Node Red.

[norcon]

Same here!