Feedback-- There's a lot of potential to create virtual doorbell buttons that drive Alexa smart home automations via outside weather events. Alexa doesn't support weather triggers which is a significant omission. My use case is primarily weather triggered events such as wind over a certain speed to retract an outdoor awning (bond hub controlling somfy awning) or weather below freezing to enable a smart plug for pipe heat tape on pipes subject to freezing in an attic. With the free account limit, I can't do both of these simple tasks using a single common applet Mkzense. This would require 3 triggers, one to close the awning, one to turn on the heat tape at 32f and one to turn off the heat tape at 34f. Can't be done with Ifttt free account even though it creates 3 virtual buttons when linked to Alexa.1) why have three virtual buttons by default in alexa when the effective limit is two triggers? with their nomenclature, any trigger you create becomes a new applet even if they share the same common applet. As soon as you enable/link Ifttt to alexa, it has you name 3 virtual buttons. This implies that the minimum account should support this, but that would assume a level of thinking that has left the building. Good luck using them as Mkzense now limits you to 2 virtual triggers. Very confusing and shows the roadmap to monetization hasn't involved much thought.2) Inability to delete applet triggers (Mkzense). As soon as you add 2, the service is grayed out. The only way to add new triggers is to "Archive" them. Even when you archive, sometimes it takes the website time to un-gray the applet. Is this intentional to strong arm subscriptions?3) Inability to edit trigger actions other than the name unless you create it from scratch or restore from archive. can't edit an active trigger in mkzense. the only edit field is for the title of the trigger. You have to archive the trigger, then once you reenable it suddenly there is a one-time ability to edit the action. you could get around this by creating a new trigger but you will be blocked from doing so because of the 2 applet limit. why so kludgy? very tedious4) mkzense wu underground defaults to some random address in california. i had a wind event triggering my awning at 5:21 am because there was wind at the developer's house lol. locally it was dead calm. location services are enabled on my device. of course, i couldn't edit the address field without first archiving, then re-enabling the trigger. every time i want to change mph, i have to archive and re-enable or archive and create a new trigger from scratch. if you make the mistake of publishing, you likely can't delete and then you are sol with the 2 applet limit. Hasty monetization without any consideration for who will actually use this.5) The 2 applet limit (free service) isn't just restrictive of applets but it also applies to triggers. You could have one applet (mkzense) but each trigger counts against the 2 limit. Since most automations have a separate trigger for 'on' and a separate trigger for 'off,' this is basically limited to one solitary device. It's not even enough access to validate its usefulness.
