11–20 of 256 posts
I'm not opposed to smart homes, I love being able to turn my lights on and off from across the room. But I don't know if I understand the use case for a networked washing machine.
I'm not opposed to smart homes, I love being able to turn my lights on and off from across the room. But I don't know if I understand the use case for a networked washing machine.
Earlier quoted context omitted.
It shouldn't even need internet access. IoT is a stupid name. It's just networking.
Uhhh, alright. Anyhow, many devices require network access for useful functionality. That network is ideally zigbee. (It's also possible for Bluetooth to make up for some of the lost featureset for non-realtime applications, so I'd favor Bluetooth smart devices over wifi smart devices.)
I'm not opposed to smart homes, I love being able to turn my lights on and off from across the room. But I don't know if I understand the use case for a networked washing machine.
It's apparently possible to track a washing machine's progress with a smart switch that monitors power draw; I've got one lying around so might try to implement that soon, to complement my hacky RPi-Ring-doorbell-announcer :)
> In a follow-up post a day after his initial Tweet, Johnie noted “inaccuracy in the ASUS router tool.” Other LG smart washing machine users showed device data use from their apps. It turns out that these appliances more typically use less than 1MB per day.
> In a follow-up post a day after his initial Tweet, Johnie noted “inaccuracy in the ASUS router tool.” Other LG smart washing machine users showed device data use from their apps. It turns out that these appliances more typically use less than 1MB per day.
Are people so uncomfortable saying "we don't know" that they use such loose reasoning to "get the answer"?
I'll re-read the article/tweets, maybe I missed something.
A couple of notes: 1. If you must have an IoT device, favor zigbee. 2. Put your IoT devices on a segmented network that you've throttled. IoT devices neither need nor deserve privileged network access. 3. Probably don't use a consumer grade router if you know how to monitor network traffic. 4. That all being said, it feels unlikely that an IoT device would be exposed on a properly configured router to anything beyond…
1. Z-wave is better, but Wifi can be fine in the right environment. Like, my weather station uses Wifi because it sends a few bytes of data to a server once a minute. No need for an additional protocol going on that interferes with everything else on 2.4GHz anyway. I also use Wifi for a sensor I put in my box that stores 3D printer filament to measure its humidity, so I know when to recharge the desiccant. An ESP32 wakes up every half hour, measures the humidity, and sends it over HTTPS to an InfluxDB instance in "the cloud". Its tiny lithium polymer battery lasts a year. It took me maybe an hour to design the hardware and write the software for it. Why do anything more complicated? Why bother with an esoteric protocol when you just want to use the Internet?
3. Consumer grade routers are great these days. I have a 10G WAN, 10G LAN, and Wifi6e on the router that Verizon provides with my service for free. To buy something like that myself, I'd be spending 700 or 800 dollars so that I can pretend to be a sysadmin on my day off. Why bother?