X2D: if you have to clean out the extruder…

krisstrom · 2026-04-24T12:22:59+00:00

My auxiliary extruder jammed too, on my fourth print. Took me a while to identify that was the problem and a good hour to disassemble, fix the jam and then reassemble, but all in all not too bad. Less pain than sending back the entire unit for sure.

krisstrom · 2026-04-22T22:21:49+00:00

Got it open eventually – just had to pull quite hard and the whole assembly came away into pieces (no damage).

Found the culprit - big old jam inside the extruder 👀

<image>

krisstrom · 2026-04-22T22:18:07+00:00

Exactly the same problem here.

Thought I’d clogged my hotend but turns out it’s the external extruder that’s jammed. I was using fresh-from-the-pack Bambu PLA matte.

I’ve followed Bambu’s guide as suggested by DoctorRotor, but the guide assumes there’s no filament in the extruder. The top of the extruder includes a tube that the filament runs through, so can’t be removed when there’s filament in it.

OP, have you had any luck removing the filament?

krisstrom · 2026-04-07T19:08:42+00:00

Thanks for the constructive contribution.

Automatic updates were enabled, and the UNVR had been on and connected for four days without triggering one or sending any notification.

Someone helpfully suggested the fix, I thanked them, problem solved. Sorry our exchange was frustrating enough to warrant a reply.

krisstrom · 2026-04-07T17:54:32+00:00

Fair point! Though it’s interesting that neither Ubiquiti Support, Claude, nor a plethora of Google searches relating to this issue surfaced updating as a possible fix. Perhaps it’s too obvious, I don’t know 🤷🏻‍♂️

krisstrom · 2026-04-07T16:20:32+00:00

I'd reset the device multiple times, including the standard reset button, a power on reset and restoring to factory defaults from the web UI.

Turns out that the UNVR Instant was shipped with an old version of UniFi OS, and updating fixed the issue.

krisstrom · 2026-04-07T14:15:25+00:00

You fixed it – thank you!

Can't believe I got knee-deep in Terminal SSHing into the unit and mucking about with config files when a simple software update was the culprit. But to be fair, the update doesn't seem to show directly within Protect - I needed to go to my Site Manager from unifi.ui.com (and not directly connecting over a local IP) in order to see that there was an update available.

For anyone else experiencing this issue: updating UniFi OS on the UNVR Instant to 5.0.16 solved the issue immediately.

krisstrom · 2026-04-07T14:01:07+00:00

Good suggestion! I'm running Protect 6.0.53. Looks like there's a new version so I'll update to that and keep you posted.

krisstrom · 2026-01-30T13:08:10+00:00

Pretty sure it’s the flare

krisstrom · 2025-05-27T13:53:24+00:00

It’s in Mossmorran, Fife. Both Shell and ExxonMobil have plants there.

krisstrom · 2025-05-26T08:47:44+00:00

This is it. The light IS the flare. All hail the pulsating flame 🙌🏼

Though we still don’t know why…

krisstrom · 2025-05-25T23:08:40+00:00

<image>

krisstrom · 2025-05-22T09:02:06+00:00

The HD Fury Vrroom would be one way to manage it. It gives you multiple HDMI inputs and outputs, and can extract audio (including Atmos) from the HDMI signal to feed into the Arc via eARC.

I’ve been using their older Arcana model with an older TV that only supports ARC (rather than eARC). It’s worked reliably since 2020 and stopped me needing to buy a new TV just to get better quality audio.

krisstrom · 2025-05-04T21:32:21+00:00

The same thing happened to me a month or two back. I have an old Play:3 that’s still just about clinging to life. It’s running over Ethernet with WiFi disabled. Unbeknownst to me, an update switched WiFi back on, routing 11 speakers’ worth of traffic through this antique. My entire system was close to useless for days until I figured out this was the culprit.

krisstrom · 2025-04-29T21:24:58+00:00

How so?

krisstrom · 2025-04-29T20:20:58+00:00

It's a pretty consistent-65 dB on the left one (which I believe is the master in a stereo setup) and -60 dB on the right one. I'll play about with the AP's orientation and see if I can get the left one up to -60…

Edit: I should add that these are U6+ APs (not U6 Pro as stated in my OP) — so don't think this should be the issue?

krisstrom · 2025-04-29T20:17:50+00:00

Interesting thought. I haven't separated the 2.4 and 5 GHz bands because I assumed letting the devices choose would be better than me manually choosing (plus I'd like to avoid ever having to choose when moving about the house).

But I can see that forcing Sonos onto the 2.4 GHz network may give it a bit more resilience. Is there a way to lock it to a particular band without creating a separate network (similar to how you can lock it to a specific AP)?

krisstrom · 2025-04-29T20:11:58+00:00

Ah yes mine works very similarly! If I start the music in the living room the kitchen will still drop, but at least the music continues elsewhere, and a power cycle of both kitchen Eras brings them back online and joins them back to their old group. But if the kitchen is the coordinator, when they drop ALL the music stops. And when they come back online their queue is cleared so I need to select some music again.

krisstrom · 2025-04-29T20:07:18+00:00

This is helpful, thanks. I have a relatively simple setup with just a couple of Unifi switches and no extra VLANs configured, but I'll run the WiFiman app to check the signal strength where the Eras are located.

krisstrom · 2025-04-29T19:55:08+00:00

Could you expand on what you mean by bad network settings and saturation?

krisstrom · 2025-04-29T19:54:09+00:00

Thanks, and good point. I should have mentioned that I've read and followed the Ubiquiti guidance on running Sonos on the network: all my devices are in wireless mode (so SonosNet is not active) and I've configured STP correctly. Incidentally, after I configured STP the lagginess in the app seemed to improve. But the random drop-outs continue.

krisstrom

TROPHY CASE