search

evcc-io / evcc

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

Apsystems EZ1 - invalid Syntax #14324

Closed lstefan123 closed 3 weeks ago

lstefan123 commented 1 month ago

Describe the bug

Bei Integration eines Apsystems-EZ1 Microwechselrichters (über UI), erhalte ich im Logfile folgende Fehler:

[site ] ERROR 2024/06/13 07:51:29 pv 2 power: strconv.ParseFloat: parsing "": invalid syntax [site ] ERROR 2024/06/13 07:51:30 pv 2 power: strconv.ParseFloat: parsing "": invalid syntax [site ] ERROR 2024/06/13 07:51:32 pv 2 energy: strconv.ParseFloat: parsing "": invalid syntax [site ] ERROR 2024/06/13 07:51:34 pv 2 power: strconv.ParseFloat: parsing "": invalid syntax [site ] ERROR 2024/06/13 07:51:36 pv 2 energy: strconv.ParseFloat: parsing "": invalid syntax [site ] ERROR 2024/06/13 07:51:39 pv 2 energy: strconv.ParseFloat: parsing "": invalid syntax

Release 0.127.0 (Fehler trat auch schon bei 0.126.* auf)

Trotz Fehlermeldung werden die Daten aber bereitgestellt. Die Daten werden auch per MQTT veröffentlicht: evcc/site/pv/2/power, evcc/site/pv/2/energy

Steps to reproduce

  1. Wechselrichter über UI konfiguriert
  2. EVCC neu gestartet

  3. ...

Configuration details

Konfiguration des Wechselrichters ist über UI unter Angabe der IP-Adresse erfolgt

Log details

[site ] ERROR 2024/06/13 07:51:29 pv 2 power: strconv.ParseFloat: parsing "<nil>": invalid syntax
[site ] ERROR 2024/06/13 07:51:30 pv 2 power: strconv.ParseFloat: parsing "<nil>": invalid syntax
[site ] ERROR 2024/06/13 07:51:32 pv 2 energy: strconv.ParseFloat: parsing "<nil>": invalid syntax
[site ] ERROR 2024/06/13 07:51:34 pv 2 power: strconv.ParseFloat: parsing "<nil>": invalid syntax
[site ] ERROR 2024/06/13 07:51:36 pv 2 energy: strconv.ParseFloat: parsing "<nil>": invalid syntax
[site ] ERROR 2024/06/13 07:51:39 pv 2 energy: strconv.ParseFloat: parsing "<nil>": invalid syntax

What type of operating system are you running?

Linux

Version

evcc version 0.127.0 (2fb309e6)

andig commented 1 month ago

Bitte 

evcc meter --log trace
lstefan123 commented 1 month ago 
evcc meter --log trace
[main  ] INFO 2024/06/13 10:56:11 evcc 0.127.0 (2fb309e6)
[main  ] INFO 2024/06/13 10:56:11 using config file: /etc/evcc.yaml
[db    ] INFO 2024/06/13 10:56:11 using sqlite database: /home/pi/.evcc/evcc.db
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT * FROM `settings` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT * FROM `settings` 0 <nil>
[mqtt  ] INFO 2024/06/13 10:56:11 connecting evcc-1 at tcp://localhost:1883
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="devices" -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="device_details" -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
[mqtt  ] DEBUG 2024/06/13 10:56:11 tcp://localhost:1883 connected
[db    ] TRACE 2024/06/13 10:56:11 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
[mqtt  ] ERROR 2024/06/13 10:56:11 tcp://localhost:1883 connection lost: EOF
[db    ] TRACE 2024/06/13 10:56:11 SELECT * FROM `configs` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="config_details" -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "config_details" AND sql IS NOT NULL order by type = "table" desc 2 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT * FROM `config_details` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT ""fk_configs_details"" %" OR sql LIKE "%CONSTRAINT fk_configs_details %" OR sql LIKE "%CONSTRAINT `fk_configs_details`%" OR sql LIKE "%CONSTRAINT [fk_configs_details]%" OR sql LIKE "%CONSTRAINT      fk_configs_details      %") -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "config_details" AND name = "idx_unique" -1 <nil>
[mqtt  ] DEBUG 2024/06/13 10:56:11 tcp://localhost:1883 connected
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT ""fk_devices_details"" %" OR sql LIKE "%CONSTRAINT fk_devices_details %" OR sql LIKE "%CONSTRAINT `fk_devices_details`%" OR sql LIKE "%CONSTRAINT [fk_devices_details]%" OR sql LIKE "%CONSTRAINT      fk_devices_details      %") -1 <nil>
[db    ] TRACE 2024/06/13 10:56:11 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%""device_id"" %" OR sql LIKE "%device_id %" OR sql LIKE "%`device_id`%" OR sql LIKE "%[device_id]%" OR sql LIKE "%        device_id       %") -1 <nil>
[pulse ] TRACE 2024/06/13 10:56:11 POST https://api.tibber.com/v1-beta/gql
[pulse ] TRACE 2024/06/13 10:56:11 {"query":"{viewer{websocketSubscriptionUrl}}"}
--
{"data":{"viewer":{"websocketSubscriptionUrl":"wss://websocket-api.tibber.com/v1-beta/gql/subscriptions"}}}
[pulse ] TRACE 2024/06/13 10:56:11 {"type":"connection_init","payload":{"token":"***"}} client
[pulse ] TRACE 2024/06/13 10:56:11 {"type":"connection_ack"} server
[pulse ] TRACE 2024/06/13 10:56:11 {"id":"ea3dfe09-b672-4380-bd7f-0a781ec7bc50","type":"subscribe","payload":{"query":"subscription ($homeId:ID!){liveMeasurement(homeId: $homeId){power,powerProduction,lastMeterConsumption,lastMeterProduction,currentL1,currentL2,currentL3}}","variables":{"homeId":"***"}}} client
[mqtt  ] ERROR 2024/06/13 10:56:12 tcp://localhost:1883 connection lost: EOF
[mqtt  ] DEBUG 2024/06/13 10:56:13 tcp://localhost:1883 connected
[pulse ] TRACE 2024/06/13 10:56:14 {"id":"ea3dfe09-b672-4380-bd7f-0a781ec7bc50","type":"next","payload":{"data":{"liveMeasurement":{"power":0,"powerProduction":1087,"lastMeterConsumption":2614.6722,"lastMeterProduction":188.8985,"currentL1":null,"currentL2":null,"currentL3":null}}}} server
[db    ] TRACE 2024/06/13 10:56:14 SELECT * FROM `configs` WHERE `configs`.`class` = 2 ORDER BY id 0 <nil>
grid3
-----
Power:          -1087W
Current L1..L3: 0A 0A 0A

grid1
-----
Power:  outdated
Energy: outdated

pv2
---
Power:  outdated
Energy: outdated

![image](https://github.com/evcc-io/evcc/assets/104157664/08206de0-257f-490a-b17e-821956e6a5f9)
andig commented 1 month ago

Könntest Du das bitte formatieren? Danke :)

andig commented 1 month ago

Das ist alles sehr merkwürdig. apsystems-ez1 nutzt http. Dein Log enthält aber keinen einzigen http Request.

lstefan123 commented 3 weeks ago

Fehler war woanders. PV2 war doch nicht das AP-Systems Balkonkraftwerk, sondern ein altes Balkonkraftwerk, das seine Daten über MQTT aus einem Shelly erhalten hatte. Ich habe PV2 in der evcc.yaml entfernt und stattdessen über UI den Shelly ordentlich konfiguriert. Jetzt sieht es wieder fein aus. Sorry!!!