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

help-circle
  • Going to be tough to answer any of these questions with authority, as I do not bake much, and nothing I’ve ever baked has used sour cream. My experience with sour cream substitutes is just slipping it on top of tacos/fajitas/burritos. And for that purpose- it works just fine.

    Regarding using four cream as a thickener for soups- any thickener is going to work. Another poster suggested coconut cream, that works well for me. Adding starch of any kind will also work to thicken soups. If you’re looking for extra protein: blend up some cooked white beans, or silken tofu works really well for this too.

    Now for your question #2: I don’t know if I’ve ever encountered vegan sour cream with oat or almond bases, but I know when comparing oat/soy/almond milk— the soy is the only one with protein and fat content. Oat and almond milk tend to have very little nutrition, and are mostly cloudy water (exaggeration). So I tend to use unsweetened soy for most my cooking. Your mileage may vary.

    Good luck!! And remember that you don’t have to only cook from physical cook books- the internet is LOADED with good vegan recipes. Do some experimenting. Don’t be discouraged when something doesn’t turn out, it takes a while to get the hang of using so many new ingredients!


  • Same.

    I dont do much customization, but the endevorOS community edition has decent defaults.

    Just working cleanly with tiling feels so good. You dont have to use the mouse to move all the windows around. But if you hold the super key, you can just drag windows around to make a perfect layout. But often than not, i just want 2 windows side by side, with no wasted space. Done.











  • 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”}