BLU Motion Blind Time malfunctioning?

[Snappy]

I have 3 BLU motion connected to a Shelly Mini Gen 3. Their purpose is to switch on the light in a corridor and stairway when ppl walking in and out, to the cellar, etc. All 3 sensors are less than 10m away from the Mini with no major obstacles in their way (thin wooden door, glasss, but no walls). Switching of the light is implemented as a Scene in the Mini.

The LEDs in the sensors indicate, that they are properly detecting every motion. However, the switch is not properly triggered all the time and I suspect this is an issue with the blind time of the sensors: min. Blind Time you can configure is 30sec. It looks like this is not counted from the last signalling to the Mini but actually from the last motion detected. Meaning: if you're moving around in sight of the same sensor, it will only fire once until you leave for at leadt 30sec. As a result, the light turns off automatically after a while and will never turn on again until you leave the sensor alone for a while. 

My expectation would be, that the sensor continues to detect alls motion (as it does), but only sends 1 action to the Mini every 30 sec (or any other configured interval) but does not keept that information for itself. 

Anyone here who can explain the behavior and ideally has a workaround for me? 

BTW: I understand that scenes are cloud-hosted and executed. Not ideal, but simple to set up and works usually fine. While my Mini looses Wifi signal once in a while (visible in the app), the behavior described above also happens when the Mini is properly connected to the Wifi (verified via app) and verified then by triggering another sensor of which the blind time has already run out. 

[Rumpel]

Hi Snappy,

I have the same problem and after some testig I am pretty shure it is exactly as you described but I don't know any workaroud for it yet.
I also noticed that the blu motion led is longer when outside of the "blind time" and then fires immediatly.

I also tried using the actions inside my M1 mini Gen 3 insted of the cloud to prevent the problem with internet connectivity but that doesn't change anything.

If I turn on the debugging I don't see any movement triggerd during the blind time and beyond when a motion accured (with short blinking led) during that time.

I hope someone or a firmwareupdate can change it...

 

[Rumpel]

Hi Snappy,

I've researched a bit and it seems that we got the function of the blind time wrong.
I've found this video: https://support.shelly.cloud/en/support/solutions/articles/103000308252-how-to-use-shelly-blu-motion-set-up-blind-time-

So apparently you'le have to use two actions. One when the motion is detected which turns your Relais on, and the other when there is no more motion detected. And here comes the blind time in handy. This defines the minimum time for the relais to be "on".
And as we discovered the time gets reset every time a motion is detected.

As I've mentioned earlier I've setup two actions directly on my Mini1G3 so I dont have to rely on a internet connection.
The first turns the relais on when Motion is true, and the second turns the relais off when the motion is false.

It seems to work fine now.

But I think that only works fine if you pare a single blu motion with relais, if you have a long room and need more motion sensors that won't help you because there will always be a sensor which doesnt detect motion any more.

[Lukmin]

your video didn't help. I am using sensor for light control and lights stays ON only if you do not leave the area it can detect you during next blind time interval e.g every 150 seconds. If you leave the room and come back for example after 180 seconds (light is still on because delay time for OFF is also 150 seconds), sensor indicates presence immediately, and logically time for lights ON should reset or scene for OFF deactivate. But no, it doesn't matter, because the OFF command was already triggered 🙂 And when sensor turns lights OFF you have to wait 150 seconds in the darkness 🙂

Shit product 2/10

Edited October 10, 2024 by Lukmin
mistakes in grammar

[Maxpa1966]

Hi Rumpel,

 

can you explain me exactly how to set the same action you run directly on your 1PM Gen3.

I’m using the Cloud but often my Scene are delayed.

Thanks

[Heinz]

20 hours ago, Maxpa1966 said:

Hi Rumpel,

 

can you explain me exactly how to set the same action you run directly on your 1PM Gen3.

I’m using the Cloud but often my Scene are delayed.

Thanks

To run then directly from the device you need to set actions. Scenes are Cloud based Actions are local based 

[Maxpa1966]

Dear Heinz,

I know but the problem and my question, is that I don’t know how to set the script in the right way.

[al3x]

On 22.10.2024 at 18:14, Maxpa1966 said:

Dear Heinz,

I know but the problem and my question, is that I don’t know how to set the script in the right way.

What exactly do you want to do with the script?

[SteffenH]

How to Use Multiple Shelly BLU Motion Sensors in a Hallway Scenario

Hello Shelly users,

I’ve found a solution for using multiple motion sensors to control a light, like in a long hallway or staircase. The concept is similar to what’s described in this video: How to use Shelly BLU Motion & set up Blind Time.

Here’s how I set it up for a hallway/staircase with two motion sensors:

---

What I Used:

• 2 Shelly BLU Motion Sensors (m1 and m2)
• 1 Shelly 1PM Mini Gen 3 (a1) (any actuator would work)
• 1 Light (l1) (any connected device like a lamp or ceiling light)
• A long hallway or staircase (mine leads to the basement)
• Shelly Cloud for scene configuration

---

Steps to Set Up:

1. Configure the Blind Timer:

Set the blind timer on both motion sensors (m1 and m2) to the desired duration you want the light (l1) to remain on after motion is detected.

---

2. Create Two Scenes:

To automate the light, you’ll need two scenes in the Shelly Cloud app:

1. Scene 1: Turns the light ON when motion is detected.
2. Scene 2: Turns the light OFF when no motion is detected from both sensors.

---

Scene 1: Turning the Light ON

Condition:

• IF
  • Motion detected by m1 (EVENT)
  • OR
  • Motion detected by m2 (EVENT)

Action:

• Switch on l1 (light)
• Note: Do not set a timer here; the motion sensors' blind timers will handle the duration.

Explanation:
Any motion sensor detecting motion will trigger the light to turn on.

---

Scene 2: Turning the Light OFF

Condition:

• IF
  • m1 sends a "no motion" EVENT, AND m2 is in the "no motion" STATE
  • OR
  • m1 is in the "no motion" STATE, AND m2 sends a "no motion" EVENT

Action:

• Switch off l1 (light)

Explanation:
After the blind timer expires on the first triggered motion sensor, it sends a "no motion" EVENT. The light turns off only if the second motion sensor is also in a "no motion" STATE or has sent a "no motion" EVENT.

---

Key Ideas:

1. The light-on duration is defined by the blind timer of the sensors.
2. The first scene ensures the light turns on with any motion detected.
3. The second scene ensures the light turns off only after both sensors indicate no motion.

---

Examples:

Here are two sample scenes from my setup (attached screenshots for reference):

• Scene 1: "LichtAnBeiBewegung" (Light On When Motion)
• Scene 2: "LichtAusBeiKeinerBewegung" (Light Off When No Motion)

Devices Used:

• m1: "KellertreppeBewegung" (Stairway Motion)
• m2: "KellerBewegung" (Basement Motion)
• l1: "KellerHauptlicht" (Basement Main Light)

---

I hope this helps! Feel free to ask questions or share improvements for similar setups. 😊

   

 

[Heinz]

Awsome explanation @SteffenH

[KRISCHKA]

Ein unbeschreibliches DANKE @SteffenH

Passt auch für mein Szenario: Ein Raum der zum Durchgang genutzt wird, man sich aber auch "ohne" Bewegungen mal drin aufhält.

m1, r1 (Relais), l1 und zusätzlich einem s1 (physischer Schalter). Somit erweitert sich meine WENN um die Prüfung (Zustand/Bedingung) des Eingangsstatus von r1 durch s1.