Skip to content
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

Closed
stilllman opened this issue Jun 19, 2018 · 7 comments

Comments

@stilllman
Copy link

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.

@manatlan
Copy link

same trouble here

@pdecat
Copy link

pdecat commented Jun 23, 2018

Hi @manatlan, you should try the code in #3

@manatlan
Copy link

@pdecat ok, it's work for my ".freeboxos.fr" domain now, not for the fbxos one !
It's great like that !
thanks !

@manatlan
Copy link

manatlan commented Jun 23, 2018

BTW, i'm not sure to understand what I can do with the freebox in my hass ?!
now, I've got a "device_tracker.freebox_player" which seems to work : but what can I do with that ? (turn on/off ? change channels ?)
Can someone provide a simple example somewhere ?
(I'm aware of the providing api)
(need to ignore the discovery freebox to avoid bug for fbxos domain)

@stilllman
Copy link
Author

@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.

@stilllman
Copy link
Author

This issue has been fixed by PR #3.

stilllman added a commit to stilllman/home-assistant that referenced this issue Jun 23, 2018
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.
@manatlan
Copy link

@stilllman thanks a lot ; it's clearer !

balloob pushed a commit to home-assistant/core that referenced this issue Jun 25, 2018
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.
eavanvalkenburg pushed a commit to eavanvalkenburg/home-assistant that referenced this issue Jun 28, 2018
)

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.
girlpunk pushed a commit to girlpunk/home-assistant that referenced this issue Sep 4, 2018
)

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants