evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.56k stars 659 forks source link

Externe Quelle fehlt e3dc-rscp #13779

Closed winfotiker closed 6 months ago

winfotiker commented 6 months ago

Describe the bug

Nach Umstellung vom template e3dc auf das e3dc-rscp wird nur noch die Leistung vom internen Wechselrichter angezeigt und nicht mehr die Leistung vom externen Wechselrichter. Ebenso fehlt seit dem der Hausverbrauch. grafik

Steps to reproduce

Änderung der evcc.yaml entsprechend Anleitung zum e3dc

Configuration details

meters:
- type: template
#  template: e3dc 
  template: e3dc-rscp
  usage: grid  
  host: 192.168.178.20  
#  port: 502  
  port: 5033
  name: grid1
  user: ***
  password: ***
  key: ****
- type: template
  template: e3dc-rscp 
  usage: pv 
  host: 192.168.178.20  
  port: 5033  
  name: pv2
  user: ***
  password: ***
  key: ****
- type: template
  template: e3dc-rscp 
  usage: battery  
  host: 192.168.178.20  
  port: 5033  
  name: battery3
  user: ***
  password: ***
  key: ****

Log details

[main  ] INFO 2024/05/06 12:11:03 evcc 0.126.2
[main  ] INFO 2024/05/06 12:11:03 using config file: /etc/evcc.yaml
[main  ] INFO 2024/05/06 12:11:03 starting ui and api at :7070
[db    ] INFO 2024/05/06 12:11:03 using sqlite database: /root/.evcc/evcc.db
[eebus ] INFO 2024/05/06 12:11:03 Local SKI:  d1e1654222435487ddd585473051fb2cd055386d
[eebus ] DEBUG 2024/05/06 12:11:03 mdns: announce
[eebus ] DEBUG 2024/05/06 12:11:03 mdns: using zeroconf
[eebus ] DEBUG 2024/05/06 12:11:03 starting websocket server on :4712
[eebus ] DEBUG 2024/05/06 12:11:03 mdns: start search
[eebus ] DEBUG 2024/05/06 12:11:03 ski: e6fbee384f24fac2f8cfe1369ffb932d841502f2 name: Elli-Wallbox-2109A184ND brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2109A184ND register: false host: wallbox-2109A184ND.local. port: 4712 addresses: [192.168.178.83]
[eebus ] DEBUG 2024/05/06 12:11:03 delaying connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 by 2.899s to minimize double connection probability
[eebus ] DEBUG 2024/05/06 12:11:04 ski: c04cc6e65dec6a3c308f178017bef67693856a78 name: Elli-Wallbox-2109A181H6 brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2109A181H6 register: false host: wallbox-2109A181H6.local. port: 4712 addresses: [192.168.178.91]
[eebus ] DEBUG 2024/05/06 12:11:04 delaying connection to c04cc6e65dec6a3c308f178017bef67693856a78 by 220ms to minimize double connection probability
[eebus ] DEBUG 2024/05/06 12:11:04 trying to connect to c04cc6e65dec6a3c308f178017bef67693856a78 at 192.168.178.91
[eebus ] DEBUG 2024/05/06 12:11:04 initiating connection to c04cc6e65dec6a3c308f178017bef67693856a78 at 192.168.178.91:4712
[eebus ] DEBUG 2024/05/06 12:11:04 Send:  read 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement read 2750854 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 reply 2 2750854 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 result 3 2750854 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement reply 2750856 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:04 Send:  call 4 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 read 5 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 read 6 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 read 7 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement call 2750858 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:04 Send: d:_i:47859_Elli-Wallbox-2109A181H6 result 8 2750858 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to DeviceClassification reply 2750862 5 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement result 2750867 4 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:04 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to DeviceDiagnosis reply 2750868 6 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/05/06 12:11:05 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement reply 2750869 7 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:05 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement read 2750870 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 reply 9 2750870 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 result 10 2750870 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:05 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement read 2750871 NodeManagementDestinationListData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 reply 11 2750871 NodeManagementDestinationListData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 result 12 2750871 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:05 Recv: d:_i:47859_Elli-Wallbox-2109A181H6: to NodeManagement read 2750872 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 reply 13 2750872 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:05 Send: d:_i:47859_Elli-Wallbox-2109A181H6 result 14 2750872 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:06 trying to connect to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83
[eebus ] DEBUG 2024/05/06 12:11:06 initiating connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83:4712
[eebus ] DEBUG 2024/05/06 12:11:07 Send:  read 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement read 260 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND reply 2 260 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND result 3 260 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement reply 262 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/05/06 12:11:07 ev connected
[eebus ] DEBUG 2024/05/06 12:11:07 Send:  call 4 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 6 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 5 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 7 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 8 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 9 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 10 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 11 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 12 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 13 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 14 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND call 15 NodeManagementBindingRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 16 DeviceConfigurationKeyValueDescriptionListData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 17 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 18 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 19 ElectricalConnectionDescriptionListData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 20 ElectricalConnectionParameterDescriptionListData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 21 MeasurementDescriptionListData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 22 LoadControlLimitDescriptionListData
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND read 23 IdentificationListData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement call 265 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/05/06 12:11:07 Send: d:_i:47859_Elli-Wallbox-2109A184ND result 24 265 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to DeviceClassification reply 268 6 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to Measurement notify 270 MeasurementListData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 272 4 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 276 5 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to ElectricalConnection notify 275 ElectricalConnectionPermittedValueSetListData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to DeviceDiagnosis reply 278 7 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to ElectricalConnection notify 280 ElectricalConnectionPermittedValueSetListData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement reply 282 8 NodeManagementUseCaseData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to ElectricalConnection notify 284 ElectricalConnectionPermittedValueSetListData
[eebus ] DEBUG 2024/05/06 12:11:07 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 286 9 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 288 10 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to Measurement notify 290 MeasurementListData
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 293 11 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 298 12 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 301 13 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 Recv: d:_i:47859_Elli-Wallbox-2109A184ND: to NodeManagement result 303 14 ResultData 0
[eebus ] DEBUG 2024/05/06 12:11:08 e6fbee384f24fac2f8cfe1369ffb932d841502f2 websocket read error:  websocket: close 1006 (abnormal closure): unexpected EOF
[eebus ] DEBUG 2024/05/06 12:11:08 ev disconnected
[eebus ] DEBUG 2024/05/06 12:11:08 restarting mdns search
[eebus ] DEBUG 2024/05/06 12:11:08 delaying connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 by 2.224s to minimize double connection probability
[eebus ] DEBUG 2024/05/06 12:11:10 trying to connect to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83
[eebus ] DEBUG 2024/05/06 12:11:10 initiating connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83:4712
[eebus ] DEBUG 2024/05/06 12:11:10 connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 failed:  dial tcp 192.168.178.83:4712: connect: connection refused
[eebus ] DEBUG 2024/05/06 12:11:10 trying to connect to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at wallbox-2109A184ND.local.
[eebus ] DEBUG 2024/05/06 12:11:10 initiating connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at wallbox-2109A184ND.local.:4712
[eebus ] DEBUG 2024/05/06 12:11:10 connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 failed: dial tcp: lookup wallbox-2109A184ND.local. on 192.168.178.1:53: no such host
[eebus ] DEBUG 2024/05/06 12:11:10 restarting mdns search
[eebus ] DEBUG 2024/05/06 12:11:10 delaying connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 by 9.577s to minimize double connection probability
[site  ] WARN 2024/05/06 12:11:11 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower
[site  ] INFO 2024/05/06 12:11:11 site config:
[site  ] INFO 2024/05/06 12:11:11   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/05/06 12:11:11     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/05/06 12:11:11     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/05/06 12:11:11     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2024/05/06 12:11:11   vehicles:
[site  ] INFO 2024/05/06 12:11:11     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓
[site  ] INFO 2024/05/06 12:11:11     vehicle 2: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓
[lp-1  ] INFO 2024/05/06 12:11:11 loadpoint 1:
[lp-1  ] INFO 2024/05/06 12:11:11   mode:        pv
[lp-1  ] INFO 2024/05/06 12:11:11   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/05/06 12:11:11   meters:      charge ✓
[lp-1  ] INFO 2024/05/06 12:11:11     charge:    power ✓ energy ✗ currents ✓
[lp-2  ] INFO 2024/05/06 12:11:11 loadpoint 2:
[lp-2  ] INFO 2024/05/06 12:11:11   mode:        pv
[lp-2  ] INFO 2024/05/06 12:11:11   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-2  ] INFO 2024/05/06 12:11:11   meters:      charge ✓
[lp-2  ] INFO 2024/05/06 12:11:11     charge:    power ✓ energy ✗ currents ✓
[site  ] DEBUG 2024/05/06 12:11:11 set buffer soc: 95
[site  ] DEBUG 2024/05/06 12:11:11 set buffer start soc: 100
[site  ] DEBUG 2024/05/06 12:11:11 set priority soc: 85
[lp-1  ] DEBUG 2024/05/06 12:11:11 phase timer inactive
[lp-1  ] DEBUG 2024/05/06 12:11:11 pv timer inactive
[lp-2  ] DEBUG 2024/05/06 12:11:11 phase timer inactive
[lp-2  ] DEBUG 2024/05/06 12:11:11 pv timer inactive
[site  ] WARN 2024/05/06 12:11:11 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/05/06 12:11:11 ----
[lp-1  ] DEBUG 2024/05/06 12:11:11 charge power: 0W
[lp-1  ] DEBUG 2024/05/06 12:11:11 charge currents: [0 0 0]A
[lp-2  ] DEBUG 2024/05/06 12:11:11 charge power: 0W
[lp-2  ] DEBUG 2024/05/06 12:11:11 charge currents: [0 0 0]A
time="2024-05-06T12:11:11+02:00" level=info msg="Connecting to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully connected to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="hiding auth request for security, use debug >= 99 to debug authentication"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully authenticated (level: AUTH_LEVEL_USER)"
time="2024-05-06T12:11:11+02:00" level=debug msg="write [{ EMS_REQ_POWER_PV None <nil> } { EMS_REQ_POWER_ADD None <nil> }]"
[site  ] DEBUG 2024/05/06 12:11:11 pv power: 8510W
time="2024-05-06T12:11:11+02:00" level=info msg="Connecting to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully connected to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="hiding auth request for security, use debug >= 99 to debug authentication"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully authenticated (level: AUTH_LEVEL_USER)"
time="2024-05-06T12:11:11+02:00" level=debug msg="write [{ EMS_REQ_POWER_BAT None <nil> }]"
time="2024-05-06T12:11:11+02:00" level=debug msg="write [{ EMS_REQ_BAT_SOC None <nil> }]"
[site  ] DEBUG 2024/05/06 12:11:11 battery soc: 100%
[site  ] DEBUG 2024/05/06 12:11:11 battery power: 12W
time="2024-05-06T12:11:11+02:00" level=info msg="Connecting to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully connected to 192.168.178.20:5033"
time="2024-05-06T12:11:11+02:00" level=info msg="hiding auth request for security, use debug >= 99 to debug authentication"
time="2024-05-06T12:11:11+02:00" level=info msg="successfully authenticated (level: AUTH_LEVEL_USER)"
time="2024-05-06T12:11:11+02:00" level=debug msg="write [{ EMS_REQ_POWER_GRID None <nil> }]"
[site  ] DEBUG 2024/05/06 12:11:11 grid meter: -10289W
[site  ] DEBUG 2024/05/06 12:11:11 site power: -10277W
[lp-1  ] ERROR 2024/05/06 12:11:11 charger status: timeout
time="2024-05-06T12:11:13+02:00" level=debug msg="write [{ EMS_REQ_POWER_GRID None <nil> }]"
time="2024-05-06T12:11:13+02:00" level=debug msg="write [{ EMS_REQ_POWER_PV None <nil> } { EMS_REQ_POWER_ADD None <nil> }]"
time="2024-05-06T12:11:13+02:00" level=debug msg="write [{ EMS_REQ_POWER_BAT None <nil> }]"
time="2024-05-06T12:11:13+02:00" level=debug msg="write [{ EMS_REQ_BAT_SOC None <nil> }]"
time="2024-05-06T12:11:20+02:00" level=debug msg="write [{ EMS_REQ_POWER_GRID None <nil> }]"
time="2024-05-06T12:11:20+02:00" level=debug msg="write [{ EMS_REQ_POWER_PV None <nil> } { EMS_REQ_POWER_ADD None <nil> }]"
time="2024-05-06T12:11:20+02:00" level=debug msg="write [{ EMS_REQ_POWER_BAT None <nil> }]"
time="2024-05-06T12:11:20+02:00" level=debug msg="write [{ EMS_REQ_BAT_SOC None <nil> }]"
[eebus ] DEBUG 2024/05/06 12:11:20 trying to connect to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83
[eebus ] DEBUG 2024/05/06 12:11:20 initiating connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at 192.168.178.83:4712
[eebus ] DEBUG 2024/05/06 12:11:20 connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 failed:  dial tcp 192.168.178.83:4712: connect: connection refused
[eebus ] DEBUG 2024/05/06 12:11:20 trying to connect to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at wallbox-2109A184ND.local.
[eebus ] DEBUG 2024/05/06 12:11:20 initiating connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 at wallbox-2109A184ND.local.:4712
[eebus ] DEBUG 2024/05/06 12:11:20 connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 failed: dial tcp: lookup wallbox-2109A184ND.local. on 192.168.178.1:53: no such host
[eebus ] DEBUG 2024/05/06 12:11:20 restarting mdns search
[eebus ] DEBUG 2024/05/06 12:11:20 delaying connection to e6fbee384f24fac2f8cfe1369ffb932d841502f2 by 24.456s to minimize double connection probability

