{"action":"created","issue":{"url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/28","repository_url":"https://api.github.com/repos/daneedk/com.uc.heimdall","labels_url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/28/comments","events_url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/28/events","html_url":"https://github.com/daneedk/com.uc.heimdall/issues/28","id":374388180,"node_id":"MDU6SXNzdWUzNzQzODgxODA=","number":28,"title":"\"No Information Received\" into AND column?","user":{"login":"vaderag","id":17175988,"node_id":"MDQ6VXNlcjE3MTc1OTg4","avatar_url":"https://avatars0.githubusercontent.com/u/17175988?v=4","gravatar_id":"","url":"https://api.github.com/users/vaderag","html_url":"https://github.com/vaderag","followers_url":"https://api.github.com/users/vaderag/followers","following_url":"https://api.github.com/users/vaderag/following{/other_user}","gists_url":"https://api.github.com/users/vaderag/gists{/gist_id}","starred_url":"https://api.github.com/users/vaderag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vaderag/subscriptions","organizations_url":"https://api.github.com/users/vaderag/orgs","repos_url":"https://api.github.com/users/vaderag/repos","events_url":"https://api.github.com/users/vaderag/events{/privacy}","received_events_url":"https://api.github.com/users/vaderag/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-26T13:38:45Z","updated_at":"2018-10-27T12:34:04Z","closed_at":null,"author_association":"NONE","body":"Would there be a possibility of sticking the “No Information Received” card in the And column?\r\n\r\nReason being I’d like to do something like:\r\nWhen the time is 7.30pm, and No Information Received and Last Update 24hours and device is not xyz, then send an alert\r\n\r\nBasically, so I can get the alerts at the same time every day, when I generally have some way of actioning it?"},"comment":{"url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/comments/433616569","html_url":"https://github.com/daneedk/com.uc.heimdall/issues/28#issuecomment-433616569","issue_url":"https://api.github.com/repos/daneedk/com.uc.heimdall/issues/28","id":433616569,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMzYxNjU2OQ==","user":{"login":"daneedk","id":16610696,"node_id":"MDQ6VXNlcjE2NjEwNjk2","avatar_url":"https://avatars2.githubusercontent.com/u/16610696?v=4","gravatar_id":"","url":"https://api.github.com/users/daneedk","html_url":"https://github.com/daneedk","followers_url":"https://api.github.com/users/daneedk/followers","following_url":"https://api.github.com/users/daneedk/following{/other_user}","gists_url":"https://api.github.com/users/daneedk/gists{/gist_id}","starred_url":"https://api.github.com/users/daneedk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daneedk/subscriptions","organizations_url":"https://api.github.com/users/daneedk/orgs","repos_url":"https://api.github.com/users/daneedk/repos","events_url":"https://api.github.com/users/daneedk/events{/privacy}","received_events_url":"https://api.github.com/users/daneedk/received_events","type":"User","site_admin":false},"created_at":"2018-10-27T12:34:04Z","updated_at":"2018-10-27T12:34:04Z","author_association":"OWNER","body":"I've looked into this and brainstormed on how to best implement this. Adding a condition card is not the way I want to go, that would require quite a large change in Heimdall and would also not scale well when there are a lot of devices connected to Homey. \r\n\r\nSo I decided to go for an action card that would enable you the run the **Check Last Communication** function at your desired condition in the same way it is now run at setting a **Surveillance Mode**.\r\nThat will result in the same action that's already in place in **Heimdall** so writing a line to the history and triggering a flowcard.\r\n\r\nSo basically if you have this flow now, that gets triggered at setting the **Surveillance Mode**: \r\n![image](https://user-images.githubusercontent.com/16610696/47604013-4e144900-d9f4-11e8-8934-75c5baca9c36.png)\r\n\r\nYou will be able to trigger it with this new flow using the new **Check Last Communication** card:\r\n![image](https://user-images.githubusercontent.com/16610696/47604049-a3505a80-d9f4-11e8-82e7-3450c46c590d.png)\r\n\r\nThis new flow card will be available in version 1.0.26.\r\n(Current version is 1.0.24, version 1.0.25 is pending approval by Athom)\r\n"}}
{"actor":{"display_login":"daneedk"}}