Discussions
Charging cost start at a (high) random number
Sinde the last few days I have experienced that when I start a charge through the API the field "cost" is populated with a high, random number. After one reading the number goes down to normal again. Seems like there is a spike in the beginning of the charge session.
Posted by Lars Bluhme 8 months ago
New status after 'charge stop' request'
Hi,
I am controlling my charger through the API, and start the charge every day at 00:05 and stop it at 07:55. The car prioritizes the charge between 02:00 and 04:00, for the ultra-low EV tariff, but using the whole 7:50h period if needed.
Until now, after running the 'stop charge' request, the new status of the charger was **`available`**, but it is now **`busy-non-released`**
This is the API call I use to stop the charge:
```
curl -s --request POST --url 'https://public-api.monta.com/api/v1/charges/<ChargeSessionId>/stop' \
--header 'accept: application/json' --header 'content-type: application/json' \
--header 'authorization: Bearer <TOKEN>'
```
It worked fine until now, because after that call, the new status for the charger was **`available`**,
```
{
"id": *******,
"createdAt": "2023-04-24T09:04:57Z",
"updatedAt": "2024-01-06T11:18:40Z",
"serialNumber": "*******",
"name": "************",
"visibility": "private",
"maxKW": 7.4,
"maxKw": 7.4,
"type": "ac",
"note": null,
"state": "available",
"location": {
"coordinates": {
"latitude": 00.000000,
"longitude": 0.0000000
},
"address": null
},
"connectors": [
{
"identifier": "type2",
"name": "Type 2"
}
],
"lastMeterReadingKwh": 3666.186,
"cablePluggedIn": true,
"brandName": "SyncEV",
"modelName": "SyncEV - BG",
"firmwareVersion": "AC7K-88071-V3.05"
}
```
But it is now **`busy-non-released`**
```
{
"id": *******,
"createdAt": "2023-04-24T09:04:57Z",
"updatedAt": "2024-02-02T09:54:57Z",
"serialNumber": "*******",
"name": "************",
"visibility": "private",
"maxKW": 7.4,
"maxKw": 7.4,
"type": "ac",
"note": null,
"state": "busy-non-released",
"location": {
"coordinates": {
"latitude": 00.000000,
"longitude": 0.0000000
},
"address": null
},
"connectors": [
{
"identifier": "type2",
"name": "Type 2"
}
],
"lastMeterReadingKwh": 4071.03,
"cablePluggedIn": true,
"brandName": "SyncEV",
"modelName": "SyncEV - BG",
"firmwareVersion": "AC7K-88071-V3.05"
}
```
The problem with this is that when I try to start the charge again I get this:
```
{
"status": "PRECONDITION_FAILED",
"message": "Charge point cannot start: not available",
"readableMessage": "Charge point cannot start: not available",
"errorCode": "CHARGING_CHARGEPOINT_NOT_AVAILABLE",
"context": null
}
```
So, in short, at some point between `2024-02-01 / 00:05 UTC` (last time I was able to start the charge with the API) and `2024-02-02 / 00:05 UTC` (first time I tried and it failed) the status of the charger after stopping has changed.
What is the problem with this? That we are forced to unplug and plug back again the car before we can start a new charge again. And that can be a problem.
Any solution for this?
Thanks
Posted by null 9 months ago
Alternate input parameters for /api/v1/auth/token
Hello, we are further developing our app Elly to use your Public API. We believe that ClientId and ClientSecret are difficult to handle for normal users through copy/paste. We think that /api/v1/auth/token should be able to be called with email/phonenumber and a password, like we do in your app and your portal. This way it would be much easier to give our users a smoother way of signing up for your Public API. What is your opinion on this?
Best regards
Esben Rud Nielsen, NetBryggeriet, Denmark
Posted by Esben Rud Nielsen 9 months ago
Retrieve a list of wallet transactions returns 404
Cannot retrieve wallet transactions.
When using the wallet transaction endpoint i get this message:
```
"status": "NOT_FOUND",
"message": "No wallet found for team = XXXXXX",
"readableMessage": "Not Found",
"errorCode": null,
"context": null
```
Posted by null 9 months ago
Set Limit
Hi
Is there a possibility to set limits with the API? Because we want to set limits (power consumption) because of power usage, PV & battery?
Posted by Peter 9 months ago
Endpoint for receiving list of charges is broken
When calling <https://public-api.monta.com/api/v1/charges> to receive a list of charges, the returned list is using the chargePointId value for both the chargePointId AND the id of the charge. Therefore, you never receive the id's of the charges.
Eg. requesting for chargePointId 3025881 returns a list of charges with incorrect id:
```
{
"data": \[
{
"id": 3025881,
"chargePointId": 3025881,
```
Posted by Kenni 9 months ago
Stop charge responging with BAD_REQUEST
Hi,
I have a cron work to stop the charge everyday at 07:55 (night tariff ends at 08:00) and it was working fine until yesterday.
Today I am getting an error every time I run the call to stop the charging session:
```
{
"status": "BAD_REQUEST",
"message": "Bad Request",
"readableMessage": "Bad Request",
"errorCode": "BAD_REQUEST",
"context": null
}
```
Example of a few days ago stop:
```
{
"id": xxxxxxx,
"chargePointId": xxxxxxx,
"createdAt": "2023-12-07T00:05:02Z",
"updatedAt": "2023-12-07T07:55:02Z",
"cablePluggedInAt": "2023-12-07T00:05:02Z",
"startedAt": "2023-12-07T00:05:03Z",
"stoppedAt": null,
"fullyChargedAt": null,
"failedAt": null,
"timeoutAt": null,
"state": "stopping",
"consumedKwh": 36.85,
"kwhLimit": null,
"startMeterKwh": 3314.989,
"endMeterKwh": 3314.989,
"cost": 12.14,
"price": 0,
"priceLimit": null,
"averagePricePerKwh": 0,
"averageCo2PerKwh": 0,
"averageRenewablePerKwh": 0,
"failureReason": null,
"stopReason": null,
"note": null,
"currency": {
"identifier": "eur",
"name": "Euros",
"decimals": 2
},
"soc": null,
"socLimit": null
}
```
Starting a charge session works fine.
Any idea?
Posted by null 10 months ago
Retrieve a list of wallet transactions returns 404
Hi
I have had a working integration for some time, however since 2023-11-09, I haven't been able to query the wallet endpoint.
I get a message of "No wallet found for team = xxxxx" (Removed the actual team id).
I am using a personal wallet which has been working fine, but no longer works.
Have you made any changes to the wallet backend?
Posted by Conrad Juhl Andersen 11 months ago
Bug in charge information
Just noticed a bug in the charge info. The startedAt date/time gives the current time for the charge whilst still plugged in and will update if the api call is re-done. It also shows as being after the stoppedAt time.
```
"id": 5954168,
"chargePointId": 2975778,
"createdAt": "2023-10-26T20:45:44Z",
"updatedAt": "2023-10-27T03:22:21Z",
"cablePluggedInAt": "2023-10-26T20:45:44Z",
"startedAt": "2023-10-27T07:07:52Z",
"stoppedAt": "2023-10-27T03:20:26Z",
```
```
"id": 5954168,
"chargePointId": 2975778,
"createdAt": "2023-10-26T20:45:44Z",
"updatedAt": "2023-10-27T03:22:21Z",
"cablePluggedInAt": "2023-10-26T20:45:44Z",
"startedAt": "2023-10-27T07:14:57Z",
"stoppedAt": "2023-10-27T03:20:26Z",
```
Posted by Roger Selwyn 12 months ago
Enterprise wallet transactions not available
I have a charger via the Sevadis enterprise license. You previously enabled me to see chargers and charges for the api, but I am unable to see the wallet transactions for the charger/team.
The charger is 2975778, the team is 217263.
Is it possible to make these transactions visible?
Posted by null 12 months ago