I simply won’t install anything that doesn’t support a local API. Happy to pay for the hardware; but if your plan is to monetize it via cloud services somehow, or just assume planned obsolescence, I’m not your customer.
If your device requires, in any way, an internet or cloud connection, even just for setup, it doesn't exist for me. If you have some FULLY OPTIONAL services I might like as a SAAS free or subscription option, ok; but the device MUST 100% work without ever knowing your cloud exists. It must also be designed to fail-safe and have manual fall-back operability (e.g., when the power goes out, I can still manually switch its state to OFF).
I recall an article or comment on HN talking about the advantages of a "MidWit Home", devices that weren't really smart, and just had remote control. I've got a bit of that with some remote switches to use around the house with enough range we can turn on from the car when arriving home. Also timers. Seems like a good way to go.
Even with local API I'm quite a bit hesitant, I'd rather not use anything that does not let me install an opensource firmware (e.g. wled for RGBCCT led strip controller).
I haven't made a vlan yet for IoT stuff because my ISP's router do not let me, I can't wait to have my own openwrt / opnsense router and put the ISP in bridge mode.
I've seen people suggest that instead of bridge mode go ahead and leave the ISP router in router mode, with wifi turned off, with your own router as the only device connected. Give your router a static IP on the ISP router's LAN and set it up on the ISP router as the DMZ.
That advantage of this is that some ISPs will try to blame your router (and your modem if you are using your own modem) for any problem you call in about no matter how obviously it is a problem on their end or with their equipment. This way it is not obvious to the tier 1 tech support people that you are using a different router.
I suppose if you want to be really thorough leave the wifi on, either with whatever the default network names the ISP router starts with or with names that don't match the ones you really use which are on your router.
Great to know but that will result in double NAT. Tbf my ISP (Free / iliad) is quite good and pretty friendly so I probably wont have issues (i've never had to call them in like 6-8 years)
kashunstva · · focus · HN ↗
toss1 · · focus · HN ↗
If your device requires, in any way, an internet or cloud connection, even just for setup, it doesn't exist for me. If you have some FULLY OPTIONAL services I might like as a SAAS free or subscription option, ok; but the device MUST 100% work without ever knowing your cloud exists. It must also be designed to fail-safe and have manual fall-back operability (e.g., when the power goes out, I can still manually switch its state to OFF).
I recall an article or comment on HN talking about the advantages of a "MidWit Home", devices that weren't really smart, and just had remote control. I've got a bit of that with some remote switches to use around the house with enough range we can turn on from the car when arriving home. Also timers. Seems like a good way to go.
Oxodao · · focus · HN ↗
I haven't made a vlan yet for IoT stuff because my ISP's router do not let me, I can't wait to have my own openwrt / opnsense router and put the ISP in bridge mode.
tzs · · focus · HN ↗
That advantage of this is that some ISPs will try to blame your router (and your modem if you are using your own modem) for any problem you call in about no matter how obviously it is a problem on their end or with their equipment. This way it is not obvious to the tier 1 tech support people that you are using a different router.
I suppose if you want to be really thorough leave the wifi on, either with whatever the default network names the ISP router starts with or with names that don't match the ones you really use which are on your router.
Oxodao · · focus · HN ↗
amelius · · focus · HN ↗