I have just tried the BalenaLocating app. Installation and setup works fine. Also all data of detected beacons show up within the influx dashboard but not on my loacal dashboard or on the external ip dashboard.
Is there anything to help me to get this running? I went through all the settings a couple of times but cannot find what is wrong.
I am using a raspberry pi 3.
Hi @forensic_research welcome to the forums.
Could you confirm that the beacons are shown within the logs in the balenaCloud dashboard? You should see entries like:
11.02.21 13:17:26 (+0000) beaconService Beacon: beacon,device=969e6deadbeef78b9070,deviceName=long-flower,tag=532E8C62-F425-4A80-6282-6410 rssi=-43
These should be coming up at regular intervals at the bottom of the logs if they are continuing to be detected.
Could you also confirm if you’re seeing anything on the ‘Devices’ page, or by clicking the ‘Show Un-Named Tags?’ button?
No, unfortunately all pages do not show any devices nor tags etc.
this is what i get within the log. (see attached)
(Attachment balena-locating_autumn-dust-11.02.21_15_13_28_(+0100).txt is missing)
as attachment did not work.
Can you try to share the log again? Thanks.
(Attachment balena-locating_autumn-dust-11.02.21_15_13_28_(+0100).txt is missing)
11.02.21 14:02:30 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 23.153seconds ago.
11.02.21 14:02:31 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 24.085seconds ago.
11.02.21 14:02:32 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 25.255seconds ago.
11.02.21 14:02:33 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 26.121seconds ago.
11.02.21 14:02:35 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 27.925seconds ago.
11.02.21 14:02:35 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 28.164seconds ago.
11.02.21 14:02:35 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 28.277seconds ago.
11.02.21 14:02:36 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 28.855seconds ago.
11.02.21 14:02:36 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 29.422seconds ago.
11.02.21 14:02:36 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 29.662seconds ago.
11.02.21 14:02:38 (+0100) Beacon: beacon,device=1fec3e49a56f76d0c398c0eb0a4a2f94,deviceName=autumn-dust,tag=50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 rssi=-93
11.02.21 14:02:38 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 0.105seconds ago.
11.02.21 14:02:38 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 0.563seconds ago.
11.02.21 14:02:39 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 1.28seconds ago.
11.02.21 14:02:39 (+0100) Beacon for tag: 50765CB7-D9EA-4E21-99A4-FA879613A492-26195-46946 ignored because it was reported only 1.846seconds
Hey @forensic_research - That log confirms that the beacon is being found, and you said you could find the data in InfluxCloud - so that’s good. The question is why the beacons don’t show in your balenaLocating dashboard. Have you either named the tags:
If you don’t name the tags, you’ll need to click this button:
that is what I did. It does show absolutely nothing. Very strange but maybe you have another idea what I did wrong? I followed the very good instructions step by step.
Hi,
Could you enable support access for a few days and private message me the device UUID, and I’ll take a look for you.
sure thanks for your help.
Thanks to Phil from the balena team the issue is solved. 
My mistake was to use the influx_bucket “id” instead of the influx_bucket “name” within the device variables.
Now everything looks fine.
Thanks for the good support
No worries Josh - I’m glad you’re up and running! Let me know if you need help clearing out your influxDB bucket after all your tests trying to make it work. 
Phil
yes, would be a very nice move. I cannot find an “empty bucket” button.
I would just delete it and recreate it?
Hi Josh,
Just had a look - I could have sworn you could drop the data in the bucket - but it’s not working for me. I think you’ll have to do as you say: delete and recreate the bucket. You might then need to bounce the services on your device to pick up the new bucket.
Either that, or just wait 2 days, and the old data will expire and disappear anyway.
Phil