Can't find any ConfigurableDevices after updating to 1.0.0 #207
Labels
Comments
|
Hello @joharei Sad to read this! The one way to check this is to write your code in typical java - maybe Kotlin is somehow not compatible? I will also take a look at this . Don't worry, we will figure this out :) |
|
I've tried implementing with Java, but there's no difference. Disabling the hardware filters didn't work either. These are the phones I've tried:
The log gets filled with these lines:
|
|
Hey @joharei ! Ok, I'm on it - will try checking this on Samsung Galaxy S6 phone. We are in touch! |
|
Tried the faster foreground scan - no joy.
Ranging works fine as well :) |
|
Ok, I launched our test suite on Samsung Galaxy S6 phone with Android 6.0.1. |
|
Here are my logs. I filtered out Logs
|
|
Hello @joharei This is really unusual. First thing - you said that you are using Samsung Galaxy S6 with android version 6.0.1, but from the logs I can read that this is version 5.0.1. Here is the source:
And info from our SDK which is creating service for API 21 (5.0.1):
It's seems that this is Samsung Galaxy S4 LTE-A device. Could you confirm that? Secondly, it seems that the scan results logs from stack below our SDK (Samsung implementation) scans a couple of Bluetooth devices with Service UUID For now, the questions is does our Estimote app from Google Play store discovers your Beacons? We need to do some troubleshooting before we find the solution. Cheers! |
|
Hi, That's right, I changed to another phone since that post, so this is indeed Samsung Galaxy S4, with API 21. Sorry I forgot to mention that! The Estimote app from Play Store works fine. I can connect to our beacons and make changes, and the changes are reflected in the cloud. |
|
Hey, I just released some fixups and improvements to scan filters - it may be connected to those issues on Samsung devices. You can check the new version Let me know if this changes anything :) |
|
Tried the |
|
Are you doing any additional stuff with your |
|
I created a sample project that's not working for me: https://github.com/joharei/BulkUpdaterTest I'm not doing anything else than scanning for configurable devices and starting the BulkUpdater. Could there be a problem with the authentication with the cloud? |
|
Hey @joharei Scanning for configurable devices doesn't involve any cloud communication. You need it later when authenticating to your device, but this is not the case here. I compiled and run your project on devices here, at Estimote, and uhm... Everything works just fine:
We don't have Samsung Galaxy S4 phone, so I can't tell you if it works on this specific device. Are you able to check this code on any other device? |
|
I have also run the sample app on a Samsung Galaxy A5, a Google Pixel, and (for experimenting) on a Raspberry Pi 3 running Android Things. They all report this:
Even though I have a whole bag of beacons on my desk. The beacons are a bit old (one says rev. D3.4 (07-01-2015)), but the Estimote app can connect to them, and they work for monitoring/ranging. |
|
Hey @joharei Wow, that was an extremely useful info! It seems that there is some bug on our side that screws up scanning for configurable proximity devices (old beacons). I'm investigating that. If this happen to be true, I will push fixups for you as quick as possible :) I'll keep you informed. |
|
Ok @joharei, there was a bug with parsing old configurable beacons. It's already fixed and will be released soon :) I'll inform you about the next release :) |
|
Hi @pawelDylag , I need a help. I'm trying to configure multiple beacons using the deviceConnection way and then SettingsEditor for configuring but have been unsuccessful so far.. Could you please give me a pointer or suggest a better way to configure them.. ? |
|
@pawelDylag , also can you help me with the following exception.. Since the device is connected first, and in the success callback, the device settings are edited ?! java.lang.NullPointerException: Protocol not yet detected - cannot edit device settings. You need to successfully connect to device first. 04-12 11:49:05.603 E/AndroidRuntime(31812): at com.estimote.coresdk.common.internal.utils.Preconditions.checkNotNull(Preconditions.java:21) 04-12 11:49:05.603 E/AndroidRuntime(31812): at com.estimote.mgmtsdk.connection.strategy.DeviceConnectionInternal.getCloudSyncEngine(DeviceConnectionInternal.java:157) |
|
Hey @puja1908 For the sake of clarity, would you kindly open a separate issue for your problem? Also please read this doc about establishing connection to you beacons, and take a look at this issue, where I have just posted some info about |
|
@pawelDylag , |
|
Hey @joharei Checkout the version Cheers! |
|
Hello again @pawelDylag! This update has improved things, but it's still not working unfortunately. The
This is the full log:
|
|
Hi @pawelDylag! Is there any progress on this issue? |
|
Hello @joharei
Basically, if Also, could you show me how you build your |
|
Some beacons seem to get the status SUCCEED, but still have pending changes. The next time a scan triggers the BulkUpdater though, that beacon seems to get updated, and will no longer have pending changes. This confused me, but it looks like it's working now, even though some beacons seem to need two rounds with the BulkUpdater to really be updated. Thanks for all the help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm actually trying to use the new BulkUpdater, but in order to do that, I need to scan for
ConfigurableDevices. The problem is that the callbackonConfigurableDevicesFounddoesn't return any devices.In my
Application'sonCreate, I initialize the SDK:And I start the discovery like this (this is Kotlin; bear with me):
The list of
ConfigurableDevicesis always empty, even though I have many Estimote beacons nearby.The text was updated successfully, but these errors were encountered: