-
Notifications
You must be signed in to change notification settings - Fork 0
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
Dev changes #2
Merged
Merged
Dev changes #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the battery of a device is too low, the service yields the `unavailable` event type with the `low_battery` reason. Then the device may charge itself (for example because it has been plugged to a charging dock by the last customer, or because the device has a solar panel). Once the battery is charged enough, the service can yield an `available` event type with the `battery_charged` reason. [closes #210]
drop UUID4 requirement in favor of simply UUID
…ll be developed in different endpoint(s) or API(s)
also clean up some telemetry wording
Depending on the actual device on board of the vehicle, some information can be unavailable.
Add new `battery_charged` event type reason
…battery_charged Revert "Add new `battery_charged` event type reason"
Update README.md
noting this missing step in ReleaseGuidelines
…etry Relax telemetry constraints
Fix broken link to Feb 7 webinar presentation
specify behavior for GET /vehicles with no device_id
add PUT /vehicles/{device_id}
Fixing a number of inconsistencies in the state diagram and adding a graphical representation. Also, adding event_reason to separate the more granual event designators.
…ced due to desire to handle out-of-order events
Updating schema version
Consistency with Provider API
Clarify and fix event state model
Remove reference to 412 for policy/business-logic
Updated to reflect that the process applies only to provider for now.
Clarified language around release notes and change descriptions.
Updated based on compliance changed approved by LADOT Compliance will exist in a seperate document.
Approved by LADOT. Updated compliance for in-trip telemetry for scooters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.