💬 Motion Sensor

[LastSamurai]

I would actually not do this in a node but in the controller (at least if I get what you are trying to do right). I have done that with some scripting in domoticz. I have lights that that are switched on for 5 minutes when motion is detected and shut down 5 minutes after the last motion stopped. Motion sensor and rgbw controller are different mysensor nodes. Much more versatile then hardcoding this in you node's code.

[ben999]

@LastSamurai
Would you do that through "rules" ?

[gohan]

@ben999 yes.

@LastSamurai I know that hardcoding is less flexible, but at least it can work even if controller is down or disconnected, of course it depends how critical is the actuator.

[maghac]

So, I notice that the HC-SR501 has a 7133-1 voltage regulator on-board which I guess means that the logic is actually driven with 3.3V and not 5V.

Is it possible to bypass the regulator and power the sensor directly with the 3.3V I am using to power my nano with?

[maghac]

@maghac Aha, guess I should read old posts first :)

[gohan]

Just make sure the power source is stable otherwise you will end up with random triggers from pir sensor

[ben999]

@gohan @maghac

From my little experience : when running from 2 AA batteries with sketch as it is I got random triggers continuousely

Adding a delay() before entering sleep() sorted things out (something like 3 sec is necessary to get power stable again)

Not sure it's the smartest way of doing it, but it works...

Any comment on the security side of it? Could my node miss some action during these 3 sec ? Or the interrupt pin would still listen to the PIR sensor pin ?

[gohan]

I think it will miss the pir trigger

[ben999]

@gohan

Thank you for your reply

Could you please explain a bit further ?

Interrupt pin would still read the trigger during delay()?
Data would be lost as the sketch is frozen during delay() ?
Or data is saved in some buffer, ready to be used as soon as sketch comes back to life ?

My view is that it shouldn't matter too much if i miss a trigger after a trigger : the first trigger will wake my node and transmit to gateway. So job done. Alarm goes off.

On the other hand, I guess a millis() would be neater ?

Thanks a lot for your input

[gohan]

I am saying that during delay no code is executed and interrupt only attaches to pin when executing the sleep function, so if motion if triggered during the delay it will not be detected by interrupt; maybe it could detect the CHANGE when pir goes from high to low but it will then report "no motion" and it will not trigger alarm if it set to go off on "motion" only.

[ben999]

@gohan

Thanks a lot

Got it now

delay() to be avoided then !

I will have a look at millis() instead

[gohan]

Delay is not bad, depends how you use it. Maybe you could use an if statement to check pin state is low before entering sleep

[skywatch]

Millis won't work with the SLEEP funtion either. REcently added to the API....

[siod]

Hi, I´ve read this above

"however this sensor requires 5 VDC so you will need to use a step-up regulator if you are running the 3.3V version of the Arduino Pro Mini."

So I am using 3 V, could you propose a fitting step up regulator so I can use this PIR (best from ebay)? Thank you!

[maghac]

@siod said in 💬 Motion Sensor:

a

You have a HC-SR501 sensor? I had that same question before and then I realized that the HC-SR501 actually has a 3.3 V regulator and if you bypass it you can run it on 3.3V.

[sellier]

@Cliff-Karlsson
For dual Sensors

one error is present on the line sleep:
it is not : sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR_1 || DIGITAL_INPUT_SENSOR_1), CHANGE, SLEEP_TIME);

but : sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR_1 )|| digitalPinToInterrupt(DIGITAL_INPUT_SENSOR_2), CHANGE, SLEEP_TIME);

[MCF]

hi,
i want to ad a motion sensor to my project (3 dimmers on a arduino uno using nrf24).
My first problem is that the 2 and 3 pins are not available (nrf24 and pwm dimmer), so i will take the pin 1 for testing
second is the sleeping time during i can't send any light message to my dimmers...

[MCF]

this is my code

/**
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
 * Copyright (C) 2013-2015 Sensnology AB
 * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * REVISION HISTORY
 * Version 1.0 - February 15, 2014 - Bruce Lacey
 * Version 1.1 - August 13, 2014 - Converted to 1.4 (hek)
 *
 * DESCRIPTION
 * This sketch provides a Dimmable LED Light using PWM and based Henrik Ekblad
 * <henrik.ekblad@gmail.com> Vera Arduino Sensor project.
 * Developed by Bruce Lacey, inspired by Hek's MySensor's example sketches.
 *
 * The circuit uses a MOSFET for Pulse-Wave-Modulation to dim the attached LED or LED strip.
 * The MOSFET Gate pin is connected to Arduino pin 3 (LED_PIN), the MOSFET Drain pin is connected
 * to the LED negative terminal and the MOSFET Source pin is connected to ground.
 *
 * This sketch is extensible to support more than one MOSFET/PWM dimmer per circuit.
 * http://www.mysensors.org/build/dimmer
 * 
 * 
 * LISTE DE POINTS:
 * D0  DISPO
 * D1  MOTION
 * D2  IRQ NRF
 * D3  LED1
 * D4  DISPO
 * D5  LED2
 * D6  LED3
 * D7  DISPO
 * D8  DISPO
 * D9  CE NRF
 * D10 CSN/CS NRF
 * D11 MOSI NRF
 * D12 MISO NRF
 * D13 SCK NRF
 * D14 DISPO
 * 
 * 
 */

// Enable debug prints to serial monitor
#define MY_DEBUG 

// Enable and select radio type attached
#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69

//#define MY_NODE_ID 153 

#include <SPI.h>
#include <MySensors.h> 

#define SN "BUREAU PARENTS"
#define SV "1.2"

#define noLEDs 3
const int LED_Pin[] = {3, 5, 6}; 

#define FADE_DELAY 10  // Delay in ms for each percentage fade up/down (10ms = 1s full-range dim)

static int currentLevel1 = 0;  // Current dim level...
static int currentLevel2 = 0;  // Current dim level...
static int currentLevel3 = 0;  // Current dim level...

MyMessage dimmer1Msg(1, V_DIMMER);
MyMessage light1Msg(1, V_LIGHT);
MyMessage dimmer2Msg(2, V_DIMMER);
MyMessage light2Msg(2, V_LIGHT);
MyMessage dimmer3Msg(3, V_DIMMER);
MyMessage light3Msg(3, V_LIGHT);

// MOTION SENSOR
uint32_t SLEEP_TIME = 120000; // Sleep time between reports (in milliseconds)
#define DIGITAL_INPUT_SENSOR 1   // The digital input you attached your motion sensor.  (Only 2 and 3 generates interrupt!)
#define CHILD_ID 4   // Id of the sensor child
MyMessage msg(CHILD_ID, V_TRIPPED);

/***
 * Dimmable LED initialization method
 */
void setup()  
{ 
  // LEDS
  // Pull the gateway's current dim level - restore light level upon sendor node power-up
for (int sensor=1; sensor<=noLEDs; sensor++){
  request( sensor, V_DIMMER );
 }
 // MOTION
 pinMode(DIGITAL_INPUT_SENSOR, INPUT);      // sets the motion sensor digital pin as input
}

void presentation() {
  // Register the LED Dimmable Light with the gateway
 for (int sensor=1; sensor<=noLEDs; sensor++){
 present(sensor, S_DIMMER);
 wait(2);
 }
  // MOTION
  present(CHILD_ID, S_MOTION);
  
  sendSketchInfo(SN, SV);
}

/***
 *  Dimmable LED main processing loop 
 */
void loop() 
{
  // Read digital motion value
    bool tripped = digitalRead(DIGITAL_INPUT_SENSOR)== HIGH;
    
    Serial.println("coucou");
    Serial.println(tripped);
    send(msg.set(tripped?"1":"0"));  // Send tripped value to gw
    }
    // Sleep until interrupt comes in on motion sensor. Send update every two minute.
    sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
}



