-
Notifications
You must be signed in to change notification settings - Fork 8
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
Receive "scan_evt timeout" on serial monitor #58
Comments
Im on 1.11.144 at the moment with a few drops a day |
The drop of all online devices time to time is the only issue I currently have after long time use. I even restarted the device every 30 minutes, but the drops still happen. I had running without issue for like 2 months with restarts once a week for example. I thought more frequent restarts will eliminate the issue, so I set it to restart every day now. It seems the problem is independent on the restart frequency. I have it setup to monitor cars in garrage, so I see both cars going away in same time and then reappear in few minutes later, sometimes it repeats several times in short time. After that it runs for weeks without such error. |
I hope when I solve this issue, you both can use this without any issues. |
@Goodwillson @Seinuh Every test and feedback is appreciated. |
Up and running |
Okay, I made a mistake, selfclean mechanism and update process set the statuses to false. |
Up and running 👍 |
Unfortunately, it stopped for me yesterday. Soon I commit this solution and we will see |
Up and running since yesterday 19:00 boot time 2 hours |
Yes, I've tried with no reboot timer |
With a boot time of 2 hours it still runs great. for me this is the most stable v1.11 |
@Seinuh |
|
The scan task is moved to another CPU core. Hope it helps to solve the issue. |
|
@redakker v1.11 177 up and running |
@redakker 2.... one stable v1.9 and a bèta version 1.11 same Observed devices and reboot time |
@Seinuh I changed back the scanning mechanism similar to v1.11-177 |
@redakker v1.11.179 lets go.. up and running |
@redakker Unfortunately, devices drop again only come "home" after a reboot |
Found another opened ticket on this topic: It looks to me it is not depend on my code. It is totally random, just we think it is because of different versions :( I'll go deeper and try to find a proper workaround. |
no problem, good luck |
In the ticket above I found a library. I've changed it on my computer and compile with it. It is up and running on my side, if it helps then I'll find out how to use this in the future |
Up and running 👍 |
The board stops, it was not a good build |
Same here |
Will try the passive mode for scan, somebody mentioned it solved the issue. |
@Seinuh |
It looks like the scan performance has not changed for me. |
Fingers crossed |
@redakker so far so good 🤞 |
On my side too 😊 |
@redakker im on .188 Lets go |
@redakker .192 up and runnning |
@redakker last night a spontaneous disconnect connect with one device... im on .192 |
Are you talking about BLE device? Is the battery is okay in it? |
Yes it is, just a little drop battery ok 3.3v |
@redakker Unfortunately I can't recall the moment here, but the bug is 100% in the wrong message 1> |
@redakker I have now made an adjustment that the message from the topic must be exactly present or not_present. my variable will never switch when there is a strange entry |
I create a ticket for this. Maybe the message processing has bug |
thanks, but thanks to your ha log I have now been able to build in extra security 😀 |
Recently I met with this problem (never seen before). Probably it is the reason for the device stops and BLE devices are gon even if they are presented.
I found an open issue about this topic:
espressif/arduino-esp32#5860
Unfortunaltely it is quite old issue, but 1technophile
/
OpenMQTTGateway has a solution for that.
Related commit:
1technophile/OpenMQTTGateway@6e8b463
Implement this Watchdog to the BLEcker too.
The text was updated successfully, but these errors were encountered: