-
Notifications
You must be signed in to change notification settings - Fork 20
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
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2578) #38
Comments
Same error here since upgrade....help please |
Same as above, but this component is now holding up HA core restarts by a couple of minutes, possibly due to this issue. |
I haven't noticed it....but it is the same...it restarts periodically due to this topic |
Still having the problem. I have tested the API in the Google Developer Console and its works well. It is hapenning to me in the Weight and in the Heart Rate sensor. I am going to try adding new scopes... |
same here, I had heart rate, weight and height sensors failing over time. I also had random restarts of HA Core at least once a day, not entirely sure if it's related though. but since I've disabled. HA is now up for 24hours+ |
Still having the problems. I have put in the code sleep 2 or 3 seconds if it could be related to timeouts...but still with problems with sensors... |
@daniperaleda Does your HASS still restart? If so, do you have a |
@syphernl I have one:
Right now it's running for 24+ hours without any restarts (with integration disabled). Never hat a restert before I updated to 2023.5 and google_fit sensors started failing |
It is a big file...but the last one that appears...(I have rebooted manually several times trying to fix the problem is this) Thread 0x00007f5e15f7fb30 (most recent call first): |
Anyway, right now what I get most is TIMEOUT...this is an example Logger: homeassistant.helpers.entity Update for sensor.google_fit_oxygen fails |
@daniperaleda @AlexKusnezov Which HASS versions do you run? Does this happen with HASS |
@syphernl it happened with 2023.5.0 , then I updated and then it happened with 2023.5.1, which I'm currently on |
I have it in 2023.5.2...but happened in all 2023.5.x One comment...I have put time.sleep(1) in some parts of the code...and it is getting better...for example I am getting the heart rate sensor. So it seems that there is limitations in the HA side for sockets or SLL calls |
Downgraded to 2023.4.6....and all the sensors worked fine....so for me is a limitation of the version 2023.5.x |
After upgrading my setup to Alpine 3.18 / Python 3.11 HASS started crashing on the ISTM something in this integration causes HASS to segfault 😢 |
I am still in version 2023.4.6...decided to downgrade as causing inestability...so for sure is a problem with the version 2023.5.x...do you know that has changed something in the calls, sockets or SSL? |
After migratin to 2023.5.3...it works stable with theis Google Fit integration...is it ok for all you too? |
Seeing this after updating HASS to
2023.5.x
when starting up.Oddly, while some sensors work just fine (e.g. steps, move time) the one for
distance
is not.The text was updated successfully, but these errors were encountered: