New answers tagged

1

I use a combination of Belkin/Wemo and other devices that are inexpensive and have had the same issues. My solution was to flash them with Tasmota: https://tasmota.github.io/docs/. This fixed my issue with them being unresponsive but of course, I broke the vendor cloud connection. My solution was to use homeassistant: https://www.home-assistant.io/ to manage ...


0

Adding to hardillb's answer... I don't know exactly what device you have, but you could consider the simple workaround of an external keyboard. If your devices have USB / microUSB port, you can get a single keyboard relatively cheap that you can plug in long enough to set up the WiFi connection. If the devices don't have USB, you could also attempt pairing ...


1

Yes, it's a perfectly valid approach that is used by many different IoT devices. One I've implemented more than once, bur here is an example that uses WebBluetooth so you don't even need a native client on the phone/laptop (but you do need Chrome) https://www.hardill.me.uk/wordpress/2016/09/13/provisioning-wifi-iot-devices/ https://github.com/hardillb/wifi-...


0

The answer to point one is because it's more efficient and cost. Mesh devices already have at least 2 radios, one to talk to clients and one to talk to other mesh nodes, the master node would then require a 3rd to talk to an existing Wi-Fi router as back haul. This also leads to more spectrum channels being used which at 2.4Ghz was a problem as there are ...


2

If your cable modem has an open ethernet port you will be good to go. The nest wifi becomes the router/mesh network so if you have a modem/router combo you may need to put it in bridge mode.


Top 50 recent answers are included