SolarNetwork could expose an OCPP 1.6J endpoint for EV chargers to connect to, so that private charging networks could be more easily managed through the SolarNetwork API. Currently SolarNode has components that allow the node to operate as a OCPP 1.5S charge point, and a OCPP 1.6J "local controller". This issue is for tracking the overall tasks needed to add an OCPP 1.6J endpoint directly in SolarNetwork that does the following:

1. Provides a OCPP 1.6J web socket endpoint for charge points to connect to.
2. Allows a SolarNetwork account user to manage credentials for any number of charge points, in such a way that the credentials can associate each charge point with a node ID associated with the same account.
3. Publishes to SolarIn the metering data collected during OCPP charging transactions as a datum stream using the node ID associated with the charge point credentials and a configurable source ID scheme that can be derived from the charge point credentials, identifier, connector, and location.
4. Publishes the same data in #3 to SolarFlux, so applications can subscribe in the same way as if it had come from a node directly.
5. Can handle SolarNetwork instructions relevant to OCPP such that the instructions are translated to OCPP messages and pushed to connected charge points.