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

[FEATURE] Support for trip tagging. #44

Open
dmbreakey opened this issue Feb 22, 2024 · 2 comments
Open

[FEATURE] Support for trip tagging. #44

dmbreakey opened this issue Feb 22, 2024 · 2 comments
Assignees
Labels
new feature New feature or request

Comments

@dmbreakey
Copy link

As a personal user, I want to tag trips based on geolocation so that I don't have to constantly use the Bouncie App to do so.

Bouncie offers a tagging function, but this doesn't appear to be available via the API. Unless I'm just blind.

The only alternative currently is to apply tags via the Bouncie App, either via my phone, or the website.

I'm aware the integration can't do anything until Bouncie exposes it, but does anyone know if this is planned, even?

@mandarons
Copy link
Owner

@dmbreakey I reached out to Bouncie to expose more APIs (see - #10 (comment)). No response yet.

Submitting a request to Bouncie to expose more (ideally, all) APIs that were used by their app, would help. You can try teaming up with other Bouncie users (e.g. users of this project) to influence Bouncie.

@mandarons mandarons added the new feature New feature or request label Feb 26, 2024
@dmbreakey
Copy link
Author

@mandarons That's pretty much what I figured; thank you. It would just be nice to be able to have HA react to various geocoded regions, and tag trips automatically, instead of having to do it by hand. Ah well! Looking at #10 it would appear they're not exactly against the idea, but it seems they're not motivated to do so, either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants