22 questions

31 answers

86 comments

109 members

0 votes
51 views 1 comments
by
In the teltonika energy app, OCPP Status stays at Authenticating even when the connection has been established.  OCPP is demonstrated to be working.  

I am using an encrypted websocket connection where the certificate/public-key is naturally provided by the central system.  None of the certificates in the app are populated.
by

Hello mick,

OCPP 1.6 standard have security profile ported from 2.0.1 https://www.openchargealliance.org/about-us/info-en-whitepapers/ (OCPP 1.6 Security Whitepaper (3rd edition)), which is not yet integrated with our firmware. This means that server can't automatically handle certificates with charger even though you would still be required to upload certificates to charger for the first time via application. We are working on implementation but for now we have ability to manage certificates via application only.


If charger can't find any certificates on device then charger still tries to connect to server.

We are going to look into problem why status stays Authenticating but if charger is connected on server then you should not worry about this status then.

Which firmware version are you using?

2 Answers

0 votes
by

Hello mick,

OCPP 1.6 standard have security profile ported from 2.0.1 https://www.openchargealliance.org/about-us/info-en-whitepapers/ (OCPP 1.6 Security Whitepaper (3rd edition)), which is not yet integrated with our firmware. This means that server can't automatically handle certificates with charger even though you would still be required to upload certificates to charger for the first time via application. We are working on implementation but for now we have ability to manage certificates via application only.


If charger can't find any certificates on device then charger still tries to connect to server.

We are going to look into problem why status stays Authenticating but if charger is connected on server then you should not worry about this status then.

Which firmware version are you using?

0 votes
by

firmware version v1.5.8L