How is the Bluetooth behaviour of ESP32 if no device found or connected .
Is it right that if no Bluetti device is found or not connected that we have to wait until new reboot is automatically initiated?
Would it be better to loop for upcoming device and re-/connect when found.
That for example let me switch the ESP32 on and it is listening, and I can press a button when I want to have the values from the device.
(when pressing Bluetti button, it (display) and Bluetooth is only active for 1 minute when nothing connects)
(
sidenote: at the moment the EB3A automatically switches Bluetooth off even if a device is connected after round about 1h -> I maybe will attach a little servo to the ESP32 which presses one of the power buttons, lower power consumption on Bluetti if Bluetooth is not running constantly if there will be no enhancement from Bluetti firmware
Edit: First PoC for servo successful ;-)
Will currectly be triggered by: http://192.168.0.13/triggerButtonPress?degree=100
)
Special UseCase for myself (for the little EB3A to optimize power consumption I will only trigger bluetooth read on demand), no need for the implementation here.
How is the Bluetooth behaviour of ESP32 if no device found or connected . Is it right that if no Bluetti device is found or not connected that we have to wait until new reboot is automatically initiated?
Would it be better to loop for upcoming device and re-/connect when found.
That for example let me switch the ESP32 on and it is listening, and I can press a button when I want to have the values from the device. (when pressing Bluetti button, it (display) and Bluetooth is only active for 1 minute when nothing connects)
( sidenote: at the moment the EB3A automatically switches Bluetooth off even if a device is connected after round about 1h -> I maybe will attach a little servo to the ESP32 which presses one of the power buttons, lower power consumption on Bluetti if Bluetooth is not running constantly if there will be no enhancement from Bluetti firmware Edit: First PoC for servo successful ;-)
Will currectly be triggered by: http://192.168.0.13/triggerButtonPress?degree=100
)