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

Attempt to share : Error ...need... Gateway... #860

Closed
DG12 opened this issue Apr 9, 2022 · 6 comments
Closed

Attempt to share : Error ...need... Gateway... #860

DG12 opened this issue Apr 9, 2022 · 6 comments

Comments

@DG12
Copy link
Contributor

DG12 commented Apr 9, 2022

A sensor that is in the cloud database, but currently not in range should be able to be shared.

SharedNeedsGateway

@priyonto priyonto self-assigned this Apr 11, 2022
@priyonto
Copy link
Collaborator

@laurijamsa Please share your thoughts. Thank you.

@laurijamsa
Copy link
Member

This is a design decision we have made earlier. If your sensor hasn't been in range of a Ruuvi Gateway in 10 days, it cannot be shared. Once we get more feedback about this, we may adjust the requirement if needed. But for now, let's go according the original spec.

@DG12
Copy link
Contributor Author

DG12 commented Apr 12, 2022

What is the reason for prohibiting sharing currently inactive, Ruuvi.

Consider scenario: sensor active for several months, now out of battery or otherwise out of range, user wants associate to view data from month ago.

@laurijamsa
Copy link
Member

Reason for this decision originally was that if a sensor has no data in the cloud, it would be a bad user experience when someone receives a shared sensor without data. And if no data in the cloud, it would mean in most cases that owner of the sensor has no Ruuvi Gateway and he/she tries to share an offline sensor which is not . But for sure some edge cases like yours could benefit an option to share it anyways. I'm ok to reopen this so that we can consider this again and decide which one is better option; restrict the sharing or not.

@laurijamsa
Copy link
Member

I encountered the same issue myself now on Android and WebUI when tried to share my sensor that has been months nearby a Gateway but it's not nearby a Gateway right now (Gateway has been offline 6 days). Would be probably better to allow sharing in these kinds of cases. But the question is, that how do we differentiate these cases from cases where user never had a Gateway nearby the sensor. Or do we even need to? Bluetooth sensor users without Ruuvi Gateways would start to share their sensors to their friends and then sharees would see no data -> bad new user experience. Should we start to store data to the cloud from the app itself at some point - this is a bigger topic to discuss about internally with our team.

I see the same error message on all clients ios/android/webui. This means that we'd need to remove this sharing restriction on all the clients if we'd like to proceed with this. Before rushing to modify this behaviour, we need to understand what kinds of problems it would cause. Comments are welcomed.

@laurijamsa
Copy link
Member

Opened a feature request topic and closing this issue.

https://f.ruuvi.com/t/sharing-a-sensor-that-hasnt-recently-been-nearby-a-ruuvi-gateway/5858

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

3 participants