Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEST: Should remoteStartStatus.duration change (or stay at 0 minutes)? #10

Open
jamisonderek opened this issue Jun 15, 2021 · 1 comment
Labels
FordConnect.EV FordConnect.ICE FordConnect test using ICE vehicle

Comments

@jamisonderek
Copy link
Owner

No description provided.

@jamisonderek jamisonderek added FordConnect.EV FordConnect.ICE FordConnect test using ICE vehicle labels Jun 18, 2021
@jamisonderek
Copy link
Owner Author

This needs to be tested on a real vehicle (doesn't matter if it is ICE or EV).

The simulator always shows a duration of 0. The documentation says this unit is in minutes. On a real vehicle, what does duration do when the engine is running? What does it do when the engine is not running? Does the timeStamp value change, or is it always at the point where the remote command was sent?

/api/fordconnect/vehicles/v1/{{vehicleId}}

        "remoteStartStatus": {
            "status": "ENGINE_RUNNING",
            "duration": 0,   <<<<<<
            "timeStamp": "06-18-2021 18:26:11"
        },

@jamisonderek jamisonderek changed the title Validate: Should remoteStartStatus.duration change (or stay at 0 minutes)? TEST: Should remoteStartStatus.duration change (or stay at 0 minutes)? Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FordConnect.EV FordConnect.ICE FordConnect test using ICE vehicle
Projects
None yet
Development

No branches or pull requests

1 participant