New device type "Channel" (IFFFT replacement)

I think it would be a good idea to integrate a new kind of object to get the functionality of IFTTT channels. The new object should offer a possibility to connect directly to a "channel" (e.g. google calendar). So it is not necessary any more to use the detour via IFFFT. You can define a rule directly on your zipabox that is triggered via the connected channel.

Privacy

It's also a matter of security because you don't have to paste your secret information of your home automation system to another plattform as IFTTT.com

Suggestion

I suggest to implement this like the virtual devices. So a new entry called "Channel" would appear when adding a new device (Analogue to "Z-Wave", "Virtual device" etc.).

The channels could be extended step by step by new channel classes. First of all I would like to have a channel class "Google calendar". This can easily be integrated by the google API.

In the device list a new entry "Channel objects" as heading will be shown after adding the first channel object. The added channel object will appear below the heading (analogue to Virtual network devices).

Maybe the name channel object is not that good. Trigger object would also be a possible name. But based on the IFFFT wording channel will express what is meant.

Usage

You can add the channel object like sensor objects. But you don't have to adjust a value. The when block that uses the channel object triggers when the connected channel event is defined to trigger.