-
Notifications
You must be signed in to change notification settings - Fork 205
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
Activating 'long range' is dangerous?!?! #299
Comments
Remove and insert the battery - option will be disabled. This is the inclusion of the Bluetooth LE standard option from 2016. BLUETOOTH SPECIFICATION Version 5.0 | Vol 1, Part C page 291 9 CHANGES FROM v4.2 TO 5.0 |
Xiaomi 12Tpro Bluetooth 5.3 also can not discover the LYWSD03MMC thermometer with 4.2 firmware |
Обращайтесь в Google Chrome. Web Bluetooth API пока не работает с BT5.0 адаптерами. (Только частично - не может самостоятельно переключать PHY. Но если в списке соединения ещё осталась запись о подключении, тогда Chrome соединится с устройством в любом режиме 5.0+. Т.е. у Chrome ошибки в меню подключения-сканирования) Для проверки адаптера смартфона используйте nRFConnect. Сброс опции возможен и в nRFConnect, как показано в README.md Home Assistant работает с LE Long Range. |
Sending 0x56 via nRFConnect, Chrome can now connect to the LYWSD03MMC thermometer |
This action sets the default configuration. And in the default configuration, "LE Long Range" is disabled (BLE advertising thermometer works in BT4.2 mode, PHY 1M - short communication distance). |
In installed 4.2, and clicked the 'long range' thinking it was just a change in power transmission. I was wrong, it seems it goes into another mode that makes it unusable. The ESP32 no longer receive beacons, and even my phone fails to recognize it when scanning, so I can't revert the setting!
I know, it's not a 'stable' firmware, but a warning on that checkbox might be useful, like "if your phone/receiver can't do that particular mode as well, you're screwed" :-)
Model: LYWSD03MMC_PVVX
The text was updated successfully, but these errors were encountered: