SSL errors #162

mathieudz · 2024-12-22T09:57:35Z

I have upgraded this HACS integration to 2.9.1, upgraded HACS to 2.0 and HASS to 2024.12 and the integration does not longer work. I removed the device and tried to add it again.
In the logs I see:

2024-12-22 10:51:04.920 DEBUG (MainThread) [custom_components.alfen_wallbox.coordinator] ClientConnectionError to 192.168.0.187 Cannot connect to host 192.168.0.187:443 ssl:default [[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] ssl/tls alert handshake failure (_ssl.c:1020)]

In the Alfen (FW5.3.1) logs I also see TLS errors:

TLS handshake failed (~0x73800) for fd=3
Failed to setup WebClient -29568

It seems that they cannot agree on a SSL/TLS connection anymore.
When I'm logged in ACE, I just get connection refused instead (as expected).
When testing with curl from the host running HASS, I can connect the HTTPS port.

The text was updated successfully, but these errors were encountered:

leeyuentuen · 2024-12-22T11:26:01Z

Could it be that you also upgrade to the latest integration version? See this issue

#161

mathieudz · 2024-12-22T11:34:26Z

Yes I did, see my message. I cannot downgrade anymore, probably due to HACS 2.

leeyuentuen · 2024-12-24T15:03:42Z

Nothing changed yet, but just cleanup.

Let me know if this helps something
https://github.com/leeyuentuen/alfen_wallbox/releases/tag/2.9.2-beta

mathieudz · 2024-12-24T16:21:10Z

I cannot install any other version anymore, it seems.

WayeeWang · 2024-12-24T16:33:06Z

I can install the 2.9.2 beta, but it doesn't fix the problem unfortunately

leeyuentuen · 2024-12-24T21:20:42Z

Maybe enable pre release?
#166 (comment)

mathieudz · 2024-12-25T12:50:56Z

Managed to upgrade to 2.9.2-beta by reinstalling 2.9.1 first. Some problem though.

GJAvV · 2024-12-29T20:03:55Z

I also have this problem.
Connection with Ace installer and MyEve works normally. I noticed the time not eing correct in the Alfen charger and synchronised. Tried multiple plugin versions. Changed the fixed ip adress via MyEve.
Any ideas?

leeyuentuen · 2024-12-29T20:05:56Z

Can everyone got this issue let me know which firmware you are using? On my 7.0.x version. I didn't got issue on it

mathieudz · 2024-12-29T20:41:06Z

5.3.1

GJAvV · 2024-12-29T21:24:10Z

6.4.0-4210

WayeeWang · 2024-12-29T21:27:59Z

5.6.0-4104
Upgraded from 5.3.1 after seeing this issue, no improvements though.

GJAvV · 2024-12-30T13:32:32Z

I did a rollback to 2.8.9; that works!
Made a few rollbacks but apparently not to 2.8.9.

WayeeWang · 2024-12-30T16:18:25Z

I did a rollback to 2.8.9; that works! Made a few rollbacks but apparently not to 2.8.9.

How did you roll back to 2.8.9? I got this message when installing anything earlier than 2.9.1:
The version 2.8.9 for this integration can not be used with HACS.

leeyuentuen · 2024-12-30T16:19:57Z

I did a rollback to 2.8.9; that works! Made a few rollbacks but apparently not to 2.8.9.

How did you roll back to 2.8.9? I got this message when installing anything earlier than 2.9.1: The version 2.8.9 for this integration can not be used with HACS.

#166 (comment)

leeyuentuen · 2024-12-30T21:53:34Z

There is a beta 2 and beta3

Can you manual try to download and put them in custom_component and see if it works?

GJAvV · 2024-12-31T14:33:52Z

Trying alfen_wallbox-2.9.2-beta-3 now

GJAvV · 2024-12-31T14:38:29Z

Trying alfen_wallbox-2.9.2-beta-3 now

Works!

Deleted alfen_wallbox folder in custom_component and copied the alfen_wallbox-2.9.2-beta-3 folder, renamed as alfen_wallbox in custom_component and restarted HA.
All entities work again.
Firmware: 6.4.0-4210

WimBra · 2025-01-02T14:37:12Z

stopped HA
removed alfen_wallbox folder in custom components
installed beta_3

I still got API connection error.
rebooted the wallbox, I still got api connection error, but connected after 2 minutes

HA reboot test failed... again multiple times "Api connection error".
no connection afterwards.
rolled back to 2.8.9

