-
-
Notifications
You must be signed in to change notification settings - Fork 250
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
Reset function makes integration unresponsive after a few days #549
Comments
@eValker Regarding the delay, I prefer to find a value that works for everybody, we already have a ton of options in BLE monitor. I will first build in a delay of the reset functionality with a hard coded 30 second delay time between resets and we will see if that works. Regarding the error, it seems that it either cannot find the BT adapter on hci0 anymore. It would be interesting to find out if the OS has changed the BT adapter to hci1 or if it isn't available at all anymore. Could you check this? |
Option to enable/disable the automatic reset of the BT adapter has been added in 6.0.0-beta |
Hello,
Also as I said before: after 2-3 days of automatic restarts BT is not responding at all even after software reset. I need to reset whole rasberry pi in order to make it work. I didn't notice this issue in my restart implementation where I have 30-60 seconds delay between restarts (I think 60 second option is more safe). Here is additional info I have got before I performed hard (hardware) restart.
Also a lot of errors in dmesg:
I wasn't sure if there is some other command I can execute in order to get more info. |
I don't understand why it is doing this. In if CONF_BT_AUTO_RESTART: CONF_BT_AUTO_RESTART should be Change line 612 to if CONF_BT_AUTO_RESTART is True: I'll add a delay timer to the reset function anyway, to only reset once every 60 seconds max. |
I've released 6.4.3 which adds a 60 seconds minimum time between BT resets. I also have added the change in the above post. Please give it a try. I assume this should fix your issue, if not, please reopen the issue. |
@Ernst79 |
Issue from #167 by @eValker
Unfortunately I had to revert back the integration to v5.5.2. I think restart happens too often and this leads to situation in which the Bluetooth device become completely unresponsive (or even undetectable like in example below).
After some time (like 1-2 days of uptime) I am getting errors like below each second:
Only way to fix it is to reset entire Pi.
I think it will be helpful to have 2 additional configurations:
My custom restart solution have 30 seconds delay between executions and I never had a problem with bluetooth device become unresponsive.
The text was updated successfully, but these errors were encountered: