Wallbe Timeout with 0.306.3

[tomdmr]

Describe the bug

Hi,
I see an error on start-up with my Wallbe Eco2.0 after upgrade to 0.306.3. See except from logfile below.

Downgrading to 0.306.2 "fixes" the issue, so looks like this was introduced freshly.

Installation is on a raspi with debian.
I have not yet tested the latest nightly, because I need to check out first how to roll back from
curl -1sLf 'https://dl.evcc.io/public/evcc/unstable/setup.deb.sh'

I will add the result later.

Steps to reproduce

1. Install version 0.306.3
2. See logs for issues

...

Configuration details

chargers:
  - name: Wallbee
    type: template
    template: wallbe
    host: 192.168.13.5
    port: 502

loadpoints:
  - title:   Carport links           # display name for UI
    charger: Wallbee                 # Wallbox Referenz
    vehicle: Cabrio                  # Referenz auf Standardfahrzeug
    mode:       off                  # charge mode (off, now, minpv, pv)
    phases:      3
    mincurrent:  6
    maxcurrent: 16
    soc:
      poll:
        mode: connected              # charging, connected, alwyas
        interval: 60m                # considered for connected and always
      estimate: true

Log details

[lp-1 ] WARN 2026/05/10 10:03:54 poll mode '{connected 1h0m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1 ] INFO 2026/05/10 10:03:54 loadpoint 1:
[lp-1 ] INFO 2026/05/10 10:03:54 mode: off
[lp-1 ] INFO 2026/05/10 10:03:54 charger: power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗
[lp-1 ] INFO 2026/05/10 10:03:54 meters: charge ✗
[lp-1 ] WARN 2026/05/10 10:03:54 ignoring deprecated phases: 3. please configure via UI
[lp-1 ] WARN 2026/05/10 10:03:54 ignoring deprecated minCurrent: 6.000000. please configure via UI
[lp-1 ] WARN 2026/05/10 10:03:54 ignoring deprecated maxCurrent: 16.000000. please configure via UI
[lp-1 ] DEBUG 2026/05/10 10:03:54 phase timer inactive
[lp-1 ] DEBUG 2026/05/10 10:03:54 pv timer inactive
[lp-1 ] INFO 2026/05/10 10:03:54 vehicle updated: unknown -> XXXXXX
[lp-1 ] DEBUG 2026/05/10 10:03:54 set charge mode: off
[lp-1 ] ERROR 2026/05/10 10:03:57 charger enabled: read tcp 192.168.13.3:51042->192.168.13.5:502: i/o timeout
[lp-1 ] WARN 2026/05/10 10:03:57 poll mode '{connected 1h0m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[lp-1 ] DEBUG 2026/05/10 10:03:57 charge power: 0W
[lp-1 ] DEBUG 2026/05/10 10:03:57 vehicle odometer: 17381km
[lp-1 ] ERROR 2026/05/10 10:04:00 charger status: read tcp 192.168.13.3:51048->192.168.13.5:502: i/o timeout
[lp-1 ] DEBUG 2026/05/10 10:04:30 charge power: 0W
[lp-1 ] ERROR 2026/05/10 10:04:33 charger status: read tcp 192.168.13.3:51052->192.168.13.5:502: i/o timeout

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

evcc version 0.306.3

[tomdmr]

OK, nightly has the same error.
evcc version 0.306.3 (d5e6253d3)

[andig]

@premultiply. Drop-in not working.

@tomdmr please reconfigure as phoenix

[premultiply]

Deprecated wallbe* was finally removed.

Use phoenix-ev-eth as replacement.

[andig]

@premultiply the point here is that the covers: wallbe doesn't work as advertised. Not sure why. This is a bug.

[premultiply]

Ah, sorry, I didn't got that

[tomdmr]

OK, one thing to add: For the wallbe I could leave out modbud: tcpip and id:255. After switching to phoenix-ev-eth AND adding these two entries, it works.
@premultiply: "phoenix-ev-cc-eth" does not exist here. Probably a typo, "phoenix-ev-eth", as per docs, is fine.
For me the bug is closed.

[premultiply]

Yes, sorry. I updated my comment.

[andig]

Can we do something about the default modbus id?

[njordan77]

I have another issue with 306.3, maybe related. the webgui does not work at all on Pi3A+ :7070. I downgraded via SSH to 306.2 all works fine again. anyone else seeing this behaviour...