LoPy stops detecting BLE advertisements

[duffo64]

Wow...

On 1.10.1.b1 it's really, really, really better !

...did I say "really" ?

[alanm101]

Thanks! I will test this weekend.

[duffo64]

@alanm101
Despite my initial enthusiasm, I must say that the situation is slightly better using 1.10.2.b1. Basically I had two issues:

• my beacons were not recognized, and this is solved
• callback for advertisements stops firing after a while, but I know that the program is not frozen somewhere. This still unsolved

The very same script is loaded on four WiPy 2.0, two WiPy 3.0 and one LoPy. Only one WiPy 3.0 survived after 18 hours. Sigh.

[livius]

@duffo64
If it survived only on wipy3, this can point me that memory is here problem (only guess).
Did you tried track it down and print gc.mem_free() in the code to see memory consumption?
And do you have gc.collect() in the code or you have enabled automatic garbage collector?

[duffo64]

@livius Hi,

Been there, done that. Unfortunately the culprit is not does not seem lack of memory (one WiPy3 still working, the other went south like all WiPy 2).
Anyway, I have collection in code as soon as a ble scan cycle ends.

[duffo64]

Follow up:

I restarted both WiPy 3 giving them another chance without modifying code at all, and this time was better: more than 24 hours of normal behavior without reboots or BLE lockups. Still, BLE acts randomly in the long run.
BTW there is an IDF related issue on Github that could lead to weird results on the BLE side, as I read.

[livius]

@duffo64
good finding on github.
I saw this kind of assert on the forum.

[duffo64]

Yet another update:

This is a WiPy 1.0 with a not-so-recent firmware. Running since two weeks and counting. BLE, WiFi and MQTT are running without hiccups :D

{"ts":1517336479,"pmac":"24xxxxxxxxxx","up":1302802,"fw":"1.12.0.b1","ip":"192.168.0.111"}

[jcaron]

Hi @duffo64,

Can you clarify what was the change that made the difference in the end?

[duffo64]

@jcaron Hi,

only the firmware :-)
I did not touch anything in my code because I was pretty sure it was working as is.
Now I am patiently waiting for the death (hope not) of two WiPy 3 with the very latest firmware that are running since 47 hours.

[tudro]

Hello,

I'm having the same problems with reading the BT advs. My setup is a lopy with a deepsleep shield and 3 ruuvi tags that adv every second. The ruuvis are placed about 3 meters apart. The lopy is on 1.17.0.b1.

The process is: read BT data, go to deepsleep for 15 sec, wake up, read BT data, deepsleep, etc.

I have tried first with the BT example in the pycom docs. The scan was set to 20 seconds. In about 40% of the cases the lopy would not read the data from all the 3 ruuvis.

Then i tried with the deinit/init. Scan for 10 sec, if not all 3 ruuvis read, deinit/init, scan for another 10 sec. It reduced the loss to only about 10%.

In the real case the deepsleep interval will be 1 hour. So, if it doesn't read all the ruuvis, some results will be 2 hours apart or even more, depending on luck, i guess :)

Is there any plan or update on this problem?

Thank you

[tudro]

My lopy4 arrived and i tested with it, too, although i was pretty sure it wouldn't make a difference. It didn't, it does the same thing.

I left my lopy running since yesterday noon and from 270 readings, 223 were correct. So that's around 17-18% loss.