Integration of HEMS for EV charger

[Ab0Ddore]

Hello,
Firstly thank you for this repository.
I am currently implementing this library to get information with the HEMS sended by an EV charger.
the problem is that I discover my charger in the mDNS and i try to connect myself to it. During the exchange of connection they transmit data correctly but when I arrived to the "ConnexionHello", I am ready and he is pending. After that he close the 4452 port (Node rejected by application). Do someone had the same problem ?
Thank you and have a nice day.

[sthelen-enqs]

Hi,
have you added the SKI of the HEMS (I assume you mean the example in this repo) to your EV-Charger? You should be able to do this in your EV-Charger's app or web-interface.

EEBus requires mutual-trust and authentication. Both your HEMS needs to trust your EV-Charger and your EV-Charger needs to trust your HEMS.

[Ab0Ddore]

I find it. By following my research i appeared some other tools wich are ONLY in the app.
Thank you so much

[Ab0Ddore]

Hello guys !
I have another question. I currently connect my simulated HEMS to my EV Charger correctly (connexionstatecompleted). Now I want to ask for packet of data like EVconnected, but I need for that the remote entity. I currently can imagine that is something like [EVSE] but i can't get it. Do you have any ideas ? Thank you and nice day !

[sthelen-enqs]

So EVConnected is part of the CEM EVCC use case which isn't enabled in the HEMS example. If you create an instance of the use case and add it to the service with a callback, that callback should get called with the EVConnected event when an EV is connected to the Wallbox (assuming the Wallbox supports the EVCC use case).

See e.g.

eebus-go/examples/hems/main.go

Lines 104 to 105 in 1edb43f

	h.uccslpc = cslpc.NewLPC(localEntity, h.OnLPCEvent)
	h.myService.AddUseCase(h.uccslpc)

for how it's done with LPC.

The examples are not complete solutions but intended as usage guidelines for the eebus-go stack and as such don't enable every usecase even if eebus-go does have an implementation for that use case.

[Ab0Ddore]

Ah ! Perfect that work perfectly. Thank you. Currently I can get EVSECC usecases informations. I'm working to get more informations !
Do you know if that works with tinyGO ? Thank you and have a nice day

[sthelen-enqs]

Considering tinyGO lists net/http as not supported (yet?) and ship builds on websockets, my gut reaction is no(t without a lot of effort on your part).

[Ab0Ddore]

Hello Guys,

I'm writing here to not open again a discussion and I think that my question is in the same way.
I currently use th HEMS to control my EVBOX and i connect myself to it perfectly ! But I have no many informations, I can't modifiate the current, I can't see if a vehicule is pluged,... Is it because I use a HEMS and so the model don't ask for this type of informations or is it because the EVSECC model isn't totally complete for my charger ? if it is that, is it to the event file that I need to modificate ?
Thank you

[Ab0Ddore]

Do you know if the access at many information are available only when a car is plugged ?

[sthelen-enqs]

You can try setting enabling debug/trace logs in the eebus-go stack and checking the output for the NodeManagementUseCaseData and NodeManagementDetailedDiscoveryData messages. Those will contain the remote device's supported use cases/features.

[DerAndereAndi]

Most E-Mobility UseCases require a car to be connected. Please take a look at the use case specifications for more details on that. The API methods descriptions usually also have a hint on it, but requires knowledge of the EEBUS wording.

[Ab0Ddore]

Ok, thanks for the informations, I will try to connect an EV and see what will change !
thank you !

[Ab0Ddore]

Ahhh thank you guys, since a vehicule is plugged i got so many more informations