yet another BLE problem
See original GitHub issueHomebridge updated Govee version v7.6.1-beta.0 and v7.6.0
[19/12/2022, 14:27:57] [Govee LAN] [BLE] disabling client as btClient.on is not a function at new default (file:///var/lib/homebridge/node_modules/homebridge-govee/lib/connection/ble.js:18:14).
>>
>>
>>
[19/12/2022, 14:27:57] [Govee LAN] [BLE] sync for thermo-hygrometer sensors disabled as required hardware/packages not available.
Issue Analytics
- State:
- Created 9 months ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Troubleshooting Bluetooth Low Energy (BLE ...
Navigate to Android settings -> Applications -> Application Manager -> InTemp or HOBOmobile (for Samsung devices) · Tap on the InTemp or HOBOmobile...
Read more >Bluetooth Low Energy BLE Problems and How to Fix them
The biggest problem with trying to use BLE for general purpose control is that the SIG specification does NOT define a standard UART...
Read more >Common BLE issues – Developex blog
Problems with BLE. According to the new announcement for Bluetooth Low Energy 5, SIG believes that BLE 4.x has two main disadvantages:.
Read more >BLE status = 133 problem · Issue #1 - GitHub
Hi, It's true that errors 133 and 129 were common among different Android phones. The BLE is not very mature on Android but...
Read more >How to Fix Bluetooth Pairing Problems - Techlicious
Try these 16 tips to solve your Bluetooth pairing problems. ... For other devices, turn off the power and restart them.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please follow here: https://github.com/abandonware/noble/issues/282#issuecomment-1359000503
This is an issue that has cropped up with a new version of the bluetooth package the plugin uses. As soon as an update to this is available, i will make a new release of the plugin 🙂
Thanks for the update…and Merry Christmas to you