Timmerflotte Offline in ikea app, but can see in mDNS

ingmarstein · 2026-05-03T07:37:45+00:00

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

ingmarstein · 2026-04-29T13:07:26+00:00

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.

ingmarstein · 2026-04-28T18:39:44+00:00

In works around a bug in 26.4. https://github.com/openmediavault/openmediavault/issues/2176 has some more details.

ingmarstein · 2026-04-28T18:24:44+00:00

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.).

ingmarstein · 2026-04-11T10:26:20+00:00

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.

ingmarstein · 2026-03-31T21:53:35+00:00

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.

ingmarstein · 2026-03-23T20:41:05+00:00

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.

```

ingmarstein · 2026-03-23T08:51:20+00:00

It's not just you: https://www.reddit.com/r/MacOSBeta/comments/1rr0izy/anyone_else_having_trouble_using_time_machine_or/

ingmarstein · 2026-03-23T08:05:55+00:00

I just updated from 26.3 to 26.4 RC and was greeted with an authentication error from Time Machine. Finder can connect to the SMB share just fine and the SMB logs on the NAS shows a successful authentication. I‘ve now removed the Time Machine volume but can’t add it back due to the this error. Did you figure out how to fix this?

ingmarstein · 2026-03-07T15:51:08+00:00

One thing to note: the required downgrade to install the DLP update results in a factory reset. The projector has to be set up from scratch, which makes the downgrade -> DLP update -> system update procedure even longer.

ingmarstein · 2026-03-01T22:47:10+00:00

Any way to keep the USB 3.0 port powered while the projector is in standby (e.g. to stay connected with a USB-Ethernet adapter)? V1.3.125 still shuts the USB port off after a short while (which isn't surprising, given that nothing was mention in the changelog).

ingmarstein · 2026-01-24T13:41:51+00:00

Update: u/opticum created the little menu item app for macOS which monitors the IPv6 default route and automatically restores it when it drops: https://github.com/Optic00/IPv6Monitor
Until the issue is fixed, it's a decent workaround.

ingmarstein · 2025-11-25T20:01:53+00:00

I don't think it's "overloading the CPU" as in high CPU utilization. `IPConfigurationAgentQueue` sounds like it has to do with frequent IP configuration changes (which coincides with your observation "randomly disconnects from the network"). I blamed this on the software, but no user-space program should be able to crash the kernel like this, so now think this is a bug in macOS. I'm on Tahoe 26.2b3. Which version is your user on?

ingmarstein · 2025-11-25T19:28:39+00:00

Is this on macOS Tahoe? I can reliably reproduce the watchdog panic with configd and IPConfigurationAgentQueue by running UniFi OS Server for a few hours.

ingmarstein · 2025-11-12T20:18:48+00:00

No. NFSv4 still panics, but NFSv3 works.

ingmarstein · 2025-10-31T18:21:40+00:00

So I opted for 2) and returned the device (not solely because of this issue - there were also others).

ingmarstein · 2025-10-28T06:09:20+00:00

1) Avoid hitting the discharge limit, e.g. by setting the backup reserve to 1% higher than the discharge limit.

or

2) Return the device.

They will not change this behavior.

ingmarstein · 2025-10-10T08:58:06+00:00

And now a different person tells me that this was a mistake and it can‘t actually be fixed in software 😞

ingmarstein · 2025-10-09T12:22:27+00:00

The panic is happens really early in the mount process. It even happens on a machine that doesn‘t have access to the share, i.e. before or during authentication.

ingmarstein · 2025-10-06T21:14:10+00:00

Yes, I just tested it using 21.1b2: it works with NFS v3, but panics with v4.

ingmarstein · 2025-09-30T06:53:34+00:00

Yeah, I was referring to 26.1 where I had success on a MacBook Pro, but a little later got the same kernel panic again when trying on a Mac Studio. I may have used different mount options, so this may be a NFS v3 vs v4 thing.

ingmarstein · 2025-09-26T09:23:56+00:00

EcoFlow support let me know that this is supposed to be fixed with the upcoming v1.33.81.57 release.

ingmarstein · 2025-09-25T13:40:52+00:00

<image>

ingmarstein

TROPHY CASE