Looking back and forward 24 hours in the Monta API

[tougher]

The code changes seem almost too simple. Should I put the 24 hours in variables like the new MatchingXToleranceMinutes?

Tested on my own data from the last 90 days, with only one failed calculation (edge-case, see more below).

The failed calculation is a super edge-case where the charge failed (for unknown reasons) at 67% and I continued it later in the app where it failed again!! after 8 minutes and I continued again. This yields 2 charges from the Monta API.
Just to make it clear, I don't think TeslaMateAgile should try to handle edge-cases like this, I just added it out of interest.

{
    "data": [
        {
            "id": 123,
            "chargePointId": 123,
            "createdAt": "2024-08-15T07:23:00Z",
            "updatedAt": "2024-08-15T11:59:08Z",
            "cablePluggedInAt": "2024-08-15T07:23:00Z",
            "startedAt": "2024-08-15T07:23:00Z",
            "stoppedAt": "2024-08-15T11:59:03Z",
            "fullyChargedAt": null,
            "failedAt": null,
            "timeoutAt": null,
            "state": "completed",
            "consumedKwh": 50.52,
            "kwhLimit": null,
            "startMeterKwh": 7955.649,
            "endMeterKwh": 8006.167,
            "cost": 12.17,
            "price": 105.01,
            "priceLimit": null,
            "averagePricePerKwh": 2.08,
            "averageCo2PerKwh": 137.83,
            "averageRenewablePerKwh": 81.73,
            "failureReason": null,
            "stopReason": "fully charged",
            "note": null,
            "currency": {
                "identifier": "dkk",
                "name": "Danish kroner",
                "decimals": 2
            },
            "soc": null,
            "socLimit": null
        },
        {
            "id": 123,
            "chargePointId": 123,
            "createdAt": "2024-08-15T07:22:22Z",
            "updatedAt": "2024-08-15T07:22:29Z",
            "cablePluggedInAt": "2024-08-15T07:22:22Z",
            "startedAt": "2024-08-15T07:22:22Z",
            "stoppedAt": "2024-08-15T07:22:25Z",
            "fullyChargedAt": null,
            "failedAt": null,
            "timeoutAt": null,
            "state": "completed",
            "consumedKwh": 0.0,
            "kwhLimit": null,
            "startMeterKwh": 7955.649,
            "endMeterKwh": 7955.649,
            "cost": 0,
            "price": 0,
            "priceLimit": null,
            "averagePricePerKwh": 0,
            "averageCo2PerKwh": 0.0,
            "averageRenewablePerKwh": 0.0,
            "failureReason": null,
            "stopReason": "regular state change",
            "note": null,
            "currency": {
                "identifier": "dkk",
                "name": "Danish kroner",
                "decimals": 2
            },
            "soc": null,
            "socLimit": null
        }
    ],
    "meta": {
        "itemCount": 2,
        "currentPage": 0,
        "perPage": 10,
        "totalPageCount": 1,
        "totalItemCount": 2
    }
}

[tougher]

D'oh - I forgot about the tests.

[MattJeanes]

This change looks great, but the tests have broken because of it that need to be fixed

See TeslaMateAgile.Tests/Services/MontaServiceTests.cs lines 59 and 106

I'd just make the URL a static value incorporating the 24 hour shift rather than being smart about it like e.g. &fromDate=2024-10-10T00:00:00Z etc

[MattJeanes]

Also I think we can just set a static 24 hours here, we don't want to add config options for everything - if we see in future that having it configurable would be valuable then we can do that. The Tibber, Energinet and Awattar services all do similar things with fixed times to add.

[MattJeanes]

Looks good, thank you!