Two "computer names" in one computer

sperezconesa · June 2, 2021, 11:49am

Hello,
So I am using macOS Big Sur 11.3.1 and I am getting the activity split over two “computers” (BB-8 and BB-8.local) although I am only really using one laptop (with name BB-8).

One of the two never records anything. I am not sure why this split is happening and it is a bit anyoning when I go to the name that has no date. Is there a way to avoid this? Is this a bug of some sort?
Thank you very much for your help and I really love this program!
Best,
Sergio

johan-bjareholt · June 3, 2021, 8:38am

This is unfortunately a known bug, we have had plans to fix it for a while but have not had time unfortunately.

Here’s a link to a comment on how to fix it permanently on macOS without a fix in activitywatch

github.com/ActivityWatch/activitywatch

Multiple hosts with duplicated watchers

opened 09:32PM - 24 Jan 21 UTC

IIPatternII

type: bug

- [x] I am on the [latest](https://github.com/ActivityWatch/activitywatch/releases/latest) ActivityWatch version. - [x] I have searched the issues of this repo and believe that this is not a duplicate.  - **OS version and name**: macOS Catalina 10.15.7 - **ActivityWatch version**: 0.10.0 ## Describe the bug I have multiple hosts and duplicated activity watchers: <img width="1107" alt="image" src="https://user-images.githubusercontent.com/48034748/105642784-b881f100-5e6a-11eb-9776-bf0db25857c4.png"> I have seen issue #454 about merging multiple hosts and the [python script](https://github.com/ActivityWatch/aw-client/pull/50/commits/7c7747fa285faa153b21a60231887f9ede5bd771) to merge the buckets. I understand that the issue is caused by a change in the hostname, but in my case, I didn't change anything and I have multiple hosts and duplicated watchers from the very beginning. I would like to know if this is a problem because of a misconfiguration of my OS and if I merge the buckets and delete one of them, the extra host will reappear or not. I'm happy to try the merge and report back, but I wanted to ask first because I don't know how this could affect my data. Right now, some days the data is attributed to one host and other days to the other. I don't really know why. ## To Reproduce  Steps to reproduce the behavior: 1. Install ActivityWatcher. 2. Wait for a few days. ## Expected behavior Just one host with one set of watchers attributed to that host.

And here’s a link to the tracking issue to fix it without manual intervention in the future

github.com/ActivityWatch/activitywatch

Change how hostname/devices work

opened 08:39AM - 16 Sep 19 UTC

ErikBjare

improves: tech debt size: medium

A few things we should consider changing: - [x] Every device/installation sh…ould have a unique ID (a UUID) that does not change if the hostname is changed. - Completed in https://github.com/ActivityWatch/aw-server/pull/61 and https://github.com/ActivityWatch/aw-server-rust/pull/69 - [ ] If a bucket is created with a special hostname/UUID "local" or similar then it should default to the hostname/UUID of the running instance. - Or it should be the responsibility of the watcher to retrieve the UUID from `/api/0/info` and use it during bucket creation. Although defaulting to the local value seems like better API ergonomics (and would maybe make migration easier). - As an example, it is required for the web watcher to work properly with sync (see https://github.com/ActivityWatch/activitywatch/issues/307) - [ ] Additionally, we might want to move the hostname (later UUID) bucket attribute into the `data` field of buckets. This would impose specific semantics on the data field of buckets (which we currently lack) so might need further discussion (i.e. which data attributes are reserved for internal use in aw-server?) Originally discussed here: https://github.com/ActivityWatch/aw-server-rust/issues/61#issuecomment-531687577