# \[APP\]\[PRO\] KEBA app

**URL:** <https://community.homey.app/t/app-pro-keba-app/68776>\
**Category:** Apps\
**Tags:** app\
**Created:** [September 12, 2022, 4:40pm UTC](https://community.homey.app/t/app-pro-keba-app/68776 "2022-09-12T16:40:39Z")\
**Posts on this page:** 20\
**Page:** 7

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 22, 2026, 6:33pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/121 "2026-03-22T18:33:31Z")

</div>

I have a little problem, and not sure how to handle.

In Modbus you can set a max A for charging (like the select we have with 6-63A).  
But I can not get this value back from the charger. I can get back the max value, I instead get back the max value that it uses based on the car etc

If i select 8A it can send back 6A and so on…

Not sure how to handle this yet…

EDIT:

I can handle it so that i keep what we set in Homey and use that - but that does not guarantee the value - it can be set by another integration / app and Homey won’t know about it.  
Homey set it to 8A, and that is what we use etc. but then if you use another app and set it to 16A Homey wont know and our UI and so on still thinks (and in some cases set to 8A)…

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 24, 2026, 4:24pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/122 "2026-03-24T16:24:15Z")

</div>

Ok, so status now.

1. I have added ev charger / energy so it should show up for those having that function (I cannot test myself)
2. I have added “P40” support, via Modbus (this also works fine for P20/30, thinking I will change those to use modbus later - much easier and less problems can arise).

For the modbus version, there are 2 changes to how the P20/P30 works

1. There is no onoff (suspend) - no support to set for P40 (works in P20/P30) and no way to read if it is suspended or not.
2. the “Charge power” is set when you select it (or initial to what your hardware has as supported), but we cannot read the actual value set on the machine so Homey will act somewhat as master and set this on intervalls based on what is set at Homey.

If anyone want to test it, and give any feedback or such I have submitted a test version.  
(note, you need to manually add your IP for now, I have not yet added the MAC address for P40)

> **[Keba | Homey](https://homey.app/en-us/app/se.cohen.keba/Keba/test/)**
>
> Automation by Innovation.

---

<div class="post-metadata">

**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\
**Post date:** [March 24, 2026, 9:13pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/123 "2026-03-24T21:13:23Z")

</div>

Welcome back, Jonathan! 🙂

> [@Jonathan\_Cohen](#):
>
> I have added ev charger / energy so it should show up for those having that function (I cannot test myself)

Now the Kebas show up in the energy tab, thank you! (I guess that can be done for the Renault app as well ;))

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/f/ef4fc2b4d587d386bc8e03dfd6a9c28da16aeb97.jpeg)

> [@Jonathan\_Cohen](#):
>
> I have added “P40” support, via Modbus (this also works fine for P20/30, thinking I will change those to use modbus later - much easier and less problems can arise).

May I suggest to keep UDP for the P20/P30 and only add Modbus for P40.  
I understand it would be easier for you. But the UDP interface is absolutly rock solid. It never misses a beat and it is unlikely they change that interface for P20/P30.

You have done an amazing job and I do not want to see that being crippled by the missing functionallity in Modbus.  
Also I rely on that functionallity in my automations for load balancing.

---

<div class="post-metadata">

**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\
**Post date:** [March 25, 2026, 7:23am UTC](https://community.homey.app/t/app-pro-keba-app/68776/124 "2026-03-25T07:23:17Z")

</div>

I have flows using Energy Total tag for calculation. They all broke with the v1.1.15 update.

On 2 of my 3 Keba P30s, I could replace the broken tag with a new. On the 3d, Energy Total was not present.  
Missing

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/3/33b60cbda9984399f9618da0502175399a032e2d.png)

Exist

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/0/d0215305decaf4954cd723ae4f75d84d0e39a7c7.png)

Will try charging later today.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 25, 2026, 9:39am UTC](https://community.homey.app/t/app-pro-keba-app/68776/125 "2026-03-25T09:39:42Z")

</div>

Thanks for the feedback!

I will keep the P20/P30 as today.

Note, a user with P20/P30 can still use the P40 just fine, if he/she wants to use modbus version instead (maybe it should be called Keba UDP and Keba Modbus as devices instead, but a but technical names…?)

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 25, 2026, 9:42am UTC](https://community.homey.app/t/app-pro-keba-app/68776/126 "2026-03-25T09:42:11Z")

</div>

Strange, I will check this - hopefully later today.  
To be able to add to energy-thingy I needed a “meter\_power” capability that would have duplicated the already existing capability… so it is removed but should look the same and exists as an option.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 25, 2026, 2:36pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/127 "2026-03-25T14:36:10Z")

