marq24
commented
3 months ago Hi,
as I tried to explain in your additional discussion https://github.com/marq24/ha-goecharger-api2/discussions/3 the integration provide the data as it was read from the wallbox.
I fully agree with you that it looks like the data the wallbox providing for the three mentioned sensors are not plausible. I have updated the documentation in order to explain the functionality (theory of operation) of this integration a bit more and added information how you can check, if the source of information already providing none-plausible data:
2. In case of implausible data
It will happen, that the data that is displayed by this integration does not make much sense (to you) - aka 'the data is not plausible'. Of course it could be the case, that something in this integration has been messed up - but so far - in all reported issues the root cause of implausible data was/is, that the go-eCharger device itself already provided this data [you can check this by directly requesting the attribute from the wallbox]
Each sensor of this integration have an API-Key identifier in its entity ID. You can manually request values from your wallbox by using this API key via a regular web browser.
E.g. assuming the value of the sensor in question is sensor.goe_123456_tpa and your wallbox is reachable via the IP 192.168.22.10, then you can request/read the 'original' value via the following link (where tpa is the API key):
http://192.168.22.10/api/status?filter=tpa
so the pattern is:
http://[wallbox-ip]/api/status?filter=[API-KEY]
If the plain data that will be returned in such a request is matching the data displayed by the integration, then I would kindly ask t get in contact with go-eCharger, since in such a case the integration is just the 'messenger'.
karliwalti
Checklist
Add a description
Three fields of the Diagnostic fields seem to be non-functional. They increase linearly or stepwise over time, despite the system running. These are sensor.goe_259493_inva sensor.goe_259493_lmsc sensor.goe_259493_lpsc
button.goe_259493_rst will be the only way to reset the "counters"
I would expect that sensor.goe_259493_inva and sensor.goe_259493_lpsc oscillate around 5s when PV is running and linearly increase when not. sensor.goe_259493_lmsc should reset at a status change.
Log below likely also contains other issues, but will report in separate issue.
Add your DEBUG log output