Support: EVCC

Alles rund um SoC (Ladezustand des Fahrzeuges). Probleme, Fragen, Fehlfunktionen gehören hier hin
Bubbagump
Beiträge: 70
Registriert: Sa Jul 25, 2020 10:52 am

Re: Support: EVCC

Beitrag von Bubbagump »

Nissan hat die API geändert, siehe

https://github.com/evcc-io/evcc/issues/13941
9,86 kWp PV, SMA STP 10, SHM 2.0
Nissan Leaf Ze1 N-connecta mit 40 kWh Akku
OpenWB Series2 Standard+
andig
Beiträge: 309
Registriert: Fr Sep 13, 2019 9:24 am

Re: Support: EVCC

Beitrag von andig »

Nissan soeben behoben, in 10min sollte es wieder klappen.
Oeffly
Beiträge: 49
Registriert: Mo Mär 07, 2022 9:35 am

Re: Support: EVCC

Beitrag von Oeffly »

leider auch bei Audi und VW bekome gerade auch keine SOC bei der OpenWB angezeigt.....

Version 2.1.4. Beta 2 und auch nun RC2

folgende Log-Eintrag:

Code: Alles auswählen


2024-05-18 16:41:03,486 - {modules.common.fault_state:49} - {ERROR:fetch soc_ev1} - EVCC: FaultState FaultStateLevel.ERROR, FaultStr <class 'grpc.RpcError'> (<_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:03.482144813+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>,), Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 71, in fetch_soc
    response = stub.SoC(
  File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1160, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1003, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:03.482144813+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
    car_state = self._get_carstate_by_source(vehicle_update_data, source)
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 110, in _get_carstate_by_source
    return self.__component_updater(vehicle_update_data)
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/soc.py", line 16, in updater
    return fetch_soc(vehicle_config.configuration, vehicle_update_data, vehicle)
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 86, in fetch_soc
    raise grpc.RpcError(rpc_error)
grpc.RpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:03.482144813+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

2024-05-18 16:41:04,802 - {modules.common.fault_state:49} - {ERROR:fetch soc_ev2} - EVCC: FaultState FaultStateLevel.ERROR, FaultStr <class 'grpc.RpcError'> (<_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:04.796329376+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>,), Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 71, in fetch_soc
    response = stub.SoC(
  File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1160, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1003, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:04.796329376+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
    car_state = self._get_carstate_by_source(vehicle_update_data, source)
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 110, in _get_carstate_by_source
    return self.__component_updater(vehicle_update_data)
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/soc.py", line 16, in updater
    return fetch_soc(vehicle_config.configuration, vehicle_update_data, vehicle)
  File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 86, in fetch_soc
    raise grpc.RpcError(rpc_error)
grpc.RpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNKNOWN
	details = "vehicle not available"
	debug_error_string = "UNKNOWN:Error received from peer  {created_time:"2024-05-18T16:41:04.796329376+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

PV 1: 13,4 kWp
PV 2: in Planung (16,4 kWp)
Hausakku: E3DC S10 Pro
WB 1: openWB series2 custom
WB 2: openWB series2 custom
BEV 1: VW ID.3
BEV 2: AUDI Q4
andig
Beiträge: 309
Registriert: Fr Sep 13, 2019 9:24 am

Re: Support: EVCC

Beitrag von andig »

Mhhm. Bitte mal im Forum einen Thread eröffnen und mrhinas mit rein nehmen. Bei mir geht das mit der Cloud:

Code: Alles auswählen

gor main.go vehicle --log trace,db:error --log-headers -c cfg/audi.yaml
[main  ] INFO 2024/05/19 11:03:21 evcc 0.0.0
[main  ] INFO 2024/05/19 11:03:21 using config file: cfg/audi.yaml
Soc:      30%
Capacity: 0.0kWh
Features: []
Bubbagump
Beiträge: 70
Registriert: Sa Jul 25, 2020 10:52 am

Re: Support: EVCC

Beitrag von Bubbagump »

andig hat geschrieben: Sa Mai 18, 2024 10:36 am Nissan soeben behoben, in 10min sollte es wieder klappen.
kann ich bestätigen, allerdings erst nachdem ich zum zweiten Mal in einer Woche evcc erneut als SOC Modul gespeichert habe und zuvor ein anderes Modul kurz ausgewählt hatte.
9,86 kWp PV, SMA STP 10, SHM 2.0
Nissan Leaf Ze1 N-connecta mit 40 kWh Akku
OpenWB Series2 Standard+
Oeffly
Beiträge: 49
Registriert: Mo Mär 07, 2022 9:35 am

SoC-modul "EVCC" Wert wird mit 0% angezeigt

Beitrag von Oeffly »

hallo,

eit gestern Mittag ca. 12 Uhr wir der SOC von denn Autos was über Evcc ausgelesen wird nicht mehr angezeigt. Die Autos haben eine SoC von 0%.
in der App wird der richtige Wert angezeigt.

Version 2.1.4. Beta 2 und auch nun RC2

Log:

2024-05-19 14:55:05,846 - {modules.common.fault_state:49} - {ERROR:fetch soc_ev2} - EVCC: FaultState FaultStateLevel.ERROR, FaultStr <class 'grpc.RpcError'> (<_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-05-19T14:55:05.839882092+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>,), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 71, in fetch_soc
response = stub.SoC(
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1160, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1003, in _end_unary_response_blocking
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-05-19T14:55:05.839882092+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 110, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/soc.py", line 16, in updater
return fetch_soc(vehicle_config.configuration, vehicle_update_data, vehicle)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 86, in fetch_soc
raise grpc.RpcError(rpc_error)
grpc.RpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-05-19T14:55:05.839882092+02:00", grpc_status:2, grpc_message:"vehicle not available"}"
>

2024-05-19 15:03:23,663 - {modules.common.fault_state:49} - {ERROR:fetch soc_ev1} - EVCC: FaultState FaultStateLevel.ERROR, FaultStr <class 'grpc._channel._InactiveRpcError'> (<grpc._channel._RPCState object at 0x6ec4ee50>,), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 110, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/soc.py", line 16, in updater
return fetch_soc(vehicle_config.configuration, vehicle_update_data, vehicle)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 57, in fetch_soc
vehicle_to_fetch = create_vehicle(evcc_config, stub)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 33, in create_vehicle
response = stub.New(
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1160, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1003, in _end_unary_response_blocking
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "token is malformed: token contains an invalid number of segments"
debug_error_string = "UNKNOWN:Error received from peer {created_time:"2024-05-19T15:03:23.654680059+02:00", grpc_status:2, grpc_message:"token is malformed: token contains an invalid number of segments"}"
>

2024-05-19 15:03:24,942 - {modules.common.fault_state:49} - {ERROR:fetch soc_ev2} - EVCC: FaultState FaultStateLevel.ERROR, FaultStr <class 'grpc.RpcError'> (<_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"vehicle not available", grpc_status:2, created_time:"2024-05-19T15:03:24.937276108+02:00"}"
>,), Traceback:
Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 71, in fetch_soc
response = stub.SoC(
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1160, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/home/openwb/.local/lib/python3.9/site-packages/grpc/_channel.py", line 1003, in _end_unary_response_blocking
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"vehicle not available", grpc_status:2, created_time:"2024-05-19T15:03:24.937276108+02:00"}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 66, in update
car_state = self._get_carstate_by_source(vehicle_update_data, source)
File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 110, in _get_carstate_by_source
return self.__component_updater(vehicle_update_data)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/soc.py", line 16, in updater
return fetch_soc(vehicle_config.configuration, vehicle_update_data, vehicle)
File "/var/www/html/openWB/packages/modules/vehicles/evcc/api.py", line 86, in fetch_soc
raise grpc.RpcError(rpc_error)
grpc.RpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "vehicle not available"
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"vehicle not available", grpc_status:2, created_time:"2024-05-19T15:03:24.937276108+02:00"}"
>
2024-05-19_15h10_34.png
2024-05-19_15h10_34.png (8.96 KiB) 909 mal betrachtet
PV 1: 13,4 kWp
PV 2: in Planung (16,4 kWp)
Hausakku: E3DC S10 Pro
WB 1: openWB series2 custom
WB 2: openWB series2 custom
BEV 1: VW ID.3
BEV 2: AUDI Q4
Oeffly
Beiträge: 49
Registriert: Mo Mär 07, 2022 9:35 am

Re: Support: EVCC

Beitrag von Oeffly »

andig hat geschrieben: So Mai 19, 2024 9:04 am Mhhm. Bitte mal im Forum einen Thread eröffnen und mrhinas mit rein nehmen. Bei mir geht das mit der Cloud:

Code: Alles auswählen

gor main.go vehicle --log trace,db:error --log-headers -c cfg/audi.yaml
[main  ] INFO 2024/05/19 11:03:21 evcc 0.0.0
[main  ] INFO 2024/05/19 11:03:21 using config file: cfg/audi.yaml
Soc:      30%
Capacity: 0.0kWh
Features: []
okay... hab mal ein Software 2.0 einen Thread erstellt. Wie nehme ich jemanden dazu?
PV 1: 13,4 kWp
PV 2: in Planung (16,4 kWp)
Hausakku: E3DC S10 Pro
WB 1: openWB series2 custom
WB 2: openWB series2 custom
BEV 1: VW ID.3
BEV 2: AUDI Q4
andig
Beiträge: 309
Registriert: Fr Sep 13, 2019 9:24 am

Re: Support: EVCC

Beitrag von andig »

ping @mrhinas
ruffieuxh
Beiträge: 181
Registriert: So Jul 07, 2019 9:02 am

Re: Support: EVCC

Beitrag von ruffieuxh »

Hallo zusammen,

In welchem Logfile stehen eigentlich die Meldungen vom EVCC? Auch im openwb.log file?

Ich habe derzeit mit meinem Mustang Mach-e das gleiche Problem (0% SoC) aber mit der 1.9er SW.

Schöne Grüsse

Heinz
rleidner
Beiträge: 965
Registriert: Mo Nov 02, 2020 9:50 am
Has thanked: 5 times
Been thanked: 22 times

Re: Support: EVCC

Beitrag von rleidner »

ruffieuxh hat geschrieben: Mo Mai 20, 2024 8:41 am Hallo zusammen,

In welchem Logfile stehen eigentlich die Meldungen vom EVCC? Auch im openwb.log file?

Ich habe derzeit mit meinem Mustang Mach-e das gleiche Problem (0% SoC) aber mit der 1.9er SW.

Schöne Grüsse

Heinz
sollte im "EV SoC-Log" sein.
openWB-2 Standard+ | openWB EVU Kit v2 MID| 9,9kWp mit Kostal Plenticore 8.5 plus | VW ID.3, Kia EV6, Smart EQ forfour
Antworten