Use to request a remote start command in eDRV
A documented eDRV operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Use to request a remote start command.
- POSTChanges data · Commands
/v1/commands/remotestart
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which eDRV operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other eDRV operations
- Create a new charge stationPOST · changes data
- Create a new tokenPOST · changes data
- Create a new driverPOST · changes data
- Create a new locationPOST · changes data
- Create a new connectorPOST · changes data
- Create connector with parametersPOST · changes data
- Delete a smart charging scheduleDELETE · changes data
- Use to delete a charge stationDELETE · changes data
Questions
- Can HumDay use to request a remote start command in eDRV?
- Yes. This operation is published in eDRV's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my eDRV data?
- Yes — this is a POST operation, so it changes something in eDRV. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your eDRV account.
Where this came from
Read from a published API description for eDRV at developers.edrv.io/openapi/5f15c43c87b0d6001ea97414. The description above is the provider’s own wording, not ours. Last published 2020-12-30.