I'm not averse to paying more if I get more. A marketing flop depends on the marketing done.
The download counts of my firmwares show that the RT-AC3200 and RT-AC5300 aren't very popular. Those two are actually the most expensive models of their respective generations. Bump their price by another 200$, and you get yourself a commercial flop.
Nobody thought a $1000 'smart phone' would sell just a few short years ago either.
Do you personally know anyone who paid 1000$ for their phone? I don't. The vast majority get it subsidized through their provider at a fraction of that price.
Personally, I think home routers need to go in a different direction:
1) Drop in price. A flagship home router should cap at 200-300$, anything above is enterprise-class, and should have totally different priorities
2) Drop all the USB storage capabilities. Having files stored on your frontline firewall is a security disaster in waiting. It's like keeping the jewelry box right beside your closed window. First thing to go once someone breaks in - those jewelries.
3) A more modular operating system design. The current monolithic design of Asuswrt (and of most other home router firmware) has become unmanageable, as evidenced by the increasing amount of bugs and security holes being discovered each year. Routers should switch to a more server-like software design, with better service isolation.
If I were to design a router firmware from scratch today, there would be zero support for file sharing. No Samba, no FTP, nada. The USB port might still be there and working, but strictly for storing applications that a user might be installing on their router (for instance if they decided to install Snort or MRTG). If you need to move files to/from it, use SCP.
But this is all far away from the original topic of this thread however. Personally, I have little interest in IFTTT. Too many random variables introduced into what is already a difficult to manage setup (having to deal with compatibility issues between wifi device manufacturers, external interference sources, etc...). If on top of that we get event-based triggers, that increases the complexity of troubleshooting by quite a bit.
Personally, a "smart home" architecture should look like this:
1) The modem/ONT, from your ISP
2) A router, doing only routing, filtering, firewalling, traffic monitoring, VPN, and directly related activities
3) A "Smart Hub", which handles your Nest thermostats, Sonos, Z-wave devices, and other IoT devices
4) A NAS, which handles file storage, including cloud sharing
5) Client devices: phone, PCs, HTPCs, IoT devices, etc...
All these five things should be physical separate boxes. Maybe combine modem and router together (not a fan of those combo devices, but a quality one would be acceptable for basic functionality), but that's it. A lot of the workload people are shoveling on the router these days should be off loaded to either the "Smart Hub" or the NAS.
The only reason I keep SMB enabled on my router is for test purposes. The only files there are test files for when I need to test and troubleshoot SMB or DLNA. All my files used to be shared by my desktop, and they are now shared by a NAS.
The IFTTT part should be only on the Smart Hub device.