Rückmeldungen 2.1.2 Beta 3

Fragen zur Nutzung, Features, usw..
MatzeL
Beiträge: 49
Registriert: Mi Mai 17, 2023 6:58 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von MatzeL »

Der SoC des Victron Hausspeichers wird nach dem Update von Beta2 auf Beta 3 falsch angezeigt. Statt 36% werden 54% angegeben.

Nach dem Neustart der openWB wurden die Daten korrekt dargestellt. Main Log wurde gesichert.
PV: Fronius Symo Speicher: Victron Auto: Skoda Enyaq mit ME3.6

openWB Pro + openWB Standalone mit Display
ChristianM
Beiträge: 166
Registriert: Di Okt 22, 2019 9:42 am

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von ChristianM »

diese Meldung erscheint beim Laden von Zeit zu Zeit für 2-5 Sekunden und verschwindet wieder.
IMG_5643.png

Code: Alles auswählen

2023-11-18 14:18:13,758 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:183} - {DEBUG:Internal Chargepoint} - ***Start***
2023-11-18 14:18:13,761 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:185} - {DEBUG:Internal Chargepoint} - {'cp0': InternalChargepoint(data=InternalChargepointData(cp_interruption_duration=0, parent_cp='5', phases_to_use=3, set_current=0, trigger_phase_switch=False), get=Get(charge_state=False, currents=[0.0, 0.0, 0.0], evse_current=0, exported=0, fault_str='Kein Fehler.', fault_state=0, imported=2678980.96, phases_in_use=0, plug_state=False, power=0, rfid_timestamp=None, rfid=None, voltages=[235.41, 235.85, 238.01])), 'cp1': InternalChargepoint(data=InternalChargepointData(cp_interruption_duration=0, parent_cp='6', phases_to_use=3, set_current=0, trigger_phase_switch=False), get=Get(charge_state=False, currents=[0.0, 0.0, 0.0], evse_current=0, exported=0, fault_str='Kein Fehler.', fault_state=0, imported=7027228.52, phases_in_use=0, plug_state=False, power=0, rfid_timestamp=None, rfid=None, voltages=[238.09, 235.3, 235.47])), 'global_data': GlobalHandlerData(heartbeat=1700313490, parent_ip='localhost', configured=True), 'rfid_data': RfidData(last_tag='')}
2023-11-18 14:18:13,766 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-11-18 14:18:14,315 - {modules.common.evse:43} - {DEBUG:Internal Chargepoint} - Gesetzte Stromstärke EVSE: 0, Status: 1, Modbus-ID: 1
2023-11-18 14:18:14,316 - {modules.common.store._api:26} - {DEBUG:Internal Chargepoint} - Raw data ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[235.10336303710938, 235.52474975585938, 238.11148071289062], frequency=49.90439987182617, imported=2678980.95703125, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:14,317 - {modules.common.store._api:30} - {INFO:Internal Chargepoint} - Saving ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[235.10336303710938, 235.52474975585938, 238.11148071289062], frequency=49.90439987182617, imported=2678980.95703125, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:14,348 - {modules.common.store._api:26} - {DEBUG:Internal Chargepoint} - Raw data ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[235.10336303710938, 235.52474975585938, 238.11148071289062], frequency=49.90439987182617, imported=2678980.95703125, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:14,352 - {modules.common.store._api:30} - {INFO:Internal Chargepoint} - Saving ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[235.10336303710938, 235.52474975585938, 238.11148071289062], frequency=49.90439987182617, imported=2678980.95703125, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:14,358 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:241} - {DEBUG:Internal Chargepoint} - Published plug state False
2023-11-18 14:18:14,436 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:93} - {DEBUG:Internal Chargepoint} - Values from parentWB: InternalChargepointData(cp_interruption_duration=0, parent_cp='5', phases_to_use=3, set_current=0, trigger_phase_switch=False)
2023-11-18 14:18:14,437 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 0']
2023-11-18 14:18:14,471 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 1']
2023-11-18 14:18:15,144 - {modules.common.evse:43} - {DEBUG:Internal Chargepoint} - Gesetzte Stromstärke EVSE: 0, Status: 1, Modbus-ID: 2
2023-11-18 14:18:15,145 - {modules.common.store._api:26} - {DEBUG:Internal Chargepoint} - Raw data ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[237.88046264648438, 235.27760314941406, 235.96640014648438], frequency=49.90107727050781, imported=7027228.515625, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:15,146 - {modules.common.store._api:30} - {INFO:Internal Chargepoint} - Saving ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[237.88046264648438, 235.27760314941406, 235.96640014648438], frequency=49.90107727050781, imported=7027228.515625, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:15,171 - {modules.common.store._api:26} - {DEBUG:Internal Chargepoint} - Raw data ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[237.88046264648438, 235.27760314941406, 235.96640014648438], frequency=49.90107727050781, imported=7027228.515625, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:15,175 - {modules.common.store._api:30} - {INFO:Internal Chargepoint} - Saving ChargepointState(currents=[0.0, 0.0, 0.0], powers=[0.0, 0.0, 0.0], voltages=[237.88046264648438, 235.27760314941406, 235.96640014648438], frequency=49.90107727050781, imported=7027228.515625, exported=0, power=0, phases_in_use=0, charge_state=False, plug_state=False, rfid=, power_factors=[1.0, 1.0, 1.0], soc=None, soc_timestamp=None, evse_current=0)
2023-11-18 14:18:15,181 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:241} - {DEBUG:Internal Chargepoint} - Published plug state False
2023-11-18 14:18:15,241 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:93} - {DEBUG:Internal Chargepoint} - Values from parentWB: InternalChargepointData(cp_interruption_duration=0, parent_cp='6', phases_to_use=3, set_current=0, trigger_phase_switch=False)
2023-11-18 14:18:15,243 - {modules.common.component_context:24} - {DEBUG:Internal Chargepoint} - Update Komponente ['Ladepunkt 1']
2023-11-18 14:18:16,372 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:183} - {DEBUG:Internal Chargepoint} - ***Start***
2023-11-18 14:18:16,376 - {modules.internal_chargepoint_handler.internal_chargepoint_handler:185} - {DEBUG:Internal Chargepoint} - {'cp0': InternalChargepoint(data=InternalChargepointData(cp_interruption_duration=0, parent_cp='5', phases_to_use=3, set_current=0, trigger_phase_switch=False), get=Get(charge_state=False, currents=[0.0, 0.0, 0.0], evse_current=0, exported=0, fault_str='Kein Fehler.', fault_state=0, imported=2678980.96, phases_in_use=0, plug_state=False, power=0, rfid_timestamp=None, rfid=None, voltages=[235.1, 235.52, 238.11])), 'cp1': InternalChargepoint(data=InternalChargepointData(cp_interruption_duration=0, parent_cp='6', phases_to_use=3, set_current=0, trigger_phase_switch=False), get=Get(charge_state=False, currents=[0.0, 0.0, 0.0], evse_current=0, exported=0, fault_str='Kein Fehler.', fault_state=0, imported=7027228.52, phases_in_use=0, plug_state=False, power=0, rfid_timestamp=None, rfid=None, voltages=[237.88, 235.28, 235.97])), 'global_data': GlobalHandlerData(heartbeat=1700313490, parent_ip='localhost', configured=True), 'rfid_data': RfidData(last_tag='')}
2023-11-18 14:29:56,875 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 12
2023-11-18 14:29:56,933 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
    raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
    plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
  File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
    set_current, _, state_number = self.client.read_holding_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
    return self.__read_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
    raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 240, in update
    state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
    raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)

