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

Add new battery_charged event type reason #237

Merged

Conversation

dbaty
Copy link
Contributor

@dbaty dbaty commented Feb 13, 2019

This pull request addresses #210.


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]

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 openmobilityfoundation#210]
@marie-x marie-x merged commit 0c703d4 into openmobilityfoundation:dev Feb 26, 2019
@bors-ltd bors-ltd deleted the bluesystems/battery_charged branch February 26, 2019 17:13
@hunterowens
Copy link
Collaborator

@Karcass this PR needs to wait on determine how to support multiple modes, see #170.

Can you prepare a PR to revert this in Dev? This also needs some tweaks on the JSON schema

@bors-ltd bors-ltd restored the bluesystems/battery_charged branch February 26, 2019 17:24
@hunterowens
Copy link
Collaborator

@dbaty, just to clarify why I asked for a reversion of this PR.

I think we need to have a clear way we add an support additional modes to MDS, as there are a number of difference in the core technologies, data we need and legal frameworks to support for different modes.

In #95, I propose a directory structure, with the generate_schema directory handling the heavy lifting of unifying subdatatypes across different modes (ie, timestamps).

What PR that we have to close #170 should have a how to guide about writing MDS support for different modes.

@dbaty
Copy link
Contributor Author

dbaty commented Feb 27, 2019

It's not clear to me how this event is linked to different transport modes. Could they not apply to electric bikes and scooters that are currently supported?

@tonial tonial deleted the bluesystems/battery_charged branch March 11, 2020 16:41
@tonial tonial restored the bluesystems/battery_charged branch March 11, 2020 16:42
@tonial tonial deleted the bluesystems/battery_charged branch May 27, 2021 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

New "battery_ok" event type reason to mirror "low_battery"
3 participants