Problems with the evcc binding

Add-ons Bindings
1

Hello, I have installed the evcc binding for a long time and it worked correctly until an update from openhab. I’m now on OH4.2.0 in a Debian 12 Proxmox VM and evcc 128.2. At first I didn’t notice anything, but suddenly the items weren’t updated anymore. All channels are recognized. When creating an item everything looks ok, but after saving there is a ? The problem has been going on for a while and has nothing to do with the latest versions of OH and EVCC. I’ve uninstalled all items/things and the binding several times and done a clean cache, but the error always remains.
Can someone help?
imageImage

2

Hi Ralf,
afaik evcc did change the API some time ago and the binding was adjusted to reflect this.
Maybe you are still running an evcc version with the older api and the latest binding does not fit anymore (actually means you evcc might be outdated).
BR,
Thomas

3

Hello Thomas,
evcc 0.128.2 ist very new. I tried in the moment the update to the newest 0.128.4. I tried to build a new item, but it is the same. I get no data, a questionmark is displayed but the link is green.
It must be something other,
thank you,
Ralf

4

To validate I just did a quick upgrade to 4.2.0 from M1 to release and checked with my evcc running.
The channel you show in the screenshot is working properly (evcc 126.4, currently can/will not upgrade it).

Maybe this is related to your Proxmox - I’m not familiar with it, so I won’t be of any help here.
Did you check evcc is reachable and responds to call from within your VM? Port issues…?

BR,
Thomas

5

It is possible with GET and POST from the oh VM to work in the evcc VM. Many weeks ago I installed the binding manually from a file from github. I mean that was the beginning of the disaster. But i cleaned up and installed from the addon store. May I did something wrong by this job?
BR,
Ralf

6

The openhab.log after making an item with the model:

2024-08-08 13:32:03.716 [DEBUG] [ab.binding.evcc.internal.EvccHandler] - Setting up refresh job ...
2024-08-08 13:32:03.716 [DEBUG] [ab.binding.evcc.internal.EvccHandler] - Running refresh job ...
2024-08-08 13:32:03.719 [DEBUG] [ab.binding.evcc.internal.EvccHandler] - Found 1 loadpoints on site Zuhause.
2024-08-08 13:32:03.719 [DEBUG] [ab.binding.evcc.internal.EvccHandler] - Found 1 vehicles on site Zuhause.
2024-08-08 13:32:03.721 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.lang.IllegalArgumentException: UID segment 'vehicledb:1#vehicleMinSoC' contains invalid characters. The last segment of the channel UID must match the pattern '[\w-]*|[\w-]*#[\w-]*'.
        at org.openhab.core.thing.ChannelUID.validateSegment(ChannelUID.java:136) ~[?:?]
        at org.openhab.core.common.AbstractUID.<init>(AbstractUID.java:76) ~[?:?]
        at org.openhab.core.thing.UID.<init>(UID.java:66) ~[?:?]
        at org.openhab.core.thing.ChannelUID.<init>(ChannelUID.java:76) ~[?:?]
        at org.openhab.binding.evcc.internal.EvccHandler.createChannel(EvccHandler.java:995) ~[?:?]
        at org.openhab.binding.evcc.internal.EvccHandler.createChannelsVehicle(EvccHandler.java:635) ~[?:?]
        at org.openhab.binding.evcc.internal.EvccHandler.createChannelsVehicle(EvccHandler.java:584) ~[?:?]
        at org.openhab.binding.evcc.internal.EvccHandler.refresh(EvccHandler.java:428) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:840) [?:?]
7

lsiepel works on the binding. He made a new version. Now it all is very fine. Thank you very much.