drc38
drc38
Looks like the charger is not responding to the TriggerMessage you can try commenting it out on line 561 of `api.py`
As it is a charger specific issue (and should be fixed in the firmware) it's not something that would get merged.
> @drc38 any idea why this is failing? Not sure, but looks like `Payload` is deprecated in ocpp and needs to be removed
Could try replacing https://github.com/lbbrhzn/ocpp/blob/d0e2da15a3569c6d1c8a57f3cf528df3ffddf83d/custom_components/ocpp/__init__.py#L93 With ``` await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS) entry.async_on_unload(entry.add_update_listener(async_reload_entry)) ```
Another thought, in `async_unload_entry` the central system is closed but the charge point instance is not. Does it need to be or does the close of the central system take...
Great! The OCPP server is setup by the integration and run on the HA box (like a hub for other integrations). When a charger connects/registers it should ideally then set...
Have a look at #1035, you'll need to enable debug to see what's going on. It'll be an issue with the charger or what you are sending it in the...
The new service hasn't been modified since its release in 5.2 (it did not exist prior), I suggest debugging to see what's going on.
Here is the compare between the two versions: https://github.com/lbbrhzn/ocpp/compare/v0.5.1...v0.5.2 Unless you can identify the issue in the code by way of debug logs there's not much anyone else can do...
The charger is not ocpp compliant, as it does not report back any `SupportedFeatureProfiles`