Home Assistant Blue Experience

Please move or delete if this doesn’t qualify as a project, didn’t find a better place for it and felt like sharing… :slight_smile:

After running primarily into memory issues with my RasPi 3b (after 3-5 days memory depleted) I decided to buy the Home Assistant Blue package. I admit price was a bit of an issue (just short of 300 EUR including customs and shipping from Switzerland) but it seemed the easiest way and I have to say it does look great (zen mode!).

So I did a snapshot, downloaded it, shutdown the Pi and fired up the Blue. Very nice boot time. :slight_smile:

Onboarding --> Restore --> Load snapshot (8 MB…) --> Restore --> Bumps me back to onboarding screen. Hm. Retry. Same. Hmhm.

Reboot -> Retry -> Works! Nice! Took 5min to restore the config. Plex Integration not connecting right now, but that might just be a hick-up, have to see after next restart. Rest went perfectly!

Aotec Z-Wave Stick was immediately found directly plugged in. Z-Wave Network came back up just as usual. Nothing out of the ordinary so far…

Now with 1500 entities and lots of integrations, automations, etc. I see 2% CPU, Loads between 0.1 and 0.2 and 2,8 GiB of free memory (so yes, Linux now takes up 1,2 GiB after startup as compared to ~ 0,5 GiB on the RasPi 3B). Interface is significantly faster. Looking forward to see how it goes…

So for everyone contemplating the move: For me it was like 45min including network config for port forwarding and making a backup of the Aotec Sticks EPROM. Home Assistant really has reached production quality!

2 Likes

Sounds like a solid upgrade! Share some more details about the failing Plex integration and I’ll try to assist.

I think I read somewhere that @balloob uses an N2, so one would it expect it to be a polished experience.

Anyone can buy an odroid N2+ - it won’t be blue, but it will perform the same. I have one running kodi for my 4K TV.

When I restored the new one from the image both were online for a short time - possible the Plex access token was then used from two systems at the same time and therefore invalidated? Anyway, I just removed the integration, re-added, went through some hick-ups with authenticating again, then it worked again, but now it fails again:

Max retries exceeded with url: /clients (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0xffff95f51640>, 'Connection to ###.plex.direct timed out. (connect timeout=30)')))

I will remove again and add after a restart, as it worked fine for a year or so…

I just removed the integration and re-added it again. HA correctly opens a browser window where I can authenticate the HA request. Afterwards it tries to contact HA but uses a wrong URL (without port :8123) so it fails. After manually adding the port in the browser window it works and seems to authenticate fine:

2021-01-20 10:11:23 INFO (SyncWorker_8) [plexapi] Testing 6 resource connections..
2021-01-20 10:11:23 ERROR (Thread-266) [plexapi] http://172.104.130.172:8443: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-01-20 10:11:23 ERROR (Thread-261) [plexapi] https://192-168-23-11.###.plex.direct:32400: HTTPSConnectionPool(host='192-168-23-11.###.plex.direct', port=32400): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffff9031dd00>: Failed to establish a new connection: [Errno -2] Name does not resolve'))
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection ERR (0s): https://192-168-23-11.###.plex.direct:32400?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection OK (1s): https://79-222-72-172.###.plex.direct:32400?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection OK (1s): https://172-104-130-172.###.plex.direct:8443?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection OK (1s): http://192.168.23.11:32400?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection OK (1s): http://79.222.72.172:32400?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Resource connection ERR (0s): http://172.104.130.172:8443?X-Plex-Token=<hidden>
2021-01-20 10:11:25 INFO (SyncWorker_8) [plexapi] Connecting to Resource: https://79-222-72-172.ec95490c101a4c1ca3ed5792b7f9a924.plex.direct:32400?X-Plex-Token=<hidden>

Let’s give it a day or so and see how it shakes out.

Does anyone have experience with HDMI CEC with the N2? The same config that worked for the RasPi3b now somehow creates 14 switch.hdmi entities - all of which don’t work. :slight_smile:

Config:

hdmi_cec:
  devices:
    TV: 0.0.0.0
    Beam: 1.0.0.0
    AppleTV: 2.0.0.0
    PiHA: 3.0.0.0
    Switch: 4.0.0.0

CEC Scanner states:
[11:19:13] INFO: Starting CEC client scan…

  • failed to open vchiq instance

Did it just use an implicit port with http/https (80/443) when connecting back to HA? Looks like it connected fine after your adjustment and I expect is continuing to work as expected after the initial Plex auth flow hiccup.

I guess it’s using port 443 (https:// was correct) - but it doesn’t seem to be a common problem. So far it works fine.

Same good experience here. What I especially like about the M2 is that you could connect it with a standard USB plug and it shows up as a USB drive. You can directly etch onto the internal disk. Installation was a breeze.

Hi, I bought a Blue and got it running last Saturday; all pretty easy with an image restore from my RPi4. Yesterday however it started hanging. I’ve now had to unplug the power and restart about 4 or 5 times.

I got Glances going, and it looks like Homeassistant is hogging all of the memory (ie, it’s completely maxed out), and then it stops responding. I can’t even SSH in (I can ping though).

@pvizeli do you have any thoughts on this?

Any thoughts?

Here’s another graph.