Nearby doesnt seem to be working again with beacons again? #882
Comments
|
I just noticed this. #880 |
|
Sorry, that was an old warning that was supposed to be taken down. Things are working fine and that page has been updated. |
|
Hi @scottjenson, I am not seeing anything on my notifications drawer. It was working a few weeks back until I wanted to do a check today. I have my locations and bluetooth enabled, the Nearby icon lights up but no notifications. Here is a screen shot. What did I miss now?
|
|
Hi @scottjenson the physical web (used via google) still works although sporadically and I have to reset at times. The nearby however has not worked at all in quite some time. As I stated above I have reset the phone, installed any updates but it simply does'nt show anything. I've never had any problems with IOS but my android phone is very inconsistent. The device is picking up beacon signals when I scan with bluetooth only so the device is fine that way...just no nearby! Thanks |
|
Sorry to hear you hare having so much trouble. There is a simple test to
help diagnose the problem: if you go into Settings>Google>Nearby and get
the list view and tap the refresh button, do you see your beacon? This test
confirms that the basic plumbing is working. I hope that is the case.
If so, then it boils down to getting notifications. You'll need the latest
version of Google Play Services (10.0/84 I believe) Also notice that
notifications only show up after you wake up the phone. Try these things
and get back to me please.
Scott
…On Thu, Feb 2, 2017 at 1:15 PM, craigahunter ***@***.***> wrote:
Hi @scottjenson <https://github.com/scottjenson> the physical web (used
via google) still works although sporadically and I have to reset at times.
The nearby however has not worked at all in quite some time. As I stated
above I have reset the phone, installed any updates but it simply does'nt
show anything. I've never had any problems with IOS but my android phone is
very inconsistent. The device is picking up beacon signals when I scan with
bluetooth only so the device is fine that way...just no nearby! Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABAbujJZmsRqqrSzNb5CEhj9yesyYZzNks5rYkdwgaJpZM4Lmzs6>
.
|
|
Hi @scottjenson, I did your tests, yes I am seeing the list with no problem. I checked Google Play Services and the version is what you said. I have woken up my phone a few times with no avail. 95% of the time the notification does not show up. |
|
Would you mind sending me the short url you are testing? |
|
Here you go http://bitly.com/beacon01 |
|
Sorry, one more thing: is your beacon showing up in the list view?
…On Fri, Feb 3, 2017 at 4:19 PM, Nino Ross Rodriguez < ***@***.***> wrote:
@scottjenson <https://github.com/scottjenson>
Here you go http://bitly.com/beacon01
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABAbuhsBoRVMmuagIF5Cdyjk27dvbSGuks5rY8QcgaJpZM4Lmzs6>
.
|
|
it is showing up in the list view. i go to setting > google > nearbly, i see the list. just not in the notifications drawer |
|
I just programed my own beacon to http://bitly.com/beacon01 and confirmed that it is showing up in the list view but not notifications. I'm exploring why that is. One thing you can do as a potential workaround is to change the URL redirector to https://cbrbus.com.au/busstop/3410 (or something similar) to just test out a different URL One trick I use is to just add a parameter onto the end (like &x) but that seems to break your server. Scott |
|
@scottjenson thanks for the information. I will try the parameter for now. Just a clarification, doesnt beacons hold only a number of characters for the URL? That is why it is suggested to use a URL shortener. I may have misunderstood it. |
|
@scottjenson by the way, I just remembered that the parameter method did pose some issues for me before. Instead of hardcoding the variables in the html, I initially used the query params method (for more flexibility). However, after a while, nearby couldnt detect it anymore. In addition to the said issue, this might pose a bigger issue if the beacons go live long term. If initially the beacons are working fine then a few weeks or months down the line the beacons are not discoverable. |
|
It's only the final URL that matters, I was suggesting you add a parm to the final crbus.com. I was just suggestion you change the redirected URL to a new one. |
|
@scottjenson okies. thank you so much for your help :) Really appreciate it |
|
I've confirmed that your beacon is being lowered and not notifying. I'm looking into why this is. Can you confirm a few things for me? This will provide valuable feedback to the ratings team, thanks, Scott |
|
@scottjenson for this project, it is not yet live. We are about to push this for research and data gathering as soon as our material is ready to use. FYI, I changed my URL shortener and added the parameter for safety. So far so good :) will keep you posted if i see any problems. |
|
@scottjenson I can confirm the same thing happened to one of my personal pages @ b3m.it/B2000038 |
|
@scottjenson Same here, yesterday our messages suddenly stopped sending messages. They were working perfectly fine day before that. |
|
Hi Scott, sorry for the late reply i have been away. I have tried it on my particular device and its not working. I have switched nearby on and off but still nothing. It isn't even populating the list using Google settings like you suggested. The device uses Android 6.0.1 I have checked google play services settings and the device is using version 8.7.03 (no options are active to allow me to disable, update, or force stop). My main concern is the consistency of operation between devices if I am to introduce aspects of the physical web to business's so just ironing out the problems so to speak. Thanks again. |
|
GPS 8.7.03 is one year old; way before Nearby was introduced, you'll need v10.0.84 or newer. |
|
Thank you Adrian, that is correct. We totally appreciate not all devices have the latest software, but Nearby has been active nearly 6 months now, the number of devices with it is growing quickly. |
|
Same issue with Huawei P8 Lite 2017, Android 7 I found a short-term solution, which may not work in some devices because of disabled "force stop" button..
|
|
Notifications of my beacons do not appear. Only when I go into "Settings" => "Google" => "Nearby" finally found the link and suddenly appears also in the pull-down notifications |
|
Device: Pixel XL |
|
I have the same problem with notification drop down after re-installing and my Samsung S6. Before the re-install it worked fine. I can see the beacons in the nearby app. Current versions which doesn't work Google Play Services: 10.2.98 |
|
I have stopped receiving notifications for beacons since a couple of days ago. This is on three different devices. Device: Nexus 5X (two phones) Device: Nexus 6P Location and Bluetooth is on and nearby is set to show notifications for beacons on all devices. I can see the the preview in the nearby app on all devices. |
|
At this point, things should be working with the latest GPS. keep in mind that Nearby monitors notifications and if no one clicks on them, they will eventually stop creating notifications. So we strongly recommend that you test with a debug URL that you can use until you go live. If your beacon shows up in the listview you're 99% of the way there. Most of the time, the notification doesn't show up because you haven't power cycled your phone. The scan only happens when you wake up. |
|
Hi @scottjenson, do you mean that if the notification link isnt clicked for some time, it just doensnt show up anymore? That is my case now. I managed to broadcast a url in a beacon and im picking it up. But i didnt want to click it as i was enjoying just seeing that notification (yeah im weird). But now i have to go to Nearby just to see the link. |
|
@scottjenson what is the time period for witch a notification stops being shown if no one clicks it? Feels as this can happen quite easy with beacons in remote areas were a interaction isn't expected to happen very often or like now when beacons are a very new thing, people aren't used to it and will less likely click these notifications. My main use of beacons is for interaction with virtual functions in remote places and these will be clicked extremely seldom. A bit concerned that this de-notification could potentially ruin the whole experience and product since the user will not find it unless they explicitly search for itwith the nearby app. |
|
Mine's working here as well. Android 6.0.1 |
|
We have given up on the Physical Web. It no longer functions as a meaningful mechanism for notifying users that web content is available nearby. We now support nearby notification for users using our own iOS and Android background apps (launched by beacons). This provides for a level playing field between iOS and Android, makes for simple user opt-in (everybody knows how to install and app quickly and painlessly) and gives us far better control of notifications. They show up everywhere along with audio and vibration ... even on the Always On Display on some phones including Samsung Galaxy S*. |
|
HI @scottjenson ive noted you've been a bit quite on the subject of the physical web lately. It's understandable that your a very busy guy so I respect that. As there are a few poeple still putting their time and other resources into this is it safe to say that the physical web is still progressing as their are a few people on here who seem to be giving up over a few issues.....or are you looking into these issues and ways of maybe addressing them. The main issues seems to be:
|
|
Sorry for my silence but I'm no longer working on the Chrome team and no longer working on the Physical Web project. This was obviously a big passion of mine and it's frustrating that i can no longer support you folks. I've always said that the Physical Web could only work if it was an open standard supported by many players. I strongly hope others continue with the Physical Web. The Eddystone standard isn't going anywhere and you can still find beacon URLs through Android Nearby. |
|
Hi Scott,
Well thank you for getting back to us and I hope your next project is exciting for you. Has the project effectively been "shelved". Or has it been passed to the hands of the public to develop?
As your probably aware many people are starting new businesses or creating ideas based on the physical web and if it is going to end up like "betamax video" then maybe we should all consider this.
Or perhaps the google chrome team are continuing the project in your absence?
If this is something you could answer then that would be great as I am concentrating a business based on the physical web so I'm a bit worried :)..
I wish you all the best for the future and I hope you can reply to my final message just for your opinion on the future of the physical web.
Kind regards
Craig Hunter
… On 28 Aug 2017, at 21:36, Scott Jenson ***@***.***> wrote:
Sorry for my silence but I'm no longer working on the Chrome team and no longer working on the Physical Web project. This was obviously a big passion of mine and it's frustrating that i can no longer support you folks. I've always said that the Physical Web could only work if it was an open standard supported by many players. I strongly hope others continue with the Physical Web. The Eddystone standard isn't going anywhere and you can still find beacon URLs through Android Nearby.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Chrome should have specified many months ago their intended direction on the Physical Web. While I can't speak for them any more, everyone in this community has pretty much figured out that it's clearly not a high priority item for them. I've always said that the Physical Web project was 'free like the air' type of project. It was setup so that it could continue even if Google dropped support. So I do hope people understand that any Eddystone beacon can broadcast any URL and any scanner can find it. There is nothing stopping anyone from building experiments/research/products on top of this. Of course, the value of using URLs (instead of fixed IDs tied to only your database) is that it encourages an inter-operable space. Most single projects won't likely get this value if they are just a 'one off' type of approach. What will really help is if a group of projects feel like having a common shared way to describe objects. I still feel strongly in this approach, especially in AR and IoT use cases and will personally continue to explore this space. |
|
Hi @scottjenson, I tried finding any news or update about this. Couldn't find it :( |
|
Hi @scottjenson , We are developing a proximity marketing webpanel using Eddystone UID which is interacting with the google dashboard. We registered the Eddystone UID beacons from our panel to google dashboard with message and URL. So far it was working fine and we are able to get the near by notification in all our smart phone's near by app as well as in notification bar. But suddenly we are now facing an issue like we are able to discover the URL and message for all the registered Eddystone UID beacons in near by app. but somehow the notification is not generated in the notification bar for all the Eddystone UID. We checked in different forum but we are not getting any help from that. Can you please suggested what could be the issue. Thanks, |
|
Hi @Himen007, Were you able to make these work? I am facing the exact same behavior as you described for the last few days. I had around 100 beacons in 1 project and they stopped showing up in the notification bar since a week. I created a new project and added a beacon. It shows up both in the nearby app and in the notification bar. The ones in the older project show up only in the nearby app but not in the notification bar. Like others in the group here, my use case is to show them in the notification bar. |
|
@dipbiswas Do you use URL shortener? |
|
@ferencbrachmann, Yes. We use EddystoneUID and some of these beacons use URL shorteners. |
|
Do you have your own shortener or use some existing service? |
|
We use our own shortener.
…On Sep 26, 2017 6:59 PM, "Ferenc Brachmann" ***@***.***> wrote:
Do you have your own shortener or use some existing service?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALUypocGjvk49S8IuS1i78PdtXJ91yTHks5smYHUgaJpZM4Lmzs6>
.
|
|
FYI. At this moment even if I give a plain https url, it is still showing
up in the notification bar. Some beacons in the project have Urls with
shorteners and some dont. None of them show up.
Thanks
Dip
…On Sep 26, 2017 6:59 PM, "Ferenc Brachmann" ***@***.***> wrote:
Do you have your own shortener or use some existing service?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALUypocGjvk49S8IuS1i78PdtXJ91yTHks5smYHUgaJpZM4Lmzs6>
.
|
|
|
Hi @dipbiswas, No we are still not getting any solution. we follow the same steps as you done like creating a new project and added all the beacon into that project. and delete the old beacon from old project and also delete the project from google console. Hope we can get some more info from @scottjenson. Thanks, |
|
Hi there, Scott Jenson no longer works for the chrome team or the physical web project.
It seems that google themselves are still pushing beacons and eddystone. But do not seem to have a "goto" right now for technical issues.
I personally just use the physical web without the google console and have not had any problems. Some beacons come and go but I feel that is down to search parameters set by google. (This silly idea that unused beacons should drop if the search list)
Craig Hunter
… On 27 Sep 2017, at 06:39, Himen ***@***.***> wrote:
Hi @dipbiswas,
No we are still not getting any solution. we follow the same steps as you done like creating a new project and added all the beacon into that project. and delete the old beacon from old project and also delete the project from google console.
Hope we can get some more info from @scottjenson.
Thanks,
Himen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I have verified your link in: But as far as I know Google Nearby only works with HTTPS links. |
|
This problem comes and goes for us. Currently trying to setup 20 beacons. For two days we have setup the beacons the same way we have been, Beacon Tools see them on my Pixel and my Nexus 5, but Nearby on my Pixel will not see it, nor is it seen by Nexus 5. Sometimes it comes down to needing to send the URLs through the Physical Web Validator a few times and somehow that magically can start to make them work. (Some sort of caching issue on Google's backend?) We use goo.gl, all urls are HTTPS. It all points to an issue on the backend as far as we can tell. It is hard to use something that only works sometimes. |
|
I will throw something out there that I have found out, yet I can’t for the world of me understand why! But if it happens to me it may happen to others.
My WiFi at my office for some reason doesn’t like beacons. If my device is connected to WiFi on IOS then it won’t show beacons. As soon as I put it on 4G they show instantly. I’ve checked for security settings on router, and my android device still works and shows notifications when connected to the same WIFI.
Maybe some people have similar issues so try switching to network on your phone and not WIFI
Craig Hunter
… On 12 Oct 2017, at 04:42, cgslaughter ***@***.***> wrote:
This problem comes and goes for us. Currently trying to setup 20 beacons. For two days we have setup the beacons the same way we have been, Beacon Tools see them on my Pixel and my Nexus 5, but Nearby on my Pixel will not see it, nor is it seen by Nexus 5. Sometimes it comes down to needing to send the URLs through the Physical Web Validator a few times and somehow that magically can start to make them work. (Some sort of caching issue on Google's backend?)
We use goo.gl, all urls are HTTPS.
Tried updates to the phones
Turning tons of settings on and off
Different devices, about 10 of them
It all points to an issue on the backend as far as we can tell. It is hard to use something that only works sometimes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Here is my other observation. When I'm connected to another bluetooth
device like an earphone or bluetooth speaker, my notifications don't show
even when refreshing it multiple times but soon after I stop playing and
not use the bluetooth speaker, I get my notifications.
…On 12 October 2017 at 05:45, craigahunter ***@***.***> wrote:
I will throw something out there that I have found out, yet I can’t for
the world of me understand why! But if it happens to me it may happen to
others.
My WiFi at my office for some reason doesn’t like beacons. If my device is
connected to WiFi on IOS then it won’t show beacons. As soon as I put it on
4G they show instantly. I’ve checked for security settings on router, and
my android device still works and shows notifications when connected to the
same WIFI.
Maybe some people have similar issues so try switching to network on your
phone and not WIFI
Craig Hunter
> On 12 Oct 2017, at 04:42, cgslaughter ***@***.***> wrote:
>
> This problem comes and goes for us. Currently trying to setup 20
beacons. For two days we have setup the beacons the same way we have been,
Beacon Tools see them on my Pixel and my Nexus 5, but Nearby on my Pixel
will not see it, nor is it seen by Nexus 5. Sometimes it comes down to
needing to send the URLs through the Physical Web Validator a few times and
somehow that magically can start to make them work. (Some sort of caching
issue on Google's backend?)
>
> We use goo.gl, all urls are HTTPS.
> Tried updates to the phones
> Turning tons of settings on and off
> Different devices, about 10 of them
>
> It all points to an issue on the backend as far as we can tell. It is
hard to use something that only works sometimes.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK213WOfJX35OPQeZ2UUWbS0-_mucyGkks5srfv3gaJpZM4Lmzs6>
.
|
|
Interesting observations. To me this hints at scanning issues? Are you able to detect the beacon using a bluetooth scanning tool, or even just the Nearby list? Even that test isn't a fair test, since using a high powered foreground scan can change the test results of the low power background scan, but it may give some clues. |
|
I am able to detect the beacons with other scanning tools no problem. I tried MarkCasiano's and craigahunter's observations to see if that would make a difference for us, but it did not. |
|
i'm only testing this with samsung s7 and my observation is consistent with
different scanning software. When phone is connected to a bluetooth device,
it's taking to long to scan and and times shows up but disappears right
right away.
…On 12 October 2017 at 18:28, cgslaughter ***@***.***> wrote:
I am able to detect the beacons with other scanning tools no problem.
I tried MarkCasiano's and craigahunter's observations to see if that would
make a difference for us, but it did not.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK213d4tXgj9Sh4bxLA3S5Lg0YsYnS90ks5srq7DgaJpZM4Lmzs6>
.
|
|
The another issue I have found although not often is on IOS they stop showing on google chrome notifications but show everywhere else.
I switch the device off totally and the switch it on and let it reboot and everything shows up.
Craig Hunter
… On 13 Oct 2017, at 01:56, Mark Caesar Agpasa Casiano ***@***.***> wrote:
i'm only testing this with samsung s7 and my observation is consistent with
different scanning software. When phone is connected to a bluetooth device,
it's taking to long to scan and and times shows up but disappears right
right away.
On 12 October 2017 at 18:28, cgslaughter ***@***.***> wrote:
> I am able to detect the beacons with other scanning tools no problem.
>
> I tried MarkCasiano's and craigahunter's observations to see if that would
> make a difference for us, but it did not.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#882 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AK213d4tXgj9Sh4bxLA3S5Lg0YsYnS90ks5srq7DgaJpZM4Lmzs6>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
It seems that nearby notification are sporadic and do not follow any logic if not used via an APP. |
|
Hello everyone, santosh |
|
Hello everyone, I am working with EddyStone URL, and I have found that notices for URLs with the "HTTP" protocol are simply not shown, only those that have "HTTPS", even if they are masked under a URL shortener. |
|
@hulkco Please read this: http://blog.beeem.co/2018/02/the-ultimate-nearby-notification-troubleshooting-guide/ The end URL (and all resources on it as well!) requires HTTPS exclusively. |
|
Thanks @ferencbrachmann, with this article it is more clear to me how to configure the beacons !! |
and others
Hi, I am wondering if the Nearby using beacons has been disabled again. I have reset the Android phone (lollipop) back to factory state after it is not picking anything up. It does show during a scan that bluetooth beacons are recognised but no notifications appear. I have even used a new beacon with a new secure URL and still nothing.
I know a few months ago Nearby was disabled and I am thinking this may have been done again. It seems to work so consistently on Apple devices but is very much hit and miss on Android. I think this will be a big point that prevents consumer uptake if its going to be so inconsistent.
Please advise if you can, kind regards Craig
The text was updated successfully, but these errors were encountered: