Gizmo that remotely turns on house lights.

I am using this device that for the royal amount of $6 including shipping, provides wifi on-off control to anything. You can use it out-of-the-box, but the downside is that they have a clunky app that controls the thing via an AWS server (so that you can control while you are not at home) but is an inconvenience and security risk. The upside to the downside is that you can flash the thing with open-source software and connect it to most any smarthome app.

And since it has a 10A rated relay, you can control loads up to 1.1KW@110V or 2.2KW@220V, which means a whole set of lights.

I’ll admit my laziness and ignorance in this matter. I know that I can use a different subnet to increase my IP space, but it’s never been a concern for me (especially given that I’m not using light bulbs with IP addresses :p).

I’m pretty sophisticated when I need to be, and I’ve been fine with my current internal IP address allocation. I do run Tomato, which is definitely not hard-coded for anything. It’s my DHCP server and set up with custom hostnames and static IP addys for everything I know about (except one device… who the hell is 192.168.1.15? I will track you down!).

Although I’m back in the States and it doesn’t matter, in the past I’ve been able to configure custom IP tables for access using (or not) the VPN (I was in a country that has a grand fire-blocking wall), given that it’s just Linux, too.

The damnable thing is you’ve got my curiosity piqued and now I’ve got to decide if I want to continue down this path or just leave it for now. :frowning:

I have never seen a router that does not allow to change the network address and mask to anything you want. And I’ve seen at least 20 types.

Very cool. It’s like WiFi’s early days. Security always trails behind the rapid pace of innovation, I guess.

Interesting, and thanks. I’ll run this by my husband (who IS an IT security person and in fact got me interested in learning about IoT security issues after the recent DDOS attack).

I don’t see it as being an issue for us any time soon, whatever the options are, as I truly can’t think of any application around the house where remote-controlled lights would be all that useful to us. Of course that may change someday…

Also, routers themselves are good but not perfect, as googling turns up lots of stories of hacked routers.

Huh. My Linksys allows me to set the router’s LAN-side IP address (all octets) and netmask manually. As to the DHCP server, as I mentioned it seems to be restricted, but for me it’s a non-problem since I disable it in the router and run dhcpd on my Linux server. That’s a simple matter of tweaking a text-based config file (/etc/dhcp/dhcpd.conf) and restarting the server program (“service dhcpd restart”).

It’s something each home-network administrator will have to check for themselves if they’re interested.

I just got two “smart outlets” and am using them on my Christmas tree and the fireplace garland. The plugs for both are hard to get to, which makes turning the lights on and off a pain (and yes, I know they’ve had foot controls for trees forever, but you bury that cord under presents, and you’re back to square one).

Anyway, for the time being I named them “garland” and “tree” and put them both in a group, so I can say, “Alexa, turn on the Christmas lights,” and everything lights up in a flash.