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

BLE discovery doesn't give `live` results. #6

Closed
koktaildotcom opened this Issue Dec 10, 2018 · 28 comments

Comments

Projects
None yet
@koktaildotcom
Copy link

koktaildotcom commented Dec 10, 2018

I've tested by app beacon on v2.0.0. This app does a discovery of BLE beacons and check if the added devices are in that list to check if they are in/out range.

What do i expect:
Homey.ManagerBLE.discover gives a list of BleDevices that are in range.

What is the result:
Homey.ManagerBLE.discover gives a list of BleDevices that are not in range anymore, but where the first time the function ran.

It looks like a cache related issue.

@Swiftnesses

This comment has been minimized.

Copy link

Swiftnesses commented Dec 11, 2018

I wondered why my devices stayed connected!

@koktaildotcom

This comment has been minimized.

Copy link
Author

koktaildotcom commented Dec 17, 2018

Still an issue with rc4

@koktaildotcom

This comment has been minimized.

Copy link
Author

koktaildotcom commented Dec 20, 2018

Still an issue with rc7

@zwaardemaker

This comment has been minimized.

Copy link

zwaardemaker commented Dec 21, 2018

Still an issue with rc8 and 9. Would be great if this issue will be resolved soon ;-)

@rvmuilekom69

This comment has been minimized.

Copy link

rvmuilekom69 commented Dec 25, 2018

Indeed, eagerly waiting when this Will be resolved

@koktaildotcom

This comment has been minimized.

Copy link
Author

koktaildotcom commented Jan 4, 2019

@WeeJeWel any idea when you can take a look at this issue?

@rvmuilekom69

This comment has been minimized.

Copy link

rvmuilekom69 commented Jan 4, 2019

I think this issue is solved in firmware rc11, or is this another problem?

@koktaildotcom

This comment has been minimized.

Copy link
Author

koktaildotcom commented Jan 4, 2019

This issue still exist on rc11

@fantomnotabene

This comment has been minimized.

Copy link

fantomnotabene commented Jan 5, 2019

Yep, same here

@fantomnotabene

This comment has been minimized.

Copy link

fantomnotabene commented Jan 7, 2019

rc12, still the same behaviour

@zwaardemaker

This comment has been minimized.

Copy link

zwaardemaker commented Jan 7, 2019

Very annoying! Not much magic behind this

@zwaardemaker

This comment has been minimized.

Copy link

zwaardemaker commented Jan 8, 2019

RC13, still the same behaviour

@koktaildotcom

This comment has been minimized.

Copy link
Author

koktaildotcom commented Jan 11, 2019

Still an issue with 2.0.0

@rvmuilekom69

This comment has been minimized.

Copy link

rvmuilekom69 commented Jan 11, 2019

I am not going to update if this does not get fixed 😕

@zwaardemaker

This comment has been minimized.

Copy link

zwaardemaker commented Jan 11, 2019

@WeeJeWel will athom look at this issue?

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

WeeJeWel commented Jan 12, 2019

Yes. All BLE issues: We will address this issue in a 2.x release. Sorry for the delay!

@rvmuilekom69

This comment has been minimized.

Copy link

rvmuilekom69 commented Jan 12, 2019

So waiting until 2020 before upgrade to version 2.x?

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

WeeJeWel commented Jan 12, 2019

By 2020 v2.x is definitely available.

@rvmuilekom69

This comment has been minimized.

Copy link

rvmuilekom69 commented Jan 12, 2019

I know you/athom probably have more pressing issues to solve, but is this one of the more high priority issues or does it have a low(er) priority?
Thanks 😉

@zwaardemaker

This comment has been minimized.

Copy link

zwaardemaker commented Jan 12, 2019

high priority!

@Eternity-again

This comment has been minimized.

Copy link

Eternity-again commented Jan 16, 2019

Bump :-)

@Shadowz7

This comment has been minimized.

Copy link

Shadowz7 commented Jan 21, 2019

beacon is the best presence app, please fast!

@mrquincle

This comment has been minimized.

Copy link

mrquincle commented Jan 28, 2019

Required for Crownstone (https://github.com/crownstone/crownstone-homey) as well.

@mrquincle

This comment has been minimized.

Copy link

mrquincle commented Jan 28, 2019

Do you have Crownstones at Homey? We can send a few samples if this would make the debugging process of BLE faster.

@bvdbos

This comment has been minimized.

Copy link

bvdbos commented Feb 13, 2019

It looks like a cache related issue.

Couldn't this just be a typo in creating an array ?

@wzhick

This comment has been minimized.

Copy link

wzhick commented Feb 26, 2019

still not work

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

WeeJeWel commented Feb 28, 2019

Fixed in Homey v2.0.5. BLE discover results now expire after 45s.

@WeeJeWel WeeJeWel closed this Feb 28, 2019

@WeeJeWel WeeJeWel self-assigned this Feb 28, 2019

@WeeJeWel WeeJeWel added the bug label Feb 28, 2019

@WeeJeWel WeeJeWel added the fixed label Feb 28, 2019

@WeeJeWel WeeJeWel added this to the Homey v2.0.5 milestone Feb 28, 2019

@fantomnotabene

This comment has been minimized.

Copy link

fantomnotabene commented Apr 11, 2019

What am I doing wrong?
Still the same behaviour.
I have code like this:

Homey.ManagerBLE.discover().then(advertisementsArray => {
    let advertisement = advertisementsArray.first(advertisement => {
        return this.devices.hasOwnProperty(advertisement.uuid)
    })
    if (advertisement) {
        this.updateCapabilities(advertisement)
    }
})

But the serviceData attribute of advertisement is the same data every single time.
Explanation: I'm developing app for Mijia Hygrothermographs, which sends data to every thing around 'em. There are battery, humidity and temperature data in this serviceData. And it was working till 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.