Closed 1technophile closed 5 years ago
The whole problem is in miband's BLE. When attempting to extract service data. When it is far away, there are no problems (tested). I am using a separate mcu for BLE and only problem is that the time between the scans is not followed (e.g.: If I set the time to 60s, I get 2 equal messages every 120s). But when used together with RF, it stops after a while.
nodemcu v2 Amica
Please click on Placa "NodeMCU 1.0 ...", on board manager, search for esp and you should have the ESP8266 board version (2.5.0beta or 2.4.2 or other)
2.4.2
Could you indicate about how long does it take to crash?
@1technophile I have tested many times. There is no clear time. It depends on how much time Mi Band is around. The shortest time until RF stop was around 3 hours approximately.
@1technophile
Mi band 3
Creating BLE buffer Pub json into: home/OpenMQTTGateway_BLE/BTtoMQTT/CDEDE7B9F4D2 {"rssi":-51} 4f4b2b444953413ad2f4b9e7edcd01cd1f0201061bff57010036eae16345127ea5e151aea4c712cf4203cdede7b9f4d20d0a Creating BLE buffer Pub json into: home/OpenMQTTGateway_BLE/BTtoMQTT/CDEDE7B9F4D2 {"rssi":-51} 4f4b2b444953413a98396acb696d03d50a09ffe0001640ca7ec6480d0a 4f4b2b444953413a98396acb696d03d51c03039ffe17169ffe00000000000000000000000000000000000000000d0a
Google Home
Creating BLE buffer Pub json into: home/OpenMQTTGateway_BLE/BTtoMQTT/6D69CB6A3998 {"rssi":-45}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug Reported by @jeanniquini On NodeMCU with V0.9beta with RF and BLE activated, RF stop after a moment
To Reproduce Steps to reproduce the behavior:
Expected behavior No crash
Environment (please complete the following information):
Additional context @jeanniquini, could you indicate wich version of nodemcu hardware you have, and the ESP8266 version used in arduino IDE (tools->boards->boards manager)