Beiträge von AZSlow3

Update. With 2 sensors. ALMOST works...

Hardware:

• Shelly1 (s1) with local light, local taster and Motion Sensor (m1) on the first floor. Taster area is covered by (m1).
• Shelly1 (s2) with 2x lights, local taster and Motion Sensor (m2) on the ground floor. The taster area is not covered by (m2) (and should not). Extra taster wired to (s1) near the entrance door, its area is covered by (m2).

Scenarios which work:

• during day light motion does not activate the light. Any taster can activate all lights for 90seconds, prolonged by motions in covered areas
• during dark time tasters or motions in covered areas activate the light, prolonged by motions in covered areas

Still doesn't work:

• in case the light is switched off by tasters, but motion was already detected, the light will be switched on again after motion dead time (for 30 seconds)
• not possible to unconditionally (for long period) switch on the light in case used taster is in covered by motion area and it is dark (so (m1) or (m2) are in Dead timer). An attempt is not in correct configuration.

And so, (4) how to shut-up this sensor if it is in "dead time" so it doesn't call "end of movement"?

Complete current configuration:

(s1) momentary, "Auto OFF": 90. Following actions defined:

• Button short pressed: (s2)/relay/0?turn=toggle
• Output switched on: (m1)/settings?motion_operating_mode=0
• Output switched off: (m1)/settings?motion_operating_mode=1

(s2) momentary, "Auto OFF": 90. Following actions defined:

• Button short pressed: (s1)/relay/0?turn=toggle
• Output switched on: (m2)/settings?motion_operating_mode=0
• Output switched off: (m2)/settings?motion_operating_mode=1

(m1) mode: "Dark", blind time: 1. Following actions defined:

• Motion detected:
  • (m2)/settings?sleep_time=3600
  • (s1)/relay/0?turn=on&timer=3600
  • (s2)/relay/0?turn=on&timer=3600
• End of motion:
  • (s1)/relay/0?turn=on&timer=30
  • (s2)/relay/0?turn=on&timer=30
  • (m2)/settings?sleep_time=0

(m2) mode: "Dark", blind time: 1. Following actions defined:

• Motion detected:
  • (m1)/settings?sleep_time=3600
  • (s1)/relay/0?turn=on&timer=3600
  • (s2)/relay/0?turn=on&timer=3600
• End of motion:
  • (s1)/relay/0?turn=on&timer=30
  • (s2)/relay/0?turn=on&timer=30
  • (m1)/settings?sleep_time=0

Explanation

I use toggle sync, without detached button. Once in a while connection is lost or router is down. I want to be sure I can switch the light on manually.

I use timers everywhere. In case the connection is down / command was lost / etc., I prefer to have "self healing" configuration (up to 1h to recover is better then nothing). I don't live in the corridor/stairs area.

Shellys switch Motion detection mode to Any once they have switched on corresponding light. Motions will not be detected otherwise.

Activated Motion sensor deactivate another one for own Dead time. Afterwards it allows another sensor to take the lead (f.e. someone has moved from the first floor to the ground floor and he/she is staying here for a while).

I will not mark the topic as "solved" for now. I am going to test current configuration for several days first.

Update. I am still with just one sensor...

I already have to switch motion_operating_mode from Shelly1 output, as a workaround for (2). So, on Light On -> Mode = Any, on Light Off -> Mode = Dark. Motion actions moved from Dark specific to general (Motion).

Reasons:

(a) during the day motions will not be detected and so "No motion" actions will not be called (apart from not calling Shelly1 all the day and may be reducing power consumption, that opens some options for double sensor...).

(b) the following sequence works, in addition to "normal" motion activated scenario:

- button for Shelly1 pressed -> Light On for 1.5min

- When no-one walks near the sensor (in my environment possible), the light is Off after 1.5min

- By any movement near the sensor, the sensor takes the lead (prolong the light till there is no motion).

Without mode switching, the sensor can't take the lead since motion is detected in Twilight and so does not trigger Dark actions.

If someone has an idea how to do that without switching the mode (I still have not found any info how fast it can damage Motion Sensor memory), please let me know.

In the perfect world I would like to switch the light unconditionally. But the best switch for that is near the sensor, so it is already in blind timer when I want activate that scenario. And so the question:

(4) Is it possible to CANCEL blind timer? I have seen a "trick" to reset it (by setting some actions related parameter to the value it already has...). But that immediately calls "End of motion" actions (was ok in different thread, but not for my purpose). Unfortunately asking to Sleep doesn't reset the timer, "End of motion" is triggered within sleep time.

Zitat

My Shelly Motions didn't arrive yet, but if I understood correct, if the dark mode is choosen and motion was detected, the dark parameter will be deactivated, in order to retrigger the Motion, as long as motion is detected, plus set blind time.
Once the Motion gets deactivated, it will stay off until another motion will be detected under "dark" mode.

"Motion detected in the Dark" is activated in "Any" or "Dark" Modes, if lux condition is in the "Dark" range (at the moment first motion is noticed). But as soon as you switch the light on, lux condition is no longer in the "Dark". So in the "Dark" mode "Off" Actions will come exactly after blind time, independent from any future motions. Only in "Any" mode the sensor reset blind timer independent from current lux. That is my problem number (2).

But in "Any" mode once motion was detected (independent form lux) the sensor sends "Off" in any case (so it sends "Off" all the day long after any motions). That is my problem number (1).

Update.

I have checked one way to workaround (2). As soon as the light is on, Shelly 1 can request to change Mode from Dark to Any. When the light is off, it can switch it back into Dark.

But I have worries since Mode is a permanent parameter, that will write into EPROM every time I turn the light on.

"Dark" at 4 lux is still too high, this morning the light was triggered. But that I can accept, it was relatively dark.

I am trying to automate the light on stairs, 2 floors. So 2 sensors required to cover the area. The light is controlled by Shelly 1.

I don't want cloud/Home Assistant/other external scripts. I am theoretically ready to use Shelly 1 Plus if required.

Note that I have already seen:

Thema

Nur bei Dunkel schalten, dann aber bei Bewegung Licht verlängern?

Hallo alle, ich habe jetzt auch die ersten Motion in Betrieb und machen soweit was sie sollen. Stehe aber noch etwas auf dem Schlauch. Ich habe einen Motion in unserer Werkstatt hängen. Er schaltet nur bei Dark das Licht ein. Wie sage ich ihm, wenn bei Dark eingeschaltet wurde er erst ausschalten soll wenn keine Bewegung mehr. Leute halten sich länger als Timerzeit aus. Er erkennt dann ja nicht mehr dunkel weil ja das Licht leuchtet.

Danke euch.

superfranki

24. Februar 2021 um 00:02

Thema

Perfekte Einstellungen für "Licht so lange wie Bewegung" möglich?

Moin Mädels,

Ich habe ein bisschen mit dem Motion-Sensor experimentiert. Bislang hängt er in einem Durchgangsraum, in dem man sich aber gelegentlich auch mal aufhalten möchte. eingestellt habe ich ihn so:

MOTION DETECTED IN DARK: http://babladeckenlicht/light/0?turn=on

Im Dimmer für das Deckenlicht habe ich wiederum einen Timer von 5 Minuten eingestellt. Dieser läuft auch korrekt ab, sowohl bei Motion als auch bei Tastendruck. OK.

Richtig gut würde es jetzt aber, wenn der Bewegungsmelder während…

Rapid#Limit#27587

21. Februar 2021 um 19:49

Thema

1 Shelly Motion soll einen zweiten Shelly Motion schalten

Hallo,

ich hätte ein Frage und zwar ist folgendes möglich....

.....ich möchte gerne , dass ein Shelly Motion , nach Ende der "Blind Time", nicht das Licht ausschaltet , sondern einen zweiten Shelly Motion aktiviert , ist das möglich ?

Hintergrund ist , dass ich ein Treppenhauslicht über mehrerer Stockwerke mittels 2 Shelly Motions steuern möchte. Gleichzeitig aber auch verhindern will, dass der erste der z.B. beim runter gehen aktiviert wurde, nach Ende der Blind Time das Licht wieder…

W_Christian

14. März 2021 um 16:42

And mentioned proposals are far from perfect.

I currently see the problem in two rather strange "features" and one not existing feature:

1. "No motion" actions are called independent from "Motion detected" actions. In case I want detection in the "Dark" only, I can specify corresponding actions explicitly. But "No motion" actions are called after any motion detection. In case the intention is just main stream "turn off", that is not a problem. But if, for example, I want "keep light for another 30 seconds", it will turn light during the day. Natural solution is "Mode" "Dark". But...

2. As soon as lux is in different range (the light is on), motion is no longer detected. I mean if the motion is already detected, it logically should continue "track" it independent from the mode. But it does not.

3. There is no "I still observe the motion" actions. So, external devices have no way to reset own times when the sensor reset the timer. The only next message they can get is "No motion", but feature (1) kills any practical usefulness of that second action set, except "switch off now" (so it works in case nothing was or should be on).

I have not tested "self sleep" combinations yet. But obviously during sleep time the sensor does nothing (not detecting motions) and the author of that proposal writes that is not always working.

Apart from written, even with one sensor I have already installed, I see lux problematic. I effectively have to set "Dark" to 4 lux to avoid switching during the day, since I see down to "7" when my stairs have sufficient light for me. The sensor is not broken, when the light is on it shows ~60 in my case. Outside during the day >1000. But somehow for in-door use light detection precision is far from perfect.

Mentioned threads are relatively "old", taking rapid firmware updates into account. Have I overseen something? Are there any plans to fix (1) and/or (2) and implement (3)? May be in some "beta" already?

I don't think "2+ sensor -> 1 light" is so exotic wish (till most users have small open areas only). Are there plans to make "several sensors as one" internally in firmware? That could make installation as simple as with just one device.