• 7 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle






  • I’ve thought more on this yesterday, and I think my issue is-

    I don’t want something that ‘just works’, I want to BUILD something that ‘just works’

    The distinction is that I don’t want to buy premade solutions. I want to make them. Not because of the customizability, but because the fun is in the building. Think Lego- hundreds of people build the exact same product in the end, but why are they sold in pieces? Just assemble the damn things and sell them complete (with markup). You think more people wanna buy that?? I’d bet against it.


  • Hard agree. In fact, I think there’s a market for JUST the guides. It’s true that there’s a TON of guides out there already, from old blogs to YouTube, but the issue is: all of them start or end with: “your use case might differ, so perhaps this solution isn’t for you.” Or “make sure this setup is compatible with your specific hardware”

    For example: I want to set up some sort of backup/cloud storage type system. Well there’s about 1400 ways to accomplish that. I can easily just grab one and go, but I’ll always wonder- should I have done this a different way? Would my life be easier/more secure if I chose a different set up?

    So offering hardware that is compatible with whatever “stack” of services included would be a huge plus. Sorta like getting a raspberry pi and following a specific raspberry pi tutorial- you know the issues you get aren’t gonna be due to incompatibility.

    I think it really boils down to the scale of one’s home lab- are you just tinkering to get some skills and make something cool? Or are you hoping to do something much much bigger? Different software solutions fit those extremes differently.

    Sorry, got off rambling there. I guess I’ve been down the home lab hardware/software wormhole for too long these last few weeks.




  • Nimrod@lemm.eeOPtohomeassistant@lemmy.worldMQTT automation trigger help
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    Edit: I remember why - I wanted to use a single button dimming option, and as far as I can tell, there wasn’t that option in Shelly natively. There isn’t really a “native” version of this in Tasmota, but someone had already laid out the method to do such a thing with rules and whatnot within the Tasmota console. But after tinkering with it all this morning, I think I busted it beyond repair, so I might give the native Shelly a try!

    Mostly because I’m lazy. This device was set up before Shelly made it so easy to run offline versions of the native firmware. And I’ve got a handful of devices already running Tasmota, so I’m just resistant to change.


  • Yeah, Tasmota has ‘setoption19’ to enable autodiscovery, and I triggered it, and it finds a whole host of SENSORS - but none of them are the switches. It does add one entity which is a single switch. But it seems this just correlates to switch1. I’m thinking it has something to do with how I originally set up the dimmer… it was years ago, so I guess I need to dig into my notes and see if I can figure out what options I set on it before I moved it to it’s current spot.

    for reference, the data spit out by Tasmota: {“Time”:“2024-08-29T15:17:19”,“Switch1”:“OFF”,“Switch2”:“OFF”,“ANALOG”:{“Temperature”:35.1},“ENERGY”:{“TotalStartTime”:“2021-07-13T17:05:01”,“Total”:37178.152,“Yesterday”:0.000,“Today”:0.000,“Period”:0,“Power”:0,“ApparentPower”:0,“ReactivePower”:0,“Factor”:1.00,“Voltage”:117,“Current”:0.000},“TempUnit”:“C”}




  • I’ll just add that I’m a fan of valetudo, but it can be a bit more involved than your standard firmware swap. I had to build a pin breakout board, and race against time to root my vacuum because there is an auto-reset programmed into some robots that can brick your vacuum if the jailbreak isn’t finished when the reboot is triggered.

    Just read the process through all the way before you decide on device.

    I was sweating like I was in the hurt locker when I did mine, because my partner would have NEVER let me forget the time I bought a $900 robot vacuum and broke it before it even cleaned the floor once!







  • Oh wow. That is a good tip. Because that could drive someone like me insane. (Un)fortunately— I know there’s an issue. Any traffic I pass through my wg vpn ends up nowhere. So I know the tragic is being redirected, but I can’t tell where or why it doesn’t make it inside my home network.

    Either way, I got Tailscale to work right out the rip, so I’m just rocking that until I have more time to tinker with WG.


  • This is the first time I have attempted to port forward. So there is only one rule: this one. Port 5xxxx:5xxxx to the internal IP with the wg-easy docker container.

    Thanks for the reply, but I’ve bailed on this project for now. I fly to Europe tomorrow, so I don’t have any extra time to tinker. I gave Tailscale a try, and it works flawlessly, so I’m not likely to try WireGuard any time soon. I’ll wait for them to try an monetize their “free plan” users.