Translation via google:
marcusn I have a Ruuvi Gateway and several RuuviTags connected to it.
In addition to these, there is 1 piece “gig model” Ruuvitag, which can be taken with you or jammed somewhere outside the home to store heat for a while.
Ever since I started Ruuvi Gateway, I haven’t been able to get a synchronized history from that loose RuuviTag with the mobile application. The job is successful when you log out of your account and install the program again. You wouldn’t want to do it every time. Is this a bug or a feature?
Lauri Nov '22
Sounds like a bug. We haven’t seen or heard anything like it before. We need to be able to reproduce the problem to be able to fix it
Do you use Android or iOS and what is the model of your phone/tablet? Which version of the app?
marcusn Dec '22 Iphone 13 pro ios 16.1 Ruuvi app: 1.3.0(320)
That is, if Ruuvi Gateway is in use and one RuuviTag is directly connected to the phone via BT, the history of this single RuuviTag cannot be synced. The buttons Synchronize and clear do not appear.
Lauri Dec '22
Thanks for the additional information. We tried to reproduce this problem, but so far without success.
What came to mind now: could it be possible that you have set the application to cloud mode in the settings? In this case, the phone rejects Bluetooth messages from the sensors and the result is that the application does not know that your travel tag could share its internal history via Bluetooth.
marcusn Dec '22 Hi!
This is exactly the question. Apparently cloud mode is a global setting for everyone, so only one sensor cannot be read by BT.
The only solution seems to be to get another device to read the history and information of this one screw tag?
Lauri Dec '22
You can also not use cloud mode. There is no major disadvantage in itself that your phone receives measurement data from the same sensor both from the cloud and via Bluetooth.
Do you possibly have several iOS devices connected to this sensor at the same time? The Gateway just listens for information and is not connected, so then the synchronization should work normally.
This solved it. I will turn off the cloud mode when I read the history of this single sensor.