DreadPotato

[SOLVED] I changed the IP of my Adguard yesterday and forgot to update DNS in HA. It updates just fine after I updated the DNS IP in HA. I'm guessing everything else worked outbound, despite the wrong DNS in HA, because I had the correct DNS set it in my router.

I wanted to update my HA this morning but got .

Which is a bit weird, because my HA is reachable from outside my home network via nabu casa, and all my integrations relying on internet work just fine. It can even ping outside my home network.

[SOLVED] Turns out I'm just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.

As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don't need to access the host remotely/outside my home network, this is just for updating it etc.

I can't see the host under active devices in my router though.

I have been trying to figure why, but so far without any luck.

I've just about convinced myself that I need a voron trident to replace my current cheap bedslinger. Since I can't live with the small print area of the 0.2, that one is out of the picture although I was thinking of that first. I like the DIY and open aspect of them, but many of the kits I can get locally seem grossly overpriced at around 1700 euros for a trident or 2.4 kit that I have to do all the work on myself.

Is there actually any significant saving by sourcing all parts yourself instead of buying the kits? Anyone here have experience buying all the individual parts? Brands to go for or avoid?

I have trouble fixing the terrible seams I'm getting. I've followed Elli's print tuning guide and calibrated extruder, tuned PA (it's now 0.035) and extrusion multiplier.

I've tried adjusting both retraction length and speed, but it doesn't seem to have much impact. I'm not using "wipe on retract" or "retract on layer change", I only retract if travel distance is longer than 3mm. Retract is 0.3mm @35mm/s.

I've tried reducing PA smooth time too, but this also doesn't seem to have a noticable impact.

I've tried reducing seam gap from the default 10% in Orca all the way down to 0%, but the bad seams persist.

I've tried with "wipe on loops" both disabled and enabled with no difference.

I've tried with both arachne and classic wall generator, no difference.

I've tried different wall orders, inner/outer, inner/outer/inner and outer/inner, all with the same bad seams.

Filament in the picture is matte PLA, it is without doubt dry and generally prints well aside from the seams. It's stored vacuum sealed with silica, and I use a filament dryer to dry if I suspect wet filament.

I'm running out of ideas for where to tweak to get a decent result.

How difficult would it be to increase the build plate size of a 0.2R1 from 120 to something larger like 200mm? I would be OK keeping the 120mm Z-axis print height

How long do you have filament sitting "in the open"? I mostly print with a single filament roll at a time, and just leave it on the printer. A 1kg roll lasts me several weeks. For long time storage I keep it in an air tight box with disiccant pouches.

But how long can I let it sit before I should start storing it with disiccant and/or drying the filament before use?

I wanted to print a temperature tower, but the custom Gcode entered in prusa slicer doesn't seem to actually change the temperature of the nozzle? It just uses the temperature that's configured on "other layers" under the filament tab.

I'm attempting gaaZolee's temperature tower, using the custom Gcode supplied with it, in the "before layer change" part of custom Gcode in prusa slicer.

Når man nu har smidt Lineage OS på sin gamle android telefon (oneplus 9pro), så vil MitID jo ikke rigtig lege med fordi bootloaderen ikke er låst. Findes der et fix så jeg ikke skal have en anden telefon med stock ROM for at bruge det? Hvis jeg låser bootloaderen igen så havner den bare i et bootloop :/

Edit: forslaget fra humanplayer2 virkede, rettede fire tekststrenge i build.prop på telefonen fra "Lineage"/"userdebug" til "Linage"/"user" og voila! så virker mitID.

Recap fra reddit linket nedenunder, så vi har det på feddit.dk også.

Hvis man slår "Rooted debugging" til under Developer Options kan man gøre:

adb root
adb pull /system/build.prop

Redigér filen på computeren, udskift følgende tekststrenge:

"dev-keys"/“test-keys” til “release-keys”
“userdebug” til “user”
“lineage” til f.eks. "linage"

overfør build.prop tilbage til telefonen

adb remount
adb push build.prop /system/build.prop

genstart telefonen

adb reboot

slet cache og data på mitID appen, og så virkede det for mig