This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed
Improved actions
I am suggesting to improve action capabilities.
Here is a list
We have two actions:1. Fetch Youtube video
Here is a list
- async parallel & sequential actions
- sorting of conditions & actions
- action tokens (output for input of next action)
- complex condition logic (and/or/nested)
- add token types (text, number, url, email...)
- new argument types (eg url, email), useful for validation feedback
Example: Play youtube video on chromecast
We have two actions:
- which can be auto complete preselected video
- live search from query token or text
- random from playlist
- etc.
2. Play any supported media on chromecast (it has one argument: URL) in our example token from Youtube action
Actions are async & sequental.
We've built something similar at Celtra.
Take a look at video and seek to 3:20 where you can see events and actions.
https://vimeo.com/35588252
https://vimeo.com/35588252
You can have multiple events and multiple actions for each event.
Actions are async and can execute in mixed order of parallel & sequence.
Some actions can have nested actions (actually core parallel & sequential are actions with nested actions)
With this concepts we get very powerful tool to build complex flows.
Some actions can have nested actions (actually core parallel & sequential are actions with nested actions)
With this concepts we get very powerful tool to build complex flows.
This discussion has been closed.
Comments
"action tokens (output for input of next action)"