Very true, but the IO isn’t going to matter much simply for home assistant, unless you are running an entire apartment block or something.
What’s it like with noise, can you hear the fan or did you get a fanless one?
Depends on how many sensors you have and how often they update? Even with a normal usage Patten, the logbook and history aren’t real fast… some of that is likely due to how the sqlite3 db is being used by storing blobs of JSON that needs to be parsed. Other aspect is just running that off the storage medium fast enough.
In my case, I have a 32 channel power monitoring system that updates every two seconds. While this gets piped into Home Assistant, all those sensors are excluded from the recorder/history database, and just get sent along to influxdb.
I think that many home assistant users will end up with influxdb and grafana or something similar to do longer term analysis of weird things. Like how I used the outside temperature and packet loss measurements to demonstrate to my ISP that there’s some temperature-related failure in their Network, that painfully obvious when you look back over a couple of weeks of data.
Nick, That is what I initially thought also.
But what Louis says is also in my mind.
At this moment the I3 would be more than enough but as we go along, there will be more sensors, more cameras, an more and more addons. I also want to run the Unify.
The main reason I want to swap to a nuc is because restarts take long, history takes long. And most of the time I need to restart twice because the first time the cameras are missing.
As I am learning every day, the the database will grow and the list of features will grow.
My motto always has been, get the best performing unit available for the money.
That way it takes longer before you run out of performance.
Especially if power consumption does not make much difference.
So I think maybe the I7 is my best option.
Sorry if this is way off topic, but have anyone had the luck to pull the data about the RPM’s from the Fans on your NUC?
Hi there,
I’m chasing the same answer 
.
I’m not sure if I shell go for SBC (like the ROCKPro64) or NUC. I read through the discussion and may summerise as follows:
-
CPU power improves boot/start-up → it is not little was is loaded
-
operation is mainly improved by SSD or flash (what is obviously)
-
power consumption is top requirement for me
but which of them as there is not only one configuration Intel® NUC Kit with 8th Generation Intel® Core™ Processors
but statements like
lead me the question, is HA a foreground or background process (in case of CCTV is properly is)? The reason is, that if HA is installed on an external HDD, it will prevent the HDD going idle, so it will spin a time long. This, of course, depends on how HA is configured, run un-demand, e.g it act as a remote control, doing cronjobs or recording data (video or sensors) continuously.
Asking differently, what is carried out in the memory and what has to be pulled from the HDD?
hi @PackElend
on my case i didn’t go NUC but still on x86 solution and I suggest it compared to RPI-like SBC (in my case was RPI3B+).
I took a beelink N41 (N4100 celeron CPU + 4GB ram) which is rated to be a 6W TDP CPU hence consuming less power than 15/25W NUC options available.
If I had to do it again I would go same route but maybe looking for something with 6-8Gbyte ram to have a bit more slack.
Only thing you could miss wrt NUC is GPU power (CPU you are plenty enough) for image processing: i sorted it out with Google Coral stick and TensorFlow lite thanks to the job of @robmarkcole
1 Like
I have a NUC with a dual core Celeron J4005. It runs great.
I installed Ubuntu Mate on it - the 18.04 LTS
And then followed the normal procedure installing first docker-ce
And then Hass.io
In addition I run Mosquitto. Not in docker. I see no reason. Mosquitto can be installed by a simple apt installl mosquitto and the configuration adding a username and password is dead simple. I see no reason why I should make myself depending on Home Assistant running it as an addon.
Inside Home Assistant I do run a number of addons. Most important one is deconz for my zigbee stuff.
I installed the desktop version of Ubuntu Mate because setting fixed IP and other stuff is so convenient from a GUI. And if you are not logged into the GUI its CPU overhead is nothing to talk about.
I also run a Ubiquiti Unifi controller - also installed directly on the Ubuntu using apt. Again why should my Unifi controller not be working if I have a situation where HA will not start because of a broken release.
Having my MQTT and Unifi running outside Docker means they run along uninterrupted even if I have to stop HA. That is how I prefer things
What else… I have ssh daemon running in the Ubuntu host. I have a samba share daemon running so I can edit the HA config even when docker is dead.
You can run everything in docker and it is dead easy to install things as addons in hass.io
But the simple things like Mosquitto, Samba, ssh is actually so simple to setup that I prefer the good old way. That is my preference
One thing. As the previous maintainer of Motion and still a user with 7 cameras I say this!!
If you want to run Motion with out without Motioneye … then you need much more computer power than a Celeron.
I run Motion on a different computer with a fast 6 core i5. If you want to run many cameras at high speed and high resolution then you need CPU power to plow through every video frame looking at changed pixels after it has done a lot of filtering and identified and labelled and voted the areas of Motion. I know how much it takes. Especially when something moves in several of the cameras. For Motioneye running as an addon in HA with many cameras go for an i5 with 4 or more cores.
But just HA - a celeron at 2 GHz is more than enough. Even with 100+ devices and 1000s of event per day. A celeron is still much much faster than a Raspberry pi 4
A NUC with a Celeron or small i3 is great without Motion(eye)
A NUC running HA and Motion(eye) go for an i5 or i7
3 Likes
Mine is a 7th Gen i3
Why not just skip hass.io entirely, and just run the Home Assistant container on native docker on Ubuntu or something? That’s what I do with great success. I run mosquitto in a container (and a number of other fairly trivial containers, some home-built) just to make dependency management easier to deal with.
In particular, it’s really great to have all the Ubiquiti stuff isolated in a container since it’s got a bunch of stuff going on in there. LIkewise with Shinobi and influx and gafana – i just want to avoid dependency management hell.
As I’ve mentioned before, I have a fanless, SSD-based NUC-like clone that runs all this stuff. No moving parts, more reliable. Stuff that moves is stuff that breaks.
1 Like
FYI
is answered in Does HA prevent a HDD go idle?
hass.io is promoted to handle all add-ons, dependency and so on. So that get me to the question, it is easy to manage? Where to pay extra attention?
Woody4165 I have my HASSIO on the promox as well but I am new to the inner workings of the command line. How did you create the file.py, is there some place it needs to go? And how do you do the cron jobs in the tab? Just like you show it? I really need to get this temp and cpu information up and running since it will not let me pull it with the command cat /sys/class/thermal/thermal_zone_1/temp or 0 for that matter. Thanks
It’s all written in my post.
I created the py file in /root with nano and with the chmod command I made it executable.
You can create it also in /home or other folder, the important is that you then reference it in crontab
Then you edit crontab with -e option and add the the two lines and restart crontab with sudo service cron restart
1 Like
Using a NUC8i7BEH, running Proxmox with MotionEye and other add-ons.
Ok thanks Woody I was not 100% sure on running the commands. Thanks again.
Woody,
I got it all setup like you showed with MQTT user and password to my server. How do I know if it is working? I do not see any data being pulled into the MQTT. Is there something more I need to do to make it show that data? I did a package to pull the CPU temp using the cat /sys/class/thermal/thermal_zone_1/temp since that seems to be the one that shows a temp of 42000 and the temp0 shows a - 263200 value. So how do I pull this cron job information into HA? Thanks a bunch for this it is the only thing I can get to monitor on the system. I tried to install Netdata application on the NUC but no joy there.Do you have mosquitto installed on the instance you’re running the py file?
You can check executing mosquitto_pub and if it works just double check the MQTT credentials.
You should see in MQTT…
The MQTT is running on a VM on Proxmox under HASSIO addons I put the IP, Username, and Pass to it but it is not showing up in the MQTT section of HA. Does this have to run on Proxmox or the VM because the file is in the root of the Proxmox server not the VM.
I have it as Hasio addon and it’s working perfectly.
I have the addon called MQTT and Web Client or something similar.
Then if you want to execute the MQTT publish (via mosquitto_pub) from Proxmox (not from the VM with Hassio), you need to install moquitto also there, at least the client part