NodeManager

@nick-willis strange, I run exactly the same test and was working fine, I wonder if there was any change in the code just after messing this up. I will test it again, meanwhile if you can collect NodeManager's logs based on this configuration and share would be great. Thanks!

@rakeshpai I've got the same problem. Occasionally found out that this reproduces if DEBUG is off (#define DEBUG 0). As soon as I turned it on - it works.

I think there are some elements missing.

@gohan yes, I certainly could treat these sensors manually but of course that is more work! I think I will create a feature request on NodeManager to add a "virtual" sensor capability anyway because it would be useful and probably not that hard to build. This concept already exists for things like the battery sensor which has a pin "-1". Edit: added request for this feature as issue #257.

Referencing the enhancement request on https://github.com/mysensors/NodeManager/issues/233 Thanks!

@MCF I spent some time thinking about it and I'm afraid with the current implementation it may be a bit too hard because would require a completely different sensor and a way to share variables among the two sensors. I think https://github.com/mysensors/NodeManager/issues/198 would help solving the problem so I'd wait until that issue will be fixed. Not a quick task though since it implies a complete review of the architecture. Thanks

Thanks @user2684 for your reply, I was using the wrong package, downloaded the latest version and now it works! Thanks again for your help and for the development of NodeManager!

Sorry for the delayed answer! Referencing https://github.com/mysensors/NodeManager/issues/219 to follow the resolution which as I mentioned might be a bit more complex unfortunately :)

@ArduiSens do you have the full logs to share for the setSleepSeconds / setPowerPins issue? because from what you have posted, that 3;255;3;0;22;7368 should be a heartbeat response not the value of the temperature. Thanks!

Hi, the workaround of using a static variable is ok but of course would not necessarily work well in any situation but I'm glad you got it working somehow :). However you're right, this is a known issue in NodeManager. https://github.com/mysensors/NodeManager/issues/176 should tell you why and answer your question #2. The solution unfortunately is not that easy since would require re-thinking the way sensors are mapped to child IDs. Work is in progress though :) (https://github.com/mysensors/NodeManager/issues/198)

@jaylove thanks, CHANGE has been made the default option indeed in v1.6-dev. Btw in case you can give it a try, it would be great (https://github.com/mysensors/NodeManager/tree/development) Thanks!

@Getz99 cool, and don't worry, this is good use of the time, ensuring something which is supposed to work actually works is worth of any effort :)

@MCF no worries. Thanks for reporting the solution. and welcome to the forum :)

Thanks for your help, I'll start with Simon Monk's Programming Arduino :smile: !