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.

Sign up for GitHub

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

Jump to bottom

eebus error #17758

Closed
jomach opened this issue Dec 16, 2024 · 7 comments
Closed

eebus error #17758

jomach opened this issue Dec 16, 2024 · 7 comments
Labels
question Rather clarification than issue

Comments

@jomach
Copy link
Contributor

jomach commented Dec 16, 2024 •
edited
Loading

Describe the bug

Since the last two or three releases my evcc with eebus stopped working with the error:

nc -vz 192.168.1.230 4712 [±main ✓▾]
Connection to 192.168.1.230 port 4712 [tcp/*] succeeded!

does someone else have the same issue ? @andig

Steps to reproduce

.

Configuration details

eebus:
  URI: 192.168.1.216:4712
  interfaces:
    - end0
  certificate
....

Log details

[eebus ] DEBUG 2024/12/16 16:48:30 trying to connect to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at wallbox.local.
[eebus ] DEBUG 2024/12/16 16:48:30 initiating connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at wallbox.local.:4712/ship/
[eebus ] DEBUG 2024/12/16 16:48:30 connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f failed: remote error: tls: internal error
[eebus ] DEBUG 2024/12/16 16:48:30 trying to connect to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at 192.168.1.230
[eebus ] DEBUG 2024/12/16 16:48:30 initiating connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at 192.168.1.230:4712/ship/
[eebus ] DEBUG 2024/12/16 16:48:31 connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f failed:  remote error: tls: internal error



### What type of operating system are you running?

HomeAssistant Add-on

### Nightly build

- [X] I have verified that the issue is reproducible with the latest nightly build

### Version

0.131.11
@andig
Copy link
Member

andig commented Dec 16, 2024 •
edited
Loading

That's an interesting error... Are you using official builds? Could you pls add log of last working version?

@andig andig added the question Rather clarification than issue label Dec 16, 2024
@jomach
Copy link
Contributor Author

jomach commented Dec 16, 2024

Yes, sadly I cannot rollback on homeassistant. Will try it locally to see . Will keep you posted

@andig
Copy link
Member

andig commented Dec 16, 2024

Only reference I can find is golang/go#58434

@jomach
Copy link
Contributor Author

jomach commented Dec 16, 2024

I can confirm this is also happening on 0.131.7 . So I think this is something to do with my network which I did not change.

> $ evcc -c evcc.yaml
[main  ] INFO 2024/12/16 19:13:36 evcc 0.131.7
[main  ] INFO 2024/12/16 19:13:36 using config file: evcc.yaml
[db    ] INFO 2024/12/16 19:13:36 using sqlite database: /Users/jorge/.evcc/evcc.db
[mqtt  ] INFO 2024/12/16 19:13:36 connecting evcc-100160542 at tcp://homeassistant.local:1883
[eebus ] INFO 2024/12/16 19:13:41 Local SKI: 9a46bcb42045efb7a5f449a89482621ca87eb4dc
[eebus ] DEBUG 2024/12/16 19:13:41 starting websocket server on :4712
[eebus ] DEBUG 2024/12/16 19:13:41 mdns: announce
[eebus ] DEBUG 2024/12/16 19:13:41 mdns: using zeroconf
[main  ] INFO 2024/12/16 19:13:41 listening at :7070
[eebus ] TRACE 2024/12/16 19:13:41 registering ski: ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f
[eebus ] DEBUG 2024/12/16 19:13:41 mdns: new - ski: ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f name: Livo-EVB-500-015-503 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-500-015-503 register: false host: wallbox.local. port: 4712 addresses: [192.168.1.230]
[eebus ] DEBUG 2024/12/16 19:13:41 trying to connect to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at wallbox.local.
[eebus ] DEBUG 2024/12/16 19:13:41 initiating connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at wallbox.local.:4712/ship/
[eebus ] DEBUG 2024/12/16 19:13:41 connection to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f failed: remote error: tls: internal error
[eebus ] DEBUG 2024/12/16 19:13:41 trying to connect to ae82347bb2de22aa304c83fb1d8f1d94aeb29b4f at 192.168.1.230

@jomach
Copy link
Contributor Author

jomach commented Dec 16, 2024 •
edited
Loading

So, it basicly stays in the loop from eebus. When I kill it with -6 I get:
This is now on my laptop

goroutine 244 gp=0x14001f38700 m=nil [IO wait]:
runtime.gopark(0x14001971d58?, 0x14001ef41b0?, 0x20?, 0x9a?, 0x14001be85f0?)
	runtime/proc.go:424 +0xc8 fp=0x14001971cf0 sp=0x14001971cd0 pc=0x100b291e8
runtime.netpollblock(0x102b1926f?, 0x3?, 0x0?)
	runtime/netpoll.go:575 +0x158 fp=0x14001971d30 sp=0x14001971cf0 pc=0x100aea4e8
internal/poll.runtime_pollWait(0x14cf94a70, 0x72)
	runtime/netpoll.go:351 +0xa0 fp=0x14001971d60 sp=0x14001971d30 pc=0x100b28490
internal/poll.(*pollDesc).wait(0x14001daa880?, 0x50?, 0x0)
	internal/poll/fd_poll_runtime.go:84 +0x28 fp=0x14001971d90 sp=0x14001971d60 pc=0x100bb19a8
internal/poll.(*pollDesc).waitRead(...)
	internal/poll/fd_poll_runtime.go:89
internal/poll.(*FD).RawRead(0x14001daa880, 0x14001be85f0)
	internal/poll/fd_unix.go:717 +0x12c fp=0x14001971df0 sp=0x14001971d90 pc=0x100bb710c
net.(*rawConn).Read(0x1400082a138, 0x0?)
	net/rawconn.go:44 +0x30 fp=0x14001971e30 sp=0x14001971df0 pc=0x100cb5da0
golang.org/x/net/internal/socket.(*Conn).recvMsg(0x14001d904e0, 0x14001bf4d80, 0x0)
	golang.org/x/net@v0.31.0/internal/socket/rawconn_msg.go:27 +0x138 fp=0x14001971e90 sp=0x14001971e30 pc=0x1016e2158
golang.org/x/net/internal/socket.(*Conn).RecvMsg(...)
	golang.org/x/net@v0.31.0/internal/socket/socket.go:247
golang.org/x/net/ipv4.(*payloadHandler).ReadFrom(0x14001d8eba0, {0x1400221a000, 0x10000, 0x10000})
	golang.org/x/net@v0.31.0/ipv4/payload_cmsg.go:31 +0x468 fp=0x14001971f40 sp=0x14001971e90 pc=0x1016ec0b8
github.com/enbility/zeroconf/v2.(*Server).recv4(0x14002535560, 0x14001d8eb90)
	github.com/enbility/zeroconf/v2@v2.0.0-20240920094356-be1cae74fda6/server.go:275 +0xb8 fp=0x14001971fb0 sp=0x14001971f40 pc=0x101749df8
github.com/enbility/zeroconf/v2.(*Server).start.gowrap1()
	github.com/enbility/zeroconf/v2@v2.0.0-20240920094356-be1cae74fda6/server.go:213 +0x2c fp=0x14001971fd0 sp=0x14001971fb0 pc=0x10174998c
runtime.goexit({})
	runtime/asm_arm64.s:1223 +0x4 fp=0x14001971fd0 sp=0x14001971fd0 pc=0x100b32044
created by github.com/enbility/zeroconf/v2.(*Server).start in goroutine 374
	github.com/enbility/zeroconf/v2@v2.0.0-20240920094356-be1cae74fda6/server.go:213 +0x90

goroutine 4646 gp=0x14001ddcc40 m=nil [select]:
runtime.gopark(0x14001f54f98?, 0x2?, 0x70?, 0x0?, 0x14001f54f6c?)
	runtime/proc.go:424 +0xc8 fp=0x14001f54e00 sp=0x14001f54de0 pc=0x100b291e8
runtime.selectgo(0x14001f54f98, 0x14001f54f68, 0x14002672a80?, 0x0, 0x140019941a0?, 0x1)
	runtime/select.go:335 +0x67c fp=0x14001f54f30 sp=0x14001f54e00 pc=0x100b049bc
crypto/tls.(*Conn).handshakeContext.func2()
	crypto/tls/conn.go:1544 +0x7c fp=0x14001f54fd0 sp=0x14001f54f30 pc=0x100d0faac
runtime.goexit({})
	runtime/asm_arm64.s:1223 +0x4 fp=0x14001f54fd0 sp=0x14001f54fd0 pc=0x100b32044
created by crypto/tls.(*Conn).handshakeContext in goroutine 4916
	crypto/tls/conn.go:1543 +0x1e8

@jomach
Copy link
Contributor Author

jomach commented Dec 16, 2024

ok, crazy, I renamed the wallbox in the router a couple of weeks ago. And only now I did a restart. Guess what. The MDNS uses this name and the eebus protocol matches it to the DNS name. That's why I saw there wallbox.local instead of EVB-500-015-503.local

@jomach jomach closed this as completed Dec 16, 2024
@andig
Copy link
Member

andig commented Dec 16, 2024 •
edited
Loading

So, it basicly stays in the loop from eebus

That doesn‘t say much- it‘s waiting for network packets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Rather clarification than issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andig @jomach