Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No Information Received" into AND column? #28

Closed
vaderag opened this Issue Oct 26, 2018 · 5 comments

Comments

Projects
None yet
2 participants
@vaderag
Copy link

commented Oct 26, 2018

Would there be a possibility of sticking the “No Information Received” card in the And column?

Reason being I’d like to do something like:
When the time is 7.30pm, and No Information Received and Last Update 24hours and device is not xyz, then send an alert

Basically, so I can get the alerts at the same time every day, when I generally have some way of actioning it?

@daneedk

This comment has been minimized.

Copy link
Owner

commented Oct 27, 2018

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.

So 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.
That will result in the same action that's already in place in Heimdall so writing a line to the history and triggering a flowcard.

So basically if you have this flow now, that gets triggered at setting the Surveillance Mode:
image

You will be able to trigger it with this new flow using the new Check Last Communication card:
image

This new flow card will be available in version 1.0.26.
(Current version is 1.0.24, version 1.0.25 is pending approval by Athom)

@daneedk

This comment has been minimized.

Copy link
Owner

commented Nov 5, 2018

While testing over a longer period I discovered a nasty bug in the communication check which I want to fix before releasing this flowcard.

@daneedk

This comment has been minimized.

Copy link
Owner

commented Nov 20, 2018

I've created a bug report with Athom but no response yet...
athombv/homey#2917

@daneedk

This comment has been minimized.

Copy link
Owner

commented Dec 27, 2018

At releasing Homey V2 (RC) firmware Athom has made their repository to submit bugs read-only. I am not expecting Athom to fix this for the 1.5.13 firmware as Emile also said the (now old) api was beta and unsupported anyway.
When V2 matures I'll make sure I will test this functionality.

@daneedk

This comment has been minimized.

Copy link
Owner

commented Jan 11, 2019

During some testing this function seems to work good on V2 and the bug that seems to be in 1.5.13 seems to be absent in 2.0.

This function can be started in 2 ways: By setting the Surveillance Mode or by using the action card Check Last Communication.
When the function is executed the result will be written to the History and to the Timeline (optional).
Also the trigger card No information received card is triggered with the tags Hours no information, Last Update, Device and Zone so you can use a method of your choice to inform you.

@daneedk daneedk closed this Jan 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.