teslamate-org/teslamate

[Feature Request] More detailed Geo-Fence cost entry

Open

#4,454 opened on Dec 24, 2024

View on GitHub
 (5 comments) (1 reaction) (0 assignees)Elixir (932 forks)batch import
Hacktoberfestenhancementkind:ideanote:discussion

Repository metrics

Stars
 (7,981 stars)
PR merge metrics
 (Avg merge 5d 19h) (41 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

There's at least two situations that I've encountered where the Geo Fencing cost entry is missing some details that impact cost calculations.

  1. Flat fees 89F0C958-8130-454B-B939-AF1E1DDD20A5_1_201_a 1144BB09-04C7-4250-9D13-9C7CEDB06BE4_1_201_a

  2. Station Time Rate (aka "Parking Fees") 02749BA0-7760-4DFF-9E01-1573B625BB1F_1_201_a

Expected Behavior

I should be able to provide a detailed breakdown of a stations' costs and use those values to get an accurate price across different visits. Note: I'm interested in contributing to the project, I might open a PR if I can get things set up

Steps To Reproduce

No response

Relevant log output

.

Screenshots

Additional data

No response

Type of installation

Docker

Version

v1.32.0

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.