2023-11-18 14:37:19,691 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 12
2023-11-18 14:37:19,739 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 0: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
    raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
    plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
  File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
    set_current, _, state_number = self.client.read_holding_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
    return self.__read_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
    raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 240, in update
    state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
    raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)

2023-11-18 14:43:32,856 - {modules.common.evse:57} - {DEBUG:Internal Chargepoint} - FW-Version: 12
2023-11-18 14:43:32,905 - {modules.common.fault_state:55} - {ERROR:Internal Chargepoint} - Ladepunkt 1: FaultState FaultStateLevel.ERROR, FaultStr modules.internal_chargepoint_handler.chargepoint_module <class 'modules.common.fault_state.FaultState'> ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>), Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 90, in __read_registers
    raise FaultState.error(__name__+" "+str(response))
modules.common.fault_state.FaultState: ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 80, in get_values
    plug_state, charge_state, self.set_current_evse = self.__client.evse_client.get_plug_charge_state()
  File "/var/www/html/openWB/packages/modules/common/evse.py", line 39, in get_plug_charge_state
    set_current, _, state_number = self.client.read_holding_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 123, in read_holding_registers
    return self.__read_registers(
  File "/var/www/html/openWB/packages/modules/common/modbus.py", line 105, in __read_registers
    raise FaultState.error(__name__+" "+str(type(e))+" " +
modules.common.fault_state.FaultState: ("modules.common.modbus <class 'modules.common.fault_state.FaultState'> ('modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/internal_chargepoint_handler.py", line 240, in update
    state = self.module.get_values(phase_switch_cp_active, rfid_data.last_tag)[0]
  File "/var/www/html/openWB/packages/modules/internal_chargepoint_handler/chargepoint_module.py", line 125, in get_values
    raise FaultState.error(__name__ + " " + str(type(e)) + " " + str(e)) from e
modules.common.fault_state.FaultState: ('modules.internal_chargepoint_handler.chargepoint_module <class \'modules.common.fault_state.FaultState\'> ("modules.common.modbus <class \'modules.common.fault_state.FaultState\'> (\'modules.common.modbus Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 2 bytes (0 received)\', <FaultStateLevel.ERROR: 2>)", <FaultStateLevel.ERROR: 2>)', <FaultStateLevel.ERROR: 2>)
vuffiraa
Beiträge: 260
Registriert: Mo Apr 19, 2021 11:26 am
Been thanked: 2 times

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von vuffiraa »

Ich habe noch einen Nachtrag zu meiner Meldung im Beta 2 Thread https://www.openwb.de/forum/viewtopic.p ... 952#p96952.

Im SoC-Log gibt es vielleicht den richtigen Hinweis zum Problem:

Code: Alles auswählen

2023-11-18 14:14:15,512 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev1} - mqtt: FaultState FaultStateLevel.ERROR, FaultStr <class 'AttributeError'> 'NoneType' object has no attribute 'soc', Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 57, in update
    log.debug(f"Requested start soc from {source.value}: {car_state.soc}%")
AttributeError: 'NoneType' object has no attribute 'soc'
Ich konnte das Problem auch im Simulator nachstellen. Einfach einen MQTT-SoC konfigurieren und virtuell ein Auto anstecken und die Ladung starten. Wenn man nun per MQTT einen SoC übermittelt, wird der alle 5 Minuten zurückgesetzt.

Der component_updater eines MQTT-SoC (packages/modules/vehicles/mqtt/soc.py) liefert einfach keinen CarState, da auch nichts zu aktualisieren ist. Mit einer Prüfung, ob es einen CarState gibt, läuft es im Simulator bei mir (wieder). Alternative wäre vielleicht auch ein CarState, der zum MQTT-SoC passt.

VG
openWB serie 2 custom 11kW
Skoda Enyaq iV80
PV 9,4kWp SSW, Fronius Symo 8.2-3-M, Fronius Smart Meter 63A
jub
Beiträge: 64
Registriert: Mi Aug 10, 2022 1:29 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von jub »

der SOC wird mit dem aktuellen Master noch nicht von der openWB Pro übernommen. Die Pro bekommt den Wert vom Auto.
Und ich seh erst jetzt, dass es eigentlich um das Gleiche wie beim vorherigen Post geht: nur ein kleiner Unterschied im log
<class 'TypeError'> unsupported operand type(s) for -: 'int' and 'NoneType', Traceback:


Das ist das Logfile vom SoC-Log:

Code: Alles auswählen

2023-11-18 21:48:35,216 - {modules.common.component_context:24} - {DEBUG:fetch soc_ev1} - Update Komponente ['Manueller SoC']
2023-11-18 21:48:35,223 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev1} - Manueller SoC: FaultState FaultStateLevel.ERROR, FaultStr <class 'TypeError'> unsupported operand type(s) for -: 'int' and 'NoneType', Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 56, 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 96, in _get_carstate_by_source
    return CarState(soc=calc_soc.calc_soc(vehicle_update_data,
  File "/var/www/html/openWB/packages/modules/vehicles/common/calc_soc/calc_soc.py", line 13, in calc_soc
    imported_since_start = vehicle_update_data.imported - imported_start
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'

2023-11-18 21:48:45,255 - {modules.common.component_context:24} - {DEBUG:fetch soc_ev1} - Update Komponente ['Manueller SoC']
2023-11-18 21:48:45,257 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev1} - Manueller SoC: FaultState FaultStateLevel.ERROR, FaultStr <class 'TypeError'> unsupported operand type(s) for -: 'int' and 'NoneType', Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 56, 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 96, in _get_carstate_by_source
    return CarState(soc=calc_soc.calc_soc(vehicle_update_data,
  File "/var/www/html/openWB/packages/modules/vehicles/common/calc_soc/calc_soc.py", line 13, in calc_soc
    imported_since_start = vehicle_update_data.imported - imported_start
TypeError: unsupported operand type(s) for -: 'int' and 'NoneType'

2023-11-18 21:52:01,276 - {modules.common.component_context:24} - {DEBUG:fetch soc_ev1} - Update Komponente ['Manueller SoC']
2023-11-18 21:52:01,277 - {modules.common.configurable_vehicle:57} - {DEBUG:fetch soc_ev1} - Requested start soc from manual: 30%
2023-11-18 21:52:01,286 - {modules.common.store._api:26} - {DEBUG:fetch soc_ev1} - Raw data CarState(soc=30, range=None, soc_timestamp=None)
2023-11-18 21:52:01,319 - {modules.common.store._api:30} - {INFO:store soc_ev1} - Saving CarState(soc=30, range=None, soc_timestamp=None)
2023-11-18 21:52:21,367 - {modules.common.component_context:24} - {DEBUG:fetch soc_ev1} - Update Komponente ['Manueller SoC']
2023-11-


Danke! jürgen
smhex
Beiträge: 29
Registriert: Sa Mär 05, 2022 12:44 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von smhex »

vuffiraa hat geschrieben: Sa Nov 18, 2023 3:58 pm Ich habe noch einen Nachtrag zu meiner Meldung im Beta 2 Thread https://www.openwb.de/forum/viewtopic.p ... 952#p96952.

Im SoC-Log gibt es vielleicht den richtigen Hinweis zum Problem:

Code: Alles auswählen

2023-11-18 14:14:15,512 - {modules.common.fault_state:55} - {ERROR:fetch soc_ev1} - mqtt: FaultState FaultStateLevel.ERROR, FaultStr <class 'AttributeError'> 'NoneType' object has no attribute 'soc', Traceback: 
Traceback (most recent call last):
  File "/var/www/html/openWB/packages/modules/common/configurable_vehicle.py", line 57, in update
    log.debug(f"Requested start soc from {source.value}: {car_state.soc}%")
AttributeError: 'NoneType' object has no attribute 'soc'
Ich konnte das Problem auch im Simulator nachstellen. Einfach einen MQTT-SoC konfigurieren und virtuell ein Auto anstecken und die Ladung starten. Wenn man nun per MQTT einen SoC übermittelt, wird der alle 5 Minuten zurückgesetzt.

Der component_updater eines MQTT-SoC (packages/modules/vehicles/mqtt/soc.py) liefert einfach keinen CarState, da auch nichts zu aktualisieren ist. Mit einer Prüfung, ob es einen CarState gibt, läuft es im Simulator bei mir (wieder). Alternative wäre vielleicht auch ein CarState, der zum MQTT-SoC passt.

VG
Ich habe dasselbe Problem. SoC kommt über MQTT aus HA rein und alle 5 min erscheint die o.g. Fehlermeldung. Sieht man dann auch gut im Auswertediagramm.

Thomas
Thunderfart
Beiträge: 19
Registriert: Mi Mai 31, 2023 8:42 am

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von Thunderfart »

Hallo,

wenn ich bei Auswertungen-Diagramme beide Wallboxen auswähle aber nicht die Summe der Ladepunkte, zeigt das Diagram für die Zweite Wallbox (bei mir "OpenWB Pro Rechts") die Summe aus der ersten und zweiten Wallbox an. Wenn ich mit dem Cursor über den Zeitpunkt gehe, zeigt er aber die richtigen Werte in der kleinen Tabelle an. Wenn ich die erste Wallbox ausblende, zeigt er die richtige Linie für die zweite Wallbox an. Siehe auch die zwei Screenshots im Anhang.

Beste Grüße
Philipp
Dateianhänge
Bildschirmfoto 2023-11-19 um 11.58.28.png
Bildschirmfoto 2023-11-19 um 11.57.10.png
OpenWB Standalone mit Display / OpenWB Series 2 Standard+ / 2x OpenWB Pro / 17,1 kwp / SMA SHM 2.0 / 3x SMA Sunny Boy 5.0 / SMA Sunny Island 8.0 / BYD LVS 32 kwh / Mercedes EQC 400 / BMW ix50 (22kw AC-Laden)
MatzeL
Beiträge: 49
Registriert: Mi Mai 17, 2023 6:58 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von MatzeL »

PV min SoC startet nicht nach anstecken.

SoC wird aus Fahrzeug ausgelesen und von openWB übernommen.

SoC: 63%

min SoC: 66%
min SoC Strom: 6A

Offered Current Limit (in openWBpro): 6.0 A

-> Ladung wird nicht gestartet.

Erst Fahrzeug anstecken und anschließend von "Stop" auf "PV" umschalten funktioniert.
PV: Fronius Symo Speicher: Victron Auto: Skoda Enyaq mit ME3.6

openWB Pro + openWB Standalone mit Display
Nasdero
Beiträge: 482
Registriert: Mo Dez 16, 2019 9:01 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von Nasdero »

Soll das so? Zielladen war aktiv.
20231120_Zielladen.jpg
Dateianhänge
20231120_main.txt
(92 KiB) 62-mal heruntergeladen
smhex
Beiträge: 29
Registriert: Sa Mär 05, 2022 12:44 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von smhex »

Nasdero hat geschrieben: Mo Nov 20, 2023 5:44 am Soll das so? Zielladen war aktiv.

20231120_Zielladen.jpg
Das Diagramm sieht bei mir auch so aus, allerdings treten die Spitzen nur zu den Zeiten auf, in denen der SoC auf 0% steht (anderes Thema hier im Thread).

Eine Frage: stoppt bei Dir das Zielladen zur konfigurierten Uhrzeit? Bei mir nicht, aber das könnte auch an den sporadischen 0% SoC Werten liegen...

Thomas
Nasdero
Beiträge: 482
Registriert: Mo Dez 16, 2019 9:01 pm

Re: Rückmeldungen 2.1.2 Beta 3

Beitrag von Nasdero »

smhex hat geschrieben: Mo Nov 20, 2023 5:53 am Eine Frage: stoppt bei Dir das Zielladen zur konfigurierten Uhrzeit? Bei mir nicht, aber das könnte auch an den sporadischen 0% SoC Werten liegen...
Ich habe es hier abgebrochen, aber beim letzten Versuch mit dem ZOE hat die openWB gestoppt als sie fertig war, hat nur zwischendurch 2x angehalten und neu gestartet.
Zuletzt geändert von Nasdero am Mo Nov 20, 2023 8:05 am, insgesamt 1-mal geändert.
Gesperrt