</div>

Have you tried to restart the Keba APP (i guess it already have, because of install), it is in the INIT it registers the capabilities (and removes old ones).

You could else try to send a diagnostic report directly after restart and I could see if I can see aything.

When I check both P30 and P40 at home I have the “Energy Total”

Do you see it in capabilities and/or in statistics correct for all chargers?

EDIT

@aste there is a new version for testing, some clean up but not sure if it will help..

Else I think i need to add the old one back and follow this guideline to let it work, but not use in the APP UI (in parallel) - strange that it works for some of the devices for you…

> **[Breaking Changes | Homey Apps SDK](https://apps.developer.homey.app/guides/how-to-breaking-changes)**
>
> This guide gives hints and guidance in the case that you need to make a change to your app that might break functionality for current users.

---

<div class="post-metadata">

**Author:** ![aste](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aste/32/9729_2.png) [@aste](https://community.homey.app/u/aste)\
**Post date:** [March 25, 2026, 9:29pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/128 "2026-03-25T21:29:16Z")

</div>

I just got the update and now all 3 was populated with Energy Total. I repaired my flows and will charge tonight.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 26, 2026, 7:21am UTC](https://community.homey.app/t/app-pro-keba-app/68776/129 "2026-03-26T07:21:26Z")

</div>

If no more things found…

( Please run the test app and come with feedback @_Gesperrt @Daniel_Lenfort @Roland_Brandmayr @Gabriel_Kreutzer, install it from [Keba | Homey](https://homey.app/sv-se/app/se.cohen.keba/Keba/test/) )

I will just wait for Homey to design some nice icons, ref: [se.cohen.keba · Issue #386 · athombv/homey-vectors-public · GitHub](https://github.com/athombv/homey-vectors-public/issues/386) before releasing the app.

If anyone in this thread are good designers they could chip in and do 2 icons following Homeys guidelines 🙂

---

<div class="post-metadata">

**Author:** ![Gabriel\_Kreutzer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_kreutzer/32/113628_2.png) [@Gabriel\_Kreutzer](https://community.homey.app/u/Gabriel_Kreutzer)\
**Post date:** [March 26, 2026, 8:41am UTC](https://community.homey.app/t/app-pro-keba-app/68776/130 "2026-03-26T08:41:13Z")

</div>

Hallo Jonathan, vielen Dank für deine Arbeit, ich kann dir leider nur mit Bildern helfen da ich keine Ahnung habe was du machst. Also Garage ist auf keba wird auch erkannt. Mehr kann ich noch nicht sagen da das Auto erst später nach Hause kommt.

 ![](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a2bb1bba3a28c3f4f20b37c7fb4f671c4bc822a4.jpeg)  
TypeError: Cannot read property ‘value’ of undefined

Component stack:  
at DevicePickerControl (address at index.android.bundle:1:5056890)  
at DeviceGeneratedControl (address at index.android.bundle:1:5048091)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at SceneView (address at index.android.bundle:1:4836232)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at RNCViewPager ()  
at PagerView (address at index.android.bundle:1:7658367)  
at Animated(Anonymous) (address at index.android.bundle:1:5679059)  
at PagerViewAdapter (address at index.android.bundle:1:4834098)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at TabView (address at index.android.bundle:1:4833235)  
at Carousel (address at index.android.bundle:1:5069471)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at DeviceControlsView (address at index.android.bundle:1:7757191)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at anonymous (address at index.android.bundle:1:4301719)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at DeviceScene (address at index.android.bundle:1:5038748)  
at withNavigation(DeviceScene) (address at index.android.bundle:1:7207160)  
at ThemeProvider (address at index.android.bundle:1:3160445)  
at WithThemeDarkComponent ()  
at SurfacePortalProvider (address at index.android.bundle:1:3912397)  
at SurfacePortalBoundary (address at index.android.bundle:1:3912535)  
at SurfacePortalHostWrapper (address at index.android.bundle:1:6842780)  
at StaticContainer (address at index.android.bundle:1:3214242)  
at EnsureSingleNavigator (address at index.android.bundle:1:3187293)  
at SceneView (address at index.android.bundle:1:3213215)  
at RNSScreenContentWrapper ()  
at ScreenContentWrapper ()  
at DebugContainer (address at index.android.bundle:1:3922570)  
at RNSScreen ()  
at Animated(Anonymous) (address at index.android.bundle:1:5679059)  
at Suspender (address at index.android.bundle:1:3918612)  
at Suspense ()  
at Freeze (address at index.android.bundle:1:3918678)  
at DelayedFreeze (address at index.android.bundle:1:3918344)  
at InnerScreen (address at index.android.bundle:1:3916487)  
at anonymous (address at index.android.bundle:1:3918181)  
at ScreenStackItem (address at index.android.bundle:1:3921040)  
at SceneView (address at index.android.bundle:1:4443204)  
at RNSScreenStack ()  
at anonymous (address at index.android.bundle:1:3920913)  
at ScreenStack (address at index.android.bundle:1:3920342)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at FrameSizeProvider (address at index.android.bundle:1:4400964)  
at SafeAreaProviderCompat (address at index.android.bundle:1:4407631)  
at NativeStackView (address at index.android.bundle:1:4442897)  
at PreventRemoveProvider (address at index.android.bundle:1:3188625)  
at NavigationStateListenerProvider (address at index.android.bundle:1:3215011)  
at NavigationContent (address at index.android.bundle:1:3214767)  
at anonymous (address at index.android.bundle:1:6218951)  
at NativeStackNavigator (address at index.android.bundle:1:4449598)  
at NavigatorRoot (address at index.android.bundle:1:4373439)  
at ThemeProvider (address at index.android.bundle:1:3187488)  
at EnsureSingleNavigator (address at index.android.bundle:1:3187293)  
at BaseNavigationContainer (address at index.android.bundle:1:3179519)  
at NavigationContainerInner (address at index.android.bundle:1:3217412)  
at AppNavigationContainer (address at index.android.bundle:1:4357927)  
at SurfacePortalProvider (address at index.android.bundle:1:3912397)  
at ThemeProvider (address at index.android.bundle:1:3160445)  
at Provider (address at index.android.bundle:1:3172368)  
at RNGestureHandlerRootView ()  
at GestureHandlerRootView (address at index.android.bundle:1:2823922)  
at RNCSafeAreaProvider ()  
at SafeAreaProvider (address at index.android.bundle:1:3174281)  
at ErrorBoundary (address at index.android.bundle:1:6286398)  
at App (address at index.android.bundle:1:4355797)  
at RCTView ()  
at View\_withRef (address at index.android.bundle:1:2408518)  
at AppContainer (address at index.android.bundle:1:2562293)

Stack trace:  
TypeError: Cannot read property ‘value’ of undefined  
at DevicePickerControl (address at index.android.bundle:1:5057421)  
at renderWithHooks (address at index.android.bundle:1:2444071)  
at beginWork (address at index.android.bundle:1:2475890)  
at workLoopSync (address at index.android.bundle:1:2493055)  
at renderRootSync (address at index.android.bundle:1:2492890)  
at performWorkOnRoot (address at index.android.bundle:1:2489774)  
at flushSyncWorkAcrossRoots\_impl (address at index.android.bundle:1:2438174)  
at processRootScheduleInMicrotask (address at index.android.bundle:1:2438569)  
at anonymous (address at index.android.bundle:1:5549024)

---

<div class="post-metadata">

**Author:** ![Gabriel\_Kreutzer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_kreutzer/32/113628_2.png) [@Gabriel\_Kreutzer](https://community.homey.app/u/Gabriel_Kreutzer)\
**Post date:** [March 27, 2026, 8:18pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/131 "2026-03-27T20:18:41Z")

</div>

Geht leider nicht, kann nicht mal starten. Bleibt ganze Zeit auf inaktiv.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 28, 2026, 9:15am UTC](https://community.homey.app/t/app-pro-keba-app/68776/132 "2026-03-28T09:15:24Z")

</div>

A new version is added for testing (1.1.17), added back the old capability (not in UI now, but accessible in flows) and named it …(deprecated) - so the app is backward compatible and should not throw errors or break flows.

@Gabriel_Kreutzer - what version of the app are you running now? Also do you have the P30 or P40 device? If you still have any problem after updating to the newest testversion - try this,

1. install the “old” version, the public version (1.1.13) - [Keba | Homey](https://homey.app/sv-se/app/se.cohen.keba/Keba/)
2. check that it works as it should
3. install the new “test” version again (1.1.17) - [Keba | Homey](https://homey.app/sv-se/app/se.cohen.keba/Keba/test/)
4. restart device
5. if problems, send in an diagnostic report
  1. Go to **More** → **Apps**.
  2. Tap the Keba app in.
  3. Go to the app’s **Settings** (gear wheel)
  4. Select **Create diagnostic report**.

---

<div class="post-metadata">

**Author:** ![Gabriel\_Kreutzer](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_kreutzer/32/113628_2.png) [@Gabriel\_Kreutzer](https://community.homey.app/u/Gabriel_Kreutzer)\
**Post date:** [March 28, 2026, 9:37am UTC](https://community.homey.app/t/app-pro-keba-app/68776/133 "2026-03-28T09:37:28Z")

</div>

Jonathan 👋, funktioniert, brauchst du noch die Daten? Kann ich gerne schicken. Vielen vielen vielen Dank

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 28, 2026, 11:03am UTC](https://community.homey.app/t/app-pro-keba-app/68776/134 "2026-03-28T11:03:45Z")

</div>

If it is working, Then I am happy and need no more information

---

<div class="post-metadata">

**Author:** ![\_Gesperrt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/_gesperrt/32/68736_2.png) [@\_Gesperrt](https://community.homey.app/u/_Gesperrt)\
**Post date:** [March 29, 2026, 6:45pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/135 "2026-03-29T18:45:29Z")

</div>

Hello @Jonathan_Cohen thank you for your app. I’ve installed it and I was able to pair it with my P40. In my first attempts to use your app, I was not able to set the max. A value. But I’m not sure if the problem sits in front of the monitor 🙂 I’m going to test it for the next few days.

---

<div class="post-metadata">

**Author:** ![Roland\_Brandmayr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roland_brandmayr/32/79135_2.png) [@Roland\_Brandmayr](https://community.homey.app/u/Roland_Brandmayr)\
**Post date:** [March 30, 2026, 6:54am UTC](https://community.homey.app/t/app-pro-keba-app/68776/136 "2026-03-30T06:54:31Z")

</div>

Hi Jonathan,

thank you for the app — it is working well with my P40. However, there are a few open points I’d like to discuss.

1. **Charging power control**  
At the moment, the charging power can only be adjusted in amperes (6–63 A). In the KEBA app, this can be set directly as charging power (from 4.1 kW to 11 kW, or up to 22 kW for the Pro model). It would be great to have a similar option in your app, allowing the user to define the maximum charging power in kW.

2. **Start/stop charging control**  
Currently, there is no flow card available to start or stop charging on the P40. Would it be possible to add this functionality?

My goal is to automate the charging process based on the state of charge of my home battery.

Thanks in advance, and I’m looking forward to your feedback.

---

<div class="post-metadata">

**Author:** ![Roland\_Brandmayr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/roland_brandmayr/32/79135_2.png) [@Roland\_Brandmayr](https://community.homey.app/u/Roland_Brandmayr)\
**Post date:** [March 30, 2026, 9:39am UTC](https://community.homey.app/t/app-pro-keba-app/68776/137 "2026-03-30T09:39:32Z")

</div>

I’ve just noticed that these are current limitations of the Modbus protocol. I’ve contacted KEBA to address this. At the moment, the P40 cannot be used for the charging automation I would like to achieve.

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 31, 2026, 4:20pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/138 "2026-03-31T16:20:09Z")

</div>

Yes, there are some missing features and some coming (according to docs).

I can/will add as soon they are available.

is there any workaround that I can add for your workflows in the meantime, I guess not ☹

---

<div class="post-metadata">

**Author:** ![Jonathan\_Cohen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jonathan_cohen/32/32700_2.png) [@Jonathan\_Cohen](https://community.homey.app/u/Jonathan_Cohen)\
**Post date:** [March 31, 2026, 4:20pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/139 "2026-03-31T16:20:59Z")

</div>

Did you solve it?

Else send screenshots, steps to reproduce and/or diagnostic report.

---

<div class="post-metadata">

**Author:** ![\_Gesperrt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/_gesperrt/32/68736_2.png) [@\_Gesperrt](https://community.homey.app/u/_Gesperrt)\
**Post date:** [March 31, 2026, 4:46pm UTC](https://community.homey.app/t/app-pro-keba-app/68776/140 "2026-03-31T16:46:04Z")

</div>

Hello Jonathan, I did solve it until now.

I set the current to 16A

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/3/d30bae425827e59a8bdf1d5a1389aa45ea907b44.png)

but the settings of my P40 didn’t change the setting.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/994d78a37eef61136aa7c4d4197d15dcf44d469f.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/b/0b76fd17b6cd0427349e6c9f35084ea97f2ac064.jpeg)

[Previous page](https://community.homey.app/t/app-pro-keba-app/68776.md?page=6)

[Next page](https://community.homey.app/t/app-pro-keba-app/68776.md?page=8)
