-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Aw-Watcher-Spotify data not visible in ActivityWatcher #13
Comments
There's no visualization currently available for the Spotify watcher, but
you should be able to browse the data through the "Raw Data" tab.
…On Wed, 16 Sep 2020, 04:46 B1zguy, ***@***.***> wrote:
I seemed to have correctly followed the instructions in the README.
Program works when running poetry run aw-watcher-spotify, yet no data
seems to be appearing in the ActivityWatcher webapp. Is there a step I've
missed?
I've also noticed the program not as a module/watcher in the menubar,
perhaps I need to add it there. How would I do that?
I'm running this all on MacOS Catalina (10.15.6). Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#13>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKXDOT7IE4DQWJZTVZ6TETSGARG7ANCNFSM4RODMKWA>
.
|
Noticed the same. Currently I see now point using it because of no visualisation. Also a question: Do I need to keep it running on command line via |
@ronilaukkarinen run it in the background and close that terminal |
how does one connect this to activitywatcher? i can't see it in my raw data tab. |
I seemed to have correctly followed the instructions in the README. Program works when running
poetry run aw-watcher-spotify
, yet no data seems to be appearing in the ActivityWatcher webapp. Is there a step I've missed?I've also noticed the program not as a module/watcher in the menubar, perhaps I need to add it there. How would I do that?
I'm running this all on MacOS Catalina (10.15.6). Thanks in advance!
The text was updated successfully, but these errors were encountered: