I’m just getting into home automation, so I don’t really know what I’m doing. I care a lot about supporting open standards (which is partly why I never bothered with it until now that Matter is coming out), but I also very much like the idea of having everything I own running Open Source firmware instead of whatever potentially untrustworthy stuff it comes with.

So anyway, I got some TP-Link Kasa smart plugs (KP125MP2), but have since been doing some more research and found that some folks don’t think there’s actually much, if any, advantage to Matter devices compared to older wi-fi devices that’ve been flashed with Tasmota or ESPHome. So now I’ve also got some Sonoff S31 smart plugs and a USB to serial adapter to flash them with, and I’m wondering which set of things I should actually keep.

I kinda feel like I need to try installing and using them to know which I prefer, but I’d also feel bad about returning stuff after it’s got provisioning info stored on it (or worse, flashed firmware). So maybe I can decide based on advice y’all give me instead?

  • troplin
    1•1 year ago

    These are Matter/Wi-fi devices, not Matter/Thread devices, so I don’t think that part applies?

    No, this is a property of Thread and not limited to Matter devices. For example you can mix Thread/HomeKit devices with Thread/Matter devices in the same Thread mesh.

    Only wired devices act as range extenders though, like smart plugs or outlets.

    • @grueOPEnglish
      2•1 year ago

      I think I’m confused about a different aspect of it than you think I’m confused about. I was under the impression that my KP125M Matter smart plug wouldn’t be able to communicate directly with Thread devices (Matter or otherwise) because it didn’t have the right kind of transceiver. On the side of the box it says it supports 802.11b/g/n along with bluetooth 4.2 for onboarding, which are not the same thing as the (checks Wikipedia) 802.15.4 that Thread apparently uses. Are you suggesting that my understanding is wrong, and that my KP125M would function as a Thread “Border Router” even though such functionality is advertised nowhere on the box or product webpage?

      I wasn’t even thinking about Thread <-> Thread interoperability between devices using different higher-level protocols. I don’t think that will, err, matter to me much since I don’t plan to get any Thread/HomeKit (etc.) devices, but it’s neat to know!