@rpunkt you just need to set setSleepMinutes() which will automatically put the board to sleep for the given timeframe. At the end of it, any sensor due to report at that time or before it, will do

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

#define NODEMANAGER_POWER_MANAGER ON
PowerManager power(5,6, 500);
nodeManager.setPowerManager(power);

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

@rpunkt my recommendation would be to create a custom sensor in NodeManager which is implementing the logic you like. Feel free to copy from https://github.com/mysensors/NodeManager/blob/master/sensors/SensorVL53L0X.h and create your own or make your own class by inheriting directly from SensorVL53L0X.

@rpunkt just use those directives in your sketch, no differences with NodeManager, those will be seen by the MySensors library and applied. Thanks

@ncollins thanks for the at-mention! I've just got a NRF52832 shipped so when I'll get it I will run some tests by myself. So far tests on these platforms have been based on user feedback which is ok but not ideal since couldn't really test in an extensive way. I'll keep you posted. Thanks!

@adampr1 thanks for letting me know. There are definitely a few issues with NodeManager on STM32 that need to be solved (https://github.com/mysensors/NodeManager/issues?utf8=✓&q=stm32)
and specifically for the first problem I've added a reference to the existing ticket https://github.com/mysensors/NodeManager/issues/460.
It will for definitely be fixed in the next release. Thanks!

mitchmitchell created this issue in mysensors/NodeManager

open STM32 processor does not have analog reference available, constant DEFAULT not defined #460

@getz99 I remember we had a similar issue with the display before releasing v1.8 but I was sure it was fixed. Do the values stay at 0 forever or just at the very beginning? Meanwhile I've opened https://github.com/mysensors/NodeManager/issues/469 so to track this down. Thanks

user2684 created this issue in mysensors/NodeManager

open Values not presenting in DisplaySSD1306 #469

Thanks @fredswed and @gomba777 I've added to the roadmap the capabilities you are referencing to from https://www.mysensors.org/build/pulse_water so the align with NodeManager's. I'll likely come back to you once the development will get to that point for reviewing the implementation if you don't mind. Thanks

@fredswed thanks for your analysis. I think you hit a bug here,I believe is correct that _total is set to 0 when the value is sent (so to start counting again) but it should not send that 0 value message. Keeping track with https://github.com/mysensors/NodeManager/issues/458

user2684 created this issue in mysensors/NodeManager

open SensorWaterMeter reports 0 just after reporting the value #458

@fredswed ok looks like the interrupt is intercepted and accumulated value is calculated correctly but the values are just not sent at the specified interval, right? Try calling setReportIntervalSeconds()
on waterMeter rather than nodeManager. When you call nodeManager.setReportIntervalSeconds(30), this is applied to all the sensors with a report interval not set yet. But since SensorPulseMeter already calls setReportIntervalMinutes() I believe NodeManager will skip it. Thanks