I have two HiFiBerry DACs running on my network, which I use for multiroom audio via Roon. This works fine, but I have a problem. I would like to be able to power off the RPi boards when I am not using them, e.g. when I am not at home. I can do this via ssh with the first DAC installed (a DAC+) but when I try to connect to the second unit (a DAC2HD) I get the message "Connection reset by 192.168.1.xxx port 22". I also cannot get to the second DAC via HiFiBerryOS to power it down, as presumably there can only be one "hifiberry.local" on the network. (But powering down from HiFiBerryOS does not seem to be working at the moment anyway.) I would also like to be able to use a USB-C switch to cut the power connection fully, but I see that this is no longer available from yourselves (although it is still available from the Pi Hut). How do I safely power down my HiFiBerry DACs?
8 comments
-
HiFiBerry team You can just rename one of the systems to something different then "hifiberry". This way you can access both by their individual names.
The "connection reset" looks like something isn't working fine on one of the systems. Try disabling/enabling SSH on this one. -
alancaemawr I already renamed the first one (in HiFiBerryOs) to HiFiBerryDAC+Pro, although it still shows up on the router as "hifiberry". The second one was named HiFiBerryDAC2HD when I installed it (and shows up as such on the router), although I can't seem to get to it on HiFiBerryOS any more. See attached photos. Does the port matter, and what can I do about it if it does? What do you mean by "access both by their individual names"? / Thanks
-
alancaemawr Update:
Changed the name of the first DAC in the router to "hifiberrydacpluspro", and now I can use "hifiberrydacpluspro.local" to access it. Sadly I still have no access to "hifiberrydac2hd". I think I may need to reflash the SD card...
-
alancaemawr Reflashed the SD card but still didn't solve the problem.
After connecting a monitor, keyboard and mouse to the RPi, I discovered the following issues.
- The DAC is correctly identified as a DAC2 HD in HiFiBerryOS but the "name" is apparently blank and I can't set it (see attached). Or possibly it is set to "DAC2_space_HD", which means I can't access <name>.local.
- At boot, remote logins are disabled by default, which is why ssh doesn't work in a terminal.
So, how can I set remote logins to be allowed by default, so that I can "poweroff" the RPi cleanly without the risk of trashing it. Pulling the power cable is never recommended, of course, which is the weak point of all Raspberry Pi-based systems.
Thanks. -
HiFiBerry team You can enable it in the web UI at "General/Remote login"
-
alancaemawr OK, I seem to have got to the bottom of this issue. This appears to be a resurfacing of an bug that was supposed to be fixed in HiFiBerryOS v 20201101 (Bugfix: DAC2HD not detected correctly). I have now installed this version on my DAC2HD and my problem appears to have gone away. I also have a HiFiBerry DAC+Pro running HiFiBerryOs v 20200805 and that also runs without issue. I even have remote login enabled for both units by default. So I am going to report this as a FAULT. I would recommend that no-one installs the newest version of HiFiBerryOs (v 20201213) until the problem is resolved.
-
HiFiBerry team I'm not sure what bug exactly you mean. The majority of users runs 20201213 without issues.
-
alancaemawr But maybe they don't have a DAC2 HD? I have submitted this as a bug now. Please see notes for version 20201101 for details.