You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have since today a strange behaivour. I´m using the modbus Proxy to connect ioBroker modbus adapter to read some values. These values do all look fine. But in evcc all (SOC and amps look ok) values seems to be random (see log) The values from the wallbox seem ok.
I deleted the MQTT values and I first thought it might be that the configuration was not fully applied to use Modbus, I change to that yesterday.
However I restarted evcc, deleted the container and also "evcc migrate --reset".
Steps to reproduce
...
Configuration details
Konfiguration (/etc/evcc.yaml):
# open evcc at http://evcc.local:7070network:
schema: httphost: evcc.local # .local suffix announces the hostname on MDNSport: 7070# mqtt message brokermqtt:
broker: 172.27.1.10:1884topic: evcc # root topic for publishing, set empty to disable publishing# clientid: foouser: *****password: *****log: infolevels:
cache: error# unique installation idplant: *****interval: 30s# control cycle intervalsponsortoken: *****# sponsors can set telemetry: true to enable anonymous data aggregation# see https://github.com/evcc-io/evcc/discussions/4554telemetry: falsechargers:
- type: templatetemplate: alfen id: 1host: 172.27.1.182 port: 502modbus: tcpip name: wallbox2vehicles:
- type: templatetemplate: vw title: Tiguan user: *****password: *****vin: *****capacity: 11timeout: 10sname: Tiguanicon: tractor # Icon in der Benutzeroberfläche (optional)phases: 1# Die maximale Anzahl der Phasen welche genutzt werden können (optional)cache: 15m# Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (optional)mode: PV # Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional)minCurrent: 6# Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)maxCurrent: 16# Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)identifiers: # Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional)priority: # Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)
- name: MGtype: templatetemplate: mg2mqtttitle: MG 4user: *****timeout: 1hvin: *****capacity: 64# Akkukapazität in kWh (optional)icon: car # Icon in der Benutzeroberfläche (optional)phases: 3# Die maximale Anzahl der Phasen welche genutzt werden können (optional)mode: PV # Möglich sind Off, Now, MinPV und PV, oder leer wenn keiner definiert werden soll (optional)minCurrent: 6# Definiert die minimale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)maxCurrent: 16# Definiert die maximale Stromstärke pro angeschlossener Phase mit welcher das Fahrzeug geladen werden soll (optional)identifiers: # Kann meist erst später eingetragen werden, siehe: https://docs.evcc.io/docs/features/vehicle (optional)priority: # Priorität des Ladepunktes oder Fahrzeugs in Relation zu anderen Ladepunkten oder Fahrzeugen für die Zuweisung von PV-Energie (optional)loadpoints:
- title: Garagecharger: wallbox2mode: pvsite:
title: Mein Zuhausemeters:
#grid: grid1#battery: battery1#pv: pv1grid: my_gridbattery: my_batterypv: my_pvmeters:
- name: my_gridtype: templatetemplate: sofarsolarusage: gridmodbus: tcpipid: 1host: 172.27.1.190port: 502
- name: my_pvtype: templatetemplate: sofarsolarusage: pvmodbus: tcpipid: 1host: 172.27.1.190port: 502
- name: my_batterytype: templatetemplate: sofarsolarusage: batterymodbus: tcpipid: 1host: 172.27.1.190port: 502#- type: custom# power:# source: mqtt# topic: ME3000SP/state/grid_power# timeout: 10s# scale: -1# energy:# source: http# uri: http://172.27.1.10:8087/getPlainValue/1-0:1_8_0__255.value# name: grid1#- type: custom# name: battery1# power:# source: mqtt# topic: ME3000SP/state/battery_power# timeout: 10s# scale: -1# soc:# source: mqtt# topic: ME3000SP/state/batterySOC# timeout: 10s#- type: custom# name: pv1# power: # source: mqtt# topic: ME3000SP/state/solarPV# timeout: 10smodbusproxy:
- port: 502uri: 172.27.1.190:502tariffs:
currency: EURgrid: # price using energy from the gridtype: fixedprice: 0.335# EUR/kWh start 8.1.25 (39,7 - 15%)feedin: # price for feeding solar energy to the gridtype: fixedprice: 0.078# EUR/kWhinflux:
url: http://172.27.1.241:8086database: evcc # InfluxDB v2.x uses term `bucket` but for compatibility still named `database` heretoken: *****org: orgVersion: `0.133.0`
What type of operating system or environment does evcc run on?
Docker container
External automation
I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
I have verified that the issue is reproducible with the latest nightly build
Version
0.133.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Hello,
I have since today a strange behaivour. I´m using the modbus Proxy to connect ioBroker modbus adapter to read some values. These values do all look fine. But in evcc all (SOC and amps look ok) values seems to be random (see log) The values from the wallbox seem ok.
I deleted the MQTT values and I first thought it might be that the configuration was not fully applied to use Modbus, I change to that yesterday.
However I restarted evcc, deleted the container and also "evcc migrate --reset".
Steps to reproduce
...
Configuration details
Log details
What type of operating system or environment does evcc run on?
Docker container
External automation
Nightly build
Version
0.133.0
The text was updated successfully, but these errors were encountered: