-
Notifications
You must be signed in to change notification settings - Fork 17
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
[HTTPS] Certificate validation fails when using the default assigned domain #2
Comments
same trouble here |
@pdecat ok, it's work for my ".freeboxos.fr" domain now, not for the fbxos one ! |
BTW, i'm not sure to understand what I can do with the freebox in my hass ?! |
@manatlan The Freebox hass component is just a device tracker for now. A device tracker is typically used as a presence detector, to know who is present in the home by tracking which devices are detected nearby. In this case, the Freebox component tells hass which devices are connected to the wifi, allowing you to know which smartphones are nearby for example. If there is a need, a more complete component could be written, to provide access to other functions of the Freebox: turning wifi on/off, rebooting, getting the list of missed calls, etc. Note however that only the Freebox server can be interacted with, not the Freebox tv box, so you won't be able to swich tv channels and stuff like that. |
This issue has been fixed by PR #3. |
The previous version of aiofreepybox was not working with custom domain names, which uses a Let's Encrypt certificates. Also, it was not working with the default domain name when connecting to Freebox v6. This should be fixed in aiofreepybox 0.0.4. See hacf-fr/freebox-api#1, hacf-fr/freebox-api#3 and hacf-fr/freebox-api#2 for more info.
@stilllman thanks a lot ; it's clearer ! |
The previous version of aiofreepybox was not working with custom domain names, which uses a Let's Encrypt certificates. Also, it was not working with the default domain name when connecting to Freebox v6. This should be fixed in aiofreepybox 0.0.4. See hacf-fr/freebox-api#1, hacf-fr/freebox-api#3 and hacf-fr/freebox-api#2 for more info.
) The previous version of aiofreepybox was not working with custom domain names, which uses a Let's Encrypt certificates. Also, it was not working with the default domain name when connecting to Freebox v6. This should be fixed in aiofreepybox 0.0.4. See hacf-fr/freebox-api#1, hacf-fr/freebox-api#3 and hacf-fr/freebox-api#2 for more info.
) The previous version of aiofreepybox was not working with custom domain names, which uses a Let's Encrypt certificates. Also, it was not working with the default domain name when connecting to Freebox v6. This should be fixed in aiofreepybox 0.0.4. See hacf-fr/freebox-api#1, hacf-fr/freebox-api#3 and hacf-fr/freebox-api#2 for more info.
According to @pdecat (see comments on his PR), the validation of the default certificate provided by the Freebox when using the default domain does not work correctly, preventing the SSL handshake from succeeding.
The text was updated successfully, but these errors were encountered: