Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
3
Comments
91
Joined
2 yr. ago

  • Absolutely love Valetudo!

  • Is this done by keeping recursion set to the default and leaving Forwarders blank?

  • I'd love to hear from anyone has used this, especially if you moved from Pi-hole to Technitium. I run Pi-hole in an LXC and on a Pi3b and it's mildly annoying to make changes or updates, so clustering has piqued my curiosity.

  • That's a fantastic option.

    Also something used like a NUC or a little miniPC could be great as well.

  • I've been really happy with an Ambient Weather WS2000. You can integrate it into HA locally. They're not cheap brand new, but if you don't mind waiting you can run across great deals from Goodwill.

  • mmm

    Jump
  • What does this have to do with Home Assistant?

  • Totally agree. Rock solid.

  • For your RGBW LED controller, I really like the WLED ones from GLEDOPTO.

  • I think both of these ways are good and valid in their own way, they both have upsides and downsides. For me, having things separated is working well. I especially like being able to reboot HAOS more frequently and as soon as it comes back up all my Z-wave devices are ready to go. Back when I ran Z-wave inside of HAOS it took a lot longer for the Z-wave network to calm down and be ready after a reboot.

  • Avoid using device IDs in automations, use entity IDs instead.

  • Get something small, maybe something like a Lenovo ThinkCentre mini. Put Proxmox on it and install HAOS as a VM. Then when you want to add software, add them as LXC containers on the Proxmox host. Like Z-wave, MQTT, ESPHome, zigbee, etc. I really like having things in separate containers so that way I can work on things separately. If I need to restart the HAOS VM, it's a lot faster because my entire Z-wave network doesn't have to restart.

    Avoid adding things that require cloud access. I have to have a damned good use case before I add anything that requires Internet access.

    Oh and I like this place: https://cloudfree.shop/

  • Had mine for a while now and it's been rock solid. Love it.

  • Congratulations on the new job!

    I really like this blueprint because all its features, especially getting the light to turn on a little bit before my alarm does.

  • I've dabbled with a few different distros in VMs and laptops that I don't use a whole lot over the years. I recently moved my main desktop to Bazzite and I love it. The built-in 'ujust' scripts, or whatever you call them, are fantastic. Setting up an 8bitdo pro 2 was a breeze. Getting new apps installed, even with distrobox, is really easy. I'm sold on ublue, probably going to move my work laptop to Aurora soon.

  • It's been a few years, but back when I was using crappier hardware I restored from a backup a few times. From a quick glance of the docs, it sounds like it's the same as what I remember. So yeah, just make sure you've got a good, recent backup, then give it a whirl. If anything goes wrong you could always wipe the new machine and start again, and/or roll back to your current hardware.

    I don't know a lot about HA green/yellow, but from a very quick glance, I would be surprised if you couldn't find a little miniPC for less. Especially with lots of people getting rid of computers because of the whole Windows 11 thing. That way you wouldn't be paying for any built in radios and you could spring for their new z-wave radio.

    Other benefits of going to an actual PC would be running something like proxmox, then running HA in a VM. That's what I'm doing and I love it, especially with scripts from this site. I especially like separating things like z-wave and zigbee from HA, that way a HA reboot takes less time and the z-wave network doesn't go down.

    Whatever way you decide to go, there's a lot of different ways to peel this potato. You could even just get a new SD card and keep it as a spare, then setup backups to automatically be uploaded somewhere else and restore to that spare SD card if you have a failure, that could be the path of least resistance.

  • You've shared nothing to make me think anything other than this accusation being projection.

  • Your first link:

    "supports 500 series](https://support.shopyalehome.com/yale-assure-lock-2-with-wi-fi-faq-B1q1o8M5q)"

    It has wi-fi in the URL.

    The title at the top of that page is:

    "FAQ: Yale Assure Lock 2 with Wi-Fi"

    And we know that it comes with a WiFi module because of this question from your same link:

    "Do I need a Yale Connect Wi-Fi Bridge?

    Because it has a Wi-Fi Smart Module, the Assure Lock 2 does not require a Wi-Fi bridge."

    Notice how they put in the "ZW2" module part number in that last question? To get one of their locks to work with Z-wave you have to take out the WiFi module and put in a Z-wave module.

  • homeassistant @lemmy.world

    Tracking the temperature drop during the eclipse with Home Assistant!

  • homeassistant @lemmy.world

    Cloud services for controlling things inside your house are the worst

    github.com /home-assistant/core/issues/99947
  • homeassistant @lemmy.world

    The ratgdo local-only replacement for myQ is fantastically easy to setup

    paulwieland.github.io /ratgdo/