SteidlD / homebridge-inkbird-bt-thsensor

A homebridge-plugin for the Inkbird bluetooth temperature and humidity sensors.
GNU General Public License v3.0
8 stars 2 forks source link

Cannot Connect #17

Closed MMV17 closed 2 years ago

MMV17 commented 2 years ago

When I try to run this plugin I get this [Tank] Warning - Waiting for bluetooth low energy hardware to power on, over and over.

Also I would like to add I have tried sudo setcap cap_net_raw+eip $(eval readlink -f which node) many times. As well, as that I get these errors [12/05/2022, 19:57:29] [homebridge-inkbird-bt-thsensor] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/05/2022, 19:57:29] [homebridge-inkbird-bt-thsensor] This plugin slows down Homebridge. The read handler for the characteristic 'External Sensor' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/05/2022, 19:57:29] [homebridge-inkbird-bt-thsensor] This plugin slows down Homebridge. The read handler for the characteristic 'Current Relative Humidity' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/05/2022, 19:57:29] [homebridge-inkbird-bt-thsensor] This plugin slows down Homebridge. The read handler for the characteristic 'Status Low Battery' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/05/2022, 19:57:29] [homebridge-inkbird-bt-thsensor] This plugin slows down Homebridge. The read handler for the characteristic 'Battery Level' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

SteidlD commented 2 years ago

Hi @MMV17,

did you get it running? Well, the only thing I could think of at the moment is the setcap command. Be sure to use it with the ticks: sudo setcap cap_net_raw+eip $(eval readlink -f which node) and not with those ' or without ticks like in your comment. This is usually the problem when the complete bluetooth module doesn't start running like in your case.