Keba Wallbox P30C

Setup, Configuration and Use Items & Sitemaps
1

Hello all.

I am using the Keba-Addon with my openhab 5.1.0. Keba Wallbox is using the latest version (P30 v 3.10.74 (250723-164227) : 3985 : 318.0 : 2040003).

I do have issues with setting maxpresetcurrentrange. As explained in the manual I am using this Item with a slider.

Unfortunately the slider is jumping and I am not able to set a correct value. It take ~10-15 attemps till the value is updated.
I tried to update via habPanel, Basic UI and the App. All of them shows similar behaviour.

The Item is:

Number KebaCurrentRange     "Ladestrom [%d %%]"                                               <energy>    (gWallbox,gRange)   {channel="keba:kecontact:011265477b:maxpresetcurrentrange", autoupdate="true"}

And Sitemap:

Slider item=KebaCurrentRange

Even sometimes the value shows a different status as the slider bar.

Some examples:

1

In previous versions it was working without any trouble. Did something change? Am I doing something wrong?

Appreciate your feedback since it is very useful for charging the vehicle via solar energy.

Thanks

2

I don’t know this binding but in general I recommend against setting autoupdate to true unless the binding doesn’t report state changes on this channel at all.

Beyond that, set the releaseOnly property on the Slider sitemap property to true. This will only send the command to the Item when you release the slider instead of sending intermittent commands.

These two should quiet things down as only one command will go out to the device and only one update will come back.

3

Thanks for the feedback and explanation

Unfortuantely there is no difference if I am using releaseOnlyproperty. Same behavior.

Any other ideas?

4

Since I don’t know the binding I don’t have any other ideas except to file an issue on the add-on.

5

Thanks for quick feedback. Opened a ticket….

lets see

6

I suspect that you send the command. Then the autoupdate sets the value to the commanded value.
Then after x seconds the binding updates to the actual value.
For you in the UI this results in a jumping value.
You can check if the jumping value corresponds with the poll interval of the binding.

I can only recommend to set autoupdate=false which should fix the behavior.