this post was submitted on 24 Nov 2023
1 points (100.0% liked)
Home Automation
79 readers
2 users here now
Home automation is the residential extension of building automation.
It is automation of the home, housework or household activity.
Home automation may include centralized control of lighting, HVAC (heating, ventilation and air conditioning), appliances, security locks of gates and doors and other systems, to provide improved convenience, comfort, energy efficiency and security.
Warning: Working with electricity can result in injury, property damage, or even death if it is not done properly. Please keep this in mind while assisting others. If you are not sure about what you are doing, hire a licensed professional.
Rules
- No abusive behaviour. This is a forum for friendly discussion; personal attacks will not be tolerated and you will be banned without warning.
- Referral/affiliate links are NOT ALLOWED!
- NO POLITICS! There are plenty of other communities to discuss them; this is not one.
- When posting project details must be included. Posting a video or image without detail will result in a removed post and may result in a ban.
- Crowdfunding links are not allowed.
- Reposts, low-effort content and karma farming may be removed at the discretion of the mods. Posters may be banned without warning.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Latency is that wifi devices don't typically talk to each other and have to go out the the cloud and back again, that's everything from the fairly minor network latency to processing to various polling etc times all put together. It's not the medium rather the protocol thats running over it.
Z-wave is a lot slower but the latency between pressing a button and the light turning on far lower than your random wifi with a phone app and cloud junk. This is a function of the protocol used not the medium it's working over.
He's already using kasa locally with HA, cloud latency isn't the issue. It's that the kasa API needs local polling (not the best design). A wifi IoT network (that's been configured properly) with proper devices that notify on state change will always be faster than slower networks like zwave and zigbee.
Only if they have a device to device communication channel that most wifi devices lack. Like I said the problem is not the medium but the protocol design. Wifi's orders of magnitude faster throughput does not fix a bad protocol.
The original suggestion was that it was a wifi latency problem. It's not, there is no perceivable latency due to using wifi. And it's not cloud, this is a local API.
Kasa picked a poor implementation - there is indeed a TCP protocol standard available (UPNP/SSDP) that works very well over wifi and includes device to device eventing. Most devices, including kasa, don't implement it - that's a manufacturer failing. Don't buy those, or at least buy the ones with a local API that will work with HA (et al).
Yes, zwave has a (expensive) way to solve it by building a redundant network. Most IoT users already have house wide wifi, and many already have a automation/consolidation hub like HA to work around the mismatched API. Zigbee works too, so does wifi if you pick the right devices.
Your fixated on wifi throughput. That's what I originally said, it's a protocol issue typical of wifi devices. Not that you can't get wifi to work well rather that IoT over wifi tend to be implemented badly.
Again, the problem is not Wi-Fi or that the devices use Wi-Fi to communicate. The problem is the protocol that they are communicating with. You can't immediately say that any Wi-Fi smart home device is inherently bad just because it uses Wi-Fi. Wi-Fi is synonymous with cloud control, but more and more products are including Wi-Fi and local control, including some official standards like matter and MQTT.