TeltoCharge

[xrado]

Hi, I would like to inform you that TeltoCharge ( https://teltonika-energy.com/ ) works nicely over OCPP.
I got the charger installed a few days ago and as their official mobile app is not working well with my phone I'm happy this works.

This are currently supported measurands:
Energy.Active.Import.Register,Current.Import,Current.Offered,Voltage,Temperature

[xrado]

Things I noticed:

1. If you start charging and then stop it with Charge_Control, starting it again does not work. It throws an exception until you unplug the charging cable and plug it in again, Transaction Id changes, and then the start works again. Is this normal? Is there a way to get a new transaction id so I can restart?

2. Changing Maximum_Current does nothing. I have dynamic load balancing enabled, maybe that's why? I have to ask them if this is possible.

3. Don't know what Current.Offered shows. When charging Current.Import shows current amperage going to EV and Current.Offered shows less. When charging stops Current.Import goes to zero, Current.Offered stays

[lbbrhzn]

Hi xrado,

Thanks for your update on this charger.
It would help if you could add a log file for the issues you report.

Kind regards,

lbbrhzn

[xrado]

Attaching logs for all 3 cases

1:

2022-10-27 15:00:08.950 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to 'charger': ping=3.0 ms, pong=66.0 ms
2022-10-27 15:00:27.799 INFO (MainThread) [ocpp] charger: send [2,"67678563-69e2-46b7-bcb3-d2292a3655ab","GetConfiguration",{"key":["AuthorizeRemoteTxRequests"]}]
2022-10-27 15:00:28.278 INFO (MainThread) [ocpp] charger: receive message [3,"67678563-69e2-46b7-bcb3-d2292a3655ab",{"configurationKey":[{"key":"AuthorizeRemoteTxRequests","readonly":false,"value":"1"}]}]
2022-10-27 15:00:28.284 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for AuthorizeRemoteTxRequests: 1
2022-10-27 15:00:28.303 INFO (MainThread) [ocpp] charger: send [2,"b7a99201-134c-4807-aae6-bfa097dcdd5c","RemoteStartTransaction",{"idTag":"charger","connectorId":1}]
2022-10-27 15:00:28.480 INFO (MainThread) [ocpp] charger: receive message [4,"b7a99201-134c-4807-aae6-bfa097dcdd5c","GenericError","",{}]
File "/config/custom_components/ocpp/switch.py", line 125, in async_turn_on
File "/config/custom_components/ocpp/api.py", line 283, in set_charger_state
File "/config/custom_components/ocpp/api.py", line 663, in start_transaction
File "/usr/local/lib/python3.10/site-packages/ocpp/charge_point.py", line 274, in call
File "/config/custom_components/ocpp/api.py", line 855, in _get_specific_response
ocpp.exceptions.GenericError: GenericError: , {}
2022-10-27 15:00:29.027 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to 'charger': ping=6.0 ms, pong=69.0 ms

2:

2022-10-27 20:09:49.286 INFO (MainThread) [ocpp] charger: send [2,"46e1b1f4-7166-459b-9b3c-44a5b8d685aa","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]
2022-10-27 20:09:49.604 INFO (MainThread) [ocpp] charger: receive message [3,"46e1b1f4-7166-459b-9b3c-44a5b8d685aa",{"configurationKey":[{"key":"ChargingScheduleAllowedChargingRateUnit","readonly":true,"value":"Current"}]}]
2022-10-27 20:09:49.608 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargingScheduleAllowedChargingRateUnit: Current
2022-10-27 20:09:49.609 INFO (MainThread) [custom_components.ocpp] Charger supports setting the following units: Current
2022-10-27 20:09:49.609 INFO (MainThread) [custom_components.ocpp] If more than one unit supported default unit is Amps
2022-10-27 20:09:49.611 INFO (MainThread) [ocpp] charger: send [2,"8f6bc554-112a-4c92-833c-3b1b2077a76e","GetConfiguration",{"key":["ChargeProfileMaxStackLevel"]}]
2022-10-27 20:09:49.990 INFO (MainThread) [ocpp] charger: receive message [3,"8f6bc554-112a-4c92-833c-3b1b2077a76e",{"configurationKey":[{"key":"ChargeProfileMaxStackLevel","readonly":true,"value":"3"}]}]
2022-10-27 20:09:49.993 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargeProfileMaxStackLevel: 3
2022-10-27 20:09:49.999 INFO (MainThread) [ocpp] charger: send [2,"520104e7-bffe-452d-8479-b84b64781e79","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":3,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":30.0}]}}}]
2022-10-27 20:09:50.300 INFO (MainThread) [ocpp] charger: receive message [3,"520104e7-bffe-452d-8479-b84b64781e79",{"status":"Accepted"}]
2022-10-27 20:09:56.095 INFO (MainThread) [ocpp] charger: send [2,"79359b29-66ff-4b17-b9f4-46b362dcef22","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]
2022-10-27 20:09:56.257 INFO (MainThread) [ocpp] charger: receive message [3,"79359b29-66ff-4b17-b9f4-46b362dcef22",{"configurationKey":[{"key":"ChargingScheduleAllowedChargingRateUnit","readonly":true,"value":"Current"}]}]
2022-10-27 20:09:56.259 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargingScheduleAllowedChargingRateUnit: Current
2022-10-27 20:09:56.260 INFO (MainThread) [custom_components.ocpp] Charger supports setting the following units: Current
2022-10-27 20:09:56.260 INFO (MainThread) [custom_components.ocpp] If more than one unit supported default unit is Amps
2022-10-27 20:09:56.261 INFO (MainThread) [ocpp] charger: send [2,"2137ac51-7e74-42ca-9de6-9eb631bc69b2","GetConfiguration",{"key":["ChargeProfileMaxStackLevel"]}]
2022-10-27 20:09:56.674 INFO (MainThread) [ocpp] charger: receive message [3,"2137ac51-7e74-42ca-9de6-9eb631bc69b2",{"configurationKey":[{"key":"ChargeProfileMaxStackLevel","readonly":true,"value":"3"}]}]
2022-10-27 20:09:56.755 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargeProfileMaxStackLevel: 3
2022-10-27 20:09:56.759 INFO (MainThread) [ocpp] charger: send [2,"1a6ca489-263a-4e2c-a876-970e67e53b26","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":3,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":11.0}]}}}]
2022-10-27 20:09:56.854 INFO (MainThread) [ocpp] charger: receive message [3,"1a6ca489-263a-4e2c-a876-970e67e53b26",{"status":"Accepted"}]
2022-10-27 20:09:59.725 DEBUG (MainThread) [custom_components.ocpp] Connection latency from 'central' to 'charger': ping=4.0 ms, pong=76.0 ms
2022-10-27 20:10:10.619 INFO (MainThread) [ocpp] charger: send [2,"1d8ccd5d-9c4a-4162-a8f3-1b85d80aa585","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]
2022-10-27 20:10:10.985 INFO (MainThread) [ocpp] charger: receive message [3,"1d8ccd5d-9c4a-4162-a8f3-1b85d80aa585",{"configurationKey":[{"key":"ChargingScheduleAllowedChargingRateUnit","readonly":true,"value":"Current"}]}]
2022-10-27 20:10:10.988 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargingScheduleAllowedChargingRateUnit: Current
2022-10-27 20:10:10.988 INFO (MainThread) [custom_components.ocpp] Charger supports setting the following units: Current
2022-10-27 20:10:10.989 INFO (MainThread) [custom_components.ocpp] If more than one unit supported default unit is Amps
2022-10-27 20:10:10.990 INFO (MainThread) [ocpp] charger: send [2,"8e4eccce-d87f-4e21-96c9-508b00f48d93","GetConfiguration",{"key":["ChargeProfileMaxStackLevel"]}]
2022-10-27 20:10:11.308 INFO (MainThread) [ocpp] charger: receive message [3,"8e4eccce-d87f-4e21-96c9-508b00f48d93",{"configurationKey":[{"key":"ChargeProfileMaxStackLevel","readonly":true,"value":"3"}]}]
2022-10-27 20:10:11.312 DEBUG (MainThread) [custom_components.ocpp] Get Configuration for ChargeProfileMaxStackLevel: 3
2022-10-27 20:10:11.318 INFO (MainThread) [ocpp] charger: send [2,"d9a266bb-2d94-4f7d-8689-bfda27aace63","SetChargingProfile",{"connectorId":0,"csChargingProfiles":{"chargingProfileId":8,"stackLevel":3,"chargingProfileKind":"Relative","chargingProfilePurpose":"ChargePointMaxProfile","chargingSchedule":{"chargingRateUnit":"A","chargingSchedulePeriod":[{"startPeriod":0,"limit":32.0}]}}}]
2022-10-27 20:10:11.603 INFO (MainThread) [ocpp] charger: receive message [3,"d9a266bb-2d94-4f7d-8689-bfda27aace63",{"status":"Accepted"}]


3:

2022-10-27 20:11:21.745 INFO (MainThread) [ocpp] charger: receive message [2,"66","MeterValues",{"connectorId":1,"transactionId":1666893355,"meterValue":[{"timestamp":"2022-10-27T18:11:20Z","sampledValue":[{"value":"1800","context":"Sample.Periodic","measurand":"Energy.Active.Import.Register","location":"Outlet","unit":"Wh"},{"value":"12","context":"Sample.Periodic","measurand":"Current.Import","phase":"L1","location":"Outlet","unit":"A"},{"value":"12","context":"Sample.Periodic","measurand":"Current.Import","phase":"L2","location":"Outlet","unit":"A"},{"value":"0","context":"Sample.Periodic","measurand":"Current.Import","phase":"L3","location":"Outlet","unit":"A"},{"value":"19","context":"Sample.Periodic","measurand":"Current.Offered","unit":"A"},{"value":"238","context":"Sample.Periodic","measurand":"Voltage","phase":"L1","location":"Outlet","unit":"V"},{"value":"237","context":"Sample.Periodic","measurand":"Voltage","phase":"L2","location":"Outlet","unit":"V"},{"value":"244","context":"Sample.Periodic","measurand":"Voltage","phase":"L3","location":"Outlet","unit":"V"},{"value":"2","context":"Sample.Periodic","measurand":"Voltage","phase":"N","location":"Outlet","unit":"V"},{"value":"30","context":"Sample.Periodic","measurand":"Temperature","location":"Body","unit":"Celsius"}]}]}]
2022-10-27 20:11:21.759 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Current.Import, phase_info: {'unit': 'A', 'L1': 12.0, 'L2': 12.0, 'L3': 0.0} value: 24.000000 unit :A
2022-10-27 20:11:21.760 DEBUG (MainThread) [custom_components.ocpp] process_phases: metric: Voltage, phase_info: {'unit': 'V', 'L1': 238.0, 'L2': 237.0, 'L3': 244.0, 'N': 2.0} value: 239.666667 unit :V
2022-10-27 20:11:21.761 INFO (MainThread) [ocpp] charger: send [3,"66",{}]```

[drc38]

There's no issue with the integration based on your logs, you'll need to ask the charger manufacturer and provide the logs

[MigliusBudriunas]

1. After stop transaction EVSE is probably stops in "Finishing" state. It seems it doesn't transition properly to "Preparing" state before starting new transaction. We will investigate ant try to fix this in future FW releases.
2. Available stackLevel options are: 0, 1, 2. We will change ChargeProfileMaxStackLevel parameter to 2 in future FW releases.
3. Current.Offered shows current that is offered to EV on every available phase. In this case it means 19A on L1, 19A on L2 and 19A on L3. Log shows that Current.Import is 12A on L1, 12A on L2 and 0A on L3. 19A limit is not violated on any phase. The system just sums currents on all phases when representing charger.Current.Offered value.

[danielszilagyi]

Hi,

Another fresh TeltoCharge user here :)
@MigliusBudriunas I have bought a TeltoCharge recently from a fully official reseller, and I could only update it to the L version firmware. It says hardware revision 000 in the information section in the app, and it is working correctly after the update, though I have issues with Dynamic Load Balancing and would like to get support, if possible, haven't found any contact, the reseller is also very helpful but I'm happy to investigate this directly.

To be ontopic, I have a dozen of unavailable entities, but generally starting and stopping charging worked. Energy metering did not, though in the app it is working. When OCPP is configured, availability cannot be changed, it stays off, in the log the following is seen:
2022-10-29 00:21:40.353 INFO (MainThread) [ocpp] TeltoCharge: send [2,"055bbf79-9a10-4c55-88ef-a1ba724105ec","ChangeAvailability",{"connectorId":0,"type":"Operative"}] 2022-10-29 00:21:40.510 INFO (MainThread) [ocpp] TeltoCharge: receive message [3,"055bbf79-9a10-4c55-88ef-a1ba724105ec",{"status":"Accepted"}]

Sometimes charging can be started sometimes not. Any hint would be appreciated.

[danielszilagyi]

Managed to get to where @xrado got :) and the current sensors are indeed calculated as multiple phases, my car takes 2x16A and this was taken at almost full battery with the Teltonika app reporting 8Amp charge.

It would be great to know if dynamic load balancing can be troubleshooted anyhow.

[danielszilagyi]

I can see in the log that the charger is reporting parameters for all 3 phases but only one is displayed. How could all be displayed as sensors?

2022-10-29 01:56:28.739 INFO (MainThread) [ocpp] TeltoCharge: receive message [2,"6","MeterValues",{"connectorId":1,"transactionId":1667001377,"meterValue":[{"timestamp":"2022-10-28T23:56:27Z","sampledValue":[{"value":"0","context":"Sample.Periodic","measurand":"Energy.Active.Import.Register","location":"Outlet","unit":"Wh"},{"value":"0","context":"Sample.Periodic","measurand":"Current.Import","phase":"L1","location":"Outlet","unit":"A"},{"value":"0","context":"Sample.Periodic","measurand":"Current.Import","phase":"L2","location":"Outlet","unit":"A"},{"value":"0","context":"Sample.Periodic","measurand":"Current.Import","phase":"L3","location":"Outlet","unit":"A"},{"value":"32","context":"Sample.Periodic","measurand":"Current.Offered","unit":"A"},{"value":"240","context":"Sample.Periodic","measurand":"Voltage","phase":"L1","location":"Outlet","unit":"V"},{"value":"241","context":"Sample.Periodic","measurand":"Voltage","phase":"L2","location":"Outlet","unit":"V"},{"value":"237","context":"Sample.Periodic","measurand":"Voltage","phase":"L3","location":"Outlet","unit":"V"},{"value":"2","context":"Sample.Periodic","measurand":"Voltage","phase":"N","location":"Outlet","unit":"V"},{"value":"35","context":"Sample.Periodic","measurand":"Temperature","location":"Body","unit":"Celsius"}]}]}] 2022-10-29 01:56:28.749 INFO (MainThread) [ocpp] TeltoCharge: send [3,"6",{}]

[drc38]

Details are stored in the attributes of the sensor. You can specify template sensors to turn them into sensors.

[G1EDR1US]

Hi danielszilagyi,

Does devices become unavailable after starting device as initiale state or you swtitched to unavailable and could not set back to operative state?

are you receiving any energy metering information or none? or incorrect?

Which current version are you using?

---

Also,
Please ask questions on this official Teltonika forum. As it would help others who get in trouble, and also development and support teams would see your post and may respond more quickly.

https://community.teltonika-energy.com

Best Regards
Giedrius Pupeikis

[danielszilagyi]

Hi Giedrius,

Thanks for the reply, I posted my questions and comments on the Teltonika board.

thanks,
Daniel

[gaborvar]

Hi @xrado Hi @danielszilagyi, great work, thank you very much.

The Teltonika documentation ([https://wiki.teltonika-energy.com/view/OCPP_1.6_JSON_guide]) states that TeltoCharger needs internet access and you have to "Set up a charging station account on your OCPP 1.6 JSON server.". Do I understand correctly that in your Home Assistant - OCPP -TeltoCharger architecture , an internal HA based component will play this role, and I don't need external Internet and additional OCPP registration?

Based on your experience, can you help me decide if I really have to duplicate my smart energy meter?
My setup:

1.A: Huawei SUN 10k KTL solar inverter. (to be installed very soon) with a Huawei Smart meter DTSU-666 https://support.huawei.com/enterprise/en/doc/EDOC1100020898/90c19c20/application-scenarios
1.B: I plan to implement Huawei HA Solar integration through Modbus TCP to provide power meter data to HA https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/789585-100027
2. TeltoCharger, installed later, optionally with its supported Smart Meter
3. I access the P1 DSMR port of the electricity service provider ELMŰ, works fine currently one-way, although the I (current) readings are rounded to integer. Power consumption and voltage readings are more than sufficient.

I am considering to remove unnecessary duplications from the 3 meters. With the Huawei installation I will get a smart meter with the same capabilities, measuring power on the very same point where TeltoCharger would also measure the same power flow parameters. Both are Modbus based but the Telto and the Huawei master cannot read the same device.
I am considering to drop the optional Huawei smart meter from the project. It will be required only when I might install batteries - which may never happen. My short term goal with the Huawei smart meter is only to get access to power meter readings.

My question: can I get detailed and timely smart meter readings through the OCPP interface of the TeltoCharger through the integration discussed in this article?

Many thanks!

[xrado]

@gaborvar you better write these questions to https://community.teltonika-energy.com or email them to [email protected]
About OCPP I don't think the internet is required, just your local network.
About the meter, I already had one for SolarEdge inverter (inepro PRO380), but at the time when the charger was installed it was not supported yet, so we had to install Carlo Gavazzi next to it just for the charger.