-
Notifications
You must be signed in to change notification settings - Fork 9
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
config_builder SSL issues with dyson API #14
Comments
Thanks for filing :-) I'm pretty sure this was addressed by shenxn/libdyson#14 which imported the new DigiCert certificates. I pushed release 0.3.2 to pick up this change (https://github.com/seanrees/prometheus-dyson/releases/tag/v0.3.2). I'm guessing you're having issues? If you're building from source you'll likely need to upgrade |
Thanks for the response. I'm using the precompiled .deb v0.3.2. on a clean ubuntu server 20.04.3 LTS install. Just tested after running the pip3 upgrade for libdyson, no change unfortunately. |
Got it, thanks! Verified the issue and raised a PR (shenxn/libdyson#16) to fix. As soon as that goes in & there's a fresh release of |
hi @seanrees Is there an update on this issue? I can see that:
However the config_builder still fails with the same errors. Happy to assist with testing etc. |
Happy New Year :) I just published v0.3.3 which picks up a new |
Thanks, and happy new year! 0.3.3 solves the SSL issue! However I'm seeing a new issue with the OTP validation. I'll go ahead and open a new issue for that. |
Hi There,
This is a heads-up, I don't believe the issue I'm facing is your code, but thought I'd report it.
When running the config builder I currently get errors relating to ssl validation failures.
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)
However, this is because dyson has incorrectly applied their certificate which can be verified with curl and openssl:
This can be further validated using ssllabs which reports the same:
The text was updated successfully, but these errors were encountered: