A couple of months ago total Supervised users were 14% from memory and has now dropped to 10.7%. They wanted to deprecate Supervised last year and by adding more obstacles, like this unnecessary flagging of Docker containers, they push even more people towards using OS.
It’s waste of energy pushing back on anything Supervised related I feel. As soon as the user base is small enough, it will become “too difficult for them manage / too much workload for such a small user base”. The plan was to get rid of it, it’s just a matter of time until that happens, unfortunately.
… which has pushed me to start to look elsewhere. Additionally it gets difficult to accept the tune which lately often emerges to criticism and/or suggestions.
I don’t know where these numbers are coming from and if they’re reliable enough. For example I have a supervised install and I have toggled off the options to send analytical usage etc. (may be I should revert that ). Others with simpler installs may not bother with these settings.
Anyways, I didn’t know that an installation method which is still officially supported is now called “Frankenstall” for whatever reasons. The project may very well stop supporting this method, as it tried in the past, and be done with that, instead of trying to indirectly push people away of it.
Within this frame a simple on-off message “that the installation is not fully supported” etc. would suffice, instead of a permanent big yellow notification which implies a broken situation in an otherwise perfectly good-working system.
This is working for me, except the Official Raspberry Pi 7" touchscreen works at boot for a first 12-13 seconds, then goes blank. It starts off showing the boot output with the timestamps, which is what I see on the HDMI.
Is this expected behavior? Is there a way to get it to work? Do I need to install vcgencmd?
Hi there! Once you have flashed Debian on the MicroSD card. Remove it from the computer and insert it again. You will see a “RASPIFIRM” drive. Open it and then look for a file named “sysconf.txt”. In this file, you will add the following line at the end:
After the public key is generated, copy the content inside the text box that says “Public key for pasting info OpenSSH authorized_keys file” and that is what you will paste in the “sysconf.txt”
( Do NOT close puttygen yet)
Save it, and you can remove the MicroSD now and plug it onto the Raspberry.
Before closing the puttygen, click the “Save private key” button and save your PPK file on a location of your preference.
Now finally, to connect to your Raspberry, you need to know its IP address. You can find it on your router web management or by using Nmap to scan your network.
Open putty.exe, enter the IP address, and to load your PPK file, go to “Connection” → “SSH” → “Auth”, there you will see an option to load your previously saved Private key file.
You can now connect using root, and no password will be asked since you are using public key authentication.
Not the smartest idea to manage your RPI solely as the root user (which is what juan89’ instructions are about). It is generally recommended to not log in as root… and if you do, keep your root sessions short and system administration works only.
Just follow exactly the instructions from the OP and pay special attention to paragraph 1.5).
This way you will avoid running CLI-sessions automatically as “root” but instead you’ll run them as the unprivileged user you have defined by the adduser-command before thus protecting your installation from mistakenly potential destructive cli-commands.
Juan, I just tried to follow your instruction : it works fine, thank you.
BUT, even if I can reach my rpi by ssh, it doesn’t explain why I can’t see anything on my screen.
(After SD flashing, I can see the first screen of my rpi and the color screen two… After I have some lines which go down very fast and I lost the connection to my screen. I can connect by ssh but I don’t know the user to use: I tried “root” and “root” for the password).
As I can’t find any help on this point, if someone can give me some support …
If you have followed Juan’s instructions you should already have been logged-in (as root) automatically since a key-exchange has happened in the background between the ssh server on the RPI and the connecting device (which should have the referring public key stored with the ssh client (i.e. Putty). Therefore there will be no login-prompt anymore.
You can check as what user you are connected to the ssh server by using the cli-command: whoami
Yes I have no problem with that. I just want to understand why I can’t have access on my laptop screen (which is linked with my Rpi) => I didn’t have this problem with my old Debian 10 / RaspianOS installation. If I put my Raspian SD Card, I have no problem.
But, I can also confirm that after creating new user, I can connect to my rpi via ssh… (but still without the screen).
@kanga_who thanks for providing this install instructions
I have installed Home Assistant with the help of your script/the commands in Supervised mode.
Right now I cannot find the configuration.yaml file. I have searched with the find command the whole pi SD card but it is not existing.
In which location is the configuration.yaml or do I have to generate it manually somehow?
). Others with simpler installs may not bother with these settings.