NRGKICK 2 (KfW)

[thecem]

Version of the custom_component

v0.3.21

Configuration

Configured like in the repo description:

charge point Identity: NRGKICK

charge point Identity: NRGKICK

Describe the bug

The NRGKICK could not connected. Is the config right? What do you need to analyze or add NRGKICK to this repo?

Thanks a lot!

Debug log

Add your logs here.

2021-11-28 10:16:50 INFO (MainThread) [custom_components.ocpp] {'host': '0.0.0.0', 'port': 9000, 'csid': 'central', 'cpid': 'NRGKICK', 'meter_interval': 60, 'monitored_variables': 'Energy.Active.Import.Register,Energy.Reactive.Import.Register,Energy.Active.Import.Interval,Energy.Reactive.Import.Interval,Power.Active.Import,Power.Reactive.Import,Power.Offered,Power.Factor,Current.Import,Current.Offered,Voltage,Frequency,RPM,SoC,Temperature,Current.Export,Energy.Active.Export.Register,Energy.Reactive.Export.Register,Energy.Active.Export.Interval,Energy.Reactive.Export.Interval,Power.Active.Export,Power.Reactive.Export'}

[lbbrhzn]

It appears your charger did not contact the OCPP central server.

• You may need to reset you charger before it switches to the new OCPP server.
• Is the charger on the same network as your home assistant server?

[thecem]

Same network, access to ocpp server in HAis possible. Charger is rebooted after configuration. I tried to sniff the packets from the NRGKICK no response. I captured some traffic between the app and the NRGKICK via Charles, seems to be ws:// too. But was never able to get a try (packet) from NRGKICK to the OCPP Server. Seems to be that there is some issue with the firmware, I try to get some information from the vendor Dinitech.at.

Actually installed:

[thecem]

captured some packets:

.100 is HA .151 is nrgkick2 nrg21.zip

[dreimer1986]

Just a idea on my side. As I NEED the last / on my wallbox, did you try ws://192.168.176.100:9000/ ?

[thecem]

I tried, but even with / no result. Thanks a lot..

[lbbrhzn]

did you try withouth ws:// ?

[bardahlm]

The packet dump show traffic from HA to the web port (port 80) on the charging station, there is no OCPP traffic in the capture.

1   0.000000    192.168.76.100  192.168.76.151  TCP 74  36938 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1 TSval=126991611 TSecr=0 WS=128
2   0.024789    192.168.76.151  192.168.76.100  TCP 60  80 → 36938 [RST, ACK] Seq=1 Ack=1 Win=28694 Len=0

[thecem]

@lbbrhzn : tried without ws:// -> not working @bardahlm : in the capture is everything what between nrgkick an HA is exchanged. I don’t know why there is a com. From ha 80 to charger…

[thecem]

In between there is some fw update:

[lbbrhzn]

This seems to be a charger issue, not related to the integration. Closing...

[KETRF]

Hi,

I wanted to share an alternative software that might be more suitable for this application and is compatible with the current software version of the NRGkick. You can check out the OCPP.Core project, which is an OCPP (Open ChargePoint Protocol) server written in .NET 8. It includes a management Web-UI for administration of charge points and charge tokens (RFID-Token).

Additionally, I had opened a bug ticket a month ago because several features were not working properly with the NRGkick. Unfortunately, the issue was not resolved.

You can find more information and the software at the following link: OCPP.Core GitHub Repository.