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
Certificate can't be generated on first boot. (Supervisor) #20
Comments
I tried to install libfaketime inside the container, wich takes forever. Signatures of repsitories are not trusted and after each restart the container seems to be resettet and libfaktime is missing again. |
I think we need to update something to HAOS manifests. @Mevel any idea? |
Is there a workaround for this? The curl option is giving me an empty response: curl "http://mariusmotea.go.ro:9002/gencert?mac=00:11:22:33:44:55" -v |
I've created a cert within a docker container (version 922) with its own ip, using the same mac address and replaced the file in the hassio addon config folder with that one. OT: I would propose to pair the Philips Hue with that docker container, too and copy the login entry form the config file. Use 922. I could not pair with the current version, because the app asks for a second push after finding the diyHue bridge, wich one could not press. |
Also seeing no |
Hello.
I just started with a fresh HA Supervisor installation to use this stunning peace of software. Unfortunatly DIY Hue fails to create the cert.pem on startup.
Steps to reproduce:
See the attached log. It complains about a missing faketime and afterwards the crt and key files.
Home Assistant 2023.10.0
Supervisor 2023.10.0
Operating System 10.5
diyhue.log
Do I miss something?
The text was updated successfully, but these errors were encountered: