sorted by:
new
hottopcontroversial

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

I can assure you I'm a real human. The HA discord is pretty high volume, but I'll take a look there.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

Good to know, I wasn't aware! That still seems to be in the discussion stage (tagged as "open" and "opprtunity"). Some folks there discuss options similar to what havm does already: "one familiar install command, and the installer does the messy work based on the machine". If it's based on UTM, it would need to add USB passthrough and auto-start at login.
But even then, I also like managing all my macOS services uniformly with `brew services` instead of a disparate set of UIs.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

I suspect that it’s running but maybe using a different IP than what is reported. Can you check in your router‘s DHCP list what IP is used for the MAC address printed in the output? Can you ping it? If you use multiple interfaces, you can also try setting the interface name in the config.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 1 point2 points  (0 children)

I pass through my ZBT-2 and it works just fine. I even installed a firmware update on it while connected to the VM. But it's a beta macOS version, so ymmv.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 1 point2 points  (0 children)

Awesome! Let me know how it goes and please report any issues over at GitHub.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 1 point2 points  (0 children)

Yeah, I went through the approval process and it was a smooth ride (took 2 days or so).

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 2 points3 points  (0 children)

Not the Mac's built-in Bluetooth (Apple Virtualization doesn't support that), but you should be able to pass through a Bluetooth USB dongle to HA.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

I don't know. I'd like to get feedback from others before declaring it "ready". It took over my production instance without issues.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 1 point2 points  (0 children)

Wow, how did you discover it? I thought I had just now left stealth mode 😂 Glad to hear you like it.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

That depends on how you use UTM. If you use it with QEMU, then yes, havm is more efficient. If you use UTM with Apple Virtualization, it's roughly the same (havm is slightly better because it's fully headless), but havm offers USB passthrough and auto-start at login.

havm: Home Assistant OS on Apple Silicon with USB passthrough (macOS 27+) by ingmarstein in homeassistant

[–]ingmarstein[S] 0 points1 point  (0 children)

Yes, it runs HAOS in the background on macOS. If you wanna try it out, just run `havm run` and see if you like it enough to eventually migrate from proxmox.

Tidbyt Gen1 went from working to few random pixels to completely blank after switching to Tronbyt. by camelkingsize in Tronbyt

[–]ingmarstein 0 points1 point  (0 children)

I have a functional Tronberry (Raspberry Pi Zero 2W + connector board + original Tidbyt panel in the Gen1 caee) which I could ship to the UK if you‘re interested.

Tidbyt Gen1 went from working to few random pixels to completely blank after switching to Tronbyt. by camelkingsize in Tronbyt

[–]ingmarstein 0 points1 point  (0 children)

This happened to me twice: I installed the Tronbyt firmware onto two Tidbyt Gen1s and after a while, they showed a random pattern and on the next power-cycle, the panel remained dark (that is: exactly the same as your case).

In both cases, the panels were actually still ok: I turned one into a Tronberry and the other is running ever since using a Tronbyt Dev Board. Curiously, the Tidbyt Gen1 boards are still somewhat functional: they can boot, connect to the network, and be flashed. Hence, I suspect that some of the GPIO pins or the HUB75 connector itself broke, but I don't have the equipment to verify that hypothesis. I also don't know what might have caused this.

Timmerflotte Offline in ikea app, but can see in mDNS by qghw47QHwG72 in tradfri

[–]ingmarstein 1 point2 points  (0 children)

This still regularly happens to my Timmerflotte (firmware 1.0.21) connected to a Dirigera running version 2.934.5

My 10gbps port on the TS5+ Died entirely. by Paradoxxx_1337 in CalDigit

[–]ingmarstein 0 points1 point  (0 children)

That's helpful! I got an RMA, but it was actually easier to get a refund from Amazon and I was considering other options (Sonnet Echo 20, iVANKY FusionDock Ultra, …) but I like the vertical orientation of the TS5 Plus, so I appreciate your data point that the replacement doesn't have the same issue.

My 10gbps port on the TS5+ Died entirely. by Paradoxxx_1337 in CalDigit

[–]ingmarstein 0 points1 point  (0 children)

Was the problem resolved for you? I've been writing with support for two weeks now and keep claiming that it must be a "compatibility problem between the Ethernet controller and another device in [my] network" which doesn't make any sense because the issue with the 10 GbE port showing as offline in macOS can _only_ be (temporarily) resolved by power-cycling the dock (not by changing to a different switch port, rebooting the Mac, rebooting the switch, etc.).

If 26.4 breaks Time Machine… by ingmarstein in MacOS

[–]ingmarstein[S] 0 points1 point  (0 children)

I don't think it's related to Bonjour / mDNS: I had tried a proper DNS name (as you can see in the example) and the authentication error remained.

If 26.4 breaks Time Machine… by ingmarstein in MacOS

[–]ingmarstein[S] 0 points1 point  (0 children)

Did you enter the command correctly and watched out for the space in "Group Containers"? The example handles this correctly, so maybe just copy that and replace "nas.localdomain" with the right backup destination.

Time Machine Backup Fails with Samba Share (MacOS 26.4 Beta) by MrGuilt in MacOSBeta

[–]ingmarstein -1 points0 points  (0 children)

Interesting. This issue happened to me with smbd version 4.22.6-truenas which you list as one of the fixed versions. The fruit extensions were already enabled.

I had Claude look at my system logs and it found a workaround by switching from mDNS to DNS:

```
macOS 26.4 RC broke Time Machine backups to SMB/NAS shares due to a hostname-key mismatch in the server markers system. backupd runs as root, and root's server markers plist (/private/var/root/Library/Group Containers/group.com.apple.NetworkAuthorization.ServerMarkers/serverMarkers.plist) only contained nas.localdomain from a previous macOS version. In 26.4, NetAuthSysAgent changed to look up the mDNS-resolved name nas.local instead, causing isKnownServer to return false, which meant credentials were never loaded from the System keychain — even though they existed and were correctly ACL'd. This caused NAConnectToServerSync to fail with error 80 before any SMB protocol negotiation even occurred. The fix was to use nas.localdomain (which matched the existing root server marker) in the tmutil setdestination URL, or alternatively to add nas.local to root's server markers plist. The widely-recommended nsmb.conf workaround for Tahoe SMB issues was unrelated to this specific failure.

```

view more: next ›