void receive(const MyMessage &message) {
  if (message.type == V_LIGHT || message.type == V_DIMMER) {

    if (message.sensor == 1) {

     //  Retrieve the power or dim level from the incoming request message
    int requestedLevel1 = atoi( message.data );
    
    // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on]
    requestedLevel1 *= ( message.type == V_LIGHT ? 100 : 1 );
    
    // Clip incoming level to valid range of 0 to 100
    requestedLevel1 = requestedLevel1 > 100 ? 100 : requestedLevel1;
    requestedLevel1 = requestedLevel1 < 0   ? 0   : requestedLevel1;

      
     fadeToLevel1( requestedLevel1, message.sensor );
    send(light1Msg.set(currentLevel1 > 0 ? 1 : 0)); 
    send(dimmer1Msg.set(currentLevel1) );}
   
    
    
     
   if (message.sensor == 2) {
   //  Retrieve the power or dim level from the incoming request message
    int requestedLevel2 = atoi( message.data );
    
    // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on]
    requestedLevel2 *= ( message.type == V_LIGHT ? 100 : 1 );
    
    // Clip incoming level to valid range of 0 to 100
    requestedLevel2 = requestedLevel2 > 100 ? 100 : requestedLevel2;
    requestedLevel2 = requestedLevel2 < 0   ? 0   : requestedLevel2;
    
    fadeToLevel2( requestedLevel2, message.sensor );
    send(light2Msg.set(currentLevel2 > 0 ? 1 : 0));
    send(dimmer2Msg.set(currentLevel2) );}
     
    if (message.sensor == 3) {
   //  Retrieve the power or dim level from the incoming request message
    int requestedLevel3 = atoi( message.data );
    
    // Adjust incoming level if this is a V_LIGHT variable update [0 == off, 1 == on]
    requestedLevel3 *= ( message.type == V_LIGHT ? 100 : 1 );
    
    // Clip incoming level to valid range of 0 to 100
    requestedLevel3 = requestedLevel3 > 100 ? 100 : requestedLevel3;
    requestedLevel3 = requestedLevel3 < 0   ? 0   : requestedLevel3;
      
     fadeToLevel3( requestedLevel3, message.sensor );
    send(light3Msg.set(currentLevel3 > 0 ? 1 : 0));
    send(dimmer3Msg.set(currentLevel3) );}
    }

    
}

/***
 *  This method provides a graceful fade up/down effect
 */
void fadeToLevel1( int toLevel1, int ledid1 ) {

  int delta1 = ( toLevel1 - currentLevel1 ) < 0 ? -1 : 1;
  
  while ( currentLevel1 != toLevel1 ) {
    currentLevel1 += delta1;
    analogWrite(LED_Pin[ledid1-1], (int)(currentLevel1 / 100. * 255) );
    wait( FADE_DELAY );
  }
}
void fadeToLevel2( int toLevel2, int ledid2 ) {

  int delta2 = ( toLevel2 - currentLevel2 ) < 0 ? -1 : 1;
  
  while ( currentLevel2 != toLevel2 ) {
    currentLevel2 += delta2;
    analogWrite(LED_Pin[ledid2-1], (int)(currentLevel2 / 100. * 255) );
    wait( FADE_DELAY );
  }
}
void fadeToLevel3( int toLevel3, int ledid3 ) {

  int delta3 = ( toLevel3 - currentLevel3 ) < 0 ? -1 : 1;
  
  while ( currentLevel3 != toLevel3 ) {
    currentLevel3 += delta3;
    analogWrite(LED_Pin[ledid3-1], (int)(currentLevel3 / 100. * 255) );
    wait( FADE_DELAY );
  }
}

[gohan]

Since it is a powered node, you don't need to put it to sleep. As for the pir you can do as you like: check pin status during loop, use an attach interrupt function on pin change, etc

[MCF]

@gohan ok thank you for answering. if i do this:

void loop() 
{
  // Read digital motion value
    bool tripped = digitalRead(DIGITAL_INPUT_SENSOR)== HIGH;
    
    Serial.println("coucou");
    Serial.println(tripped);
    send(msg.set(tripped?"1":"0"));  // Send tripped value to gw
    }
    // Sleep until interrupt comes in on motion sensor. Send update every two minute.
    //sleep(digitalPinToInterrupt(DIGITAL_INPUT_SENSOR), CHANGE, SLEEP_TIME);
}

the node never stop to send message to the gateway. i would like to send something only if D1 goes to high, is that possible ? (i'm starting combinating exemple and i want to understand what i do now!!)