Cricalix.Net - Recent changes [en-gb]

Home Automation/Tailscale

Cricalix — Thu, 02 Apr 2026 17:17:54 GMT

Cricalix deleted page Home Automation/Tailscale content was: "To get access remotely, without exposing the HA Pi. == Installation == # Add-ons # Store # Add Tailscale # Start on boot, watchdog, auto update # Start the add-on # Logs # Grab URL for auto to tailscale # Paste to new tab # Approve access", and the only contributor was "Cricalix" (talk)

Home Automation/Synology DSM

Cricalix — Thu, 02 Apr 2026 17:17:37 GMT

Cricalix deleted page Home Automation/Synology DSM content was: "Integration that pulls drive statuses, temperatures etcetera from the Synology. Not that interesting of a module to enable, other than getting SMART visibility.. but the integration hides that!?", and the only contributor was "Cricalix" (talk)

Computing/NUT

Cricalix — Thu, 02 Apr 2026 17:17:05 GMT

← Older revision		Revision as of 17:17, 2 April 2026
(One intermediate revision by the same user not shown)
Line 3:		Line 3:
	=== Installation ===		=== Installation ===
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	~~apt~~ install nut ~~nut-monitor~~		dnf install nut
	</syntaxhighlight>		</syntaxhighlight>

	=== Configuration ===		=== Configuration ===
	For the Eaton Pro UPS, '''/etc/~~nut~~/ups.conf'''<syntaxhighlight lang="ini">		For the Eaton Pro UPS, '''/etc/ups/ups.conf'''<syntaxhighlight lang="ini">
	[eaton650]		[eaton650]
	driver = "usbhid-ups"		driver = "usbhid-ups"
	port = "auto"		port = "auto"
	~~vendorid = "0463"~~
	~~productid = "FFFF"~~
	~~vendor = "EATON"~~
	~~bus = "005"~~
	~~</syntaxhighlight>Vendorid/productid/vendor/bus are not critical for single use case.~~

	~~Then~~ '''/etc/~~nut~~/upsd.conf'''<syntaxhighlight lang="bash">		</syntaxhighlight>'''/etc/ups/upsd.conf'''<syntaxhighlight lang="bash">
	LISTEN ~~127.0.0.1~~ 3493		LISTEN * 3493
	~~LISTEN ::1 3493~~
	</syntaxhighlight>~~And finally~~, ~~'''/etc/~~nut/~~nut.conf'''~~<syntaxhighlight>		</syntaxhighlight>All other files were left at defaults from the RPM installs, bar this detritus from a polkit adventure - it may or may not still apply<syntaxhighlight>
	MODE=~~standalone~~		polkit.addRule(function(action, subject) {
			if (action.id == "org.freedesktop.systemd1.manage-units" &&
			subject.user == "nut") {
			return polkit.Result.YES;
			}
			});

			</syntaxhighlight>

			=== udev ===
			<syntaxhighlight>
			ATTR{idVendor}=="0463", ATTR{idProduct}=="ffff", MODE="664", GROUP="nut"

	</syntaxhighlight>		</syntaxhighlight>

	=== Runtime ===		== Runtime ==
	<syntaxhighlight>		<syntaxhighlight>
	systemctl start nut-server		systemctl start nut-server
	</syntaxhighlight>The script behind nut-server will spin up new systemctl services to handle the UPS.		</syntaxhighlight>The script behind nut-server will spin up new systemctl services to handle the UPS.

	~~NUT Monitor can be run to get a graphical interface to the UPS status.~~		== Troubleshooting ==
			Previous attempts got stuck on custom UPS definitions in systemd, with permissions not setting up correctly etc. Ended up blowing everything away and restarting from scratch with the NUT enumerator approach.
	~~Using NUT will disable KDE's ability to communicate with the UPS and show the state of charge.~~

	==~~= Alternate installation =~~==
	~~Set MODE=netclient~~ in /etc~~/nut/nut~~.~~conf~~

	~~No entry in /etc/nut/ups~~.~~conf~~

	~~Add a MONITOR ups@synologyip 0 monuser secret secondary to upsmon.conf~~

	~~Set MINSUPPLIES to 0 in upsmon.conf~~

	~~systemctl restart nut-monitor~~

Computing/NAS/Software

Cricalix — Thu, 02 Apr 2026 17:12:23 GMT

Remove proxmox, use Incus

@@ Line 1: / Line 1: @@
-=== Proxmox ===
+== Hardware ==
-Defaults to port 8006. Given I access it from multiple machines, defaulting to 443 would be nice.
+Core is a https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ ([https://web.archive.org/web/20250624104920/https://nascompares.com/review/cwwk-q670-8-bay-gen5-nas-vpro-mobo-review/ archive] link); twin 2.5G network ports, a lot of SATA ports, and lots of compromises.
-<code>iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 8006</code>
+== Network ==
-Then use iptables-persistent to make that apply every time.
+=== Host ===
-=== Unraid VM ===
+[ethernet]
-Unraid needs a USB stick to boot from. Legacy advice on the Internet is that Proxmox won't boot a VM from a USB stick, but that's wrong with at least Proxmox V8. Config for VM
-* q35 machine
+[ethernet]
-SATA controller was assigned to a resource mapping at the Datacenter level in the Proxmox UI tree, then made available for the PCI passthrough. Two USB sticks were also configured in resource mappings; one for the boot stick, and the other for temporary use in the Unraid array. Integrated graphics also isolated for passthrough to the Media Host.
+[bridge-port]
-=== Media host VM ===
+</syntaxhighlight>
-Hit https://bugzilla.proxmox.com/show_bug.cgi?id=2381
+=== Incus Bridge ===
-Revert to 440 with PCI passthrough. Had to reinstall for some reason, and switch to SeaBIOS.
+== VMs and Containers ==
-==== Media host Sonarr ====
+=== Unraid VM ===
-<code>podman run --name=sonarr --detach -e PUID=$(id -u media) -e PGUID=$(id -g media) -e TZ=Europe/Dublin -p 8989:8989 -v /services/sonarr:/config -v /vault/video/TV\ Shows:/media --restart always lscr.io/linuxserver/sonarr:latest</code>
+Unraid needs a USB stick to boot from, as it uses the serial number of the stick as a license key. Ended up with plopkexec in the boot path for the qemu-backed VM (pc-q35)<syntaxhighlight lang="yaml">
-Needs host NFS mounted. Avoids trying to do privileged LXCs on Proxmox and working out how to maintain a copy of the configs outside of the container.
+=== HomeAssistant ===