Hi, despite the continuous effort to make NodeManager small in size to fit into any board, when there are a few sensors registered and/or features enabled you can have issues to fit the board's memory. I'm running most of the tests on Pro Mini boards so with the same memory layout of your Nano to put myself in a worst case scenario but especially when using sensors requiring external libraries, the memory consumption could become an issue. Start by disabling NodeManager debug once you trust your code enough as a starting point but if you need all of those features all together you may also consider a board with more memory available. Thanks!

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

NodeManager v1.8 is finally here!

With 8 months of development from 12 different contributors, the new NodeManager v1.8 ships now as an Arduino library to allow an easier integration, a more consistent upgrade process across the versions and a simpler way of using it.

This version includes also a number of enhancements and bug fixes, a better integration with the MySensors library (including the capability to use the web-based Log Parser) and support for an additional 11 new sensors, with a grand total of 62 built-in sensors that can be added to your project by just a single line of code.

NodeManager v1.8 can be downloaded directly from Github https://github.com/mysensors/NodeManager where detailed installation instructions are also provided.
Please read the README file carefully before starting so to get a sense on how to use it or what has changed from the previous releases.

The full release notes for this version are listed below:

• Split NodeManager's core classes in individual files and each sensor code in its own dedicated header file
• New Arduino-compatible library structure to allow easier integration and more consistent updates across version
• Included a complete set of examples which can be loaded directly from the Arduino IDE
• Simplified the template sketch with a global nodeManager object and sensors that can be imported directly from there
• Debug output is now fully compatible with the one used by the MySensors library and integrated into MySensors LogParser
• Better control on how often, if and when to sync the time with the controller for time-aware nodes
• Added a Measure Timer so to allow splitting between taking measures and reporting
• Added support for every sensor to keep track of the last value assigned to a child in EEPROM and restoring it upon a reboot
• Introduced new capabilities for reporting every minute/hour/day or only at a given minute/hour/day
• Added ability to read from the serial port at the end of each loop cycle, useful for debugging interactive sensors
• Added support for pH sensor
• Added support for PCA9685 as RGB/RGBW/W dimmer
• Added support for DSM501A dust sensor
• Added support for PN532 NFC RFID module
• Added support for CCS811 CO2/VOC sensor
• Added support for MPR121 Capacitive Touch Sensor
• Added support for serial GSM/SMS device
• Added support for FPM10A fingerprint sensor
• Added support for SDS011 Air quality sensor
• Added support for ESP32 devices
• Added support for nRF52 radio
• Improved SensorDigitalInput and NeoPixelSensor
• Si7021 sensor is now using the library from the MySensors example
• Reviewed the MQ Sensor implementation
• Optimized memory utilization
• Added Travis Continuous Integration tests
• Fixed wrong battery report when using battery pin and SensorRain/SensorSoilMoisture
• Fixed DigitalOutput safeguard not working as expected
• Fixed radio signal level reporting wrong values
• Fixed SensorLatchingRelay2Pins wrong pin selection
• Other minor bug fixes

@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!

Hi, not sure why I didn't get a notification even if mentioned directly, sorry for that. If you send a V_TEXT message to the SSD1306 child id in the format "<row_number>,<text>" then text will be printed at row_number (https://github.com/mysensors/NodeManager/blob/development/sensors/Display.h#L99). Not necessarily ideal for your use case since at the next refresh of the display the value would be lost so if you need to better control what it is displayed, probably best would be to create your custom class inheriting from DisplaySSD1306.h and implement your logic there. Thanks!

Sorry for the delay first of all, unfortunately I didn't get the notification of this thread If you are using a latching relay I'd recommend using SensorLatchingRelay1Pin or SensorLatchingRelay2Pins which should take better all the aspects of a latching relay. Then you can still use the safeguard for closing the door after a given timeframe. And yes you have to set a reporting interval even if not intuitive at all. This is because the safeguard is checked in the loop cycle which is called only if a reporting interval is set. So if you have a safeguard set to 1 minute, the report interval should be 1 minute or less. Thanks!

@jhussain the board is the one pointed out by @mfalkvidd and as for the wiring it is very simple: the door sensor has one wire connected to pin 3 (since interrupt based) and the other to ground, the flood sensor has one connected to pin 6 (can be any) and the other to ground.

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!

@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!

@ab13akl thanks for confirming, I'll then close the issue on the NodeManager side but by keeping track of it other users facing the same problem should at least be able to identify it quicker and have a ready-to-use workaround, many thanks for sharing!