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

Claim ownership: spins, please wait: does not complete . defect 240812 1740 #2115

Open
DG12 opened this issue Aug 13, 2024 · 5 comments
Open

Comments

@DG12
Copy link
Contributor

DG12 commented Aug 13, 2024

Logged in as [email protected]. I have C1:9A:0B:19:3B:B6. I wanted to share it but says no owner.
Tap Claim Ownership,

Spins,
imagePlease wait ... 12:24,12:25,12:26,,, 12:33
Tap everywhere, no longer spinning, can not exit. Close app.

Start app. Still.logged in as [email protected].
Ruuvi 3B86 is present. Owner D***2@c***u.us (too much security :-{ . Oops found [email protected] (?) from previous??_)Very interesting but not nice !
Share option is correctly not present( logged in as [email protected] who is not owner).
tap Force Claim
display: Force Claim is done...
3.When sucessfully...

(Use NFC) (Use BT)
Tap NFC . Successfully owned by logged in user [email protected].

Share with [email protected]
Successfully shared... << Not really!)

See issue#2106 possible related.

Feel free to attempt to claim C1:9A:0B:19:3B:86.
Tricky I guess, since I have it. Maybe you could fake NFC? Fake MAC ?

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Aug 28, 2024

I can add this sensor MAC in WebUI, so from my "perspective" it looks like it was never claimed to an account.
Asking Otso to confirm about this.

Image

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Sep 2, 2024

Cloud should return 409 if sensor was already claimed.

I reconfirmed that this sensor has not been seen by Ruuvi Gateway (at least in the way that any data was sent to Ruuvi Cloud).

Maybe this issue could be about your Ruuvi Gateway @DG12 not being connected to internet or this sensor being out of range of Ruuvi Gateway? Or the given MAC address can be incorrect.

Image

@markoaamunkajo markoaamunkajo assigned DG12 and unassigned markoaamunkajo Sep 2, 2024
@DG12
Copy link
Contributor Author

DG12 commented Sep 3, 2024

Hmmm. Typo of Mac in the issue. Should have been C1:9A:0B:19:3B:86 .
I have revised typos in original post
OOPs

However, sharing does not require user to enter MAC.
Now I don't know how the wrong MAC got in there!?

Just for good luck I removed marko@ruuvi and shared it again successfully.

@markoaamunkajo
Copy link
Collaborator

markoaamunkajo commented Sep 4, 2024

I received sensor successfully too. I am confused about this issue, I think it must have been that user had no updated ownership data available from cloud to the app so it created this issue. I will ask Otso more about this scenario when we do tests gain.

Owner is [email protected] for this sensor, which seems correct.

@markoaamunkajo
Copy link
Collaborator

Moving to backlog as it needs more investigation but cannot be reproduced right now

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

No branches or pull requests

2 participants