What type of operating system are you running?

Linux

Version

0.126.2

andig commented 6 months ago

Arg, ich erinnere mich. @docolli wie wollten wir die analog Modbus Template mit abfragen?

docolli commented 6 months ago

Komisch, das tust du doch im Code? Du frägst PV und ADD Power an

    case templates.UsagePV:
        res, err := m.conn.SendMultiple([]rscp.Message{
            *rscp.NewMessage(rscp.EMS_REQ_POWER_PV, nil),
            *rscp.NewMessage(rscp.EMS_REQ_POWER_ADD, nil),
        })
        if err != nil {
            return 0, err
        }

        values, err := rscpValues(res, cast.ToFloat64E)
        if err != nil {
            return 0, err
        }

        return lo.Sum(values), nil

Ich habe noch die 0.126.0 im Einsatz und ich habe keine external Power zum Test.

Die Anfragen sollten aber so wie im Code funktionieren:

./e3dc '[["EMS_REQ_POWER_PV","",""],["EMS_REQ_POWER_ADD","",""]]' | jq
{
  "EMS_POWER_PV": 551,
  "EMS_POWER_ADD": 0
}
maikheinrich commented 6 months ago

Hallo zusammen,

ich könnte das testen für Euch, Ich habe externe Erzeuger und Verbrauchszähler an meinem E3DC. Allerdings habe ich vor Do keine Möglichkeit auf das System zuzugreifen.

