drc38
drc38
In post_connect go through and comment out any lines the unit is not accepting and see if you can get to the point the integration loads.
Looks like the issue is any get_configuration call that passes a parameter. So they'll all need to be commented out and replaced with a default value.
>I make a v0.1.5. I just limit the model at 20 character, so you will have a "Grizzl-E Smart Conne". Sorry about that, I just patch the it, thje problem...
Another option would be to copy and modify the ocpp package schema length. The Mobilityhouse package needs to go into `deps/lib/python3.11/site-packages/` under your config folder and then can be modified.
@callifo any improvement with 0.5.2?
You can try using one of the ocpp services and see if the charger is still responsive. Also check what is happening at the websocket level. https://github.com/lbbrhzn/ocpp/issues/1119#issuecomment-2024682181
Very strange, looks like an issue at the charger end. You can try the diagnostic service to see if the charger is logging information that may help understand what's going...
Is there a firmware update available?
You need to debug the websocket messages to see why the connection closes.
It is `websockets`