2025-01-02 15:34:39.179 DEBUG (MainThread) [custom_components.alfen_wallbox.coordinator] Connection to 192.168.50.233 timed out
2025-01-02 15:34:51.123 DEBUG (MainThread) [custom_components.alfen_wallbox.alfen] Response <ClientResponse(https://192.168.50.233/api/info) [200 OK ]>
<CIMultiDictProxy('Content-Type': 'alfen/json; charset=UTF-8', 'Connection': 'keep-alive', 'Content-Length': '215', 'Version': '1')>

alfen logbook:

2025-01-02T14:33:57.121Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:33:57.148Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:33:57.156Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:34:04.027Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:34:29.011Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:34:29.019Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:34:29.125Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:34:29.152Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:34:29.160Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:34:34.179Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:35:01.003Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:35:01.011Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:35:01.042Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:35:01.066Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:35:01.078Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:35:14.500Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:35:33.003Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:35:33.015Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:35:33.117Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:35:33.144Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:35:33.152Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:36:02.578Z:INFO:active_lb.c:308:SMt:(0.0 0.0 0.0)A Free:(32.0 32.0 32.0)A ALB:(0.0 0.0 0.0)A
2025-01-02T14:36:14.707Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:36:36.996Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:36:37.003Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:36:37.058Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:36:37.082Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:36:37.089Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:37:55.121Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:38:12.988Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:38:13.000Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:38:13.082Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:38:14.328Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x7280) for fd=3
2025-01-02T14:38:14.335Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -29312
2025-01-02T14:39:35.492Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:40:04.976Z:WARNING:taskWebClient.c:234:Client (fd=3) disconnected (r: -0x7880)
2025-01-02T14:40:04.984Z:INFO:taskWebClient.c:166:Removing previously connected client
2025-01-02T14:40:05.003Z:INFO:taskWebServer.c:240:WebServer state BUSY -> AVAILABLE
2025-01-02T14:40:05.031Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:40:05.039Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:40:06.289Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:40:06.300Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:40:06.328Z:WARNING:taskWebClient.c:812:TLS handshake failed (-0x50) for fd=3
2025-01-02T14:40:06.335Z:WARNING:taskWebClient.c:836:Failed to setup WebClient -80
2025-01-02T14:40:19.824Z:INFO:taskWebServer.c:240:WebServer state AVAILABLE -> BUSY
2025-01-02T14:40:20.500Z:SECURITY:httpd_login.c:155:WebClient  connected (account: admin)
2025-01-02T14:40:46.015Z:USER:taskMaster.c:6147:Socket #1: L1N=227.3V L2N=0.0V L3N=0.0V L1L2=n/a L2L3=n/a L3L1=n/a 
2025-01-02T14:40:46.312Z:USER:taskMaster.c:6045:Temperature: 24.4 C

phulstaert · 2025-01-04T13:51:14Z

I am having the same issue since this morning.

I had the 7.0.2 firmware and updated HA to 2025.1 core.
next, i updated to 7.0.5, but still the same issue.

I can ping my charger (192.168.3.226)
I cannot do a curl to https://192.168.3.226/api/info

Since it seems to be an TLS/SSL issue; I tried chrome and saw (expired on 2021??)

and

and as a more detailed try i ran docker run --rm -ti drwetter/testssl.sh 192.168.3.226

