Navigation

    • Register
    • Login
    • Search
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. SuperKris
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    SuperKris

    @SuperKris

    15
    Reputation
    39
    Posts
    836
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    SuperKris Follow

    Best posts made by SuperKris

    • Old school phone as doorbell and domoitcs interface!

      So i made a really cool project with a old phone.

      The current version features the following functions:

      • Doorbell function with simple button
      • MySensors integration with NRF24 radio
      • Wirelessly activate 5 different ringtones
      • Alarm signal
      • Working dial with 10 virtual switches

      The full description of the project can be found here:
      https://superkris.tweakblogs.net/blog/16935/old-school-phone-as-doorbell-and-domoitcs-interface!

      Hope you guys like it!

      Old school phone as doorbell and domotics interface – 03:28
      — Kristiaan N.

      0_1542365227093_646237.png

      Unfortunately i cant paste the code here because its to long, but it can be found on the link provided above.

      posted in My Project
      SuperKris
      SuperKris
    • RE: Slim Node scene controller/ keypad

      Hi AWI,

      Real nice design with all the small hardware. I have a tip for you on how you can make a very simple custom design membrane keypad.

      I used to work with POS scales. Most of the older designs had membrane keyboards. We fitted custom designs with the customers SKU's just by printing a new keyboard on plain paper. Then we used Sticky Laminating slides like these to seal the design and paste it to your keyboard.

      These sheets should not cost more than 1~2 $ per A4 sheet. Cold seal versions should be available, but most work with a machine. These machines van be found for approx 20,- $

      This way you should be able to build any custom layout if you have the MSpaint skills!

      posted in My Project
      SuperKris
      SuperKris
    • RE: Retrofit sensors into 240v LED Night Light : Help a novice?

      The kind of "PSU" thats is in that night light is not ideal for a mysensors application. I suggest you use this one:

      https://www.domoticz.com/forum/viewtopic.php?f=42&t=7832

      I think using the housing is a good idea, but please throw away those electronics.

      Here in the netherlands we have a cheap ass store called "Action" where they sell those 433mhz controlled remote plug in switches. You get 3 of them + a remote control for just € 10,-. I think they can be a pretty good housing too.

      posted in My Project
      SuperKris
      SuperKris
    • RE: How do i sent "virtual switches" from node to Controller?

      Here is most of my code;

      Relay code (fully working):

      // ##### SET PROJECT NAME AND VERSION #####
      #define ProjectName "Schuur controller"
      #define ProjectVersion "0,1"
      
      // ##### SET MYSENSOR SETTINGS BEFORE INCLUDIGN LIBRARY #####
      #define MY_DEBUG // Enable debug prints to serial monitor
      #define MY_RADIO_NRF24 // Enable and select radio type attached
      #define MY_REPEATER_FEATURE // Enabled repeater feature for this node
      
      // ##### INCLUDE LIBRARYS #####
      #include <SPI.h>
      #include <MySensors.h>
      #include <Bounce2.h>
      #include <Keypad.h>
      
      // ##### DEFINE I/O PINS #####
      //#define IoPin1 4  // Arduino Digital I/O pin number for I/O 1 
      #define IoPin2 3  // Arduino Digital I/O pin number for I/O 2 
      //#define IoPin3 6  // Arduino Digital I/O pin number for I/O 3 
      //#define IoPin4 5  // Arduino Digital I/O pin number for I/O 4 
      #define IoPin5 8  // Arduino Digital I/O pin number for I/O 5
      #define IoPin6 7  // Arduino Digital I/O pin number for I/O 6
      #define IoPin7 19 // Arduino Digital I/O pin number for I/O 7
      
      // ##### DEFINE CHILD ID'S #####
      #define CHILD_ID1 1    // ID for child 1 (I/O)
      #define CHILD_ID2 2    // ID for child 2 (I/O)
      //#define CHILD_ID3 3  // ID for child 3 (I/O)
      //#define CHILD_ID4 4  // ID for child 4 (I/O)
      #define CHILD_ID5 5    // ID for child 5 (I/O)
      #define CHILD_ID6 6    // ID for child 6 (I/O)
      #define CHILD_ID7 7    // ID for child 7 (I/O)
      #define CHILD_ID10 10  // ID for child 10 (virtual switch)
      #define CHILD_ID11 11  // ID for child 11 (virtual switch)
      #define CHILD_ID12 12  // ID for child 12 (virtual switch)
      #define CHILD_ID13 13  // ID for child 13 (virtual switch)
      #define CHILD_ID14 14  // ID for child 14 (virtual switch)
      
      // ##### RELAY SETTING #####
      #define RELAY_ON 0          // Invert for some relay modules (currently inverted)
      #define RELAY_OFF 1         // Invert for some relay modules (currently inverted)
      
      // ##### OTHER VARIABLES #####
      bool state; // not sure what this does
      
      // ##### BOOLEANS FOR VIRTUAL SWITCHES #####
      bool VirtalSwitch1;  // Boolean (status) for virtual switch 1 (controlled by keypad)
      bool VirtalSwitch2;  // Boolean (status) for virtual switch 2 (controlled by keypad)
      bool VirtalSwitch3;  // Boolean (status) for virtual switch 3 (controlled by keypad)
      bool VirtalSwitch4;  // Boolean (status) for virtual switch 4 (controlled by keypad)
      bool VirtalSwitch5;  // Boolean (status) for virtual switch 5 (controlled by keypad)
      
      void setup()  
      {  
        // ##### I/O SETUP FOR PHYSICAL I/O ON ARDUINO #####
        // Setup I/O 2
        pinMode(IoPin2, OUTPUT);                        // use I/O 2 as output for relay module
        digitalWrite(IoPin2, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID2);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin2, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 4                                     Not in use  
        // pinMode(IoPin4, OUTPUT);                        // use I/O 4 as output for relay module
        // digitalWrite(IoPin4, RELAY_OFF);                // and set switch relay output off
        // state = loadState(CHILD_ID4);                   // Load last known state (using eeprom storage) 
        // digitalWrite(IoPin4, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 5
        pinMode(IoPin5, OUTPUT);                        // use I/O 5 as output for relay module
        digitalWrite(IoPin5, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID5);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin5, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 6
        pinMode(IoPin6, OUTPUT);                        // use I/O 6 as output for relay module
        digitalWrite(IoPin6, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID6);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin6, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 7
        pinMode(IoPin7, OUTPUT);                        // use I/O 7 as output for relay module
        digitalWrite(IoPin7, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID7);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin7, state?RELAY_ON:RELAY_OFF); // write last know state
        // 
      }
      
      // ###### PRESENT ALL ATTACHED SENSORS TO CONTROLLER ######
      void presentation(){
        sendSketchInfo(ProjectName, ProjectVersion); // Send the sketch version information to the gateway and Controller
      
        // ----- Actual I/O child IDs -----
        //present(CHILD_ID1, XXXXXXX); //Register child ID 1 as NONE
        present(CHILD_ID2, S_LIGHT);   //Register child ID 2 as S_LIGHT
        //present(CHILD_ID3, XXXXXXX); //Register child ID 3 as NONE
        //present(CHILD_ID4, XXXXXXX); //Register child ID 4 as NONE
        present(CHILD_ID5, S_LIGHT);   //Register child ID 5 as S_LIGHT
        present(CHILD_ID6, S_LIGHT);   //Register child ID 6 as S_LIGHT
        present(CHILD_ID7, S_LIGHT);   //Register child ID 7 as S_LIGHT
      
        // ----- virtual switch child ID (keypad)
        present(CHILD_ID10, S_LIGHT);  //Register child ID 10 as S_LIGHT
        present(CHILD_ID11, S_LIGHT);  //Register child ID 11 as S_LIGHT
        present(CHILD_ID12, S_LIGHT);  //Register child ID 12 as S_LIGHT
        present(CHILD_ID13, S_LIGHT);  //Register child ID 13 as S_LIGHT
        present(CHILD_ID14, S_LIGHT);  //Register child ID 14 as S_LIGHT
      } 
      
      void loop() 
      {
      }
      
      // ##### CODE FOR RECEIVING MYSENSORS MESSAGES FROM CONTROLLER #####
      void receive(const MyMessage &message) {                         //start mysensor receiving code
        if (message.isAck()) {                                         //Check for gateway acknowledgment
           Serial.println("This is an ack from gateway");              //Print debug code (serial print) to confirm received ack
        }
        // ----- Action taken for child ID 1: Currently set as V_LIGHT to switch relay on IoPin1 -----
        if (message.type == V_LIGHT && message.sensor == CHILD_ID2) {  //if message is V_LIGHT and the child ID is 2 
           state = message.getBool();                                  //guess this write the incomming boolean to state?
           digitalWrite(IoPin2, state?RELAY_ON:RELAY_OFF);             //change the the arduino pin from "on" to "off" or other way around
           saveState(CHILD_ID2, state);                                //guess this saves the state if child ID 2 to EEPPROM
           Serial.print("Incoming change for sensor:");                //debug info text
           Serial.print(message.sensor);                               //write received child ID
           Serial.print(", New status: ");                             //debug info text
           Serial.println(message.getBool());                          //write received boolean
         } 
        // ----- Action taken for child ID 5: Currently set as V_LIGHT to switch relay on IoPin5 -----
        if (message.type == V_LIGHT && message.sensor == CHILD_ID5) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin5, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID5, state);
         } 
        // ----- Action taken for child ID 6: Currently set as V_LIGHT to switch relay on IoPin6 ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID6) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin6, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID6, state);
         } 
        // ----- Action taken for child ID 7: Currently set as V_LIGHT to switch relay on IoPin7 ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID7) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin7, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID7, state);
         } 
         
      }
      

      **Keypad code (concept works): **

      
      // -------- USED LIBARIES -----------
      #include <Keypad.h>
      
      // ##### KEYPAD SETUP #####
      const byte ROWS = 4; // Four rows
      const byte COLS = 3; // Three columns
      // Define the Keymap
      char keys[ROWS][COLS] = {
        {'1','2','3'},
        {'4','5','6'},
        {'7','8','9'},
        {'A','B','C'}
      };
      // Connect keypad ROW0, ROW1, ROW2 and ROW3 to these Arduino pins.
      byte rowPins[ROWS] = { A0, A1, A2, A3 };
      // Connect keypad COL0, COL1 and COL2 to these Arduino pins.
      byte colPins[COLS] = { A4, 1, 0 }; 
      // Create the Keypad
      Keypad kpd = Keypad( makeKeymap(keys), rowPins, colPins, ROWS, COLS );
      
      // ##### DEFINE I/O PINS #####
      //#define IoPin1 4  // Arduino Digital I/O pin number for I/O 1 
      #define IoPin2 3  // Arduino Digital I/O pin number for I/O 2 
      //#define IoPin3 6  // Arduino Digital I/O pin number for I/O 3 
      #define IoPin4 5  // Arduino Digital I/O pin number for I/O 4 
      #define IoPin5 8  // Arduino Digital I/O pin number for I/O 5
      #define IoPin6 7  // Arduino Digital I/O pin number for I/O 6
      #define IoPin7 19 // Arduino Digital I/O pin number for I/O 7
      
      
      // ##### BOOLEANS FOR VIRTUAL SWITCHES #####
      bool VirtalSwitch1;  // Boolean (status) for virtual switch 1 (controlled by keypad)
      bool VirtalSwitch2;  // Boolean (status) for virtual switch 2 (controlled by keypad)
      bool VirtalSwitch3;  // Boolean (status) for virtual switch 3 (controlled by keypad)
      bool VirtalSwitch4;  // Boolean (status) for virtual switch 4 (controlled by keypad)
      bool VirtalSwitch5;  // Boolean (status) for virtual switch 5 (controlled by keypad)
      
      void setup()
      
      
      { // ##### PIN SETUP (FOR TESTING ONLY #####
      
        pinMode(IoPin4, OUTPUT);   //use I/O 4 as output for relay module
        digitalWrite(IoPin4, HIGH);//   and set is HIGH so relay stays off
      
        
        // ###### VARIOUS SETTINGS ######
        Serial.begin(115200); //!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SERIAL PRINT MUST BE DEACTIVATED TO MAKE THE WHOLE KEYPAD WORK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      
      
      } 
      
      void loop()
      {
        char key = kpd.getKey();     // Get key from keypad (if pressed)
        if(key)  {                   // compare key (defined in keypad setup)
          switch (key) {             // with multiple multiple options below 
            
            case '1':                // If the pressed key compares with "1"
              VirtalSwitch1 = true;  // Change te state of boolean VirtalSwitch1 to true
              Serial.println("1");   // Debug code. Print "1" to show that button 1 was pressed
              break;                 // End of code for button 1
            
            case '4':                // If the pressed key compares with "4"          
              VirtalSwitch1 = false; // Change te state of boolean VirtalSwitch1 to false
              Serial.println("2");   // Debug code. Print "4" to show that button 4 was pressed
              break;                 // End of code for button 4
      
              
            default:                 // If the pressed key does not match the cases above
              Serial.println(key);   // Print the key that was pressed 
              break;                 // End of function 
          }
        }
      
      // ##### WRITE BOOLEAN TO PIN (FOR TESTING PURPOSES ONLY) #####
        digitalWrite(IoPin4, VirtalSwitch1);
      
        
      }
      
      

      I need to join this code and get the boolean to communicate toe the controller as described in my first post.

      posted in My Project
      SuperKris
      SuperKris
    • RE: How do i sent "virtual switches" from node to Controller?

      @Boots33 said:

      @SuperKris If I understand what you are trying to do is use the keypad instead of individual push buttons to change the relay state. Is that correct?

      Yes and no... or mostly.... no. Instead of changing the relay state, i want the push button to be a separate switch which is technically not related to any relays or other outputs. Its supposed to behave like a walls witch that is available in the controller.

      In the end i may couple a push button to one of the relay outputs, but this will be done in the controller. For instance, the controller wil only allow to switch on the light with the pushbutton if its dark outside.

      In the keypad code i do use 2 keys to control the boolean. This has 2 reasons. 1) that part is just proof of concept. 2) for some of the buttons i want it to work like this. I'm aware that i can use 1 button to change the boolean and change it back. I will add this later for some buttons.

      I hope this clarifies my intentions. This makes it different from the relay+button example sketch. Otherwise i would probably find it easier. I'm currently hoping to learn how i can make these "virtual wall switches" that are controlled from the keypad.

      I just dont know how to sent the booleans to the controller. I'm also not sure how to receive them, though i'm thinking it must be similar to the actual relays.

      posted in My Project
      SuperKris
      SuperKris
    • RE: How do i sent "virtual switches" from node to Controller?

      @tboha said:

      @SuperKris
      From the first look: it could be a simple typo:

      saveState(CHILD_ID_V1), state);
      should be
      saveState(CHILD_ID_V1, state);
      it may be simply one parenthesis too much.

      Wow.. I cant believe i missed that... damn.

      Ok, so everything seems to work now. I can just copy paste code and add some "virtual" buttons. Thats great! Thank you so much.

      Next i will need to add the PIR setup, but i think i have enough understanding to do this now. After that the DHT22 code. Should be a bit more trick, but i will get there.

      Just one more question about the code you written:

        present(CHILD_ID_V1, S_LIGHT, "Partylichtjes");  
      

      What does "partytlichtjes" do? I guess its supposed to send the name of the switch to the controller, but it wont compile if i add it in my sketch.

      posted in My Project
      SuperKris
      SuperKris
    • RE: How do i sent "virtual switches" from node to Controller?

      Found it!!! I figured there must be a serial begin somewhere in the library. It was not in MySensors.h, but MySensors.h had MySensorsCore.h included which included serval other library's. One of them was MyConfig.h I looked in al library's for a serial begin by searching "serial". In MyConfig.h i found this.

      /**********************************
      *  Serial and debug options
      ***********************************/
      
      // Enable MY_DEBUG in sketch to show debug prints. This option will add a lot to the size of the
      // final sketch but is helpful to see what is actually is happening during development
      //#define MY_DEBUG
      
      // Enable MY_SPECIAL_DEBUG in sketch to activate I_DEBUG messages if MY_DEBUG is disabled.
      // I_DEBUG requests are:
      // R: routing info (only repeaters): received msg XXYY (as stream), where XX is the node and YY the routing node
      // V: CPU voltage
      // F: CPU frequency
      // M: free memory
      // E: clear MySensors EEPROM area and reboot (i.e. "factory" reset)
      //#define MY_SPECIAL_DEBUG
      
      // Enable MY_DEBUG_VERBOSE_SIGNING flag for verbose debug prints related to signing.
      // Requires DEBUG to be enabled.
      // This will add even more to the size of the final sketch!
      //#define MY_DEBUG_VERBOSE_SIGNING
      
      // Enable this in sketch if you want to use TX(1), RX(0) as normal I/O pin
      //#define MY_DISABLED_SERIAL
      
      // Enable MY_CORE_ONLY flag if you want to use core functions without loading the framework
      //#define MY_CORE_ONLY
      
      // Turn off debug if serial pins is used for other stuff
      

      Adding "#define MY_DISABLED_SERIAL" to my sketch did the trick, and i can now use the full keypad.

      // ##### SET PROJECT NAME AND VERSION #####
      #define ProjectName "Shed controller"
      #define ProjectVersion "0,3"
      
      // ##### SET MYSENSOR SETTINGS BEFORE INCLUDIGN LIBRARY #####
      //#define MY_DEBUG // Enable debug prints to serial monitor
      #define MY_DISABLED_SERIAL
      #define MY_RADIO_NRF24 // Enable and select radio type attached
      #define MY_REPEATER_FEATURE // Enabled repeater feature for this node
      
      // ##### INCLUDE LIBRARYS #####
      #include <SPI.h>
      #include <MySensors.h>
      #include <Keypad.h>
      
      etc.....
      
      posted in My Project
      SuperKris
      SuperKris
    • RE: How do i sent "virtual switches" from node to Controller?

      Ok, next problem. I saw this one coming, but i cant figure it out by myself...

      I added the DHT code for the temperature and humidity. I took the sketch that under the build section as example. It does compile and work, but the sleep in the sketch is a issue. I was surprised to find the sketch was still responding to messages from the gateway. Maybe i'm understanding sleep wrong, so that is my first question.

      1. Does sleep stop all code from running, or just the function that its in? In other words; My keypad code is in the loop function. The mysensor code for receiving messages is in another funtion outside the loop function (void receive). Does a sleep in the loop function also blocks void receive, or does it only block the loop part?

      So both my keypad code and the DHT code are in the loop part of the sketch. This makes the keypad unresponsive. If i understand right this is caused because the code is sleeping most of the time. If i keep pressing the button until it wakes up for a a fraction of a second the key is registered.

      So the easy way would be to disable sleep right.... I do not need to save any batteries, and i want the whole node to be as responsive as possible. Disabling the sleep function (with just a // ) seems to work, but its flooding (debug still enabled off course) the serial monitor "with Failed reading temperature from DHT! Failed reading humidity from DHT"

      1. So i guess this is just because of the way the DHT works, but i fear this may be slowing down the whole sketch and making the node less responsive. Is it a bad idea to just skip the sleep and keep the rest the same?

      From what i learned from earlier experiments where i needed to time things but still needed it to be responsive to other input, i think the only solution is the millis function. I think such a function could be applied to only run the DHT code every 5 seconds. Unfortunately i'm way to much of a noob, and the DHT code is way to advanced to replace the sleep function with a millis function.

      1. Can anyone help me on my wat to replace the sleep funtion with the millies code?

      My current code (its getting pretty big now) can be found below:

      
      
      
      // ##### SET PROJECT NAME AND VERSION #####
      #define ProjectName "Shed Controller" // Name that is vissible in controller
      #define ProjectVersion "0,3"          // Version that is vissible in controller
      //#define MY_NODE_ID 10               // Manual Node ID.
      
      // ##### SET MYSENSOR SETTINGS BEFORE INCLUDIGN LIBRARY #####
      #define MY_DEBUG            // Enable debug prints to serial monitor
      // #define MY_DISABLED_SERIAL  // Disable serial monitor so pins 0 and 1 can be used for the keypad. Disable this line with comment to use serial monitor so debug code works
      #define MY_RADIO_NRF24      // Enable and select radio type attached
      #define MY_REPEATER_FEATURE // Enabled repeater feature for this node
      
      // ##### INCLUDE LIBRARYS #####
      #include <SPI.h>
      #include <MySensors.h>
      #include <Keypad.h>
      #include <DHT.h>
      
      
      
      // ##### DEFINE I/O PINS #####
      //#define IoPin1 4  // Arduino Digital I/O pin number for I/O 1 
      #define IoPin2 3  // Arduino Digital I/O pin number for I/O 2 
      #define IoPin3 6  // Arduino Digital I/O pin number for I/O 3 
      #define IoPin4 5  // Arduino Digital I/O pin number for I/O 4 
      #define IoPin5 8  // Arduino Digital I/O pin number for I/O 5
      #define IoPin6 7  // Arduino Digital I/O pin number for I/O 6
      #define IoPin7 19 // Arduino Digital I/O pin number for I/O 7
      
      // ##### DEFINE CHILD ID'S #####
      #define CHILD_ID1 1     // ID for child 1 (I/O)
      #define CHILD_ID2 2     // ID for child 2 (I/O) used for relay
      //#define CHILD_ID4 4   // ID for child 4 (I/O)
      #define CHILD_ID5 5     // ID for child 5 (I/O) used for relay
      #define CHILD_ID6 6     // ID for child 6 (I/O) used for relay
      #define CHILD_ID7 7     // ID for child 7 (I/O) used for relay
      
      #define CHILD_ID_V1 10    // ID for child virtual switch 1. Used for Outside lighting button
      #define CHILD_ID_V2 11    // ID for child virtual switch 2. Used for Heater button
      #define CHILD_ID_V3 12    // ID for child virtual switch 3. Used for Anti Frost button
      #define CHILD_ID_V4 13    // ID for child virtual switch 4. Used for Party Lights button
      #define CHILD_ID_V5 14    // ID for child virtual switch 5. Used for Wifi AP button
      #define CHILD_ID_V6 15    // ID for child virtual switch 6. Used for Aux 1 button
      #define CHILD_ID_V7 16    // ID for child virtual switch 7. Used for Aux 2 button
      #define CHILD_ID_V8 17    // ID for child virtual switch 8. Used for 5 min button
      #define CHILD_ID_TEMP1 30 // ID for child 8 (I/O) used for humidity
      #define CHILD_ID_HUM1 31  // ID for child 3 (I/O) used for temperature
      
      // ##### TEMPERATURE SENSOR SETTINGS #####
      #define SENSOR_TEMP_OFFSET 0 // Offset for temperatur sensor can be set here
      static const uint64_t UPDATE_INTERVAL = 10000;
      static const uint8_t FORCE_UPDATE_N_READS = 10;
      float lastTemp;
      float lastHum;
      uint8_t nNoUpdatesTemp;
      uint8_t nNoUpdatesHum;
      bool metric = true;
      DHT dht;
      
      // ##### RELAY SETTING #####
      #define RELAY_ON 0          // Invert for some relay modules (currently inverted)
      #define RELAY_OFF 1         // Invert for some relay modules (currently inverted)
      
      // ##### OTHER VARIABLES #####
      bool state; // Not realy sure what this exatly does. I guess temporary storage of received messages and loading from EEPROM
      
      // ##### BOOLEANS FOR VIRTUAL SWITCHES #####
      bool VirtalSwitch1;  // Boolean (status) for virtual switch 1 (controlled by keypad)
      bool VirtalSwitch2;  // Boolean (status) for virtual switch 2 (controlled by keypad)
      bool VirtalSwitch3;  // Boolean (status) for virtual switch 3 (controlled by keypad)
      bool VirtalSwitch4;  // Boolean (status) for virtual switch 4 (controlled by keypad)
      bool VirtalSwitch5;  // Boolean (status) for virtual switch 5 (controlled by keypad)
      bool VirtalSwitch6;  // Boolean (status) for virtual switch 6 (controlled by keypad)
      bool VirtalSwitch7;  // Boolean (status) for virtual switch 7 (controlled by keypad)
      
      // ##### DEFINE MYSENSORS MESSAGE CONTAINERS TO COMMUNICATE WITH GATEWAY #####
      MyMessage msgTemp(CHILD_ID_TEMP1, V_TEMP); // msgTemp sends child ID CHILD_ID_TEMP1 as V_TEMP
      MyMessage msgHum(CHILD_ID_HUM1, V_HUM);    // msgHum sends child ID CHILD_ID_HUM1 as V_HUM
      MyMessage msgV1(CHILD_ID_V1,S_LIGHT);      // msgV1 sends child ID CHILD_ID_V1 as S_LIGHT
      MyMessage msgV2(CHILD_ID_V2,S_LIGHT);      // msgV2 sends child ID CHILD_ID_V2 as S_LIGHT
      MyMessage msgV3(CHILD_ID_V3,S_LIGHT);      // msgV3 sends child ID CHILD_ID_V3 as S_LIGHT
      MyMessage msgV4(CHILD_ID_V4,S_LIGHT);      // msgV4 sends child ID CHILD_ID_V4 as S_LIGHT
      MyMessage msgV5(CHILD_ID_V5,S_LIGHT);      // msgV5 sends child ID CHILD_ID_V5 as S_LIGHT
      MyMessage msgV6(CHILD_ID_V6,S_LIGHT);      // msgV6 sends child ID CHILD_ID_V6 as S_LIGHT
      MyMessage msgV7(CHILD_ID_V7,S_LIGHT);      // msgV7 sends child ID CHILD_ID_V7 as S_LIGHT
      MyMessage msgV8(CHILD_ID_V8,S_LIGHT);      // msgV8 sends child ID CHILD_ID_V8 as S_LIGHT
      
      // ##### KEYPAD SETUP #####
      const byte ROWS = 4; // Just settings for keypad library. Enter number of rows here
      const byte COLS = 3; // Just settings for keypad library. Enter number of columns here
      // Nameing of very key on the keypad. The output of keypad code will be the charaters used here.
      char keys[ROWS][COLS] = {
        {'1', '2', '3'},
        {'4', '5', '6'},
        {'7', '8', '9'},
        {'A', 'B', 'C'}
      };
      byte rowPins[ROWS] = { A0, A1, A2, A3 }; // The pins the row wires are connected to (from left to right)
      byte colPins[COLS] = { A4, 1, 0 };       // The pins the column wires are connected to (from top to bottom)
      Keypad kpd = Keypad( makeKeymap(keys), rowPins, colPins, ROWS, COLS ); // This creates the actual keypad based on specs above.
      
      
      void setup()  
      {  
        // ##### I/O SETUP FOR PHYSICAL I/O ON ARDUINO #####
        // Setup I/O 2
        pinMode(IoPin2, OUTPUT);                        // use I/O 2 as output for relay module
        digitalWrite(IoPin2, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID2);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin2, state?RELAY_ON:RELAY_OFF); // write last know state
      
      
      
      
        // Setup I/O 3
        dht.setup(IoPin3); // set data pin of DHT sensor
        if (UPDATE_INTERVAL <= dht.getMinimumSamplingPeriod()) {
          Serial.println("Warning: UPDATE_INTERVAL is smaller than supported by the sensor!");
        }
        // Sleep for the time of the minimum sampling period to give the sensor time to power up
        // (otherwise, timeout errors might occure for the first reading)
        sleep(dht.getMinimumSamplingPeriod());
      
      
      
      
        // Setup I/O 4                                     Not in use  
        // pinMode(IoPin4, OUTPUT);                        // use I/O 4 as output for relay module
        // digitalWrite(IoPin4, RELAY_OFF);                // and set switch relay output off
        // state = loadState(CHILD_ID4);                   // Load last known state (using eeprom storage) 
        // digitalWrite(IoPin4, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 5
        pinMode(IoPin5, OUTPUT);                        // use I/O 5 as output for relay module
        digitalWrite(IoPin5, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID5);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin5, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 6
        pinMode(IoPin6, OUTPUT);                        // use I/O 6 as output for relay module
        digitalWrite(IoPin6, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID6);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin6, state?RELAY_ON:RELAY_OFF); // write last know state
      
        // Setup I/O 7
        pinMode(IoPin7, OUTPUT);                        // use I/O 7 as output for relay module
        digitalWrite(IoPin7, RELAY_OFF);                // and set switch relay output off
        state = loadState(CHILD_ID7);                   // Load last known state (using eeprom storage) 
        digitalWrite(IoPin7, state?RELAY_ON:RELAY_OFF); // write last know state
      
      
      
      
      
       // ----- PIN SETUP (FOR TESTING ONLY -----
       // pinMode(IoPin4, OUTPUT);   //use I/O 4 as output for relay module
       // digitalWrite(IoPin4, HIGH);//   and set is HIGH so relay stays off
        
      }
      
      // ###### PRESENT ALL ATTACHED SENSORS TO CONTROLLER ######
      void presentation(){
        
        // ----- Sent sketch info -----
        sendSketchInfo(ProjectName, ProjectVersion); // Send the sketch version information to the gateway and Controller
        
        // ----- Physical I/O child IDs -----
        //present(CHILD_ID1, XXXXXXX); //Register child ID 1 as NONE
        present(CHILD_ID2, S_LIGHT, "Outside lighting relay"); //Register CHILD_ID2 as S_LIGHT, and sent name to controller.
        //present(CHILD_ID4, XXXXXXX); //Register child ID 4 as NONE
        present(CHILD_ID5, S_LIGHT, "Switched outlet heater"); //Register CHILD_ID5 as S_LIGHT, and sent name to controller.
        present(CHILD_ID6, S_LIGHT, "Sw outlet party lights"); //Register CHILD_ID6 as S_LIGHT, and sent name to controller.
        present(CHILD_ID7, S_LIGHT, "Gate light relay");       //Register CHILD_ID7 as S_LIGHT, and sent name to controller.
        // ----- virtual switch child ID (keypad)
        
        present(CHILD_ID_V1, S_LIGHT, "Outside light switch"); //Register CHILD_ID_V1 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V2, S_LIGHT, "Shed heater");          //Register CHILD_ID_V2 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V3, S_LIGHT, "Anti frost mode");      //Register CHILD_ID_V3 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V4, S_LIGHT, "Party lights");         //Register CHILD_ID_V4 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V5, S_LIGHT, "Wifi AP");              //Register CHILD_ID_V5 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V6, S_LIGHT, "Aux 1");                //Register CHILD_ID_V6 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V7, S_LIGHT, "Aux 2");                //Register CHILD_ID_V7 as S_LIGHT, and sent name to controller
        present(CHILD_ID_V8, S_LIGHT, "5 min. button");        //Register CHILD_ID_V8 as S_LIGHT, and sent name to controller
       
        // ----- Sensor child ID's -----
        present(CHILD_ID_TEMP1, S_TEMP, "Temp shed Inside");   //Register CHILD_ID_TEMP1 as S_TEMP, and sent name to controller
        present(CHILD_ID_HUM1, S_HUM, "Hum. shed Indide");     //Register CHILD_ID_HUM1 as S_HUM, and sent name to controller
      
        // ----- Aditional presentation setting -----
        metric = getConfig().isMetric;  //Not sure what this does, Its needed for DHT sensor
      } 
      
      void loop()
      { // ##### KEYPAD CODE TO SET A ACTION FOR A PRESSED KEY #####
        char key = kpd.getKey();       // Get key from keypad (if pressed)
        if (key)  {                    // compare key (defined in keypad setup)
          switch (key) {               // with multiple multiple options below
      
                                  // On button for outside light
            case '1':                  // If the pressed key compares with "1"
              VirtalSwitch1 = true;    // Change te state of boolean VirtalSwitch1 to true (on)
              send(msgV1.set(1));      // Sent "on" command to gateway for CHILD_ID_V1 
              Serial.println("KEY 1"); // Debug code. Print "KEY 1" to show that button 1 was pressed
              break;                   // End of code for button 1
      
                                  // Off button for outside light
            case '2':                  // If the pressed key compares with "2"
              VirtalSwitch1 = false;   // Change te state of boolean VirtalSwitch1 to false (off)
              send(msgV1.set(0));      // Sent "off" command to gateway for CHILD_ID_V1 
              Serial.println("KEY 2"); // Debug code. Print "KEY 2" to show that button 2 was pressed
              break;                   // End of code for button 2
      
                                  // 5 minute button
            case '3':                  // If the pressed key compares with "3"
              send(msgV8.set(1));      // Sent "on" command to gateway for CHILD_ID_V8
              Serial.println("KEY 4"); // Debug code. Print "KEY 4" to show that button 4 was pressed
              break;                   // End of code for button 4
      
                                  // On button for heating
            case '4':                  // If the pressed key compares with "4"
              VirtalSwitch2 = true;    // Change te state of boolean VirtalSwitch2 to true (on). This is the heater
              VirtalSwitch3 = false;   // Change te state of boolean VirtalSwitch3 to false (off). This is the anti frost funtion
              send(msgV2.set(1));      // Sent "on" command to gateway for CHILD_ID_V2. This is the heater
              send(msgV3.set(0));      // Sent "off" command to gateway for CHILD_ID_V3. This is the anti frost funtion
              Serial.println("KEY 4"); // Debug code. Print "KEY 4" to show that button 4 was pressed
              break;                   // End of code for button 4
      
                                  // Off button for heating
            case '5':                  // If the pressed key compares with "5"
              VirtalSwitch2 = false;   // Change te state of boolean VirtalSwitch2 to false (off). This is the heater
              VirtalSwitch3 = false;   // Change te state of boolean VirtalSwitch3 to false (off). This is the anti frost funtion
              send(msgV2.set(0));      // Sent "off" command to gateway for CHILD_ID_V2. This is the heater
              send(msgV3.set(0));      // Sent "off" command to gateway for CHILD_ID_V3. This is the anti frost funtion
              Serial.println("KEY 5"); // Debug code. Print "KEY 5" to show that button 5 was pressed
              break;                   // End of code for button 5
      
                                  // On button for anti frost
            case '6':                  // If the pressed key compares with "6"
              VirtalSwitch2 = false;   // Change te state of boolean VirtalSwitch2 to false (off). This is the heater
              VirtalSwitch3 = true;    // Change te state of boolean VirtalSwitch3 to true (on). This is the anti frost funtion
              send(msgV2.set(0));      // Sent "off" command to gateway for CHILD_ID_V2. This is the heater
              send(msgV3.set(1));      // Sent "on" command to gateway for CHILD_ID_V3. This is the anti frost funtion
              Serial.println("KEY 6"); // Debug code. Print "KEY 6" to show that button 6 was pressed
              break;                   // End of code for button 6
              
                                  // On button for party lights
            case '7':                  // If the pressed key compares with "7"
              VirtalSwitch4 = true;    // Change te state of boolean VirtalSwitch1 to true (on)
              send(msgV4.set(1));      // Sent "on" command to gateway for CHILD_ID_V4 
              Serial.println("KEY 7"); // Debug code. Print "KEY 7" to show that button 7 was pressed
              break;                   // End of code for button 7
      
                                  // Off button for party lights
            case '8':                  // If the pressed key compares with "8"
              VirtalSwitch4 = false;   // Change te state of boolean VirtalSwitch1 to false (off)
              send(msgV4.set(0));      // Sent "off" command to gateway for CHILD_ID_V4 
              Serial.println("KEY 8"); // Debug code. Print "KEY 8" to show that button 8 was pressed
              break;                   // End of code for button 8
      
                                      // Aux ON/OFF buton 1
            case '9':{                     // If the pressed key compares with "9"
              if (VirtalSwitch6 == false){ // check if the virtual switch (VirtalSwitch6) is OFF. If so, do the following
                VirtalSwitch6 = true;      // set the new status of the virtual swich to ON
                send(msgV6.set(1));        // Sent "on" command to gateway for CHILD_ID_V6 
              }
              else {                       // If the virtual switch was not OFF, it must have been ON, so do the following 
                VirtalSwitch6 = false;     // set the new status of the virtual swich to OFF
                send(msgV6.set(0));        // Sent "off" command to gateway for CHILD_ID_V6 
                }
              }
              Serial.println("KEY 9");    // Debug code. Print "KEY 9" to show that button 9 was pressed
              break;                      // End of code for button 9
      
                                   // On button for Wifi AP
            case 'A':                  // If the pressed key compares with "A"
              VirtalSwitch5 = true;    // Change te state of boolean VirtalSwitch5 to true (on)
              send(msgV5.set(1));      // Sent "on" command to gateway for CHILD_ID_V5 
              Serial.println("KEY A"); // Debug code. Print "KEY A" to show that button A was pressed
              break;                   // End of code for button A
      
                                   // Off button for Wifi AP
            case 'B':                  // If the pressed key compares with "B"
              VirtalSwitch5 = false;   // Change te state of boolean VirtalSwitch5 to false (off)
              send(msgV5.set(0));      // Sent "off" command to gateway for CHILD_ID_V5 
              Serial.println("KEY B"); // Debug code. Print "KEY B" to show that button B was pressed
              break;                   // End of code for button B    
      
                                    // Aux ON/OFF buton 2
            case 'C':{                     // If the pressed key compares with "C"
              if (VirtalSwitch7 == false){ // check if the virtual switch (VirtalSwitch7) is OFF. If so, do the following
                VirtalSwitch7 = true;      // set the new status of the virtual swich to ON
                send(msgV7.set(1));        // Sent "on" command to gateway for CHILD_ID_V7 
              }
              else {                       // If the virtual switch was not OFF, it must have been ON, so do the following 
                VirtalSwitch7 = false;     // set the new status of the virtual swich to OFF
                send(msgV7.set(0));        // Sent "off" command to gateway for CHILD_ID_V7 
                }
              }
              Serial.println("KEY C");    // Debug code. Print "KEY C" to show that button C was pressed
              break;                      // End of code for button C
              
            default:                  // If the pressed key does not match the cases above
              Serial.print(key);      // Print the key that was pressed
              Serial.println(" was pressed but not recognized by the keypadcode. Something is wrong!"); // print warning
              break;                  // End of function
          }
        }  
      
      
      
      // Force reading sensor, so it works also after sleep()
        dht.readSensor(true);
      
        // Get temperature from DHT library
        float temperature = dht.getTemperature();
        if (isnan(temperature)) {
          Serial.println("Failed reading temperature from DHT!");
        } else if (temperature != lastTemp || nNoUpdatesTemp == FORCE_UPDATE_N_READS) {
          // Only send temperature if it changed since the last measurement or if we didn't send an update for n times
          lastTemp = temperature;
          if (!metric) {
            temperature = dht.toFahrenheit(temperature);
          }
          // Reset no updates counter
          nNoUpdatesTemp = 0;
          temperature += SENSOR_TEMP_OFFSET;
          send(msgTemp.set(temperature, 1));
      
          #ifdef MY_DEBUG
          Serial.print("T: ");
          Serial.println(temperature);
          #endif
        } else {
          // Increase no update counter if the temperature stayed the same
          nNoUpdatesTemp++;
        }
      
        // Get humidity from DHT library
        float humidity = dht.getHumidity();
        if (isnan(humidity)) {
          Serial.println("Failed reading humidity from DHT");
        } else if (humidity != lastHum || nNoUpdatesHum == FORCE_UPDATE_N_READS) {
          // Only send humidity if it changed since the last measurement or if we didn't send an update for n times
          lastHum = humidity;
          // Reset no updates counter
          nNoUpdatesHum = 0;
          send(msgHum.set(humidity, 1));
      
          #ifdef MY_DEBUG
          Serial.print("H: ");
          Serial.println(humidity);
          #endif
        } else {
          // Increase no update counter if the humidity stayed the same
          nNoUpdatesHum++;
        }
      
        // Sleep for a while to save energy
        //sleep(UPDATE_INTERVAL); 
      
      
      
      
      }
      
      // ##### CODE FOR RECEIVING MYSENSORS MESSAGES FROM CONTROLLER #####
      void receive(const MyMessage &message) {                         //start mysensor receiving code
        if (message.isAck()) {                                         //Check for gateway acknowledgment
           Serial.println("This is an ack from gateway");              //Print debug code (serial print) to confirm received ack
        }
        // ----- Relay actors -----
        // ----- Action taken for child ID 1: Currently set as V_LIGHT to switch relay on IoPin1 -----
        if (message.type == V_LIGHT && message.sensor == CHILD_ID2) {  //if message is V_LIGHT and the child ID is 2 
           state = message.getBool();                                  //guess this write the incomming boolean to state?
           digitalWrite(IoPin2, state?RELAY_ON:RELAY_OFF);             //change the the arduino pin from "on" to "off" or other way around
           saveState(CHILD_ID2, state);                                //guess this saves the state if child ID 2 to EEPPROM
           Serial.print("Incoming change for sensor:");                //debug info text
           Serial.print(message.sensor);                               //write received child ID
           Serial.print(", New status: ");                             //debug info text
           Serial.println(message.getBool());                          //write received boolean
         } 
        // ----- Action taken for child ID 5: Currently set as V_LIGHT to switch relay on IoPin5 -----
        if (message.type == V_LIGHT && message.sensor == CHILD_ID5) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin5, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID5, state);
         } 
        // ----- Action taken for child ID 6: Currently set as V_LIGHT to switch relay on IoPin6 ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID6) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin6, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID6, state);
         } 
        // ----- Action taken for child ID 7: Currently set as V_LIGHT to switch relay on IoPin7 ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID7) {  //no further comments. See actions for child 2. Its the same
           state = message.getBool();                                  //also no debug code (serial print) written to save space
           digitalWrite(IoPin7, state?RELAY_ON:RELAY_OFF);
           saveState(CHILD_ID7, state);
         } 
        // ----- Virtual switches -----   
        // ----- Action taken for CHILD_ID_V1: Currently set as V_LIGHT. Changes the boolean of virtual switch (VirtalSwitch1) ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V1) {  //if message is V_LIGHT, the child ID is CHILD_ID_V1 do the following 
           state = message.getBool();                                    //guess this write the incomming boolean to state?
           VirtalSwitch1 = state;                                        //copy the received boolean to VirtalSwitch1 
           saveState(CHILD_ID_V1, state);                                //guess this saves the state if CHILD_ID_V1 to EEPPROM
         } 
        // ----- Action taken for CHILD_ID_V2: Currently set as V_LIGHT.  ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V2 && state == 1) {  //if message is V_LIGHT, the CHILD_ID_V2 and the message is 1 (on)
           VirtalSwitch2 = true;                                         //set VirtalSwitch2 (heating) to 1 (on)
           VirtalSwitch3 = false;                                        //set VirtalSwitch3 (anti frost) to 0. This prevents the anti frost and heating funtion being on at the same time.
           send(msgV3.set(0));                                           //sent "off" command to gateway for CHILD_ID_V3. This is the anti frost funtion.
           saveState(CHILD_ID_V2, state);                                //guess this saves the state if CHILD_ID_V1 to EEPPROM
         }  
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V2 && state == 0) {  //if message is V_LIGHT, the CHILD_ID_V2 and the message is 0 (off)
           VirtalSwitch2 = false;                                        //set VirtalSwitch2 (heating) to 0 (off)
           VirtalSwitch3 = false;                                        //set VirtalSwitch3 (anti frost) to 0 ((off)
           send(msgV3.set(0));                                           //sent "off" command to gateway for CHILD_ID_V3. This is the anti frost funtion.
           saveState(CHILD_ID_V2, state);                                //guess this saves the state if CHILD_ID_V1 to EEPPROM
         }
        // ----- Action taken for CHILD_ID_V3: Currently set as V_LIGHT.  ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V3 && state == 1) {  //if message is V_LIGHT, the CHILD_ID_V3 and the message is 1 (on)
           VirtalSwitch3 = true;                                         //set VirtalSwitch3 (anti frost) to 1 (on)
           VirtalSwitch2 = false;                                        //set VirtalSwitch2 (heating) to 0. This prevents the heating and anti frost funtion being on at the same time.
           send(msgV2.set(0));                                           //sent "off" command to gateway for CHILD_ID_V2. This is the heating funtion.
           saveState(CHILD_ID_V3, state);                                //guess this saves the state if CHILD_ID_V1 to EEPPROM
         }  
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V3 && state == 0) {  //if message is V_LIGHT, the CHILD_ID_V3 and the message is 0 (off)
           VirtalSwitch3 = false;                                        //set VirtalSwitch3 (anti frost) to 0 ((off)
           VirtalSwitch2 = false;                                        //set VirtalSwitch2 (heating) to 0 (off)
           send(msgV2.set(0));                                           //sent "off" command to gateway for CHILD_ID_V3. This is the anti frost funtion.
           saveState(CHILD_ID_V3, state);                                //guess this saves the state if CHILD_ID_V1 to EEPPROM
         }
        // ----- Action taken for CHILD_ID_V4: Currently set as V_LIGHT. Changes the boolean of virtual switch (VirtalSwitch4) ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V4) {  //if message is V_LIGHT, the child ID is CHILD_ID_V4 do the following
           state = message.getBool();                                    //guess this write the incomming boolean to state?
           VirtalSwitch4 = state;                                        //copy the received boolean to VirtalSwitch4 
           saveState(CHILD_ID_V4, state);                                //guess this saves the state if CHILD_ID_V4 to EEPPROM
         } 
        // ----- Action taken for CHILD_ID_V5: Currently set as V_LIGHT. Changes the boolean of virtual switch (VirtalSwitch5) ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V5) {  //if message is V_LIGHT, the child ID is CHILD_ID_V5 do the following
           state = message.getBool();                                    //guess this write the incomming boolean to state?
           VirtalSwitch5 = state;                                        //copy the received boolean to VirtalSwitch5 
           saveState(CHILD_ID_V5, state);                                //guess this saves the state if CHILD_ID_V5 to EEPPROM
         } 
        // ----- Action taken for CHILD_ID_V6: Currently set as V_LIGHT. Changes the boolean of virtual switch (VirtalSwitch6) ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V6) {  //if message is V_LIGHT, the child ID is CHILD_ID_V6 do the following
           state = message.getBool();                                    //guess this write the incomming boolean to state?
           VirtalSwitch6 = state;                                        //copy the received boolean to VirtalSwitch6 
           saveState(CHILD_ID_V6, state);                                //guess this saves the state if CHILD_ID_V6 to EEPPROM
         }    
        // ----- Action taken for CHILD_ID_V7: Currently set as V_LIGHT. Changes the boolean of virtual switch (VirtalSwitch7) ----- 
        if (message.type == V_LIGHT && message.sensor == CHILD_ID_V7) {  //if message is V_LIGHT, the child ID is CHILD_ID_V7 do the following
           state = message.getBool();                                    //guess this write the incomming boolean to state?
           VirtalSwitch7 = state;                                        //copy the received boolean to VirtalSwitch7 
           saveState(CHILD_ID_V7, state);                                //guess this saves the state if CHILD_ID_V6 to EEPPROM
         }   
      }
      
      posted in My Project
      SuperKris
      SuperKris
    • RE: Old school phone as doorbell and domoitcs interface!

      Thanks guys!

      @yveaux Dont know that site very well, but i might do that... If enough people like the idea and build it i might develop it further. There are some other ideas like a mute function and i have been wondering if it would be possible to develop a module that just connects to any old pone as a external box.

      posted in My Project
      SuperKris
      SuperKris

    Latest posts made by SuperKris

    • RE: Old school phone as doorbell and domoitcs interface!

      Thanks guys!

      @yveaux Dont know that site very well, but i might do that... If enough people like the idea and build it i might develop it further. There are some other ideas like a mute function and i have been wondering if it would be possible to develop a module that just connects to any old pone as a external box.

      posted in My Project
      SuperKris
      SuperKris
    • Old school phone as doorbell and domoitcs interface!

      So i made a really cool project with a old phone.

      The current version features the following functions:

      • Doorbell function with simple button
      • MySensors integration with NRF24 radio
      • Wirelessly activate 5 different ringtones
      • Alarm signal
      • Working dial with 10 virtual switches

      The full description of the project can be found here:
      https://superkris.tweakblogs.net/blog/16935/old-school-phone-as-doorbell-and-domoitcs-interface!

      Hope you guys like it!

      Old school phone as doorbell and domotics interface – 03:28
      — Kristiaan N.

      0_1542365227093_646237.png

      Unfortunately i cant paste the code here because its to long, but it can be found on the link provided above.

      posted in My Project
      SuperKris
      SuperKris
    • RE: Virtual switches that never go off and controllers

      @mfalkvidd said in Virtual switches that never go off and controllers:

      wait() will not mess with ability to receive radio - in fact, handling the radio is exactly what is done inside wait(). However, if a radio message needs to be handled, wait() can take more time than the specified number of milliseconds. Therefore, wait() won't be suitable for generating a precise 5ms square wave.

      As you probably already guessed, button presses will be ignored during wait(), unless you use interrupts.

      For a more flexible solution, you'll need to modify all code to work without wait. See https://www.arduino.cc/en/Tutorial/BlinkWithoutDelay for a simple starting point, but be aware that it gets more and more complex with multiple different things happening at the same time.

      Thanks for the info! i was afraid that was what wait was doing. The question is how bad i want to fix this... I know about millis. I dont have to rewrite that much code for it. Maybe there is some library i can use.

      Also it doesnt really matter how good the square wave is, as long as the 2 "bell" pins are never high at the same time.

      I guess millis can be the solution for sending a off signal to, or are there better ways to handle this?

      posted in Development
      SuperKris
      SuperKris
    • RE: Virtual switches that never go off and controllers

      The code so far....

      Another problem i have is in the "ringtone" in the last part of the code. It stops the whole code of the arduino while running. Is wait not a suitable function for this? or does this happen because its in a while loop?
      Are there better ways to solve this?

      /**
       * 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.
       *
       *******************************
       *
       * DESCRIPTION
       *
       * Simple binary switch example 
       * Connect button or door/window reed switch between 
       * digitial I/O pin 3 (button below) and GND.
       * http://www.mysensors.org/build/binary
       */
      
      /// ##### mysensors setup ######
      #define ProjectName "OldPhone" // Name that is vissible in controller
      #define ProjectVersion "0,1"          // Version that is vissible in controller
      #define MY_DEBUG       // Enable debug prints to serial monitor
      #define MY_RADIO_NRF24 // Enable and select radio type attached
      #define childIdDoor 1         // child ID number used by mysensors foor doorbell button
      #define chuildIdDail_1 101    // child ID number used by mysensors when the number 1 is dailed
      #define chuildIdDail_2 102    // child ID number used by mysensors when the number 2 is dailed
      #define chuildIdDail_3 103    // child ID number used by mysensors when the number 3 is dailed
      #define chuildIdDail_4 104    // child ID number used by mysensors when the number 4 is dailed
      #define chuildIdDail_5 105    // child ID number used by mysensors when the number 5 is dailed
      #define chuildIdDail_6 106    // child ID number used by mysensors when the number 6 is dailed
      #define chuildIdDail_7 107    // child ID number used by mysensors when the number 7 is dailed
      #define chuildIdDail_8 108    // child ID number used by mysensors when the number 8 is dailed
      #define chuildIdDail_9 109    // child ID number used by mysensors when the number 9 is dailed
      #define chuildIdDail_10 110   // child ID number used by mysensors when the number 0 is dailed
      
      // ###### Include libraries #####
      #include <SPI.h>              // needed for NRF24
      #include <MySensors.h>        // mysensors library
      #include <Bounce2.h>          // for debouncing buttons and dail
      
      // ###### I/O pin number setup ######
      #define button 3              // input pin activated when doorbell button is pressed
      #define edail 8               // input pin activated when dail is used (Enable Dail)
      #define pdail 7               // input pin activated with each tick of the dail (Pulse Dial)
      #define lbell 4               // output pin to swing bellh hamer left
      #define rbell 5               // output Pin to swing bellh hamer right
      
      // ##### Debouncer variables #####
      Bounce debouncerButton = Bounce(); // Create button debouncer for doorbell button 
      Bounce debouncerEdail = Bounce();  // Create button debouncer for Enable Dail
      Bounce debouncerPdail = Bounce();  // Create button debouncer for Pulse Dial 
      int valueButton = 0;               // Value 
      int oldValueButton = 0;
      int valueEdail = 0;
      int oldValueEdail = 0;
      int valuePdail = 0;
      int oldValuePdail = 0;
      int dailCount = 0;
      int newDailCount = 0;  
      
      
      int ring = 0;
      int ringX = 15;
      int onPulse = 20;
      int offPulse = 10;
      int repeat = 0;
      int repeatX = 4;
      int ringPause = 2000;
      
      // ##### setup MySensors message containers #####
      MyMessage msgDoor(childIdDoor,V_STATUS);         // message container used for doorbell button
      MyMessage msgDail_1(chuildIdDail_1,V_STATUS);    // message container used when the number 1 is dailed
      MyMessage msgDail_2(chuildIdDail_2,V_STATUS);    // message container used when the number 2 is dailed
      MyMessage msgDail_3(chuildIdDail_3,V_STATUS);    // message container used when the number 3 is dailed
      MyMessage msgDail_4(chuildIdDail_4,V_STATUS);    // message container used when the number 4 is dailed
      MyMessage msgDail_5(chuildIdDail_5,V_STATUS);    // message container used when the number 5 is dailed
      MyMessage msgDail_6(chuildIdDail_6,V_STATUS);    // message container used when the number 6 is dailed
      MyMessage msgDail_7(chuildIdDail_7,V_STATUS);    // message container used when the number 7 is dailed
      MyMessage msgDail_8(chuildIdDail_8,V_STATUS);    // message container used when the number 8 is dailed
      MyMessage msgDail_9(chuildIdDail_9,V_STATUS);    // message container used when the number 9 is dailed
      MyMessage msgDail_10(chuildIdDail_10,V_STATUS);  // message container used when the number 0 is dailed
      
      void setup()  
      {  
      //##### I/O pin function setup #####
        pinMode(button,INPUT);    //set the already defined I/O pin as input
        pinMode(edail, INPUT);    //set the already defined I/O pin as input
        pinMode(pdail, INPUT);    //set the already defined I/O pin as input
        pinMode(lbell, OUTPUT);   //set the already defined I/O pin as output
        pinMode(rbell, OUTPUT);   //set the already defined I/O pin as output
       
      // ##### Debouncer setup #####
        debouncerButton.attach(button);
        debouncerButton.interval(5);
        debouncerEdail.attach(edail);
        debouncerEdail.interval(5);
        debouncerPdail.attach(pdail);
        debouncerPdail.interval(5);
      }
      
      // ##### Function of MySensors that presents all attached sensors to the controller #####
      void presentation() { 
        sendSketchInfo(ProjectName, ProjectVersion);   // Send the sketch version information to the gateway and Controller
        present(childIdDoor, S_BINARY);                // Present doorbell button as binary switch
        present(chuildIdDail_1, S_BINARY);             // Present the dailing of number 1 as binary switch
        present(chuildIdDail_2, S_BINARY);             // Present the dailing of number 2 as binary switch
        present(chuildIdDail_3, S_BINARY);             // Present the dailing of number 3 as binary switch
        present(chuildIdDail_4, S_BINARY);             // Present the dailing of number 4 as binary switch
        present(chuildIdDail_5, S_BINARY);             // Present the dailing of number 5 as binary switch
        present(chuildIdDail_6, S_BINARY);             // Present the dailing of number 6 as binary switch
        present(chuildIdDail_7, S_BINARY);             // Present the dailing of number 7 as binary switch
        present(chuildIdDail_8, S_BINARY);             // Present the dailing of number 8 as binary switch
        present(chuildIdDail_9, S_BINARY);             // Present the dailing of number 9 as binary switch
        present(chuildIdDail_10, S_BINARY);            // Present the dailing of number 0 as binary switch
      }
      
      void loop() {
      // ##### debouncer updater ##### 
        debouncerButton.update();                      // Update debouncer for doorbell button
        valueButton = debouncerButton.read();          // Set current value of doorbell button 
        debouncerEdail.update();                       // Update debouncer for enable dail
        valueEdail = debouncerEdail.read();            // Set current value of enable dail
        debouncerPdail.update();                       // Update debouncer for pulse dail 
        valuePdail = debouncerPdail.read();            // Set current value of pulse dail
      
      // ##### Mysensors code to check doorbell button and sent message ##### 
        if (valueButton != oldValueButton) {                       // Check if the value of the button has changed 
           send(msgDoor.set(valueButton==HIGH ? 1 : 0));           // Transmit the new value
           oldValueButton = valueButton;                           // Change old value so this doenst loop
        }
      
      // ##### Mysensors code to read dail counter and sent message as one individual sensor #####
        switch (newDailCount) {         // Check the current vallue of the completed counter
           case 1:                      // if value is equal to 1 
             send(msgDail_1.set(1));    // Transmit ON message for dail switch 1 
             send(msgDail_1.set(0));    // Transmit OFF message for dail switch 1. Some home automation software prefers this.
             break;                     // end of case
           case 2:                      // if value is equal to 2 
             send(msgDail_2.set(1));    // Transmit ON message for dail switch 2
             send(msgDail_2.set(0));    // Transmit OFF message for dail switch 2. Some home automation software prefers this.
             break;                     // end of case
           case 3:                      // if value is equal to 3 
             send(msgDail_3.set(1));    // Transmit ON message for dail switch 3
             send(msgDail_3.set(0));    // Transmit OFF message for dail switch 3. Some home automation software prefers this.
             break;                     // end of case
           case 4:                      // if value is equal to 4 
             send(msgDail_4.set(1));    // Transmit ON message for dail switch 4 
             send(msgDail_4.set(0));    // Transmit OFF message for dail switch 4. Some home automation software prefers this.
             break;                     // end of case
           case 5:                      // if value is equal to 5 
             send(msgDail_5.set(1));    // Transmit ON message for dail switch 5 
             send(msgDail_5.set(0));    // Transmit OFF message for dail switch 5. Some home automation software prefers this.
             break;                     // end of case
           case 6:                      // if value is equal to 6 
             send(msgDail_6.set(1));    // Transmit ON message for dail switch 6 
             send(msgDail_6.set(0));    // Transmit OFF message for dail switch 6. Some home automation software prefers this.
             break;                     // end of case       
           case 7:                      // if value is equal to 7 
             send(msgDail_7.set(1));    // Transmit ON message for dail switch 7 
             send(msgDail_7.set(0));    // Transmit OFF message for dail switch 7. Some home automation software prefers this.
             break;                     // end of case       
           case 8:                      // if value is equal to 8 
             send(msgDail_8.set(1));    // Transmit ON message for dail switch 8 
             send(msgDail_8.set(0));    // Transmit OFF message for dail switch 8. Some home automation software prefers this.
             break;                     // end of case       
           case 9:                      // if value is equal to 9 
             send(msgDail_9.set(1));    // Transmit ON message for dail switch 9 
             send(msgDail_9.set(0));    // Transmit OFF message for dail switch 9. Some home automation software prefers this.
             break;                     // end of case       
           case 10:                     // if value is equal to 10 
             send(msgDail_10.set(1));    // Transmit ON message for dail switch 10 
             send(msgDail_10.set(0));    // Transmit OFF message for dail switch 10. Some home automation software prefers this.
             break;                     // end of case       
        }
        newDailCount = 0;                // Reset the completed counter so this doesnt loop
      
        
      // ###### Code for checking enable dail and sending state trough serial  ######  
        if (valueEdail != oldValueEdail && valueEdail == HIGH) {          // Check if enable dail has changed AND if its currently its currently activated
           Serial.println("dail is activated...");                        // If so sent message 
           oldValueEdail = valueEdail;}                                   // And change old value so this doenst loop
           else if (valueEdail != oldValueEdail && valueEdail == LOW) {   // Check if enable dail has changed AND if its currently its currently deactivated
           Serial.println("dail is deactivated...");                      // If so sent message
           newDailCount = dailCount;                                       // Write the counted pulses to the New Dail Count
           dailCount = 0;                                                 // Reset the dail count for next dail 
           oldValueEdail = valueEdail;                                    // And change old value so this doenst loop
        }
      
      // ###### Code for checking pusle dail and sending state trough serial ######
        if (valuePdail != oldValuePdail && valueEdail == HIGH) {          // Check if dail pulse has changed AND if currently its currently activated
           if (valuePdail == LOW) {                                       // Only take action when the signal goes from high to low to prevent double count
             dailCount++;                                                 // If the conditions are met increase counter by 1
             Serial.print("Tick! Total ammout of pulses: ");              // Serial print a messagge saying a pulse was detected
             Serial.println (dailCount);                                  // Serial print a the current value of the counter
           }
             oldValuePdail = valuePdail;                                  // Change old value so this doenst loop  
        }
       
        if (valueButton == HIGH) {                // If the boorbell button was pressed (read from debouncer)
           while (repeat < repeatX){              // start a loop if the number of repeats isnt reached yet (a repeat is the time a bell is ringed pauesed)
              repeat++;                           // add 1 count to the "repeat" counter
              while (ring < ringX){               // start a loop if the number of rings isnt reached yet (a ring is the hammer hitting each bell once)
                 ring++;                          // add 1 count to the "ring" counter
                 digitalWrite(lbell, HIGH);       // power the bell coil so that the hammer hits the left bell  !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 wait(onPulse);                   // hold for the amount of ms set for "onPulse"                !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 digitalWrite(lbell, LOW);        // power down the bell coil                                   !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 wait(offPulse);                  // wait for the amount of ms set for "offpulse"               !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 digitalWrite(rbell, HIGH);       // power the bell coil so that the hammer hits the right bell !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 wait(onPulse);                   // hold for the amount of ms set for "onPulse"                !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 digitalWrite(rbell, LOW);        // power down the bell coil                                   !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
                 wait(offPulse);                  // wait for the amount of ms set for "offpulse"               !!! VERY IMPORTANT: "LBELL" AND "RBELL" CAN NEVER BE HIGH AT THE SAME TIME !!!
              }                                   // go back to start if loop till "ring" has the same value as "ringX"
              wait (ringPause);                   // wait for the amount of ms set for "ringPause"
                 if (ring == ringX){              // if the amount of "ring" is the same as the amount set in "ringX"....
                    ring = 0;                     // reset the "ring" counter
                    }
               }
           }  
                    
        if (repeat == repeatX){                   // if the amount of "repeat" is the same as the amount set in "repeatX"....
           repeat = 0;                            // reset the "repeat" counter
           } 
      }
      
      posted in Development
      SuperKris
      SuperKris
    • Virtual switches that never go off and controllers

      For a project i'm working on i have converted a old 1950's phone into a doorbell/multiple switches.

      If i dail 3, for example it does a "send(msgDail_1.set(1));" This message is set up as S_BINARY and V_STATUS.

      In my experience some home automation software like Domotics doesnt like this very much as the switch never switches off. A simple solution can be to send a off command directly after the on command. This seems to be working most of the time, but sometime it seems a bit random. Maybe because the status is only high for a very low time.

      A normal switch would always have 2 states, or be pressed for several 100ms.

      A solution can be to add a "wait" for maybe 500ms. However i found that the "wait" function actually stops the Arduino from receiving input. Most of the time that wont be a problem, but i would like to get it working the right way. Both the send and wait function are in a "switch case" if it makes ant difference.

      Do you guys recognize this problem? How have you solved this?

      posted in Development
      SuperKris
      SuperKris
    • RE: What are the best settings for MY_RF24_PA_LEVEL?

      I have a node that is not working perfectly. I'm not sure about the reception problem, but it doesnt help its in a thick aluminium housing. I'll try some foil on the radio of the gateway!

      posted in Troubleshooting
      SuperKris
      SuperKris
    • RE: What are the best settings for MY_RF24_PA_LEVEL?

      @rejoe2 said in What are the best settings for MY_RF24_PA_LEVEL?:

      Hi SuperKris,

      most likely, there is not a definite answer to your questions.

      First a very good point for a lot of info around the nrf's: https://arduino-info.wikispaces.com/Nrf24L01-2.4GHz-HowTo

      Thanks for the link, there was some useful information there

      I personally got best results using the PA+LNA-Versions and additional base modules, power sourced through 5V with PA-Level set to max.

      This is the standard-level which is used as long as there is no explicitely defined other level. This is the standard mechanism using the myconfig.h settings. Keep eyes open, as this is defined to LOW e.g. in the GW-Sketch...

      One of the reasons i started asking about this that it was defined to LOW in the default gateway sketch. I started to google on these settings and found a couple of topics where they advise to lower MY_RF24_PA_LEVEL. This made me even more unsure about selecting the right voltage level.

      MAX will also work with the non PA+LNA-Boards, but keep in mind using this setting also means higher power consumption, so soucing the NRF through Arduino's 3.3V-PIN might not work.

      I always use a e-cap on every PSU. For this the radio i often use 47u, and a 470-1000u on the arduino 5V. Also always a 50n in parallel as close to the chip as possible. I dont use a extra regulator board, but i use arduino's with a strong 3V3 PSU. I love the one's by Robotdyn. They have a AMS117 (SOT223 size i think?). They specify the 3V3 at 350mA. I have not tested this, but the AMS117 should be good for 1A if it can cool enough, so i expect it to be able to deliver plenty of power.

      @rejoe2 said in What are the best settings for MY_RF24_PA_LEVEL?:

      @LastSamurai
      According to my personal experience I would answer with a clear yes! The +PA+LNA-Version gets better receiving results and generates a stronger signal when sending. So -apart form adding a capacitor- changing the module on the GW imo is also an action to recommend to improve the overall results. You may in addition think about shielding both decoder chips (not the antennas).

      Does shielding actually improve results? This is interesting to me. how should one proceed with this? First warping it in plastic, and next in aluminium foil? Should the shield be connected to the ground pin, or maybe even to the shell of the USB?

      posted in Troubleshooting
      SuperKris
      SuperKris
    • RE: What are the best settings for MY_RF24_PA_LEVEL?

      Anyone? Or am i asking stupid questions again? 😕

      posted in Troubleshooting
      SuperKris
      SuperKris
    • What are the best settings for MY_RF24_PA_LEVEL?

      I spent some time googeling the best value's for MY_RF24_PA_LEVEL, but i could not find a definitive answer. I hope my questions are not very stupid, but i would like to understand the type of radio and its settings better.

      First i would like to know which NRF24L01 are the best. From what i have read, the NRF24L01 + PA + LNA has a build in amplifier and is therefore more powerful. Usually these have a external antenna mounted by a SMA connector. The normal NRF24L01+ have a PCB antenna.

      For a gateway i would guess the NRF24L01 + PA + LNA would always be the best choice right? Same for a repeating node i would guess... Off course this is amusing power consumption, costs of the more expensive NRF24L01 + PA + LNA radio, and the lager size are no problem. Or am i missing something here?

      Considering range. The best combination is always NRF24L01 + PA + LNA for both nodes if i understand right. For some node's i prefer the smaller, cheaper, and less power hungry NRF24L01+. Does using a NRF24L01+PA+LNA as a gateway to communicate with the NRF24L01+ offer any improved performance over using a NRF24L01+ for both the gateways and the node?

      Will MY_RF24_PA_LEVEL work on both the NRF24L01+ and NRF24L01+PA+LNA, or will it only work on the NRF24L01+PA+LNA?

      From reading the library API i understand the default value is RF24_PA_MAX. I'm a bit of a noob with Arduino, so i'm not sure how this works. If i make a sketch without manually adding MY_RF24_PA_LEVEL, will the library set it to RF24_PA_MAX automatically?

      So what is the generally the best value for the MY_RF24_PA_LEVEL when used with a NRF24L01+PA+LNA on a gateway? A lower power will obviously mean less range. But i can imagine a very high power can sometime also cause problems. So is there a sweet sport for a average configuration when the gateway is inside of a regular house where all sensors are in a max 20m range (with walls) and the furthest sensor is maybe 30-40m away?

      posted in Troubleshooting
      SuperKris
      SuperKris
    • RE: NRF24L01 radio problems. (Bermuda triangle shit)

      I for sure learned to double check any print terminal i take out of sample boxes. Damn...

      The 230V part of the board has a 5.08mm pitch for all lanes. I cut out the PCB pads and via's of the experimental board on both sided for insulation. The decoupling for 5V was done with 470u and 100n as close as possible to the Arduino. Same for the radio with 47u and 100n.

      There is only 1 real way to do this. Same goes for all the other connections. There are no other components in there. Except for the psu output and the radio voltage i cant think of anything that causes the issue with the radios.

      posted in Hardware
      SuperKris
      SuperKris