CondorWonder

Matter devices should be able to use your current wifi if that’s their network. Otherwise it would use thread similar to Zigbee. I’ve only looked at the ZBT2 as a thread router for connectivity to home assistant so I don’t have a lot of experience here yet with thread but I’ve been using Zigbee for years. Yes thread or Zigbee can interfere with 2.4ghz wifi as they’re in the same band, but my experience is the opposite: wifi has a bigger effect on them then they do on wifi. Zigbee and thread are designed for low power devices so they’re easy to drown out.

I don’t know if there’s a feature difference but I don’t think there should be. I’ve used matter devices on my wifi with no issues and didn’t need a separate router, and when I pick up a thread device I’ll use a zbt2 as the hub.

I’ve done a couple of cross continent moves now with movers moving my stuff, and most things were fine - drives if they’re powered down are generally safe. The only thing that has happened is my graphics card power cable had worked itself loose and the card burned out because of it. CPU fans, hard drives, power supplies were all fine.

I’d say after you get to your destination check all the things - especially cables would have saved me a 1080 (it worked for over a year so it really wasn’t obvious from a visual inspection).

Journiv, first featured here at https://lemmy.ca/post/55005402 might be what you’re looking for as a self hosted solution

Ah right, I misread that chart as manufacturer not integration and didn’t really look at the details. That does seem odd that Tuya is that prevalent, they don’t seem that common on troubleshooting boards which I’d expect if they were used that much. I wonder how much self selection is happening here in the labs project and how much it will change when it’s opened to the community.

Does this Tuya include Zigbee devices? I don’t have any wifi based Tuya devices but it’s surprising how many generic cheap Zigbee sensors are Tuya.

Roughly 1/3 of my Zigbee devices are Tuya branded, if you buy from AliExpress it’s a strong possibility.

ddrescue doesn’t work properly on audio discs (even if you use the correct sector size of 2048 bytes). Have you tried something like cdparanoia https://www.xiph.org/paranoia/?

Not sure what you mean by this - Nabu Casa has a Zwave device already called ZWA-2 which is fully supported.

A strong mesh is a better way to go to me - ensuring you have a mesh of router devies between the coordinator and the end device has worked well to ensure that no matter where the device is it works. A better antenna may help but all it takes is a glitch like your 2.4 wifi moving to overlap with the Zigbee range and the device drops out.

I have a tubesb Zigbee device with an external antenna and I’m not sure I’ll benefit from the ZBT2 but the 2.4ghz band is very busy here. I’m tempted to try it and see if it makes any difference. I find my Zigbee network ‘slow’ - like sensor updates take 1-2 seconds before HA receives them.

Bcache can’t differentiate between data and metadata on the cache drive (it’s block level caching), so if something happens to a write-back cache device you lose data, and possibly the entire array. I wouldn’t use bcache (or zfs caching) without mirrored devices personally to ensure resiliency of the array. I don’t know if zfs is smarter - presumably is can be because it’s in control of the raw disks, I just didn’t want to deal with modules.

For your second scenario - yes you can use md under bcache with no issues. It becomes more to configure but once set up has been solid. I actually do md/raid1 - luks - bcache - btrfs layers for the SSD cache disks, where the data drives just use luks - bcache - btrfs. Keep in mind that with bcache if you lose a cache disk you can’t mount - and of course if you’re doing write-back caching then the array is also lost. With write-through caching you can force disconnect the cache disk and mount the disks.

This. If you have any sort of set up - just do a backup and restore. All the configuration, automations, etc. will come across exactly as it was, including your subscription set up.

I’ve migrated from a Pi to a mini pc so it works between different platforms too - there I had to reinstall add ons but it was still generally an easy migration.

I work around this with the uptime integration then conditions in automations that uptime must be over whatever time I want.

You could try using not_from in your state trigger but I’ve had limited success with that working recently. Something like this:

#…
  - trigger: state
    entity_id:
      - event.inovelli_on_off_switch_config
    not_from:
      - unavailable
      - unknown
#…