-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
devicesSpecific device supportSpecific device support
Description
Describe the bug
The new go-e 60.1 beta leads to a crash of evcc, resulting in evcc unable to start.
I did not try the nightly, but since there are no issues and no PR's i assume that the bug is also present in nightly
EDIT: Happens with 60.0 and 60.1, updated issue accordingly
Steps to reproduce
Install 60.0 / 60.1 beta on go-e and evcc starts to crash
Downgrade to 57.1 and evcc no longer crashes
Configuration details
no special configuration requiredLog details
starting evcc: 'EVCC_DATABASE_DSN=/config/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/11/10 15:49:23 evcc 0.209.7
[main ] INFO 2025/11/10 15:49:23 using config file: /config/evcc.yaml
panic: runtime error: index out of range [0] with length 0
goroutine 381 [running]:
github.com/evcc-io/evcc/charger/go-e.(*StatusResponse2).Identify(0xc0001a9590?)
github.com/evcc-io/evcc/charger/go-e/types2.go:69 +0x4e
github.com/evcc-io/evcc/charger.(*GoE).Identify(0x67e3ff0?)
github.com/evcc-io/evcc/charger/go-e.go:207 +0x38
github.com/evcc-io/evcc/core.(*Loadpoint).createSession(0xc000158908)
github.com/evcc-io/evcc/core/loadpoint_session.go:46 +0x224
github.com/evcc-io/evcc/core.(*Loadpoint).evVehicleConnectHandler(0xc000158908)
github.com/evcc-io/evcc/core/loadpoint.go:516 +0x1ab
reflect.Value.call({0x2a2ce40?, 0xc000b36a50?, 0x1?}, {0x323e738, 0x4}, {0x69ef5a0, 0x0, 0x67e3c30?})
reflect/value.go:581 +0xcc6
reflect.Value.Call({0x2a2ce40?, 0xc000b36a50?, 0x0?}, {0x69ef5a0?, 0x0?, 0x3?})
reflect/value.go:365 +0xb9
github.com/asaskevich/EventBus.(*EventBus).doPublish(0x1?, 0xc000f55b30, {0x324af1d?, 0x0?}, {0x0?, 0xc00093d350?, 0xc000ed8e28?})
github.com/asaskevich/[email protected]/event_bus.go:160 +0x4d
github.com/asaskevich/EventBus.(*EventBus).Publish(0xc0007f0a20, {0x324af1d, 0x7}, {0x0, 0x0, 0x0})
github.com/asaskevich/[email protected]/event_bus.go:144 +0x5e7
github.com/evcc-io/evcc/core.(*Loadpoint).updateChargerStatus(0xc000158908)
github.com/evcc-io/evcc/core/loadpoint.go:1089 +0x44b
github.com/evcc-io/evcc/core.(*Loadpoint).Update(0xc000158908, 0x407c4fd2f1a9fbe7, 0x4071900000000000, {0xc0010c8a88, 0xc0, 0xc0}, {0xc0010cb508, 0xc0, 0xc0}, 0x0, ...)
github.com/evcc-io/evcc/core/loadpoint.go:1910 +0x945
github.com/evcc-io/evcc/core.(*Site).update(0xc000684008, {0x3cdd668, 0xc000158908})
github.com/evcc-io/evcc/core/site.go:972 +0x703
github.com/evcc-io/evcc/core.(*Site).Run(0xc000684008, 0xc000bd45b0, 0x2540be400)
github.com/evcc-io/evcc/core/site.go:1112 +0x216
github.com/evcc-io/evcc/cmd.runRoot.func4()
github.com/evcc-io/evcc/cmd/root.go:362 +0x25
created by github.com/evcc-io/evcc/cmd.runRoot in goroutine 1
github.com/evcc-io/evcc/cmd/root.go:361 +0x2745
What type of operating system or environment does evcc run on?
Linux
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.209.7
Metadata
Metadata
Assignees
Labels
devicesSpecific device supportSpecific device support