Skip to content

drained: handle missed "changing" events#4188

Open
bobrippling wants to merge 1 commit intoespruino:masterfrom
bobrippling:drained-backstop
Open

drained: handle missed "changing" events#4188
bobrippling wants to merge 1 commit intoespruino:masterfrom
bobrippling:drained-backstop

Conversation

@bobrippling
Copy link
Copy Markdown
Collaborator

Sometimes my watch will change (with drained active) past the threshold and not deactivate drained. On debugging, the interval isn't set, so we set it unconditionally to ensure we have a charge "watcher".

@thyttan
Copy link
Copy Markdown
Collaborator

thyttan commented Mar 10, 2026

Does this mean something is broken in the event handling somewhere?

I mean, why would we be missing to set the interval in the 'charging'-listener?

@thyttan
Copy link
Copy Markdown
Collaborator

thyttan commented Mar 10, 2026

We also discussed some weird event listener behavior on #4141.

Could this be something similar?

@bobrippling
Copy link
Copy Markdown
Collaborator Author

Good memory! I would initially say no, and that drained just starts too late but that can't be the case - drained is running when I plug my watch in to charge 🤔

It could well be something with the firmware, like #4141. I'll see if I can get more details

@thyttan
Copy link
Copy Markdown
Collaborator

thyttan commented Apr 4, 2026

@bobrippling I'm thinking of opening an issue re event handling on espruino/Espruino. Have you managed to understand the problem any more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants