# Kinetos professional openEVSE Wallbox issues

**URL:** <https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762>\
**Category:** OpenEVSE\
**Created:** [23 June 2025 08:52 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762 "2025-06-23T08:52:24Z")\
**Posts on this page:** 11\
**Page:** 3

<div class="post-metadata">

**Author:** ![schmue](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/s/0ea827/32.png) [@schmue](https://community.openenergymonitor.org/u/schmue)\
**Post date:** [24 June 2026 09:31 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/42 "2026-06-24T09:31:53Z")

</div>

I’ve found this Kinetos-auem branch in Github, build image and flashed it. but same as before.

> **[GitHub - pohlinkzei/openevse\_esp32\_firmware at kinetos-auem](https://github.com/pohlinkzei/openevse_esp32_firmware/tree/kinetos-auem)**
>
> kinetos-auem

---

<div class="post-metadata">

**Author:** ![schmue](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/s/0ea827/32.png) [@schmue](https://community.openenergymonitor.org/u/schmue)\
**Post date:** [24 June 2026 09:54 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/43 "2026-06-24T09:54:58Z")

</div>

I found out, you was right. It is no rccb. It is an RCM (Residential Current Monitor) 14-01

And the CT Sensor ist CT303

---

<div class="post-metadata">

**Author:** ![Janis\_Vaskevics](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/janis_vaskevics/32/35309_2.png) [@Janis\_Vaskevics](https://community.openenergymonitor.org/u/Janis_Vaskevics)\
**Post date:** [24 June 2026 11:21 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/44 "2026-06-24T11:21:37Z")

</div>

Current measuring is built in Atmega firmware, that you will probably have to flash too. You will need a programmer for that. Hopefully, they haven’t fiddled with hw design too much. Seems that Kinetos have made tens of variants with zero contribution to the opensource base.

---

<div class="post-metadata">

**Author:** ![schmue](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/s/0ea827/32.png) [@schmue](https://community.openenergymonitor.org/u/schmue)\
**Post date:** [24 June 2026 12:37 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/45 "2026-06-24T12:37:35Z")

</div>

Heureka…found the problem. It was a bad crimp at the jst connection.

---

<div class="post-metadata">

**Author:** ![chloepriceless](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/chloepriceless/32/39055_2.png) [@chloepriceless](https://community.openenergymonitor.org/u/chloepriceless)\
**Post date:** [23 September 2026 03:52 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/46 "2026-09-23T03:52:46Z")

</div>

Maybe that will help all the People who bought in Germany one of the Kinetos Boxes, I updated my EVCC and now it had a problem with the EVSE Firmware on the Kinetos Boxes (Power Rock Pro), My Version was 4.1.4 and EVCC mentioned only 4.1.9 or so.

So I took my Claude together and said that it should Update my Kinetos Firmware to the latest one, so it did deliver and now my Box ist on the Latest OpenEVSE Master Image. I tried to build all Functions of the Kinetos Hardware into the OpenEVSE Firmware und let it all Document it with all the Pins and Whistles it found in the Firmware.

It also wrote a Firmware Image Downloader so that everyone can Download their Firmware as a Backup, you only had to Upload the downloader and then you habe som endpoints on the ip on the reboot that you can dump your Firmware.

After That you can update to the latest Firmware from OpenEVSE - I habe a complete guide on how to build your on Version of it.

I also released som Version which is currently running on my Kinetos Box, I did not charge my car yet, but from all what claude could read, it should function - will do a Charge in the Afternoon.

This Version also works completely with the MIDI Counter and Display and RFID Reader if you have one.  
Functions I added:

- §14a Reduction
- RGB LED Light Show
- Modbus TCP for the MIDI Counter
- trimmed down old Stuff from Kinetos like their uLM Load Balancing - now it uses OpenEVSE Loadbalancing, whit the addition of having a house budget which the boxes now can load balance arount
- Home Assistant Discovery over MQTT
- Individual RFID Card History

If you are interested, here is my Github Repo to Checkout **[kinetos-openevse-v5](https://github.com/chloepriceless/kinetos-openevse-v5)**

 ![Bildschirmfoto 2026-09-23 um 05.40.14](https://community.openenergymonitor.org/uploads/default/original/3X/5/d/5db4502a4ec7075fbc3b0819cdeb63d6f3138505.jpeg)

 ![Bildschirmfoto 2026-09-23 um 05.40.43](https://community.openenergymonitor.org/uploads/default/original/3X/3/8/3862bca663121388ed6b6b3e27bbabbe27ffe0ec.jpeg)

 ![Bildschirmfoto 2026-09-23 um 05.40.59](https://community.openenergymonitor.org/uploads/default/original/3X/6/5/65c0c1db8348d441ee2b8d97171963046caac1d4.jpeg)

---

<div class="post-metadata">

**Author:** ![Janis\_Vaskevics](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/janis_vaskevics/32/35309_2.png) [@Janis\_Vaskevics](https://community.openenergymonitor.org/u/Janis_Vaskevics)\
**Post date:** [2 October 2026 16:55 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/47 "2026-10-02T16:55:07Z")

</div>

Nice work!  
Sadly, I threw out that Bond modbus meter and modbus adapter.

Also, did you not have to flash EVSE controller? Mine is on Kinetos firmware and ignores every command, like amperage setting and so on. Just returns RAPI\_RESPONSE\_BLOCKED.  
I did want to flash it with pure OpenEVSE, but Kinetos have wired absurd pins and I cannot use AVRDude on it. I might just print an Atmega adapter to try and flash some sense into it.

---

<div class="post-metadata">

**Author:** ![chloepriceless](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/chloepriceless/32/39055_2.png) [@chloepriceless](https://community.openenergymonitor.org/u/chloepriceless)\
**Post date:** [2 October 2026 17:22 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/48 "2026-10-02T17:22:04Z")

</div>

you can look into my repo, there is a nice little tool which lets you extract your actual firmware over the update button - then you can check if all of the port settings are right - maybe use gpt or claude to confirm it - the evse controlle is working fine on my side, nothing to flash on it - only the esp which is talking to everything

---

<div class="post-metadata">

**Author:** ![Janis\_Vaskevics](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/janis_vaskevics/32/35309_2.png) [@Janis\_Vaskevics](https://community.openenergymonitor.org/u/Janis_Vaskevics)\
**Post date:** [3 October 2026 06:29 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/49 "2026-10-03T06:29:41Z")

</div>

Thank you for info!

I flashed custom esp32 version a while agoand have connection with EVSE working. I didn’t make abbackup of firmware back then. Even current shaping was working great for whole summer. Currently not much settings can be changed on EVSE module and RAPI seems “neutered” but esp32 part seems great. I even installed other energy meter for Homeqssistant, to not fiddle with EVSE. Kinetos had a great idea, but it was overpriced a bit and ended sadly.

---

<div class="post-metadata">

**Author:** ![linuxdep](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/linuxdep/32/39141_2.png) [@linuxdep](https://community.openenergymonitor.org/u/linuxdep)\
**Post date:** [3 October 2026 09:41 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/50 "2026-10-03T09:41:20Z")

</div>

Nice, i have also write at github..

Can someone send me a original firmeware from kinetos bond board (singel board Version with meter to right windows) ?

i had also build e new version, but towday the test dont work with update from blank openevse Version to my meter version (build with KI-openrouter div. models test). On my wt32-eth ESp32 Board with the meter from box it has work. i think i should flash the esp32 lokal inside the box with clear memory.

i have install my own version with external meter, it works as a default openEVSE WB on EVCC.  
But in next Time i will also test your Version,

---

<div class="post-metadata">

**Author:** ![linuxdep](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/linuxdep/32/39141_2.png) [@linuxdep](https://community.openenergymonitor.org/u/linuxdep)\
**Post date:** [4 October 2026 20:14 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/51 "2026-10-04T20:14:16Z")

</div>

i have installed the version of chloepriceless, but the voltage is not correct. has someone also installed this version?

---

<div class="post-metadata">

**Author:** ![linuxdep](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/linuxdep/32/39141_2.png) [@linuxdep](https://community.openenergymonitor.org/u/linuxdep)\
**Post date:** [5 October 2026 21:55 UTC](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762/52 "2026-10-05T21:55:41Z")

</div>

some one has also DTS4921 meter on your box, i have adapted, you can find it on

> **[GitHub - linuxdep/kinetos-openevse-v5 at DTS4921\_meter](https://github.com/linuxdep/kinetos-openevse-v5/tree/DTS4921_meter)**
>
> DTS4921\_meter

Thanks an chloepriceless for your good work.

[Previous page](https://community.openenergymonitor.org/t/kinetos-professional-openevse-wallbox-issues/28762.md?page=2)
