💬 NodeManager
-
Very good job @user2684 ! I like it very much.
Only one thing, how I can create a simple DHT22 node? I activated MODULE_DHT, and registered like this:/* Register below your sensors */ int sensorDHT_Id = nodeManager.registerSensor(SENSOR_DHT22,4); SensorDHT* sensorDHT = (SensorDHT*)nodeManager.getSensor(sensorDHT_Id); sensorDHT->setSamples(5); sensorDHT->setTackLastValue(true); sensorDHT->setForceUpdate(5); /* Register above your sensors */But when compiling it throws:
'DHT11' was not declared in this scopeI have the DHT library installed by the env, and a copy at the projects libraries folder (portable) and also at the same project folder (when opening the sketch also opens the library), but still complains.
??
@Sergio-Rius thanks! Are you sure you are using the DHT library from the arduino IDE ( https://github.com/adafruit/DHT-sensor-library) and not the one from the MySensors example folder? Thanks
-
@Sergio-Rius thanks! Are you sure you are using the DHT library from the arduino IDE ( https://github.com/adafruit/DHT-sensor-library) and not the one from the MySensors example folder? Thanks
@user2684
AH! You're right, you got me. I'll change and test it. Anyways the one I was using was failing frecuently reading the sensor.But you could also make your wrapper compatible with the MyS one. The difference between both is that the later places its declarations inside the class. You can make it work by fully qualifying the calls like the example:
NodeManager.cpp @1949: int dht_type = sensor_type == SENSOR_DHT11 ? _dht.DHT11 : _dht.DHT22;It could be interesting if there are anyone really needing the MyS DHT library. And also it seems more memory optimized. The adafruit's are two in one and also needs another library helper in cascade.
-
@user2684
AH! You're right, you got me. I'll change and test it. Anyways the one I was using was failing frecuently reading the sensor.But you could also make your wrapper compatible with the MyS one. The difference between both is that the later places its declarations inside the class. You can make it work by fully qualifying the calls like the example:
NodeManager.cpp @1949: int dht_type = sensor_type == SENSOR_DHT11 ? _dht.DHT11 : _dht.DHT22;It could be interesting if there are anyone really needing the MyS DHT library. And also it seems more memory optimized. The adafruit's are two in one and also needs another library helper in cascade.
@Sergio-Rius great idea! Will prevent people to get crazy with compile errors, thanks!
I'll track this with https://github.com/mysensors/NodeManager/issues/144 -
@Sergio-Rius great idea! Will prevent people to get crazy with compile errors, thanks!
I'll track this with https://github.com/mysensors/NodeManager/issues/144@user2684 Nevermid! I'm still struggling trying to make the TH sensor :sweat_smile:
That's the serial output I get and nothing at domoticz.REG I=1 P=4 P=6 T=0 REG I=2 P=4 P=7 T=1 NodeManager v1.5 INT1 M=255 INT2 M=255 RADIO OK PRES I=200, T=23 PRES I=201, T=30 BATT V=2.95 P=50 SEND D=0 I=201 C=0 T=38 S= I=0 F=2.95 PRES I=1 T=6 PRES I=2 T=7 READY MY I=3 M=1 -
@user2684 Nevermid! I'm still struggling trying to make the TH sensor :sweat_smile:
That's the serial output I get and nothing at domoticz.REG I=1 P=4 P=6 T=0 REG I=2 P=4 P=7 T=1 NodeManager v1.5 INT1 M=255 INT2 M=255 RADIO OK PRES I=200, T=23 PRES I=201, T=30 BATT V=2.95 P=50 SEND D=0 I=201 C=0 T=38 S= I=0 F=2.95 PRES I=1 T=6 PRES I=2 T=7 READY MY I=3 M=1@Sergio-Rius ok, this is kind of a standard startup with the temperature and humidity sensors presented as child 1 and 2, so far so good.
PRES I=1 T=6 PRES I=2 T=7By default no data is reported unless the node enters in a cycle. You would like to add:
nodeManager.setSleep(SLEEP, 10, MINUTES);Or
nodeManager.setSleep(WAIT, 10, MINUTES);To start getting periodically the data out. Alternatively you can send a REQ message to the child id with the appropriate V_type
-
@Sergio-Rius ok, this is kind of a standard startup with the temperature and humidity sensors presented as child 1 and 2, so far so good.
PRES I=1 T=6 PRES I=2 T=7By default no data is reported unless the node enters in a cycle. You would like to add:
nodeManager.setSleep(SLEEP, 10, MINUTES);Or
nodeManager.setSleep(WAIT, 10, MINUTES);To start getting periodically the data out. Alternatively you can send a REQ message to the child id with the appropriate V_type
@user2684 Mmmmm what if you have a motion sensor in the same node? (I'm trying to migrate my own sketch)
-
@user2684
AH! You're right, you got me. I'll change and test it. Anyways the one I was using was failing frecuently reading the sensor.But you could also make your wrapper compatible with the MyS one. The difference between both is that the later places its declarations inside the class. You can make it work by fully qualifying the calls like the example:
NodeManager.cpp @1949: int dht_type = sensor_type == SENSOR_DHT11 ? _dht.DHT11 : _dht.DHT22;It could be interesting if there are anyone really needing the MyS DHT library. And also it seems more memory optimized. The adafruit's are two in one and also needs another library helper in cascade.
@Sergio-Rius said in 💬 NodeManager:
The difference between both is that the later places its declarations inside the class.
Please don't waste your time as they are not compatible. In my stupidity didn't make sure that my lib wasn't "personalized".
What a pity. -
@user2684 Mmmmm what if you have a motion sensor in the same node? (I'm trying to migrate my own sketch)
@Sergio-Rius yes, you can have a motion sensor on the same node as far as it is a sleeping node. This is because the interrupt is coming from the MySensors sleep() call. Having this compatibility in a non sleeping node is instead only planned (https://github.com/mysensors/NodeManager/issues/142)
-
Hi, I would like to have smartSleep for my nodes. I read that NodeManager can do that. But I couldn't find an explanation how it is doing it. I use OpenHAB as the controller and MQTT to communicate to the MySensors-Gateway. Is smartSleep working for this scenario? Did you extend the Gateway?
-
Hi, I would like to have smartSleep for my nodes. I read that NodeManager can do that. But I couldn't find an explanation how it is doing it. I use OpenHAB as the controller and MQTT to communicate to the MySensors-Gateway. Is smartSleep working for this scenario? Did you extend the Gateway?
@strangeoptics NodeManager does use smart sleep by default. The way it works (with or without node manager) is pretty simple: when the node tells the gw/controller is about to go to sleep, it actually wait (by default 500ms I think) for new messages before powering off the radio and going to sleep. Useful if you have a sleeping node and want to communicate with it. Im not familiar with those controllers but I'm sure others are but generally speaking the way it works is the controller usually queue your messages and when the node checks in release the queue.
-
@strangeoptics NodeManager does use smart sleep by default. The way it works (with or without node manager) is pretty simple: when the node tells the gw/controller is about to go to sleep, it actually wait (by default 500ms I think) for new messages before powering off the radio and going to sleep. Useful if you have a sleeping node and want to communicate with it. Im not familiar with those controllers but I'm sure others are but generally speaking the way it works is the controller usually queue your messages and when the node checks in release the queue.
@user2684 If I understand it correct, NodeManager is basically using the smartSleep method of the MySensors library and extended it with a default delay of 500ms after the heart beat message.
The logic for queuing the messages inbetween the wakeup periods is not implementet from NodeManager and has to come from the controller. In my case OpenHAB hasn't got the logic and smartSleep wouldn't work :( -
@user2684 If I understand it correct, NodeManager is basically using the smartSleep method of the MySensors library and extended it with a default delay of 500ms after the heart beat message.
The logic for queuing the messages inbetween the wakeup periods is not implementet from NodeManager and has to come from the controller. In my case OpenHAB hasn't got the logic and smartSleep wouldn't work :(@strangeoptics not really, node manager is not extending smart sleep at all, smart sleep from the core MySensors library by itself is implemented with this delay :)
-
@strangeoptics not really, node manager is not extending smart sleep at all, smart sleep from the core MySensors library by itself is implemented with this delay :)
@user2684 so which controler are you using?
-
@user2684 so which controler are you using?
https://www.mysensors.org/controller/myhouse but since I wrote it, my opinion would be biased :P
-
Hi
I have a led ir emitter can i send to my air contiotioner a code like x0284828 by digital output in nodemanager(with irremote library is simple)@mar.conte mmm not sure I got the use case. I think we need some sort of "IR" specific output. Btw if you prefer, feel free to open a new thread on https://forum.mysensors.org/category/43/nodemanager
-
Hi, nice work!
I have changed the code for REBOOT so there is no need for a reboot-pin.
like this...else if (strcmp(message, "REBOOT") == 0) {
#if DEBUG == 1
Serial.println(F("REBOOT"));
#endif
// Software reboot with watchdog timer
// Enter Watchdog Configuration mode:
WDTCSR |= (1<<WDCE) | (1<<WDE);
// Reset enable
WDTCSR= (1<<WDE);
// Infinite loop until watchdog reset after 16 ms
while(true){}
}Hi @Dencan @core_c I'm having trouble with both the solutions you recommended. When the reboot code is triggered, I have my pro mini 3.3v board freezing with the power led blinking continuously (https://github.com/mysensors/NodeManager/issues/133). Do you guys know what the issue could be? Thanks!
-
Hi @Dencan @core_c I'm having trouble with both the solutions you recommended. When the reboot code is triggered, I have my pro mini 3.3v board freezing with the power led blinking continuously (https://github.com/mysensors/NodeManager/issues/133). Do you guys know what the issue could be? Thanks!
@user2684 It appears that this problem is caused by a bug in bootloaders used in some Arduino boards.
The solution suggested is to flash optiboot bootloader to the Arduino Pro Mini. Or not using a bootloader.
I use mostly barebone atmega328's with optiboot bootloader, working perfectly with reboot function, so I haven't been aware of the problem until now when I used a pro mini.
Please read this article which explains the cause of the problem and suggested fix.
https://andreasrohner.at/posts/Electronics/How-to-make-the-Watchdog-Timer-work-on-an-Arduino-Pro-Mini-by-replacing-the-bootloader/I will try it on a pro mini when I have time.
-
@user2684 It appears that this problem is caused by a bug in bootloaders used in some Arduino boards.
The solution suggested is to flash optiboot bootloader to the Arduino Pro Mini. Or not using a bootloader.
I use mostly barebone atmega328's with optiboot bootloader, working perfectly with reboot function, so I haven't been aware of the problem until now when I used a pro mini.
Please read this article which explains the cause of the problem and suggested fix.
https://andreasrohner.at/posts/Electronics/How-to-make-the-Watchdog-Timer-work-on-an-Arduino-Pro-Mini-by-replacing-the-bootloader/I will try it on a pro mini when I have time.
@Dencan thanks, very good information. Based on what you are saying, I'd probably re-introduce the reboot pin as a backup solution just in case somebody doesn't want or can move away from the default bootloader. In this way both the approaches will be available. Thanks!
