Since youâre not using the Veraâs native (system) keys from /etc/dropbear, you have to specify the key on your command line: ssh -i ~/.ssh/id_dss pi@192.168.1.101 whoami
Also make sure your ~pi/.ssh/authorized_keys is not world-accessible and is owned by pi.
Edit: also, itâs a bit odd that you named your key file id_dss but you had it create an RSA key. I donât think thatâs going to matter at all, but it could be misleading in future if some occasion comes up where you need to be using the correct key type.
Edit 2: and as I stare more at what youâve done, when you appended the public key to the piâs authorized_keys file, you appended two additional lines from the output of dropbearkey that should not have gone along for the ride. Go edit that file and remove the lines âPublic key portion is:â and âFingerprint:â. You only want the line that starts âssh-rsaâ to be in there.
Edit 3: agggh, no, itâs even worse than that⊠where you did this:
You copied the private key and everything into authorized_hosts, but thatâs not whatâs needed there. You need the public key (which isnât even exposed in id_dss without using dropbearkey on it).
First, on the Pi, you need to remove everything from the Vera that youâve put into authorized_keys so far. You copied binary data into it. Just delete it if thereâs nothing else in there you may have needed (no other systemsâ keys that connect to that system), otherwise, youâll need to edit.
Then, on the Vera:
Run this to copy the (Vera) system public key to the Pi:
Thatâs the one. Sorry about that. Need to specify the key. We could have used the system key anyway and left your id_dss key out of it entirely. Just do this:
Well, I canât answer for its requirements, but wherever it is started up (sysvinit/init.d? systemd?) it probably uses the java command followed by the name of the JAR file. The -Xms option to the java command sets the starting memory allocation, and the -Xmx sets the maximum. So you could supply -Xms256M -Xmx384M for example, and it would start up with 256M of RAM (thus that is its minimum RAM requirement) and top out at 384M (it will not request more RAM than this from the system and try to work within what it is allowed). If the author doesnât provide guidance, you may need to experiment. The app will likely crash with an obvious memory exception if the upper limit is too low, but if you donât set an upper limit, skyâs the limit (Java will happily exhaust system RAM and crash the system).
âI also note you have a Java process running. Javaâs runtime allocates but never frees memory from the system. It will allocate memory from its configured min/start (-Xms) to its configured max (-Xmx) linearly; it will never return unused memory to the system. You may need to periodically restart the java process to reduce overall system memory use (ideally, of course, you would find a happy setting for max that works for your other system process and the total amount of system RAM, so that java hitting its limit doesnât cause paging (swap) or system failure).â
Moved us other here, so we are not spamming his VeraFlux thread.
The âhabridge.serviceâ file located in /home/pi/habridge folder, that launches HA-Bridge on my Pi is this: