Hi Alberto, regarding UI application: Yes, exactly the one for getting visual feedback when doing simulation with NodeRed. For a python example, I can point you to this one:

Hello and happy new year! Is there any documentation or example of full python module? The UI application you mention is the one obtained using node red framework or there is also another

Welcome everyone - let's step right into 2023! May this upcoming year be extraordinarily successful for you personally and be at least as powerful for EVerest as last year has been. Let’s have a

Yes, thanks was a typo : )

Did you solved this issue already? It looks like a typo: iso151118 should be iso15118. Am Fr., 23. Dez. 2022 um 12:30 Uhr schrieb Alberto Merciai <alb3rt0.m3rciai@...>:

EVerest Discussion Upcoming Events EVerest Weekly Tech Sync When: Tuesday, January 3, 2023, 10:00am to 11:00am (GMT+01:00) Europe/Berlin Organizer:

Sent https://github.com/EVerest/ext-switchev-iso15118/pull/2 Thanks On Thu, 29 Dec 2022, 11:31 Cornelius Claussen via lists.lfenergy.org, <cornelius.claussen=pionix.de@...> wrote:

No, there isn't. But in general you should not access any of the topics directly outside of everest framework, that may confuse the internal logic and the topics are also not considered stable and may

Is there a way to retrieve all MQTT topics available given a config file?

I think you will need to add it in the everest branch here: https://github.com/EVerest/ext-switchev-iso15118 Feel free to make a PR to this branch! Most contributors are on vacation though so there

Is there a way to include optional fields like EVSEMaximumCurrentLimit EVSE>CARV2G CurrentDemandRes? Regards, Alberto

I'm asking it cause after setting device as you suggest I got this error, 2022-12-28 12:15:20.057820 [ERRO] iso15118_charge static void Log::error(const string&) :: ERROR - iso15118.shared.utils (51):

Ipv4 settings don't matter, manual is fine. Iso is using ipv6 link local addresses only. Alberto Merciai <alb3rt0.m3rciai@...> schrieb am Mi., 28. Dez. 2022, 17:59:

Cool, I install all josev modules and I will check if logs say something more about this issue. What about your eth interface, which are your ipv4 and ipv6 settings? I'm using the same iface used for

https://github.com/EVerest/ext-switchev-iso15118/blob/everest/iso15118/shared/logging/everesthandler.py Change last line to log.info instead of debug Then you see python output on console Cornelius

It should do that once the device for iso15118_charger is correct and josev starts correctly. Did you install all python deps for josev? You can also turn on debugging for josev, but I need to check

Hello Cornelius, I'm stuck with the same problem after your suggestions. By looking at wireshark logs I think that Everest needs to reply to SSDP broadcast message (SECC Discovery Protocol) but I

token_provider: module: JsDummyTokenProviderManual Change that to JsDummyTokenProvider without the manual. Normal config-sil can be used as an example. It has a dependency to evsemanager. When

Hello Cornelius, attached my config. Thanks a lot, Alberto On Wed, Dec 28, 2022 at 5:09 PM Cornelius Claussen via lists.lfenergy.org <cornelius.claussen=pionix.de@...> wrote:

Hi, Can you attach your config? Looks like it does not authorize the charging session. Make sure you have a dummy token provider module connected correctly as well as an tokenvalidator Best Cornelius