Open MikeTheTux opened 7 months ago
It is not clear, if the same UDP protocol as for the P30 is supported by the P40 / P40 Pro.
I got feedback from my electrician who has a contact at Keba. According to them the P40/P40 Pro do not support UDP, but only the Modbus TCP interface. However, the Modbus Interface is the same as for the P30, so this specification applies also for the P40 family (kecontactp30modbustcp_pgen.pdf).
I'm currently considering to order the P40, so would be willing to contribute or test.
kecontact_p40_p40pro_technicaldata_cable_dben, page 2 (Local communication protocols)
I never received feedback via my Keba request, but I came to the same conclusion that only the Modbus API might be supported. The UDP interface from P30 I would anyhow rate 'special'.
Unfortunately that will require a complete re-write of the Binding. I do not think that I will be able to work on this on mid-term. Does someone volunteer? As workaround you could realize the most important functions via the generic modbus openHAB binding. Or you steer the keba wallbox via evcc (which supports keba already in modbus) in combination with the openHAB evcc binding. Thereby you also get access to most important controls. Both options could be a proper workaround in order to be not blocked due to lack of native openHAB support.
Any idea, what "Function will be added later" means? This will be a blocker.
Any idea, what "Function will be added later" means? This will be a blocker.
I stumbled upon this question as well. Mail to my electrician is out. He's currently in vacation, so no immediate feedback expected.
I guess we need to check the release notes of upcoming firmware updates. Until now, there is none available:
Two observation that I would like to document:
I think that especially holds when writing to the registers. I haven't seen any problem so far when using MODBUS in r/w (steering) and UDP in r/o (monitoring) in parallel.
Only one single instance can connect to Keba MODBUS interface at a point in time. A second connection attempt is refused by the Wallbox. If more than a single connection is required, a modbus proxy could be the solution (again: 1 writing, n reading). EVCC comes already with a build in MODBUS proxy, that I was able to test successful with my Keba P30.
I‘ve a P40 at home since last week. Didn’t see any option to do more than pure charging. Even integration into Keba proprietary portal and app (local and w/ cloud) doesn’t work.
As far as I know, Modbus is on their roadmap for later this year.
Keba just released the next generation of their wallboxes:
P40 product naming schema:
It is not clear, if the same UDP protocol as for the P30 is supported by the P40 / P40 Pro.