๐Ÿ’ฌ NodeManager

  • Contest Winner

    Hi, for those looking for making NodeManager time aware (with and without an attached RTC), this capability has been added to the development branch through https://github.com/mysensors/NodeManager/pull/259 and it is of course transparent to the end user. When this feature is enabled, also, the node resumes the remainder sleep time when woken up by an interrupt and allows SensorPulseMeter and subclasses to support sleep mode. Thanks

  • Plugin Developer

    @user2684 Great news! I will give that a try shortly.

  • The SensorSwitch/Door/Motion all work on interrupt pins only ? Sorry if I've misunderstood the code, thats possible.

    Anyway I've made a few changes so that busywait, if thats what they are called buttons can be also used. I'll see if I can use git somehow to share the changes, or show them at least

    Great library, looking to convert other things to use this.

  • Great code, another question.

    For the SensorDimmer, each sensor has only one type set so a dimmer can't receive v_status & v_percentage messages.

    I've worked around this by registering two sensors at the same Analog out pin. But they don't then have access in a nice way to the status of each other as values are changed. So if I turn the led on/off via the v_status message I can't preserve the previous percentage, set by the other v_percentage sensor.

    Is this normal ? I'm new to all this but at least mycontroller lets you specify for a single sensor both v_status,v_percentage so both types of messages can be sent and processed in onRecieve()...

    Perhaps some enhancement on the SensorDimmer class could do this ? in ModeManager.cpp (if (message.type != _type) return;) inside Sensor::recieve.... isn't that too restrictive ?

  • Contest Winner

    @rfm69 yes, they are all interrupt-based. Reason is they would need to be functional either when sleeping or not so I went for this approach. If you need an example of such a sensor not interrupt-based, have a look at the SensorSonoff, it is using a different approach for handling the button. Thanks

  • Contest Winner

    @rfm69 you're right, this also came out a while ago. I was sure we had an associated issue on github for this but it doesn't look like. Here's the new issue for your reference https://github.com/mysensors/NodeManager/issues/296. Implementing this in v1.6 is really challenging but with the new v1.7 architecture of the development branch should be way easier since all the children share the same variables. Thanks!

  • @user2684 Thanks, I've implemented something myself with changes to the library, just playing around to understand it better. But will look at the SensorSonoff you mention.

    Thanks again, its a great library.

    Had a quick look at 1.7 dev branch ๐Ÿ™‚ is this ready for using already, testing or trying, or have you got more to do before its refactored etc ? I was interested in looking what the changes in architecture were.

  • Contest Winner

    @rfm69 v1.7 is still not completed but theoretically fully functional and with most of the architectural changes already done (https://github.com/mysensors/NodeManager/milestone/9 for the full list of things still to be completed and those already implemented). For sure safe to be tested out! Thanks

  • Contest Winner

    @rfm69 for your SensorDimmer request, feel free to give v1.7-dev a try from here https://github.com/mysensors/NodeManager/tree/development. Details on the implementation of your request can be found at https://github.com/mysensors/NodeManager/pull/302. Thanks

  • Contest Winner

    Hi, for anybody interested in giving the upcoming NodeManager v1.7 a try or share a feedback, please have a look at https://forum.mysensors.org/topic/9085/nodemanager-v1-7-beta-feedback-needed. Thanks!

  • Contest Winner

    Hi, the new version of NodeManager (v1.7) is now available! For those interested in having a look at the new features, supported sensors and capabilities, I've opened a dedicated thread on the forum here https://forum.mysensors.org/topic/9165/nodemanager-v1-7-now-available

  • @user2684 in the sensebender sketch we turn on digital pin 7 to provide power to the LDR to read it.
    i have many sensors in my house and would rather not re-wire all of them.
    how can i add this cleanly in nodemgr to make it work as before?
    pinMode(7, OUTPUT); // โ€œpower pinโ€ for Light Sensor
    digitalWrite(7, LOW); // switch power off


  • Contest Winner

    @mvader thanks for the feedback, I've added this issue on Github so to fix this in the next dev release https://github.com/mysensors/NodeManager/issues/344

  • @user2684 said in ๐Ÿ’ฌ NodeManager:

    @mvader thanks for the feedback, I've added this issue on Github so to fix this in the next dev release https://github.com/mysensors/NodeManager/issues/344

    Thanks!! here is the setup and loop part from the sketch

    pinMode(7, OUTPUT); // โ€œpower pinโ€ for Light Sensor
    digitalWrite(7, LOW); // switch power off
      digitalWrite(7, HIGH); // switch power on to LDR
      digitalWrite(7, LOW); // switch power off to LDR
    and the function
     * Sends Ambient Light Sensor information
     * Parameters
     * - force : Forces transmission of a value
    void sendLight(bool force) // Get light level
      if (force) lastLightLevel = -1;
      int rlightLevel =  analogRead(LIGHT_PIN);
      int lightLevel =  (analogRead(LIGHT_PIN) / 10.23) ;
      if (lightLevel != lastLightLevel) {
        lastLightLevel = lightLevel;

  • Hi, I am starting with MySensors and I read about the NodeManager. But I have a problem with starting with the nodemanager. I tried to make a node with a BMP280 sensor and a NRF24. Every time I tried I got the following error message
    when compiling (nodemanager actual version, arduino IDE1.8.5). Even no other sensor works.

    What is the reason, can anyone help me?

    Arduino: 1.8.5 (Windows 10), Board: "Arduino Nano, ATmega328P"
    "C:\Users\Radfedfdf\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.9.2-atmel3.5.4-arduino2/bin/avr-gcc-ar" rcs  "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\core\core.a" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\core\main.cpp.o"
    "C:\Users\Radfedfdf\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.9.2-atmel3.5.4-arduino2/bin/avr-gcc-ar" rcs  "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\core\core.a" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\core\new.cpp.o"
    Archiving built core (caching) in: C:\Users\RADFE~1\AppData\Local\Temp\arduino_cache_196944\core\core_arduino_avr_nano_cpu_atmega328_2c22347d3c992515700a8fa0ae8526cf.a
    Linking everything together...
    "C:\Users\Radfedfdf\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.9.2-atmel3.5.4-arduino2/bin/avr-gcc" -w -Os -g -flto -fuse-linker-plugin -Wl,--gc-sections -mmcu=atmega328p  -o "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539/NodeManager.ino.elf" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\sketch\NodeManager.ino.cpp.o" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\libraries\SPI\SPI.cpp.o" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\libraries\Wire\Wire.cpp.o" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\libraries\Wire\utility\twi.c.o" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539\libraries\Adafruit_BMP280_Library-master\Adafruit_BMP280.cpp.o" "C:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539/core\core.a" "-LC:\Users\RADFE~1\AppData\Local\Temp\arduino_build_123539" -lm
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `receive(MyMessage const&)':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:433: undefined reference to `NodeManager::receive(MyMessage const&)'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `loop':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:426: undefined reference to `NodeManager::loop()'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `setup':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:420: undefined reference to `NodeManager::setup()'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `presentation()':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:414: undefined reference to `NodeManager::presentation()'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `before()':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:408: undefined reference to `NodeManager::before()'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `__static_initialization_and_destruction_0':
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:313: undefined reference to `NodeManager::NodeManager(int)'
    C:\Users\RADFE~1\AppData\Local\Temp\arduino_modified_sketch_106015/NodeManager.ino:351: undefined reference to `SensorBMP280::SensorBMP280(NodeManager&, int)'
    C:\Users\RADFE~1\AppData\Local\Temp\cc796L4N.ltrans1.ltrans.o: In function `_GLOBAL__sub_D__Z6hwInitv':
    C:\Users\Radfedfdf\Documents\Arduino\libraries\NodeManager_Library/NodeManagerLibrary.h:564: undefined reference to `vtable for Sensor'
    C:\Users\Radfedfdf\Documents\Arduino\libraries\NodeManager_Library/NodeManagerLibrary.h:564: undefined reference to `vtable for Sensor'
    collect2.exe: error: ld returned 1 exit status
    Mehrere Bibliotheken wurden fรผr "Adafruit_BMP280.h" gefunden
     Benutzt: C:\Users\Radfedfdf\Documents\Arduino\libraries\Adafruit_BMP280_Library-master
     Nicht benutzt: C:\Users\Radfedfdf\Documents\Arduino\libraries\Adafruit_BMP280_Library
    Bibliothek NodeManager_Library im Ordner: C:\Users\Radfedfdf\Documents\Arduino\libraries\NodeManager_Library (legacy) wird verwendet
    Bibliothek MySensors in Version 2.2.0 im Ordner: C:\Users\Radfedfdf\Documents\Arduino\libraries\MySensors  wird verwendet
    Bibliothek SPI in Version 1.0 im Ordner: C:\Users\Radfedfdf\AppData\Local\Arduino15\packages\arduino\hardware\avr\1.6.21\libraries\SPI  wird verwendet
    Bibliothek Wire in Version 1.0 im Ordner: C:\Users\Radfedfdf\AppData\Local\Arduino15\packages\arduino\hardware\avr\1.6.21\libraries\Wire  wird verwendet
    Bibliothek Adafruit_Unified_Sensor in Version 1.0.2 im Ordner: C:\Users\Radfedfdf\Documents\Arduino\libraries\Adafruit_Unified_Sensor  wird verwendet
    Bibliothek Adafruit_BMP280_Library-master in Version 1.0.2 im Ordner: C:\Users\Radfedfdf\Documents\Arduino\libraries\Adafruit_BMP280_Library-master  wird verwendet
    Ungรผltige Bibliothek C:\Users\Radfedfdf\Documents\Arduino\libraries\NodeManager_mod in C:\Users\Radfedfdf\Documents\Arduino\libraries\NodeManager_mod gefunden
    exit status 1
    Fehler beim Kompilieren fรผr das Board Arduino Nano.

  • Contest Winner

    @cpl_ir super weird, looks like the linker cannot find NodeManager's object file. Are you sure all NodeManager's files are within the same directory? NodeManager cannot be installed as a standard Arduino's library but all the files need to be in the same directory of your main sketch. Thanks!

  • Hello, I have been experimenting with the door sensor example and have configured to wake up every hour to send a battery voltage (V_VOLTAGE)
    It will also wake whenever the interrupt state on the switch pin changes. I noticed that when the node wakes up with an interrupt it seems to send three events:
    V_TRIPPED (this is the important one)
    this is all good, however for my application it would be useful if it were to also send a V_VOLTAGE battery measurement along with the V_TRIPPED event.
    I'm not yet completely familiar with how the nodemanager sketch links together, but is it possible for the sensor readings for all sensors to be sent on an interrupt from any other sensor so I can make use of the radio as much as possible?

  • Contest Winner

    @arthurdented the I_POST_SLEEP_NOTIFICATION and I_PRE_SLEEP_NOTIFICATION are due to smart sleep which is on by default. Regarding the V_VOLTAGE I think what it comes closer to your need would be a SensorBattery configured with a very short reporting interval but regardless, when an interrupt occurs, no sensors other than the one associated with the interrupt would execute their main function. For your specific use case you can try changing or tweaking the condition at this line to make it working in the way you need: https://github.com/mysensors/NodeManager/blob/master/NodeManagerLibrary.ino#L4700

  • can anyone explain me the signal node? i get this values with setReportIntervalSeconds(1);

    271860 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    272947 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    274033 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    275120 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    276206 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    277293 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    278378 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    279468 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260
    280554 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967259
    281641 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967259
    282728 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967259
    283812 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967259
    284898 TSF:MSG:SEND,1-1-0-0,s=202,c=1,t=37,pt=5,l=4,sg=0,ft=0,st=OK:4294967260

  • is there a possibilty to only send values if the value has changed?

  • Contest Winner

    @felix-haverkamp the signal node is supposed to send the RSSI when the radio supports it. What you are looking at is a v1.7 bug, fixed in the dev branch of v1.8. If you want an easy fix without the need to upgrade, just remove the uint32_t cast at line 5017 of NodeManagerLibrary.ino (https://github.com/mysensors/NodeManager/blob/master/NodeManagerLibrary.ino#L5017).
    To send the values only if the value has changed, you need first of all to turn FEATURE_CONDITIONAL_REPORT on, then you can use setValueDelta() and setForceUpdateMinutes() of the Child class to achieve what you are looking for

  • @user2684
    thx, that is what was what i am looking for.

  • @user2684

    would be nice for other users to document this function. With this i am able to only send values to the gateway when its changed. Using it for a Light Sensor and dont need the value every 10 seconds and not every 10 Minutes....
    Just when it changes (1 second) and only when it changes.

  • Contest Winner

    @felix-haverkamp if you set setValueDelta() to e.g. 0.1 or 0.01, then the sensor will not report if the value has not changed, if I have understood correctly your point. setValueDelta() will set the minimum difference (+ or -) that the new value should have in order to be reported. Let me know I've misunderstood something. Thanks

  • @user2684 i just mean, we have to put this is the documentation.

    currently i have a strange problem:

    the Motion Sensors doesnt reset. I checked with my old Motion sketch and everything is fine.
    Only sends the Value "1".

    11132 TSF:MSG:SEND,1-1-0-0,s=2,c=1,t=16,pt=5,l=4,sg=0,ft=0,st=OK:1
    16513 TSF:MSG:SEND,1-1-0-0,s=2,c=1,t=16,pt=5,l=4,sg=0,ft=0,st=OK:1
    26243 TSF:MSG:SEND,1-1-0-0,s=2,c=1,t=16,pt=5,l=4,sg=0,ft=0,st=OK:1

  • Contest Winner

    @felix-haverkamp got it, thanks, I've opened this issue https://github.com/mysensors/NodeManager/issues/366.

    Regarding the sensor motion, weird, by default should attach to CHANGE interrupt so to intercept both. Any chance to share NodeManager's debug log as well? Thanks

    user2684 created this issue in mysensors/NodeManager

    closed Improve the documentation #366

  • @user2684
    i think conditional report is the problem:


    without it works fine.

  • Contest Winner

    Every new version of NodeManager, I try to review and hopefully improve its architecture. This time looked like a simple and quick task but eventually ended up in a complete and deep review of the code. Many many many things have changed with the main objective to better integrate with the MySensors library and simplify the life of users willing to contribute or to add support for new sensors.

    The new file structure (with a dedicated file for each supported sensor) and the way the package is delivered (as an arduino library now) go into this direction. There are also included a good amount of new features but still in most of the cases, resulting a smaller code.

    All the details are available at https://github.com/mysensors/NodeManager/pull/391 which will be merged into the development branch shortly.

    Due to the many changes, if anybody would be willing to give it a try and report any bug, would be really great. Thanks!

  • Just wanted to say that NodeManager is awesome. I can't believe I only now really had a better look at what it is. I always thought it was some kind of software you had to install, and that it was used by professionals to manage complicated sensor nets.

    For the last few months I've been thinking "wouldn't it be useful if there was some kind of beginner friendly web interface where you could select which devices you want, and then it creates the code for you". This is so close to that. Thank you for this incredible work!

  • Contest Winner

    @alowhum many thanks for the feedback, really appreciated!

  • Is it possible to "force" send SensorDoor value regularly?

    I am using magnetic sensor together with interrupt feature but when sensor status is change too fast before main loop is finished, sensor value remains in wrong state until magnetic sensor value is physically changed again.

    So I would like to set that SensorDoor value will be set regularly like e.g. temperature sensors values. I tried to add:


    But it does not work in this case. Value is not reported based on this interval. Only way how to get SensorDoor value back to right state is physically change its value (open/close magnetic sensors).

    Btw Nodemanager is really awsome. Great work!

  • Hi, I need some advice for my following problem..:

    Situation: Arduino ist connected to an raspberry gateway with openhab -> works just fine.
    To the arduino I have connected a PIR on 3 and a photoresistor (LDR) with an 10k resistor on A0 -> works just fine.
    On first boot (after connecting etc.) the arduino sends motion status + LDR value. But after that first msg. only the motion (tripped) is send.
    What I want: I want that the arduino sleeps until there is an interrupt comming from the PIR and then sends the motion status+light value (LDR) and then sleeps again 4ever until the next interrupt.
    Problem: As I said, it only sends the light value only once.. and then never again. On the arduino debug I can see, that only motion is send:
    NodeManager v1.7
    LIB V=2.3.0 R=N E=X T=N A=A S=S B=-
    LDR I=1 P=16 T=23
    MOTION I=2 P=1 T=16
    PRES I=1 T=16 D=LDR

    MY I=5 M=255
    INT P=3, V=0
    INT P=3 M=1
    INT P=2 M=255
    MOTION I=2 P=3 V=0
    SEND D=0 I=2 C=0 T=16 S= I=0 F=0.00
    LDR I=1 V=352 %=34 <-- first an last time LDR sends it's value
    SEND D=0 I=1 C=0 T=23 S= I=0 F=0.00
    INT P=3, V=1
    MOTION I=2 P=3 V=1
    SEND D=0 I=2 C=0 T=16 S= I=0 F=0.00
    INT P=3, V=0
    MOTION I=2 P=3 V=0
    SEND D=0 I=2 C=0 T=16 S= I=0 F=0.00
    Hope you can help me ๐Ÿ˜ฌ many thanks in advance ๐Ÿ™‚

    // General settings
    #define SKETCH_NAME "Test2"
    #define SKETCH_VERSION "1.0"
    //#define MY_DEBUG
    // NRF24 radio settings
    #define MY_RADIO_NRF24
    #define MY_SIGNING_SIMPLE_PASSWD "xxx"
    #define MY_RF24_PA_LEVEL RF24_PA_HIGH
    #define MY_RF24_CHANNEL (124)
    // Advanced settings
    #define MY_BAUD_RATE 9600
     * NodeManager modules for supported sensors
    #define USE_ANALOG_INPUT
    #define USE_INTERRUPT
     * NodeManager built-in features
    // Enable/disable NodeManager's features
    #define FEATURE_DEBUG ON
    #define FEATURE_SLEEP ON
    #define FEATURE_TIME OFF
    #define FEATURE_RTC OFF
    #define FEATURE_SD OFF
     * Load NodeManager Library
    #include "NodeManagerLibrary.h"
    NodeManager node;
     * Add your sensors below
    // Attached sensors
    SensorLDR ldr(node,A0);
    //SensorInterrupt interrupt(node,3);
    SensorMotion motion(node,3);
     * Main Sketch
    // before
    void before() {
      // setup the serial port baud rate
      * Configure your sensors below
      * Configure your sensors above
    // presentation
    void presentation() {
      // call NodeManager presentation routine
    // setup
    void setup() {
      // call NodeManager setup routine
    // loop
    void loop() {
      // call NodeManager loop routine
    // receive
    void receive(const MyMessage &message) {
      // call NodeManager receive routine
    #if FEATURE_TIME == ON
    // receiveTime
    void receiveTime(unsigned long ts) {
      // call NodeManager receiveTime routine

  • @fausti
    ok, I have solved it myself - the PIR made all that trouble.
    I did connect the PIR on 3.3V (similar to https://forum.mysensors.org/uploads/upload-4bdca27e-3c36-4c68-9e54-947b9f4717b4.jpg).

    Problem was, that when arduino wakes up the radio, the power drop would kinda restart the PIR, which causes an interrupt. Think a similar problem was discussed here:

    Anyways - you surly would have helped, if i would not have found it. Great forum! ๐Ÿ™‚

  • Contest Winner

    @jiri-hron I think you can achieve what you need by using FEATURE_TIME. In this way when woken up, NodeManager will go back to sleep only for the remainder time left. Not ideal but I couldn't find a better way to understand for how long the node has been sleeping before the interrupt.

  • It looks like there is a limit of 1 type of each sensor. Is there a way to modify this?

    My use-case is a french sliding glass door. I would like to use a single node with 2 magnetic sensors (one on each end of the node) with the node mounted in the middle of the door, so that if either side is moved the interrupt is triggered.

  • Contest Winner

    @iteafreely your understanding is correct. I see two options here: you can either create a new custom sensor inheriting from SensorDoor and adding an additional child and the extra logic you require or create two instances of SensorDoor and playing with hooking functions to make one checking on the other. In this latter case you probably need some additional variables to keep track of the status.

  • Hardware Contributor

    @iteafreely I don't think there is a limit of one sensor per type, not even for interrupts like door sensors. You just need to make sure you are using different pins and different child ids for the two magnetic sensors. I'm using 8 analog sensors (MQ-... gas sensors) on eight different pins on the same node and it works just fine.

    Of course, if you need some interdependence on what the two magnetic sensors report, then you must follow @user2684's suggestion of creating a custom sensor (a C++ class derived from an existing sensor class).
    But if you simply want two independent magnetic sensors (for each of the ends of your sliding door), then you can simply create two instances of SensorDoor on two different pins (here pins 3 and 4) and different hardcoded child_id (1 and 2 in this case):

    SensorDoor doorLeft(node,3,1);
    SensorDoor doorRight(node, 4,2);

    Unfortunately, both of them will report to the gateway with name "DOOR" (and there's no way to change it without subclassing SensorDoor), but they will have a different child_id 1 and 2 to distinguish the two values sent by the node.

    You can then use your smart home controller to handle the two door sensors like one.

  • @iteafreely Not sure of software issues as I don't use NodeManager, but your use-case indicates you do not need to know which door is opened, only that one or both is/are.
    If by magnetic sensor you mean magnet/reed, would a single reed where both doors meet, or two reeds (one on each door end) wired in parallel, to a single interrupt pin not provide this?

  • Contest Winner

    @reinhold just for completeness, that "DOOR" can be customized too by calling setDescription() of the (only) child of the SensorDoor instance. Thanks!

  • Hardware Contributor

    @user2684 Right, thanks for pointing this out. I mixed up the child name that was sent to the controller (which can be changed by e.g.

    void before() {
      doorLeft.children.get(1)->setDescription("Door Left");
      doorRight.children.get(1)->setDescription("Door Right");

    ) and the sensor's _name field, which is printed to the debug output. That "DOOR" debug output cannot be changed without subclassing. But as this is just debug output, it's just a minor nuissance.

  • Contest Winner

    @reinhold oh you're right I didn't even noticed that DOOR would show up in the debug output, thanks. Anyway with v1.8-dev this should have gone since debug output has been completely re-worked (and made compatible with https://www.mysensors.org/build/parser). Thanks

  • hello, I wanted to use the function for FEATURE_CONDITIONAL_REPORT for an LDR sensor but except a value when starting the arduino, no more values are transferred, must be configured for the function specifically something? Node manager 1.8dev

  • Contest Winner

    @mhofer a few issues came out with conditional reporting during some recent tests, https://github.com/mysensors/NodeManager/pull/430 just merged into development should have solved them. Could you please give it a try? Thanks!

  • Contest Winner

    Hello all, NodeManager v1.8 is almost ready and likewise with the previous releases I like to give brave users a few weeks to test it out before actually releasing it. If you are one of those, download it from https://github.com/mysensors/NodeManager/tree/development; for a full list of changes, have a look at https://github.com/mysensors/NodeManager/projects/2.

    Of course feel free to open a ticket on Github for any issue you could come across. Thanks!

  • Re: ๐Ÿ’ฌ NodeManager

    Hi @user2684,
    Hi all,

    First a great compliment for this work! This should make things just easy, but...
    It doesn't work for me. I have Ethernet Gateway and a 1wire Tempsensor node. Both flashed with the sketches from tutorials found on the mysensors.org website. Those are working without any problem.

    Now I have Tsl2561 Lux sensor. This is supported by nodemanager. Just downloaded the latest dev version uncommented two lines as expected, but it the node won't appear.

    The sketch looks as followed

    * 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-2017 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.
    This sketch can be used as a template since containing the most relevant MySensors library configuration settings, 
    NodeManager's settings, all its the supported sensors commented out and a sketch structure fully functional to operate with
    NodeManager. Just uncomment the settings you need and the sensors you want to add and configure the sensors in before()
     * MySensors node configuration
    // General settings
    #define SKETCH_NAME "NodeManager"
    #define SKETCH_VERSION "1.0"
    //#define MY_DEBUG
    //#define MY_NODE_ID 99
    // NRF24 radio settings
    #define MY_RADIO_NRF24
    //#define MY_RF24_CHANNEL 125
    //#define MY_RF24_PA_LEVEL RF24_PA_HIGH
    //#define MY_DEBUG_VERBOSE_RF24
    //#define MY_RF24_DATARATE RF24_250KBPS
    // RFM69 radio settings
    //#define MY_RADIO_RFM69
    //#define MY_RFM69_FREQUENCY RFM69_433MHZ
    //#define MY_IS_RFM69HW
    //#define MY_RFM69_NEW_DRIVER
    //#define MY_RFM69_NETWORKID 100
    //#define MY_DEBUG_VERBOSE_RFM69
    //#define MY_RF69_IRQ_PIN D1
    //#define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
    //#define MY_RF69_SPI_CS D2
    //#define MY_RFM69_ATC_MODE_DISABLED
    // RFM95 radio settings
    //#define MY_RADIO_RFM95
    //#define MY_RFM95_FREQUENCY (RFM95_868MHZ)
    //#define MY_DEBUG_VERBOSE_RFM95
    //#define MY_RFM95_MAX_POWER_LEVEL_DBM (20)
    //#define MY_RFM95_IRQ_PIN D1
    //#define MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
    //#define MY_RFM95_CS_PIN D8
    // RS485 serial transport settings
    //#define MY_RS485
    //#define MY_RS485_BAUD_RATE 9600
    //#define MY_RS485_DE_PIN 2
    //#define MY_RS485_MAX_MESSAGE_LENGTH 40
    //#define MY_RS485_HWSERIAL Serial1
    // Message signing settings
    //#define MY_SIGNING_SOFT
    //#define MY_SIGNING_ATSHA204
    //#define MY_SIGNING_ATSHA204_PIN 4
    // OTA Firmware update settings
    //#define OTA_WAIT_PERIOD 300
    //#define MY_OTA_RETRY 2
    // OTA debug output
    //#define MY_DEBUG_OTA (0)
    // Advanced settings
    #define MY_BAUD_RATE 9600
    // Optimizations when running on 2032 Coin Cell. Also set nodeManager.setSleepBetweenSend(500) and run the board at 1Mhz
    //#define MY_TRANSPORT_WAIT_READY_MS  5000
    //#define MY_PARENT_NODE_ID 0
     * MySensors gateway configuration
    // Common gateway settings
    // Serial gateway settings
    //#define MY_GATEWAY_SERIAL
    // Ethernet gateway settings
    //#define MY_GATEWAY_W5100
    // ESP8266 gateway settings
    //#define MY_GATEWAY_ESP8266
    //#define MY_ESP8266_SSID ""
    //#define MY_ESP8266_PASSWORD ""
    // Gateway networking settings
    //#define MY_IP_ADDRESS 192,168,178,87
    //#define MY_IP_GATEWAY_ADDRESS 192,168,178,1
    //#define MY_IP_SUBNET_ADDRESS 255,255,255,0
    //#define MY_PORT 5003
    //#define MY_GATEWAY_MAX_CLIENTS 2
    //#define MY_USE_UDP
    // Gateway MQTT settings
    //#define MY_CONTROLLER_IP_ADDRESS 192, 168, 178, 68
    //#define MY_PORT 1883
    //#define MY_MQTT_USER "username"
    //#define MY_MQTT_PASSWORD "password"
    //#define MY_MQTT_CLIENT_ID "mysensors-1"
    //#define MY_MQTT_PUBLISH_TOPIC_PREFIX "mygateway1-out"
    //#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "mygateway1-in"
    // Gateway inclusion mode
    // Gateway Leds settings
    //#define MY_DEFAULT_ERR_LED_PIN 4
    //#define MY_DEFAULT_RX_LED_PIN  5
    //#define MY_DEFAULT_TX_LED_PIN  6
     * NodeManager configuration
    // import NodeManager library (a nodeManager object will be then made available)
    #include <MySensors_NodeManager.h>
     * Add your sensors
    //PowerManager power(5,6);
    //#include <sensors/SensorBattery.h>
    //SensorBattery battery;
    //#include <sensors/SensorConfiguration.h>
    //SensorConfiguration configuration;
    //#include <sensors/SensorSignal.h>
    //SensorSignal signal;
    //#include <sensors/SensorAnalogInput.h>
    //SensorAnalogInput analog(A0);
    //#include <sensors/SensorLDR.h>
    //SensorLDR ldr(A0);
    //#include <sensors/SensorRain.h>
    //SensorRain rain(A0);
    //#include <sensors/SensorSoilMoisture.h>
    //SensorSoilMoisture soil(A0);
    //#include <sensors/SensorThermistor.h>
    //SensorThermistor thermistor(A0);
    //#include <sensors/SensorML8511.h>
    //SensorML8511 ml8511(A0);
    //#include <sensors/SensorACS712.h>
    //SensorACS712 acs712(A0);
    //#include <sensors/SensorDigitalInput.h>
    //SensorDigitalInput digitalIn(6);
    //#include <sensors/SensorDigitalOutput.h>
    //SensorDigitalOutput digitalOut(6);
    //#include <sensors/SensorRelay.h>
    //SensorRelay relay(6);
    //#include <sensors/SensorLatchingRelay1Pin.h>
    //SensorLatchingRelay1Pin latching1pin(6);
    //#include <sensors/SensorLatchingRelay2Pins.h>
    //SensorLatchingRelay2Pins latching2pins(6,7);
    //#include <sensors/SensorDHT11.h>
    //SensorDHT11 dht11(6);
    //#include <sensors/SensorDHT22.h>
    //SensorDHT22 dht22(6);
    //#include <sensors/SensorSHT21.h>
    //SensorSHT21 sht21;
    //#include <sensors/SensorHTU21D.h>
    //SensorHTU21D htu21;
    //#include <sensors/SensorInterrupt.h>
    //SensorInterrupt interrupt(3);
    //#include <sensors/SensorDoor.h>
    //SensorDoor door(3);
    //#include <sensors/SensorMotion.h>
    //SensorMotion motion(3);
    //#include <sensors/SensorDs18b20.h>
    //SensorDs18b20 ds18b20(6);
    //#include <sensors/SensorBH1750.h>
    //SensorBH1750 bh1750;
    //#include <sensors/SensorMLX90614.h>
    //SensorMLX90614 mlx90614;
    //#include <sensors/SensorBME280.h>
    //SensorBME280 bme280;
    //#include <sensors/SensorBMP085.h>
    //SensorBMP085 bmp085;
    //#include <sensors/SensorBMP180.h>
    //SensorBMP180 bmp180;
    //#include <sensors/SensorBMP280.h>
    //SensorBMP280 bmp280;
    //#include <sensors/SensorSonoff.h>
    //SensorSonoff sonoff;
    //#include <sensors/SensorHCSR04.h>
    //SensorHCSR04 hcsr04(6,7);
    //#include <sensors/SensorMCP9808.h>
    //SensorMCP9808 mcp9808;
    //#include <sensors/SensorMQ.h>
    //SensorMQ mq(A0);
    //#include <sensors/SensorMHZ19.h>
    //SensorMHZ19 mhz19(6,7);
    //#include <sensors/SensorAM2320.h>
    //SensorAM2320 am2320;
    #include <sensors/SensorTSL2561.h>
    SensorTSL2561 tsl2561;
    //#include <sensors/SensorPT100.h>
    //SensorPT100 pt100(6);
    //#include <sensors/SensorDimmer.h>
    //SensorDimmer dimmer(3);
    //#include <sensors/SensorRainGauge.h>
    //SensorRainGauge rainGauge(3);
    //#include <sensors/SensorPowerMeter.h>
    //SensorPowerMeter powerMeter(3);
    //#include <sensors/SensorWaterMeter.h>
    //SensorWaterMeter waterMeter(3);
    //#include <sensors/SensorPlantowerPMS.h>
    //SensorPlantowerPMS pms(6,7);
    //#include <sensors/SensorVL53L0X.h>
    //SensorVL53L0X vl53l0x(3);
    //#include <sensors/DisplaySSD1306.h>
    //DisplaySSD1306 ssd1306;
    //#include <sensors/SensorSHT31.h>
    //SensorSHT31 sht31;
    //#include <sensors/SensorSI7021.h>
    //SensorSI7021 si7021;
    //#include <sensors/SensorChirp.h>
    //SensorChirp chirp;
    //#include <sensors/DisplayHD44780.h>
    //DisplayHD44780 hd44780;
    //#include <sensors/SensorTTP.h>
    //SensorTTP ttp;
    //#include <sensors/SensorServo.h>
    //SensorServo servo(6);
    //#include <sensors/SensorAPDS9960.h>
    //SensorAPDS9960 apds9960(3);
    //#include <sensors/SensorNeopixel.h>
    //SensorNeopixel neopixel(6);
    //#include <sensors/SensorSDS011.h>
    //SensorSDS011 sds011(6,7);
    //#include <sensors/SensorFPM10A.h>
    //SensorFPM10A fpm10a(4,5);
    //#include <sensors/SensorPH.h>
    //SensorPH ph(A0);
    //#include <sensors/SensorPca9685W.h>
    //SensorPca9685W pca9685W;
    //#include <sensors/SensorPca9685Rgb.h>
    //SensorPca9685Rgb pca9685Rgb;
    //#include <sensors/SensorPca9685Rgbw.h>
    //SensorPca9685Rgbw pca9685Rgbw;
    //#include <sensors/SensorDSM501A.h>
    //SensorDSM501A DSM501A;
    //#include <sensors/SensorPN532.h>
    //SensorPN532 pn532;
    //#include <sensors/SensorCCS811.h>
    //SensorCCS811 ccs811;
    //#include <sensors/SensorGSM.h>
    //SensorGSM gsm(6,7);
     * Main Sketch
    // before
    void before() {
       * Configure your sensors
      // report measures of every attached sensors every 10 seconds
      // report measures of every attached sensors every 10 minutes
      // set the node to sleep in 30 seconds cycles
      // set the node to sleep in 5 minutes cycles
      // report battery level every 10 minutes
      // set an offset to -1 to a thermistor sensor
      // change the id of a the first child of a sht21 sensor
      // report only when the analog value is above 40%
      // power all the nodes through dedicated pins
      // call NodeManager before routine
    // presentation
    void presentation() {
      // call NodeManager presentation routine
    // setup
    void setup() {
      // call NodeManager setup routine
    // loop
    void loop() {
      // call NodeManager loop routine
    // receive
    void receive(const MyMessage &message) {
      // call NodeManager receive routine
    // receiveTime
    void receiveTime(unsigned long ts) {
      // call NodeManager receiveTime routine

    Now what's wrong, what's missing?

    Help is highly appreciated! Thanks


  • Did same body the port on Intel Edison? Arduino IDE is not finding SerialPort.h ?

  • Contest Winner

    @maddinthebrain sorry for the huge delay...would you mind sharing the logs? Also feel free to open an issue on https://github.com/mysensors/NodeManager/issues with the logs. Thanks!

  • Contest Winner

    Hello All, NodeManager v1.8 has just been released! I've opened up as usual a dedicated thread on the forum containing all the details of new release: https://forum.mysensors.org/topic/9944/nodemanager-v1-8-now-available

  • Question about PowerManger:
    I am a bit confused or I can't find the right information.
    I have an Ultrasonic sensor (SensorHCSR04) that needs to be only powered in case of measuring, due to power consumption.
    An the sensor needs to be switched on a time before the actual measuring starts.
    So my first approach was to switch the
    Then I set


    Where I a a bit surprised, why I need two pins (for vcc and ground)?
    At what logic level are the when the PowerManager switches to ON or OFF?
    Do I need to connect both pins, or is the vcc- connection enough?
    Anyway, somehow it did not work with me. It seemed, that the pins are not switched in that way, that pin5 goes to ground and pin 6 goes to 3,3 volt.
    So I found that thing :

    // power all the nodes through dedicated pins

    But here is no timing possible.
    Am I missing something?

  • Contest Winner

    @rpunkt you don't necessarily need to use an additional pin for ground, just set the value to -1 in case you don't need it (https://github.com/mysensors/NodeManager/blob/master/nodemanager/PowerManager.cpp#L34). The logic is when PowerManager is set, at the end of a sleep cycle, the virtual vcc pin is set to HIGH and all the sensors' loop are executed, then is set back to LOW and board goes back to sleep.
    To use it for all the sensors try just with:

    PowerManager power(5,6, 500);

    Also ensure the sensor can work with the limited current the arduino's pin is able to provide. Thanks

  • @user2684 Thanks for the advice. Now I got it running.๐Ÿ˜‹๐Ÿ™

  • @user2684
    Hello, it is me again. Going the next steps.
    Now I want to operate another sensor (SensorVL53L0X).
    this sensor should transmit the distance and the battery voltage every hour. in between it should sleep.
    The normal reporting interval of the battery is once every hour
    I set setReportIntervalHours(1); to report the sensor value.
    But how do I set the node to sleep in between?
    setSleepOrWait(True); and sleepBetweenSend(); ?
    setSleepOrWait(True); and setSleepMinutes(60); ?
    And is the NodeManager so clever that all the transmits are at the same time,
    meaning once every hour the sensor value and the battery voltage is transmitted.