Can you please clarify what you mean with
it doesn’t even post
Do you mean it is not reachable via its IP address or are you trying to ssh into it?
My first approach would be to check the bios settings when you’ve a monitor connected. Maybe there is some kind of strange setting set there!?
I second Valetudo. I’m using it on a roborock S5 and installation was pretty straight forward. Even if it takes more effort to „root“ your vacuum it is definitely worth it. I also integrate my vacuum in HA over mqtt.
For automated container updates I can highly recommend watchtower. It also works with updates for specific releases/versions where you’re not using the :latest tag. It was also relatively easy to configure for my small setup of 15 containers.
SelfToasted
Does the container offer SSL (https)? If so try clearing your browser history so that you can confirm again that you trust this website. Same goes for the extension (uninstall/install again). Most likely your ssl cert changed when you did the DSM Update.
But I would assume you’re used to using a ‘manual’ keyboard whereas if you only grew up on touchscreens its probably more difficult to get familiar to.
The prevelance of touchscreens much rather results in people lacking skills/efficiency/speed when using a regular computer keyboard
According point 2: I choose homepage over Heimdall. It has more direct integrations (e.g. Homeassistant, Synology, Paperless-ngx, Warchtower…) where you can display specific information directly on your dashboard. It is easily set up by a couple .yaml files. You can find lots of examples online and in the documentation.
This is the way! Don’t worry about vpn, proxies and tunneling before you know where you’re heading.
Yes it is that simple. In the beginning you can reach your services via localhost or simply the IP address of your laptop (followed by the specific port).
Start with Docker/Containers.
Once you understand the basics of it you can start selfhosting all sorts of applications from/on your laptop with very little effort. For Docker Command Line Basics there are tons of free tutorials online. If that’s to big of a step in the beginning, start with a Portainer (spinning it up is basically just copy and paste one little command) the rest can be done from the GUI. Docker will also help you to figure out what you might think is worth „selfhosting“ for yourself. Because selfhosting is almost like clothing: Everyone has their own taste and style.
Pretty much also my experience. I migrated HA stand-alone on a Pi4 to a VM on ProxMox (ThinkCenter M720) a couple weeks ago. The direct backup installation did not work so I had to create a new HA and then transfer the backup file over ssh to get it to run.
One thing I’m curious about: Do you measure the idle power consumption of your NUC and does it really drop down to 6W? Because with a Hypervisor installed I would assume that it never really goes into „idle“ hence the resources are constantly bound.
Looks neat and definitely a very good use case. Will give this a try.
Make sure you introduce your USB dongle through ProxMox to the VM on which HA ist installed. There is an USB-option in the menu for your VM where you can choose which USB device or port from the Host should be passed trough. Once that is done figure out how the USB is connected to your HA VM via the HA shell. Something like
ls /dev/tty*
should give you the path you will need to integrate it into HA (if autodiscovery doesn’t work).
That escalated quickly.
But I guess drugs and friendships never really go hand in hand.
Was looking for that comment 😅
They made private data the „new gold“ which it is today long before social media started exploiting it. Changing their motto /code of conduct „Don’t be evil“ into „Do the right thing“ (for our shareholders) didn’t benefit their reputation either…
paperless-ngx
„Old habits die hard“
&
“Anything that can go wrong will (eventually) go wrong.”
2 things I found on a quick search:
1st Look if your GPU is actually designed to have a „headless“ start - if not you most likely need that dummy adapter that others mentioned
2nd In the bios settings look for something like an “Halt on all errors” option and disable it. If the GPU is the problem than you might get to start it anyways without any monitor connected