It seems like an Alfen issue, not a plugin issue. (we could ignore SSL issues - but I'm not a fan of that...)

leeyuentuen · 2025-01-04T13:53:16Z

I am having the same issue since this morning.

I had the 7.0.2 firmware and updated HA to 2025.1 core. next, i updated to 7.0.5, but still the same issue.

I can ping my charger (192.168.3.226)

I cannot do a curl to https://192.168.3.226/api/info

Since it seems to be an TLS/SSL issue; I tried chrome and saw (expired on 2021??) and

and as a more detailed try i ran docker run --rm -ti drwetter/testssl.sh 192.168.3.226

It seems like an Alfen issue, not a plugin issue. (we could ignore SSL issues - but I'm not a fan of that...)

Try the beta version that has skip the ssl

phulstaert · 2025-01-04T14:08:48Z

I tried, but without luck.

BTW:
I was confused with "the latest beta"; It says 2.9.2-beta-5; but in the zip under manifest (and on home assistant) it says 2.9.4-beta-1; it is just a number, but nonetheless confusing :-)

phulstaert · 2025-01-04T14:30:01Z

ok; I removed the charger from the integration config
I completely removed the previous alfen_wallbox folder from the custom_componentes folder;
I unzipped the alfen_wallbox from the latest beta to the custom_componentes folder
I rebooted homeassistant (not just a reload)
I reentered the config of my charger

And now it works...
Thank you
(my steps for any other people that have issues)

WimBra · 2025-01-04T14:37:17Z

Have you also tried another HA reboot after the new config of the charger?
That's where it goes wrong with me...

phulstaert · 2025-01-04T14:49:56Z

I just rebooted HA and it came up without an issue.
I also adjusted the current of the charging of my car, just to be certain it still had a connection, and all went as it should.

Did you check there was no other application that made a connection while HA was rebooting? There can only be one connection at a time.
You could try to reboot the charger to clear any connections (turn off the breaker for a few seconds)

WimBra · 2025-01-04T19:06:23Z

It's so strange...

I will try it again.
First I will update the wallbox to 7.x.x (6.6.2 now)
Again i will remove the alfen_wallbox folder from the custom_componentes folder.
Unzip and copy the latest beta release
Reboot
Re-enter the config.

I'll keep my fingers crossed and post the result.

WimBra · 2025-01-04T20:12:58Z

Hurray
works like a charm again.
beta_5
alfen to 7.0.5
HA version 2025.1.0

1 (little) issue.
When I try to configure the categories... the dropbox isn't complete and I cannot (de)select some categories. I don't know if it is an issue with HA or the integration

leeyuentuen · 2025-01-08T23:49:23Z

i'll close this issue, there is a new release, if still some issue with SSL, open new ticket and describe the issue

WayeeWang mentioned this issue Dec 22, 2024

Cannot connect to charger all of the sudden #161

Closed

leeyuentuen self-assigned this Dec 30, 2024

leeyuentuen added Ready for release Ready for release dev tested Dev Branch test and ready for release labels Jan 2, 2025

leeyuentuen closed this as completed Jan 8, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SSL errors #162

SSL errors #162

mathieudz commented Dec 22, 2024 •

edited

Loading

leeyuentuen commented Dec 22, 2024

mathieudz commented Dec 22, 2024

leeyuentuen commented Dec 24, 2024

mathieudz commented Dec 24, 2024 •

edited

Loading

WayeeWang commented Dec 24, 2024

leeyuentuen commented Dec 24, 2024

mathieudz commented Dec 25, 2024

GJAvV commented Dec 29, 2024

leeyuentuen commented Dec 29, 2024

mathieudz commented Dec 29, 2024

GJAvV commented Dec 29, 2024

WayeeWang commented Dec 29, 2024

GJAvV commented Dec 30, 2024

WayeeWang commented Dec 30, 2024

leeyuentuen commented Dec 30, 2024

leeyuentuen commented Dec 30, 2024

GJAvV commented Dec 31, 2024

GJAvV commented Dec 31, 2024

WimBra commented Jan 2, 2025 •

edited

Loading

phulstaert commented Jan 4, 2025

leeyuentuen commented Jan 4, 2025

phulstaert commented Jan 4, 2025

phulstaert commented Jan 4, 2025

WimBra commented Jan 4, 2025

phulstaert commented Jan 4, 2025

WimBra commented Jan 4, 2025 •

edited

Loading

WimBra commented Jan 4, 2025 •

edited

Loading

leeyuentuen commented Jan 8, 2025

SSL errors #162

SSL errors #162

Comments

mathieudz commented Dec 22, 2024 • edited Loading

leeyuentuen commented Dec 22, 2024

mathieudz commented Dec 22, 2024

leeyuentuen commented Dec 24, 2024

mathieudz commented Dec 24, 2024 • edited Loading

WayeeWang commented Dec 24, 2024

leeyuentuen commented Dec 24, 2024

mathieudz commented Dec 25, 2024

GJAvV commented Dec 29, 2024

leeyuentuen commented Dec 29, 2024

mathieudz commented Dec 29, 2024

GJAvV commented Dec 29, 2024

WayeeWang commented Dec 29, 2024

GJAvV commented Dec 30, 2024

WayeeWang commented Dec 30, 2024

leeyuentuen commented Dec 30, 2024

leeyuentuen commented Dec 30, 2024

GJAvV commented Dec 31, 2024

GJAvV commented Dec 31, 2024

WimBra commented Jan 2, 2025 • edited Loading

phulstaert commented Jan 4, 2025

leeyuentuen commented Jan 4, 2025

phulstaert commented Jan 4, 2025

phulstaert commented Jan 4, 2025

WimBra commented Jan 4, 2025

phulstaert commented Jan 4, 2025

WimBra commented Jan 4, 2025 • edited Loading

WimBra commented Jan 4, 2025 • edited Loading

leeyuentuen commented Jan 8, 2025

mathieudz commented Dec 22, 2024 •

edited

Loading

mathieudz commented Dec 24, 2024 •

edited

Loading

WimBra commented Jan 2, 2025 •

edited

Loading

WimBra commented Jan 4, 2025 •

edited

Loading

WimBra commented Jan 4, 2025 •

edited

Loading