Zone activity not always working

He Guys,

Since i migrated to the New Homey Pro i experience an issue where a flow using the zone activity not always works. I use the mainly for flows turning the lights on and off.

I have 2 motion sensors in a Room/Zone, i see that they are both activated because of my movement but the lights stay off…
I have not checked if the zone itselfs is active as well, will do that the next time it happens ( but it should be active since a motion sensor triggers an alarm)

Anybody experience the same issue?

It’s not all the time btw…

If you check the “Zone activity” in top of the app, next time it does not work, then you can see if the triggering of the zone or the flow is the issue. I do not have any more suggestion, as i do not have any issues with zone-activity, and have also migrated from a HP, in my case HP19.

Hi @blueboxboz ,
there are many obstacles in Homey Pro.
For better understanding your issue, it would be helpful to get more information.
So the Flow that does not act as expected and somehow some indicators that show that the zone switched from inactive to active, but the flow does not act.

To find out if zone activity is actaully triggering: add a logging card. (App syslog)

You can also add these carss to your current flows to see what happens (and what not)

sometimes when i enter the zone even though it detects motion in that zone the lights stay off. i have to manually turn them on. since it’s working like 8 out of 10 times it’s strange that the other 2 times its not working. @fkey, i will look into it and add a card so i have more insight!

Do you have multiple devices detecting motion in that room?
Not all devices have the correct setting by default: trigger of the device does not trigger motion activity.

I had a door sensor that did not trigger the zone activity.
I thought it was intermittend, but it just never did.
But my motion sensor in the room often triggeren the zone too. So it seemed intermittend

If a device is not triggering the zone correctly you can also build a flow to trigger the zone activity.

I think it was a buggy motion sensor, one of my first ones. I replaced it and since then i no longer had issues. Was a Fibaro motion eye. Thanks guys for helping!:ok_hand:

i experience the same with zone activity.

I have a zones that indicate activity (blue dot).

Then I have in an advanced flow:

  • aa event trigger on zone activity
  • a 1 sec time trigger to check the zone still to be active

in both cases i init a timer to 3600 sec and let it cound down towards zero.

zero would mean no activity for 1 hour, turn lights off.

but while there is zone activity (we’re present) and the zone itself indicates activity (blue dot) the flowcard makes the turn “no zone activity”!?

even if I place a (virtal) “always activity” device in the zone, it just ignores the activit.

I I litterly have to reboot himey to get it bacck to work.

memory is not fully consumed, cpu is about 24%.

Could you share the flow you are talking about (screenshot)?

What might help is instead of both triggers, use the “zone inactive for [number] minutes” card.

I think you want to start a timer when the zone becomes inactive.

And stop the timer when the zone becomes active.

Hi all,

@Anoniemand Here I paste the flow. The card “the zone is active” returns often ‘false’ while the (sub)zone is active. lights turn off after 30min, it never reports the “true” state (until homey reboot). Homey seems to break somehow.

If the power is below 300 and the zone is active you should get every second a notification on your timeline.
If not the power is above 300.

Hi all,

@Anoniemand yeah sorry for that, i made some changes to get the total flow in a descent screenshot. Ignore the timeline notification.

If the power is below 300watts, then the timer is (re) initialized to 30min, and lights are turned on and dimmed accordingly triggered by

  • zone becomes active
  • Every minute the zone is (still) active

Every minute the zone is not active

  • timer will fade out (towards zero)
  • the lights are still processed
  • until the last minute (no light updates anymore)

If counter expires, just turn everything off.

I changed the flow according to your suggestion to use the “when zone inactive for.. minutes”

Hi all,

Since a few days I experience the same but only when a zone comes inactive.
I have a flow to turn my kitchen lights ON when I enter the room; this works properly with the command “When the zone becomes active”. No problems here.

But when I leave the kitchen the command “When the zone becomes INactive” does not work.
Not in an old variant of homeyflow and not in the advanced version.
I disabled the original flow (which worked fine for 3 years till a few days ago) and build this simple
flow to check if there is anything happening:

I DO NOT receive the message on my mobile so my conclusion is that the signal ‘Zone inactive’ is not triggering this flow at all.
Ergo: The card “Zone becomes active” works fine; the card “Zone becomes inactive” is not responding. Already did a PTP two times with no result.
The sensors (2) are not excluded from zoneactivitiy. The sensors are also reporting fine because the bleu dot (activity) of both sensors is going on and off accordingly and also the blue dot for the zonestatus (active/inactive) is going on and off the correct way.

Question is: why is the card “zone inactive” not sending the new status to my flow ?

Any ideas ?
Peter

Shouldn’t you use zone ‘keuken’ instead of zone ‘thuis’?

1 Like

No sorry,
As a test i removed the flow to another zone.
(Excuses voor de verwarring)

Peter

@Wim_Post

I don’t know for shure, but i put (after my tests) the flow back to zone ‘Keuken’ and now it is working fine !!!
Possibly you’re suggestion was right and was the flow placed in the wrong zone.
However; why did it work properly for so long and stopped it working without any changes made ?
(Or did i ‘reset’ something by putting the flow back to ‘keuken’).

However, thanks for your help ! It works again :wink:

Peter

Edit: I think i know what happened after the first tests:
While i was putting everything back as it was, I noticed I almost made the mistake of choosing for the (wrong) zone “Begane grond’ as the zone because ‘Keuken’ is a subzone of “Begane grond’
Because i saw no specific cards under ‘Apparaten’ (resolution of my laptop) I almost choose by mistake the wrong one:

Triggered by youre answer i scrolled the window down and there it was.

I think it became very late last night and let me fooled by the GUI of Homey :wink:

Thanks again !
Peter

Hi peter,

mines also just worked for year(s) and now I have issues with the zones for couple of weeks. Sometimes the active transitions are not triggered and sometimes the inactive zone cards return invalid states (inactive while zone IS active).

Could this be a bug/anomaly introduced in homey with a latesg release?

I cleaned up memory by removing apps and reduced loads by setting timers / intervals longer but in my case this only resolves with a full Homey reboot.

hi, no keuken is the subzone of thuis. Subzone activities are propagated to parent zones, thats the whole point of it. Parent zones are accumulation/aggregation of subzone states like activity, light(s), energy, events, etc.

controls are downsteam. And this worked for months without changes, AND it initial intenden operation is restored after a reboot. So in my opinion something breaks.