Apologies for the delayed response. I still plan to support the app, but I’ve been tied up with personal matters and haven’t had the chance to actively review reported issues or crashes. I expect to have more time later this month once some home renovations are completed, and I’ll make sure to look into it then. Thanks for your patience!
Hi @Erikvl87,
I’m using your app too. With Homey 12.4.3 and app version 2.0.0 I found a high memory consumption for your app:
I defined only 4 virtual devices with your app. But the app ist a top consumer for memory in Homey. Maybe you have an idea, why this happen.
Greetings,
David
Hi @dferch, the amount of (virtual) devices will probably not impact memory consumption significantly.
The main culprit is probably (I need to verify this) the build-in cache of all zones (and its metadata). This is used to increase performance, with unfortunately a (maybe to significant) memory penalty. The app condition cards need to be able to quickly get zone information, hence this is all cached into memory.
I’ll test some ideas that I have to bring down the memory footprint.
1 Like
@Erikvl87
I created an extensive tutorial on how to use your app together with actual PIR Motion sensor to get full control over Zone Activity in the Flow section of the Forum. I hope you and many others will find it useful.
2 Likes
That’s a really extensive tutorial! Great that you’ve discovered the potential of the app’s virtual device capabilities! I should’ve put more effort into this app (and its documentation) but I’m glad it still turned out to be useful. In a next update I’ll do my best to put some documentation online and refer to your tutorial as well.
1 Like
Released version 2.1.0
I’ve fixed an issue with the AND-card that checks a zone’s active state. Previously, when a zone had multiple devices contributing to the zone’s active state, the card could incorrectly report that the zone wasn’t active for the required number of minutes because it used the most recent activation timestamp instead of the oldest one. This is now resolved, and zone active checks should be accurate.
1 Like
Hi!
First of all, I want to say that this is a fantastic and much-needed app – thank you for creating it. I rely on it heavily, and it plays a key role in many of my Homey automations.
Since the latest update, the card “The zone XY is inactive for at least X minutes” no longer seems to work correctly.
Problem description:
The card becomes true even if the zone was active just a few seconds ago.
Example:
• Zone: Living Room
• Condition: inactive for at least 3 minutes
Even when the zone had activity a few seconds earlier, the condition still evaluates to true, as if the inactivity timer was not respected.
Because of this issue, many of my automations no longer work as intended. This is unfortunate, as I really love the app and use it extensively.
Could you please look into this?
Thanks again for this great and very useful app! 
Hi Rasket!
Great to hear you like the app! And with that said, unfortunate that it doesn’t seem to work as intended anymore since the latest update.
Could you, directly after this issue of a wrong trigger happens, send me a diagnostics report?
And I would be interested to learn if your zones affected by this bug have subzones.
You can create a diagnostics report as follows: In the Homey app → More → Apps → Zone Activity → 
-> Make diagnostic report. Make sure to copy the report ID and please share with me the report ID, the zone name and the time when the issue occurred.
You can share this via a private message if you’d like.
Thanks!
Released version 2.1.1
I’ve fixed an issue with the AND-card when specifically checking for a zone’s inactive state, which always returned true.
@Rasket787 This should fix the issue you reported.
Thank you very much for the quick fix.
I’ve tested it, and everything works perfectly now — the zone inactivity is handled correctly.
Thanks again for this excellent app!
1 Like
