2 ms·

I'm on IPV4. It's not about how many IP addresses I have available, it's that all those smart devices can pollute the list of devices connected my wifi network.

I'm on IPV4. It's not about how many IP addresses I have available, it's that all those smart devices can pollute the list of devices connected my wifi network. I like to know what's on my wifi network, and because my memory isn't what it's used to be, I find myself having to assign names to all the smart wifi devices in my Unifi controller.

oflannabhra 7y ago
A common solution (and one HomeKit enabled routers implement) is to relegate all IoT products to their own network
- slantyyz 7y ago
  Sure, but I would still want to check that network's clients as well, so I would still want to identify the devices on that network to ensure that only my devices are on it. Either way, it's still an additional step compared to Z-wave. Other than the hub, I don't need to set up an IP network for my Z-wave devices to connect to at all.
  - ViViDboarder 7y ago
    I mean, I’m using Z-wave too, but you’re describing the same level of complexity. Either you set up a dedicated WiFi network and check that to see the status of IoT devices, or set up a dedicated Z-wave network and check that for the status of devices.
    - slantyyz 7y ago
      For a z-wave device to pair to my hub, I need to put the hub itself in pairing mode. Unlike wifi devices, a zwave device can't just join my hub by knowing an SSID and password. Yes, I could do something similar with a wifi network and whitelisting mac addresses etc, but that's not nearly as simple as the way z-wave works. [addendum] When I talk about checking my network, I'm also not talking about status. With wifi, I'm checking to look for unexpected clients. I occasionally have a temporary freakout when I see an unknown device on my wifi that ended up being something that I bought, added and forgot about (like a media player), etc. That's not a concern I ever have with a z-wave network.

oflannabhra 7y ago

A common solution (and one HomeKit enabled routers implement) is to relegate all IoT products to their own network

slantyyz 7y ago
Sure, but I would still want to check that network's clients as well, so I would still want to identify the devices on that network to ensure that only my devices are on it. Either way, it's still an additional step compared to Z-wave. Other than the hub, I don't need to set up an IP network for my Z-wave devices to connect to at all.
- ViViDboarder 7y ago
  I mean, I’m using Z-wave too, but you’re describing the same level of complexity. Either you set up a dedicated WiFi network and check that to see the status of IoT devices, or set up a dedicated Z-wave network and check that for the status of devices.
  - slantyyz 7y ago
    For a z-wave device to pair to my hub, I need to put the hub itself in pairing mode. Unlike wifi devices, a zwave device can't just join my hub by knowing an SSID and password. Yes, I could do something similar with a wifi network and whitelisting mac addresses etc, but that's not nearly as simple as the way z-wave works. [addendum] When I talk about checking my network, I'm also not talking about status. With wifi, I'm checking to look for unexpected clients. I occasionally have a temporary freakout when I see an unknown device on my wifi that ended up being something that I bought, added and forgot about (like a media player), etc. That's not a concern I ever have with a z-wave network.