Ich meine allerdings, dass der EMS_POWER_ADD Tag negative Werte zurück liefert. Da seit Ihr bei der Modus Integration auch schon drüber gestolpert... https://github.com/evcc-io/evcc/issues/6433

LG Maik

docolli commented 6 months ago

@maikheinrich Ja, wäre gut, wenn du mit dem Kommandozeilentool von go-rscp die Ausgabewerte der beiden Befehle testen könntest, damit man sieht, wie sich die Vorzeichen verhalten.

Mir fällt aber oben im Log auf, dass es nur 1 Ausgabe von pv power: 8510W gibt, nach dem [lp-1 ] ERROR 2024/05/06 12:11:11 charger status: timeout gibt es zwar das Senden von RSCP Anfragen, aber keine weitere Debug Ausgabe von Werten. Vielleicht ist das Problem auch ganz woanders.

andig commented 6 months ago

Trace log sollte reichen.

docolli commented 6 months ago

Blöde Frage, aber ich bekomme es grad nicht hin, die Log Ausgaben vom go-rscp zu bekommen, auch wenn ich in der config.yaml site: trace setze. Geht das nur, wenn ich evcc manuell aufrufe und dann einen Log-Level übergebe? Welchen?

Edit: Teilerfolg evcc -l trace meter liefert mir die Ausgabe 1x, aber nicht zyklisch.

Trace log liefert nur den RSCP-Request, aber nicht die einzelnen Werte, sondern dann wieder nur das vom evcc Code aufsummierte Power. Vorzeichenfehler sind da schwer zu entdecken. Dazu muss man zum Zeitpunkt des Logs auch die tatsächlichen Erzeugungswerte von PV und ADD kennen.

time="2024-05-07T08:22:46+02:00" level=debug msg="write [{ EMS_REQ_POWER_PV None <nil> } { EMS_REQ_POWER_ADD None <nil> }]"
Power: 937W
andig commented 6 months ago

Closed in https://github.com/evcc-io/evcc/commit/3590574aa0a5f5ce7b8b4c43fb8d740efe29a3e9