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

Falsches Auto angegeben bei Benachrichtigungen #14937

Closed
pasqualito79 opened this issue Jul 19, 2024 · 1 comment
Closed

Falsches Auto angegeben bei Benachrichtigungen #14937

pasqualito79 opened this issue Jul 19, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@pasqualito79
Copy link

pasqualito79 commented Jul 19, 2024

Describe the bug

Hi zusammen,

mir ist aufgefallen, dass mein Telegram Bot bei der disconnect Message nicht das aktuell selektierte Auto nimmt, sondern das Standardauto. D.h. dasjenige welches im "loadpoint" als "vehicle" definiert ist.

Steps to reproduce

  1. Laden mit anderem auto als "vehicle" unter "loadpoint"
  2. Auto abstecken
  3. telegram message falsch
    ...

Configuration details

disconnect:
      title: "{{.vehicleTitle}} getrennt von Wallbox {{.title}}"
      msg: |
        {{.vehicleTitle}} getrennt von Wallbox {{.title}} nach {{.connectedDuration}}.
        --------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}
        Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    soc:

Log details

keine Log einträge, nur Telegram messages.

What type of operating system are you running?

Docker container

Version

0.128.2

@andig
Copy link
Member

andig commented Jul 19, 2024

Ist ein Duplikat von #7193, noch offenes Thema.

@andig andig closed this as completed Jul 19, 2024
@andig andig added the duplicate This issue or pull request already exists label Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants