Repository navigation
Edge-case: Double-deduction of points via actionable notification (duplicate payload) #320
Squirrelq
started this conversation in
Development
Replies: 1 comment
|
I was able to track his down and confirm it could happen in some scenarios. I have a fix in place #321 that should prevent it in the next release. Thanks for bringing it up. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I ran into an interesting edge case where a reward claim was approved twice in a fraction of a second, deducting double the points. Since this seems to depend on a duplicate payload from the Home Assistant companion app, I am posting it here as a Discussion rather than an Issue because I cannot definitively reproduce it on demand.
What Happened:
The Evidence:
Looking at the reward sensor attributes, you can see the system processed the second claim and approval just microseconds apart, indicating it was a machine-speed duplicate rather than a manual UI button press:
cost: 80claimed_today: 1approved_today: 2points_spent_today: 160last_claimed: 2026-09-23T05:04:29.347370+00:00last_approved: 2026-09-23T05:04:29.347344+00:00Thoughts:
Has anyone else encountered this with actionable notifications? I am wondering if the backend might need a short debounce timer to reject duplicate payloads?
I have attached a screenshot of the points ledger showing the double drop. Happy to open a formal Issue if the maintainers want to track this!

All reactions