Why does Intel keep popping into my head?
Why does Intel keep popping into my head?
•
So today, I received a Home Assistant Green. I know you can run this on anything, but I like the form factor and wanted to help support the company.
If you look on the HA website, you'll see this:
Ready. Set. Go. — The affordable Home Assistant Green is the easiest way you can start using Home Assistant. It's plug-and-play and comes with Home Assistant already installed.
That's an absolute lie. It comes installed with a bootloader stub that goes out and downloads HAOS from github. No internet connection? No workie.
That's not the best part. Home Assistant is run as a Docker container on top of a minimal Linux system. While I understand this as being useful because you can update the OS or the HA part of the system without messing with the other, it's a rather heavy-handed approach to something that's essentially nothing more than a glorified python package. Especially when you consider it's RAM intensive and the Green doesn't have that much RAM.
But the part that gets me - when it downloads, it of course starts all these containers and everything. It's got a bunch of SSL shit - another thing I can't understand, why do you need SSL for something that never should go outside of your network - and all of those SSL things fail and it doesn't get an internet connection for the Docker supervisor.
Why didn't the SSL checks pass? Because the certs aren't valid yet.
Why aren't the certs valid? Because, in all it's wisdom, the supervisor doesn't check the time UNTIL AFTER IT DOES THE SSL STUFF.
[supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1000)’)]
[supervisor.core] Whoami service SSL error
[supervisor.core] System time/date shift over more than 3 days found!
[supervisor.host.control] Setting new host datetime: 2025-02-21T17:58:06+00:00
[supervisor.core] Fatal error happening on load Task : Automatic time synchronization is enabled
[supervisor.docker.monitor] Started docker events monitor
[supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
Now you have no internet connection to the supervisor, and everything fails because there is no internet connection. i don't know if this is it's internal connection because the supervisor runs on it's own little network, or if it's going outside. That begs the question, will this thing even run locally without an internet connection?
So where does this thing get the time? I can't tell you, I assume it's the router but some things mention time.cloudflare.com. But I bet the board gets the time from the router during boot - and my router doesn't provide the time because it's not a clock. (I'm pretty sure that's what's going on. I installed the NTP package to try and fix this.)
Now I have a brick. I can't even flash the thing because it won't flash again. What gives here? Why wouldn't they check the time at the very beginning of the process? When you have things that are time dependent - like SSL certs - isn't that something you'd think you'd do immediately instead of halfway through the boot and setup process?
Fortunately, the vendor will take it back, even though I eat the shipping cost. This is my Nth try at HA, and it's never worked. I guess i'm just not compatible with it.
So today, I received a Home Assistant Green. I know you can run this on anything, but I like the form factor and wanted to help support the company.
If you look on the HA website, you'll see this:
> Ready. Set. Go. — The affordable Home Assistant Green is the easiest way you can start using Home Assistant. It's plug-and-play and comes with Home Assistant already installed.
That's an absolute lie. It comes installed with a bootloader stub that goes out and downloads HAOS from github. No internet connection? No workie.
That's not the best part. Home Assistant is run as a Docker container on top of a minimal Linux system. While I understand this as being useful because you can update the OS or the HA part of the system without messing with the other, it's a rather heavy-handed approach to something that's essentially nothing more than a glorified python package. Especially when you consider it's RAM intensive and the Green doesn't have that much RAM.
But the part that gets me - when it downloads, it of course starts all these containers and everything. It's got a bunch of SSL shit - another thing I can't understand, why do you need SSL for something that never should go outside of your network - and all of those SSL things fail and it doesn't get an internet connection for the Docker supervisor.
Why didn't the SSL checks pass? Because the certs aren't valid yet.
Why aren't the certs valid? Because, in all it's wisdom, the supervisor doesn't check the time UNTIL AFTER IT DOES THE SSL STUFF.
`[supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1000)’)]
[supervisor.core] Whoami service SSL error
[supervisor.core] System time/date shift over more than 3 days found!
[supervisor.host.control] Setting new host datetime: 2025-02-21T17:58:06+00:00
[supervisor.core] Fatal error happening on load Task : Automatic time synchronization is enabled
[supervisor.docker.monitor] Started docker events monitor
[supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection`
Now you have no internet connection to the supervisor, and everything fails because there is no internet connection. i don't know if this is it's internal connection because the supervisor runs on it's own little network, or if it's going outside. That begs the question, will this thing even run locally without an internet connection?
So where does this thing get the time? I can't tell you, I assume it's the router but some things mention time.cloudflare.com. But I bet the board gets the time from the router during boot - and my router doesn't provide the time because it's not a clock. (I'm pretty sure that's what's going on. I installed the NTP package to try and fix this.)
Now I have a brick. I can't even flash the thing because it won't flash again. What gives here? Why wouldn't they check the time at the very beginning of the process? When you have things that are time dependent - like SSL certs - isn't that something you'd think you'd do immediately instead of halfway through the boot and setup process?
Fortunately, the vendor will take it back, even though I eat the shipping cost. This is my Nth try at HA, and it's never worked. I guess i'm just not compatible with it.
(post is archived)