You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have now currently 3 devices that are being read with the Bridge and have run in a strange issue - sometimes some devices stop responding (not always the same one, though some more often than others).
But its immediately fixed with restarting the waveplus bridge python script.
so for now, I just have a cronjob that restarts it hourly...
I realize this is difficult to diagnose, with all the variables of different hardware, range and bluetooth in general...
maybe you have some idea though ?
The text was updated successfully, but these errors were encountered:
i've disabled my workaround to capture the logoutput:
2024-04-12 15:15:23 - __main__[ DEBUG] - Reading sensor data for device schlafzimmer
2024-04-12 15:15:23 - libs.waveplus[WARNING] - Failed to communicate with device schlafzimmer (attempt 1 of 4): Helper not started (did you call connect()?)
2024-04-12 15:15:24 - libs.waveplus[WARNING] - Failed to communicate with device schlafzimmer (attempt 2 of 4): Helper not started (did you call connect()?)
2024-04-12 15:15:25 - libs.waveplus[WARNING] - Failed to communicate with device schlafzimmer (attempt 3 of 4): Helper not started (did you call connect()?)
2024-04-12 15:15:25 - libs.waveplus[WARNING] - Failed to communicate with device schlafzimmer (attempt 4 of 4): Helper not started (did you call connect()?)
2024-04-12 15:15:25 - __main__[ ERROR] - Failed to communicate with device schlafzimmer: Failed to communicate with device 2930223305/schlafzimmer
I have now currently 3 devices that are being read with the Bridge and have run in a strange issue - sometimes some devices stop responding (not always the same one, though some more often than others).
But its immediately fixed with restarting the waveplus bridge python script.
so for now, I just have a cronjob that restarts it hourly...
I realize this is difficult to diagnose, with all the variables of different hardware, range and bluetooth in general...
maybe you have some idea though ?
The text was updated successfully, but these errors were encountered: