Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove em2go-home #14480

Merged
merged 5 commits into from
Jun 23, 2024
Merged

Remove em2go-home #14480

merged 5 commits into from
Jun 23, 2024

Conversation

andig
Copy link
Member

@andig andig commented Jun 19, 2024

@premultiply die Phasenerkennung sieht etwas merkwürdig aus- zusätzlich noch das Phasenregister lesen (siehe #14436 (comment))? Genau genommen prüfen wir bei keiner andere Box die Spannungen gegen. Allein aus Konsistenzgründen sollten wir das auch hier nicht tun?

Replace #14364

@andig andig added the devices Specific device support label Jun 19, 2024
@andig andig requested a review from premultiply June 19, 2024 19:33
@andig
Copy link
Member Author

andig commented Jun 20, 2024

Replace #14364

charger/em2go.go Outdated Show resolved Hide resolved
@premultiply
Copy link
Member

api.PhaseGetter fehlt noch?

@premultiply
Copy link
Member

Gleich noch Unterstützung für die Duo-Box mit einbauen? Register-Offset +256
https://wallboxcenter.de/wp-content/uploads/2024/06/EM2GO-DUO-Power-Wallbox-Modbus-TCP-Register.pdf

Co-authored-by: premultiply <4681172+premultiply@users.noreply.github.com>
@andig
Copy link
Member Author

andig commented Jun 22, 2024

@premultiply könntest Du mal einen Blick drauf werfen? Offset ist jetzt überall drin, macht aber z.B. bei Serialnummer ja gar keinen Sinn. Ist das so korrekt?

@RenatusRo
Copy link
Contributor

Offset ist jetzt überall drin, macht aber z.B. bei Serialnummer ja gar keinen Sinn. Ist das so korrekt?

bei der duo steht die serial auf 0, LPlinks ab 256, LPrechts ab 512 - ist also nicht einfach offset 256 auf pro/home

This reverts commit 99af80d.
@andig
Copy link
Member Author

andig commented Jun 23, 2024

Dann erstmal ohne- danke für den Hinweis!

@andig andig merged commit 20466a9 into master Jun 23, 2024
6 checks passed
@andig andig deleted the feat/em2go branch June 23, 2024 08:25
@kasn24
Copy link

kasn24 commented Jun 25, 2024

Wollte kein eigenes Issue aufmachen, hoffe das ist ok.
Nach Update auf 0.127.3 hab ich die config angepasst, gemäß Doku. Der Eintrag zum Port hat zum timeout geführt. Ohne Port funktioniert alles.
Neustart aller beteiligten Geräte brachte nichts. Es war der Eintrag.

so passt es:

- type: template
  template: em2go
  modbus: tcpip
  id: 255
  host: 192.168.178.150
  name: wallbox8
 25 21:12:21 raspevcc evcc[1139]: [lp-2  ] ERROR 2024/06/25 21:12:21 vehicle odometer: asleep
Jun 25 21:12:31 raspevcc evcc[1139]: [lp-2  ] ERROR 2024/06/25 21:12:31 charge meter: dial tcp 192.168.178.150:502: i/o timeout
Jun 25 21:12:41 raspevcc evcc[1139]: [lp-2  ] ERROR 2024/06/25 21:12:41 charge rater: dial tcp 192.168.178.150:502: i/o timeout
Jun 25 21:12:51 raspevcc evcc[1139]: [lp-2  ] ERROR 2024/06/25 21:12:51 charge timer: dial tcp 192.168.178.150:502: i/o timeout
Jun 25 21:13:01 raspevcc evcc[1139]: [lp-2  ] ERROR 2024/06/25 21:13:01 charge total import: dial tcp 192.168.178.150:502: i/o timeout

@andig
Copy link
Member Author

andig commented Jun 25, 2024

Ich verstehe nur Bahnhof. Mit der ohne Port wird auf 502 verbunden.

@marcogracklauer

This comment was marked as resolved.

@kasn24

This comment was marked as resolved.

@andig
Copy link
Member Author

andig commented Jun 25, 2024

Bitte

evcc charger --log trace

mit und ohne Port.

@andig

This comment was marked as resolved.

@kasn24
Copy link

kasn24 commented Jun 26, 2024

ksn@raspevcc:~ $ evcc charger wallbox8 --log trace --ignore-db
[main  ] INFO 2024/06/26 05:31:13 evcc 0.127.3
[main  ] INFO 2024/06/26 05:31:13 using config file: /etc/evcc.yaml
[db    ] INFO 2024/06/26 05:31:14 using sqlite database: /home/ksn/.evcc/evcc.db
[db    ] TRACE 2024/06/26 05:31:14 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
[db    ] TRACE 2024/06/26 05:31:14 CREATE TABLE `settings` (`key` text,`value` text,PRIMARY KEY (`key`)) 0 <nil>
[db    ] TRACE 2024/06/26 05:31:14 SELECT * FROM `settings` 0 <nil>
[mqtt  ] INFO 2024/06/26 05:31:14 connecting evcc-1214775122 at tcp://192.168.178.182:1883
[db    ] TRACE 2024/06/26 05:31:14 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="devices" -1 <nil>
[db    ] TRACE 2024/06/26 05:31:14 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="device_details" -1 <nil>
[db    ] TRACE 2024/06/26 05:31:14 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
[mqtt  ] DEBUG 2024/06/26 05:31:14 tcp://192.168.178.182:1883 connected
[db    ] TRACE 2024/06/26 05:31:14 CREATE TABLE `configs` (`id` integer PRIMARY KEY AUTOINCREMENT,`class` integer,`type` text) 0 <nil>
[db    ] TRACE 2024/06/26 05:31:14 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="config_details" -1 <nil>
[db    ] TRACE 2024/06/26 05:31:14 CREATE TABLE `config_details` (`config_id` integer,`key` text,`value` text,CONSTRAINT `fk_configs_details` FOREIGN KEY (`config_id`) REFERENCES `configs`(`id`) ON DELETE CASCADE ON UPDATE CASCADE) 0 <nil>
[db    ] TRACE 2024/06/26 05:31:14 CREATE INDEX `idx_unique` ON `config_details`(`config_id`,`key`) 0 <nil>
[db    ] TRACE 2024/06/26 05:31:14 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/26 05:31:14 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>
[db    ] TRACE 2024/06/26 05:31:14 SELECT * FROM `configs` WHERE `configs`.`class` = 1 ORDER BY id 0 <nil>
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 01 00 00 00 06 ff 03 00 c8 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 01 00 00 00 05 ff 03 02 00 03
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 02 00 00 00 06 ff 03 00 0c 00 02
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 02 00 00 00 07 ff 03 04 00 00 00 00
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 03 00 00 00 06 ff 03 00 1c 00 02
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 03 00 00 00 07 ff 03 04 00 00 07 33
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 04 00 00 00 06 ff 03 00 06 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 04 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 05 00 00 00 06 ff 03 00 08 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 05 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 06 00 00 00 06 ff 03 00 0a 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 06 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 07 00 00 00 06 ff 03 00 6d 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 07 00 00 00 05 ff 03 02 09 24
[em2go ] TRACE 2024/06/26 05:31:14 modbus: send 00 08 00 00 00 06 ff 03 00 6f 00 01
[em2go ] TRACE 2024/06/26 05:31:14 modbus: recv 00 08 00 00 00 05 ff 03 02 09 24
[em2go ] TRACE 2024/06/26 05:31:15 modbus: send 00 09 00 00 00 06 ff 03 00 71 00 01
[em2go ] TRACE 2024/06/26 05:31:15 modbus: recv 00 09 00 00 00 05 ff 03 02 09 24
[em2go ] TRACE 2024/06/26 05:31:15 modbus: send 00 0a 00 00 00 06 ff 03 00 00 00 01
[em2go ] TRACE 2024/06/26 05:31:15 modbus: recv 00 0a 00 00 00 05 ff 03 02 00 01
[em2go ] TRACE 2024/06/26 05:31:15 modbus: send 00 0b 00 00 00 06 ff 03 00 5f 00 01
[em2go ] TRACE 2024/06/26 05:31:15 modbus: recv 00 0b 00 00 00 05 ff 03 02 00 02
[em2go ] TRACE 2024/06/26 05:31:15 modbus: send 00 0c 00 00 00 06 ff 03 00 48 00 02
[em2go ] TRACE 2024/06/26 05:31:15 modbus: recv 00 0c 00 00 00 07 ff 03 04 00 00 00 00
[em2go ] TRACE 2024/06/26 05:31:15 modbus: send 00 0d 00 00 00 06 ff 03 00 4e 00 02
[em2go ] TRACE 2024/06/26 05:31:15 modbus: recv 00 0d 00 00 00 07 ff 03 04 00 00 00 00
Power:          0W
Energy:         184.3kWh
Current L1..L3: 0A 0A 0A
Voltage L1..L3: 234V 234V 234V
Charge status:  A
Enabled:        false
Charged:        0.0kWh
Duration:       0s

mit Port-Eintrag in der Konfig:

ksn@raspevcc:~ $ evcc charger wallbox8 --log trace --ignore-db
[main  ] INFO 2024/06/26 05:34:24 evcc 0.127.3
[main  ] INFO 2024/06/26 05:34:24 using config file: /etc/evcc.yaml
[db    ] INFO 2024/06/26 05:34:25 using sqlite database: /home/ksn/.evcc/evcc.db
[db    ] TRACE 2024/06/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 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/26 05:34:25 SELECT * FROM `settings` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 SELECT * FROM `settings` 0 <nil>
[mqtt  ] INFO 2024/06/26 05:34:25 connecting evcc-467939578 at tcp://192.168.178.182:1883
[db    ] TRACE 2024/06/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="devices" -1 <nil>
[mqtt  ] DEBUG 2024/06/26 05:34:25 tcp://192.168.178.182:1883 connected
[db    ] TRACE 2024/06/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="device_details" -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 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>
[db    ] TRACE 2024/06/26 05:34:25 SELECT * FROM `configs` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="config_details" -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 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/26 05:34:25 SELECT * FROM `config_details` LIMIT 1 -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 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/26 05:34:25 SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "config_details" AND name = "idx_unique" -1 <nil>
[db    ] TRACE 2024/06/26 05:34:25 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/26 05:34:25 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>
[db    ] TRACE 2024/06/26 05:34:25 SELECT * FROM `configs` WHERE `configs`.`class` = 1 ORDER BY id 0 <nil>
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 01 00 00 00 06 ff 03 00 c8 00 01
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 01 00 00 00 05 ff 03 02 00 03
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 02 00 00 00 06 ff 03 00 0c 00 02
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 02 00 00 00 07 ff 03 04 00 00 00 00
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 03 00 00 00 06 ff 03 00 1c 00 02
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 03 00 00 00 07 ff 03 04 00 00 07 33
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 04 00 00 00 06 ff 03 00 06 00 01
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 04 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 05 00 00 00 06 ff 03 00 08 00 01
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 05 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 06 00 00 00 06 ff 03 00 0a 00 01
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 06 00 00 00 05 ff 03 02 00 00
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 07 00 00 00 06 ff 03 00 6d 00 01
[em2go ] TRACE 2024/06/26 05:34:25 modbus: recv 00 07 00 00 00 05 ff 03 02 09 2e
[em2go ] TRACE 2024/06/26 05:34:25 modbus: send 00 08 00 00 00 06 ff 03 00 6f 00 01
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 08 00 00 00 05 ff 03 02 09 24
[em2go ] TRACE 2024/06/26 05:34:26 modbus: send 00 09 00 00 00 06 ff 03 00 71 00 01
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 09 00 00 00 05 ff 03 02 09 24
[em2go ] TRACE 2024/06/26 05:34:26 modbus: send 00 0a 00 00 00 06 ff 03 00 00 00 01
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 0a 00 00 00 05 ff 03 02 00 01
[em2go ] TRACE 2024/06/26 05:34:26 modbus: send 00 0b 00 00 00 06 ff 03 00 5f 00 01
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 0b 00 00 00 05 ff 03 02 00 02
[em2go ] TRACE 2024/06/26 05:34:26 modbus: send 00 0c 00 00 00 06 ff 03 00 48 00 02
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 0c 00 00 00 07 ff 03 04 00 00 00 00
[em2go ] TRACE 2024/06/26 05:34:26 modbus: send 00 0d 00 00 00 06 ff 03 00 4e 00 02
[em2go ] TRACE 2024/06/26 05:34:26 modbus: recv 00 0d 00 00 00 07 ff 03 04 00 00 00 00
Power:          0W
Energy:         184.3kWh
Current L1..L3: 0A 0A 0A
Voltage L1..L3: 235V 234V 234V
Charge status:  A
Enabled:        false
Charged:        0.0kWh
Duration:       0s

Da es bei mir ja schon beim letzten mal Diagnose-Schwierigkeiten gab: nach beiden Befehlen gab es keine Interface am Ende.

@andig
Copy link
Member Author

andig commented Jun 26, 2024

Ich sehe da keinen Unterschied. Beides funktioniert wunderbar.

@marcogracklauer
Copy link

Verstehe ich das Issue richtig

nein

Konnte ich zwischenzeitlich verifizieren, dass das Umschalten noch funktioniert. Allerdings passt nun die Doku nicht mehr:

https://github.com/evcc-io/evcc/pull/14480/files#diff-f497536ad628206c9acfc9ae37e1e71021430372221e97bb4fb9e710dea5e9e5L6
vs.
https://github.com/evcc-io/evcc/pull/14480/files#diff-cd73b81aea71d8f9bf953bd868150d2cd0b1e003feb7b83dcfac049e6fd87641L6

@andig
Copy link
Member Author

andig commented Jun 29, 2024

Ah, danke für den Hinweis!

@premultiply @naltatis wie wollen wir mit den Capabilities umgehen? Angeben und für die Home per description out of scope nehmen?

@andig
Copy link
Member Author

andig commented Jun 29, 2024

@marcogracklauer nochmal zur Sicherheit: 1p3p hatte nur die Home (sieht in https://github.com/evcc-io/evcc/pull/14480/files#diff-cd73b81aea71d8f9bf953bd868150d2cd0b1e003feb7b83dcfac049e6fd87641L6 so aus)? Oder nicht die Home?

@marcogracklauer
Copy link

@marcogracklauer nochmal zur Sicherheit: 1p3p hatte nur die Home (sieht in https://github.com/evcc-io/evcc/pull/14480/files#diff-cd73b81aea71d8f9bf953bd868150d2cd0b1e003feb7b83dcfac049e6fd87641L6 so aus)? Oder nicht die Home?

Ich habe hier eine "Home" mit der Typenbezeichnung EMH011AC1RW und die hat 1p3p.
https://www.em2go.de/en-gb/wallboxes/ac-wallbox-home-11kw-6-5m-type-2-cable-bluetooth-app-rfid-modbus-tcp

So war es auch bis vor kurzem in der Doku (wodurch ich überhaupt auf das Modell aufmerksam wurde).

@andig
Copy link
Member Author

andig commented Jun 29, 2024

In 8b7f249 ergänzt, danke!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devices Specific device support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants