search

cathiele / homeassistant-goecharger

Home Assistant custom_component for controlling the go-eCharger EV-Charger
MIT License
89 stars 29 forks source link

Fetching data problem after upgrading firmware to 051.3 #44

Closed arboeh closed 2 years ago

arboeh commented 3 years ago

Before upgrading go-e firmware to 051.3 everything worked fine for me. I get the following error now (restart of go-e before) after a few minutes constantly:

Logger: custom_components.goecharger Source: helpers/update_coordinator.py:193

Timeout fetching goecharger data

WIFI is connected with 50% signal strength. Local HTTP API v1 is activated. Home Assistant core is 2021.9.3

cathiele commented 3 years ago

my V2-Hardware charger just supports firmware 0.41. so i can not reproduce this bug.

is this the only logoutput that you get from home-assistant?

arboeh commented 3 years ago

I read something in an openHAB forum about completely turn off power by fuses. I will give it a try. Seems to be a timeout problem of go-eCharger and not of the integration.

arboeh commented 2 years ago

Wasn't the problem. Still getting timeout error:

ERROR (MainThread) [custom_components.goecharger] Timeout fetching goecharger data WARNING (MainThread) [homeassistant.components.input_select] Invalid option: 0 (possible options: 6, 8, 10, 12, 14, 16)

Btw: Casted input values to int and float. Makes no difference.

JSON-"status"-response looks good for me, so switching to rest-call would work:

{ "version":"B", "tme":"0809210624", "rbc":"62", "rbt":"30724", "car":"1", "amx":"6", "amp":"6", "err":"0", "ast":"0", "alw":"1", "stp":"0", "cbl":"0", "pha":"56", "fsp":"0", "tma":[ 23.625, 28 ], "dws":"0", "dwo":"150", "adi":"1", "uby":"0", "eto":"127", "wst":"3", "fwv":"051.3", "nrg":[ 228, 231, 229, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "sse":"XXXXXX", "wss":"XXXXXX", "wke":"********", "wen":"1", "cdi":"0", "tof":"101", "tds":"1", "lbr":"100", "aho":"0", "afi":"6", "azo":"1", "ama":"16", "al1":"6", "al2":"10", "al3":"12", "al4":"14", "al5":"16", "cid":"255", "cch":"16750080", "cfi":"65280", "lse":"1", "ust":"0", "wak":"********", "r1x":"2", "dto":"0", "nmo":"0", "sch":"AAAAAAAAAAAAAAAA", "sdp":"0", "eca":"0", "ecr":"0", "ecd":"0", "ec4":"0", "ec5":"0", "ec6":"0", "ec7":"0", "ec8":"0", "ec9":"0", "ec1":"0", "rca":"1", "rcr":"", "rcd":"", "rc4":"", "rc5":"", "rc6":"", "rc7":"", "rc8":"", "rc9":"", "rc1":"", "rna":"User 1", "rnm":"User 2", "rne":"User 3", "rn4":"User 4", "rn5":"User 5", "rn6":"User 6", "rn7":"User 7", "rn8":"User 8", "rn9":"User 9", "rn1":"User 10", "loe":0, "lot":32, "lom":6, "lop":50, "log":"", "lof":0, "loa":0, "lch":0 }

thesebastianf commented 2 years ago

This was probably a Bug in 51.3 There is 51.4 now and the Connection works again.

cathiele commented 2 years ago

@arboeh can you confirm that it works for you with 51.4?

arboeh commented 2 years ago

@cathiele: Works for me now. I migrated some entities to v2 in the meanwhile :-D Btw: Is there a complete documentation for API v2? Im thinking about to write an integration for it.

cathiele commented 2 years ago

i am not aware of any API v2 documentation. what is the advantage of using v2? does it provide more attributes? the v2 support can be discused in #40