Add documentation

[DerAndereAndi]

No description provided.

[Vasco27]

Hi,

First of all, thank you for this great EEBUS implementation!

Are there any news about adding documentation to this package? I've managed to use your CEM implementation to get things started, but now I am having some trouble in figuring out how to work with the package (looking at the source code is proving to be unfruitful :) ).

So far, I managed to announce the CEM service and connect it to another ship node via user input pairing (I can see they are paired in the logs). But I am having difficulties in applying the use cases. For example, how do I know, via ship-go, when my CEM has successfully connected to an EVSE?

For clarification, I am developing a CEM that connects to an set of Elli Charger Connect EVSEs.

Thanks!

[DerAndereAndi]

There is nothing new in this front, due to lack of time for this. But contributions are always welcome :)

I would suggestion to use the discussion section or the Slack channel (you can find it on enbility.net contacts page) for concrete questions.

Regarding Ellis current chargers: you'll need to patch go to get them talking, see https://github.com/enbility/ship-go/blob/v0.5.0/patch/patch-golang.sh

The service has interface methods that will be called when a remote service was (dis-)connected. The usecases use events to inform about data updates, see the types.go file in each usecase for the messages and the usecases/api/ folder for the public methods of each supported usecase.

For more questions please use the options mentioned above.
Thanks

Update: you can also check evcc-io/evcc#13998 on how this is supposed to work. But the adoption is also tailored on how evcc works. I wouldn't really do it like that in a newly created HEMS.

[Vasco27]

Thanks for the fast response! Of course, anything that I can do to contribute I will :)

Yes, I came across that GO patch a few days ago, it was quite the journey, but I got the Elli chargers to talk in the end.

Thank you for the hints, I will keep on using your tool and hopefully contribute to its documentation.