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

Disable the bundled afk-watcher but run server and window #43

Open
Game4Move78 opened this issue Feb 6, 2025 · 2 comments
Open

Disable the bundled afk-watcher but run server and window #43

Game4Move78 opened this issue Feb 6, 2025 · 2 comments

Comments

@Game4Move78
Copy link

Game4Move78 commented Feb 6, 2025

Is there any way to disable the bundled idle watcher? Will there be any issues if I run the ActivityWatch aw-watcher-afk at the same time?

I'd like to use the keyboard / mouse method provided by ActivityWatch for monitoring idle time. I added a PR that changes the input listener to use evdev or libinput so it should work for Wayland. I am not sure if using awatcher with ActivityWatch's aw-watcher-afk will have issues. You recommend disabling aw-watcher-afk in the README.

@2e3s
Copy link
Owner

2e3s commented Feb 8, 2025

Will there be any issues if I run the ActivityWatch aw-watcher-afk at the same time?

Yes, it would overlap, the data will likely be incorrect.

Is there any way to disable the bundled idle watcher?

I thought about that flexibility. Probably this way: branch
However, I'm not sure if you need to do it. If you use awatcher, you can equally rely on idle and window data collection (unless you have a specific issue in mind).

I'd like to use the keyboard / mouse method provided by ActivityWatch for monitoring idle time

What's wrong or incomplete with awatcher's idle time retrieval? It uses the method from the appropriate desktop environments, whether it's X11, or the detected specific Wayland implementations (example). I would suggest that it's better to rely on the builtin DE implementation which may cover more edge cases for that DE, rather than implement it on the low level.

@Game4Move78
Copy link
Author

Game4Move78 commented Feb 8, 2025

Awatchers idle implementation is perfect and complete. I agree the DE is better for detecting idle. Awatcher works very well on my Fedora 41 system. Thank you very much for your work and the contributors of this repo!

The low level implementation in that PR is for providing keyboard and mouse movements to aw-watcher-input on Wayland (pynput is X11 and XWayland only). For development I wanted to test if this caused the official aw-watcher-afk to work on Wayland as well, but since I use awatcher server, I wondered if I would always have to switch away from awatcher in order to experiment with Python implementations of aw-watcher-afk. Just wondered if this is already a feature, and I don't have a necessary use case. Thank you for answering my question!

It may be useful to have your idle and window watchers support toggling in general. To selectively disable window or idle watching if you don't want one of those recorded for a period, or want to selectively opt out of recording that data. Since neither are necessary for ActivityWatch. Also just in case these watchers deviate from this repo in the future and we need to disable them in awatcher for any reason it might be a useful feature. Feel free to close this issue if you disagree.

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

No branches or pull requests

2 participants