Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
i still think IP based smart home kit is a mistake. The internet is already such a big vuln, we don't need a shit ton of garbage sitting on the network only making it more vulnerable.
communication standards like zwave, and zigbee, are preferable here. It looks like at least one of those supports it, but perhaps both will be protocol agnostic.
Think of Thread as Zigbee with an IPv6 stack. It’s a local communication standard but with a compatible protocol.
I was excited that my current phone has a Thread radio so it can be on the local network for presence and control. Unfortunately not supported yet.
I’m definitely worried about the recent Matter standard for internet access. They say it’s optional, but that capability is easily hijacked by unscrupulous vendors.
it's definitely cool that we have the capability of things like thread/matter zigbee and zwave now.
I would be more ok with local IoT devices being IP based if they were intended on being used with an "offline" network. Though that's a little funky to setup, and causes interference issues, so i think i prefer the zigbee and zwave solution of using a different protocol entirely, especially since it mandates offline handling.
My two biggest concerns with IP connected devices are most home networks are not properly delegated, so people aren't creating a second subnet specifically for IoT devices for example, and they most definitely aren't properly providing access controls through that network as well. So if someone manages to get into one of the devices, you basically have the entire network at that point.
One of the big advantages of non IP based systems is that you have a "point of relay" or gateway between all of your IoT devices and your network, which becomes the attack vector, making it a lot easier to secure, and manage. Even if you managed to hack into a zwave/zigbee network, it would only be locally, and IoT devices only, so it's not going to be hugely problematic.
theoretically you can do all of this on a traditional IP based network, i just don't think it's the correct approach. Sort of like making a carboat, or a boatcar. You could, but why?
I think at minimum, a standalone IoT device should not be capable of connecting to the global internet, period. Through something like a gateway or "point of relay" sure, that's fine by me, but even then i would prefer open standards and documentation on that specific feature set.
You may be misunderstanding my description a bit. Think of Thread as Zigbee 2.0. It’s not, but that’s a useful way of thinking of it. It’s a_local_ mesh network just like Zigbee, even using the same frequency. The protocol stack is different: it’s IPv6 for capability, but completely separate from your Ethernet/wifi. There is no online requirement, at least from the standard.
Matter is Ethernet/WiFi based and can act as a gateway for Thread, but theirs is no online requirement, at least from the standard.
But yes, companies will ignorantly or willfully violate things like that. My most recent example is effing Netgear. I didn’t think I had to ask whether my new router’s “separate IoT network” was actually separate. I set up a different ssid, configured it to 2.4GHz only, separate password …. WTF, it’s on the same network with no separation? How is that even a useful thing?