Alpitronic Hypercharger HYC 150 not connecting to SteVe since v3.4.9

[PeterPinnau]

We use SteVe in combination with a Webasto Live and Alpitronic HYC 150 for a couple of years.

Since HYC does not connect since version 3.4.9 we are still on SteVe 3.4.8 which is the last working version for us. I tried the follwing versions over the last years:

• 3.4.9
• 3.6.0
• GIT clone from today 2025-05-27

Webasto Live works fine with all version. HyperCharger HYC 150 does not get a heartbeat and is show as offline in the "connector status" overview.

I tried to find some information in the logs (SteVe + HYC) but was not able to. I upgraded the HyperCharger firmware to latest version 2.4.0 but problem remains.

What can I do to find the problem?

[PeterPinnau]

Tested with 3.10.0, still the same. The Hypercharger log reports:

[2026-01-21 14:14:58.956] [OCPP] [info] Connection to the backend failed, reason: <Invalid HTTP status., Bad Request>
[2026-01-21 14:15:08.849] [OCPP] [err] A backend connection problem was detected!

[goekay]

what do the logs of steve say? there must be a contextual information with the reason for returning bad request. looking at the relevant handshake code, i see three potential reasons for it:

• ChargeBoxId violates the configured ChargeBoxId pattern
• Failure to extract Authentication from request (i would exclude this for your case)
• No protocol (OCPP version) is specified

i think the last one might be your case. around the time of the version 3.4.9 steve started checking and validating Sec-WebSocket-Protocol header.

[PeterPinnau]

I can start working on this topic now. Upgraded to latest git version but still the same problem.

I do not see any message in steve log about the failed charger.

The default regex for chargepoint id validation is "[^=/()<>]*" ? That means any string which does not contain one or more of =/()<> is OK?

Steve log level is INFO at the moment. I tried to change that in logback-spring-prod.xml to DEBUG but it stays at INFO.

[PeterPinnau]

I changed protocol from WSS:// to WS:// on the Apitronic charger.

Steve log is not reporting anything.

Charger log says

[2026-03-10 14:41:56.265] [OCPP] [info] Connecting to the backend...
[2026-03-10 14:41:56.302] [OCPP] [info] Connection to the backend failed, reason: <Invalid HTTP status., Bad Request>
[2026-03-10 14:41:58.397] [OCPP] [info] Charger request: [2,"555841471","BootNotification",{"chargePointSerialNumber":"HYC_150_21BZ0500A","chargePointVendor":"alpitronic GmbH","meterType":"","meterSerialNumber":"","chargePointModel":"HYC150_1_71_00_00","iccid":"8945020184547419057F","chargeBoxSerialNumber":"HYC_150_21BZ0500A","firmwareVersion":"hyc_v2.4.0","imsi":"238028230991740"}]
[2026-03-10 14:42:06.270] [OCPP] [err] A backend connection problem was detected!

Changed from wss to ws

[2026-03-10 14:26:37.112] [OCPP] [info] Connecting to the backend...
[2026-03-10 14:26:42.113] [OCPP] [info] Connection to the backend failed, reason: <Timer Expired, >
[2026-03-10 14:26:47.114] [OCPP] [err] A backend connection problem was detected!