• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle






  • Foreverwinter@lemmy.worldto3DPrinting@lemmy.worldAdvice on a Printer
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    People have made the same recommendations here already but I’ll throw my opinion in: the two I always recommend are the Ender (V2 or S1) and the Prusa (Mk4 or the Mini)

    If you’re unsure about how much you’ll use it or if you’re on a budget get the Ender.

    But if you’re confident this is something you’ll use a lot and you can afford it get the Prusa.

    The Prusa has just too many nice features to ignore, their support is amazing, and their upgrade path makes it something you can (likely) keep upgrading as new features come out.

    For example I have a Mk3 and I have the upgrade kit to make it a Mk3s+. And now that the Mk4 is out there’s upgrade kits to make it a 3.5, 3.9, or a 4. They’re really great about trying to keep your printer as feature rich as possible without having to buy a whole new one.


  • Appreciate your take on this and specifically mentioning that you have a VM for Home Assistant. That was a lightbulb moment for me as I like how easy it is to manage updates as an OS install rather than in a Docker container. If I ever get around to rebuilding my server architecture I’m definitely going to do this!


  • Each device has its own protocol/payload, but there is a utility called rtl_433 that can decode about 200 of them.

    If you’re keen on tinkering a bit I would highly recommend going this route as it’s a lot of fun and opens the doors to do all kinds of stuff.

    Start by getting an SDR. I don’t recommend the super tiny ones since they can get really hot (since it’ll be running 24/7). I have this one and recommend it as it comes with an antenna etc. Nooelec RTL-SDR v5 Bundle

    While you’re waiting for that to arrive set up an MQTT broker if you haven’t got one running already (the Mosquitto add-on in HA) and install the rtl_433 add-on as well.

    From there read the rtl_433 docs to set up a config file to scan for what you want. Out of interest I set mine to rotate through a bunch of common frequencies and let it go for 24h to see what it could pick up. It was quite interesting! Another good way to do this is any wireless device will have an FCC number on it. You can look that up on their website and it’ll tell you what frequency it’s using and you can have your SDR scan that. If you don’t specify any protocols the rtl_433 utility will try everything it knows how to decrypt. This can be CPU intensive especially on a Pi so once you know what protocol it is you can specify it in the config file to reduce CPU load.

    Hopefully that’s enough to set you down the right path. Happy scanning!