@aste The discovery only find the “current” one, it does not find 2 Keba. so it goes in to Standard homey pairing flow. I try to manually filter current to force it into manual pair but no luck yet.
Homey pairing and me are not very good friends…
The mac on the other start with same as in topic?
I’m no programmer myself, so whatever you are doing, I find it as magic 
As changing the IP for one or the other works like a charm. Is there a way to duplicate current objects?
The old box:
LAN: 00:60:B5:3A:54:F8
WLAN / WiFi: 88:6B:0F:97:53:54
The new box:
LAN: 00:60:B5:3E:C7:DB
WLAN / WiFi: 84:2E:14:71:C3:73
So LAN MAC is the same. For me, that’s the connection I want to use. WIFI, however, is new.
@Jonathan_Cohen I checked my installed apps for add device process ending in an option for manual add. Both Shelly and SMA Energy do that.
Shelly by Allterco Robotics:
SMA Energy by @Richard_B:
Maybe it’s possible to ask @Richard_B how he implemented the manual add option following a failed auto discovery?
I also found this documentation about pairing devices and there seems to be an option for supplying additional information such as port and IP under “Device Pairing Data” header: Pairing - Homey Apps SDK
I hope this can be of any help making Homey pairing more of a friend
@aste, please try the new test version - if OK I will publish it live.
I used the Shelly app before to get the first version of fallback to work -but now I got a hint on something - it seem to work for me now to get up fallback, but do not have 2 boxes so cannot test so well - when I try to add my current box i get a duplicate error so I guess that is good
@Jonathan_Cohen Almoast, I can feel how close it is
Cannot read properties of undefined (reading “id”)
Great news!
After Homey updated itself to v8.1.2 last night a new Keba was found and added! Don’t know why it worked after reboot of Homey. No error messages this time, just added as expected.
The current Keba was added as Charge box1. I did change IP on the object to Charge box2. When the second Keba was added i found Charge box2 and added it even though it was already in Homey. Are you keeping track of the originally added MAC address and not the MAC addresses of the objects currently in Homey?
I have the Auto discovery checkbox checked as default.
Hi @aste, glad to here it ow works…
The missing ID thing should not really be able to happen (both the current and new have ID)… but I added more log rows to try to catch that in the future.
About MAC I do not have that, the identification on different devices is by the device serial. When using discovery it is Homey who handle the Mac and try to find/update the IP when any change or reconnect to network.
Anyway, a new version with the changes on pairing is submitted to production and already is in test.
1 Like
Thank you!
Is it possible next to have a look at my feature request in post 55?
Sent a donation for beverages of your choice as appreciation for your work.
I think I found a calculation issue.
Keba app indicates 3,9kW with “curr 6000” set = “Curr user 6000”. When charging my Zoe, that is not correct. From a “report 3” I get more accurate “P 704158” = 0,7kW
Could it be that you are calculating P from I values insted of using the P value from report 3?
@aste - yes I calculate… u*i=p…
But I will update to use P.
I will look into the wishlist and add those…
For #1 - you mean calculate u*i=p…/ phase?
@Jonathan_Cohen Tnx!
Regarding point 1 on the wishlist. Just realised that this is kind of wierd when you can’t trust I*U=P. Since Keba only supply total P this is of no use as it won’t reflect real world in every case. Or maybe this is only relevant for the Zoe. When I think about it, all other vehicals is actually following the formula.
As for number 2, you can just use “E total” for the total energy incresing.
And as a 2.5, you can add “E pres” for energy during current/last session 
For my usecase the priority order is in reverse. 5 being the most wished for item.
@aste for the #4 - a slider does not give any visual indicator on the value, also it seem to not “stick” where you drop it.
I do not think this will be usefull.
I could add more values / steps to the one I already use (between 6-63 A). These are available UI components in Homey, Capabilities - Homey Apps SDK
@Jonathan_Cohen I agree. The thermostat component would be the most visually pleasing, but that would probably count as bad code. The Picker is clearly the best option. Try 6-16 in 1A increments, 20-32 in 4A increments. I can’t find any Keba supporting more then 32A so you can most likely stop at 32A.
After 1.0.12 It does not seem to update the object. Last night it didn’t identify I was charging and never updated the power. Last update was 9 hours ago. That’s 12:00 today. I unplugged before 7 and replugged at 20.
But I also updated that Keba v1.12 to v1.15. There are a few more capabillities for UDP in v1.15.
I don’t know which one broke the updating.
report 2:
report 3:
55714bc7-5b0c-4c49-b8b9-e5c655f4d7e0
edit:
Box2 is active and charging: b3a3b0cb-fbf2-49aa-ace7-7768500761bb
@aste - the problem is the listening on UDP that gives error, the box on IP 10.199.99.220:7090 seem to work - the other get error “Error _sendUDPasCallback: Error: bind EADDRINUSE 0.0.0.0:7090”.
So the problem should not be any updates - but actually some kind of problem having 2 boxes and me not killing/closing the listening process correct.
I will try to look into this - but it is a bit hard without 2 boxes, but I will try to mimic and see if I can find a solution.
@Jonathan_Cohen I understand. Let me know if you like to setup a remote session and try on a live 2 box environment.
@Jonathan_Cohen Had a strange issue last night.
I deactivated Box1 on a schedule at 01:00.
It then self activated 9 seconds later.
How can that be?
Diag: a4a29c3d-010d-42f8-9f65-24aa981c6b2b
Hi Jonathan,
Box got deactivated after upfraded to 1.1.4
Is there anything I can do about this?
Br
Jørgen
@Zigme ,how do you mean deactivated, a red error message?
Please send me a Diagnostic Report from the app.
From what version did you update, and have you restated app and/or Homey since update.
