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.

Sign up for GitHub

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

Jump to bottom

Manage stats.json entries that are not present (anymore) in LoxPlan #118

Open
christianTF opened this issue Nov 17, 2021 · 1 comment
Open

Manage stats.json entries that are not present (anymore) in LoxPlan #118

christianTF opened this issue Nov 17, 2021 · 1 comment
Labels
enhancement important A must-have feature

Comments

@christianTF
Copy link
Collaborator

https://www.loxforum.com/forum/projektforen/loxberry/plugins/315626-stats4lox-das-statistik-plugin?p=325661#post325661

If an collected element is deleted in LoxConfig, the element is still collected.

  • Manage these elements, by UI (user interaction), or possibly automatically.
@christianTF christianTF added the enhancement important A must-have feature label Nov 17, 2021
@christianTF
Copy link
Collaborator Author

christianTF commented Nov 17, 2021 •
edited
Loading

Ich würde - nach meinen Überlegungen - kein weiteres Mapping LoxPlan<->stats.json machen, sondern dem Fetcher die Errors erfassen lassen (x Fehler) und das im UI präsentieren, und anbieten, den stats-Eintrag zu entfernen.

Das hätte den Vorteil, dass auch Fehler-Elemente aufgezeigt werden, die von Loxone nicht abrufbar sind, auch wenn sie im LoxPlan sind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement important A must-have feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@christianTF