@Nicklas-Starkel
After some reading and thinking, I came to a very similar conclusion. There are tons of parameter which will influence the mesurement.
I am planning to use four or five moisture probes distributed at various places in my garden for irrigation automatisation. I guess my lawn will not suffer if I start watering at a reading of 41 % instead of 44 %
During the upcoming winter months there is enough time to gather empirical data about the behaviour of my probes.
Anyway, it's a fun project ...

Hello,
I am relatively new to MySensors and now trying to get my first sensor up. My serial gateway runs on an Arduino Uno, which is connected to a Raspbery Pi 2. So far, so good.
I am now trying to prototype a temperature/humidity sensor with a DYPTH01.
I get a bunch of debug output from the gateway and from the sensor (also on a Uno) , with quite a few of "fail", so I guess that something is wrong. Now I am trying to find out what is wrong ...K
I have searched quite a bit, but I was not successful to find any documention on how to interpret the debug output. May I ask a kind soul to please point me to a description ? Or have I really browse through the source code of MySensors ?
Any help is highly welcome. Thanks a bunch in advance.
Cheers,
Josh

@korttoma
OK, after some fiddling I was able to exchange mysensors V2.0 with V1.5.4 and to compile mfalkvidd's sketch. I will adapt it now to my hardware (removing references to LED etc) and give it a twirl. Please be patient, since I need to run it at least a coupl eof days to see if there is a difference in power consumption.
Very interesting stuff

@rvendrame
Thank you very much for your reply. I know that part of the documentation quite well, since I have written a serial gateway emulator to send sensor data, which is collected locally on the Raspberry Pi to the controller (Domoticz). My question relates to the other stuff, which looks like 0-0-255-255 pt=7 c=3 etc. My guess is that this is the debug information, whereas the other stuff (0;0;3;9; as an example) is the serial gateway protocol. I would like to know the meaning of the debug messages, because I think these may be useful to help me in debugging my code.

Thanks a lot again
Josh

@Nicklas-Starkel
Strange ...
But since I am not missing / using any of the advanced features offered by V 2.0, I don't see a problem (at least for now) to stick with V 1.5.4
In any case it is amazing what you can do with low power battery poweroperated sensors.

Just to give a feedback on power consumption: I have switched back to mysensors V 1.5.4. This was roughly one month ago. I take meadurements every two hours. Battery voltage hasn't changed a bit since then. So my guess is, that - for whatever reason - mysensors V 2.0 seems to produce a more power hungry code.
Whatever ...
I am happy now and will stick with V 1.5.4
I am

@Nicklas-Starkel
After some reading and thinking, I came to a very similar conclusion. There are tons of parameter which will influence the mesurement.
I am planning to use four or five moisture probes distributed at various places in my garden for irrigation automatisation. I guess my lawn will not suffer if I start watering at a reading of 41 % instead of 44 %
During the upcoming winter months there is enough time to gather empirical data about the behaviour of my probes.
Anyway, it's a fun project ...

@korttoma
OK, after some fiddling I was able to exchange mysensors V2.0 with V1.5.4 and to compile mfalkvidd's sketch. I will adapt it now to my hardware (removing references to LED etc) and give it a twirl. Please be patient, since I need to run it at least a coupl eof days to see if there is a difference in power consumption.
Very interesting stuff

@korttoma
OK, thanks for the hint. I will try if I can get this version work with the Arduino version I am using.

@mfalkvidd
I think that in a previous post you mentioned that you are using mysensors V1.6, right ? Where did you get it from ? On the mysensors pages I only found references and links to V1.4 and V1,5, not V1.6. I would like to try to remove V2.0 from my system and switch to V1.6 - no idea if this will work ...
I would like to use a setup as close as possible to yours to track down the problem. Your very low power consumption is really amazing and I would like to come as close as possibe to int in my case. I have a 'clone' of your hardware setup described in openhardware.io - minus the LED. So in my case, power consumption should be even lower than yours

@mfalkvidd, @Nicklas-Starkel
similar problem here. I have a bare ATMega 328P, running @ 8 MHz internal oszillator. no LED, bod disabled, (if enabled, the ADC is running also during sleep, so this means additional power consumption), nothing else connected that could draw additional power.
I use mfalkvidd's sketch (BTW, thanks a lot for it !), but converted to mysensors 2.0. I see a voltage drop way higher than mfalkvidd, although I don't use a china clone ;-).
So it seems, that the higher power consumption may be due to mysensors V2 ? I cannot imagine a reason for that, because why should relatively low level functions like power save routines be different in 2.0 ?
Perhaps hek can comment ?

@hek said:

@joshmosh said:

Would

gw.begin(incomingMsg, MY_NODEID, true)
turn this node into a working repeater ?

Yes, this enables the repeater feature.
OK,thank you. This will save me an additional node..
Cheers
Josh

Hi,
I have a similar problem and would like to use an already existing node as a repeater. It does not run from battery, so no problem here.

But I have incoming messages which this node needs to react on. In the code, I check if the incoming message has a child id known by this node. If not, nothing happens. In addition, I am using static node IDs.

So, instead of

gw.begin(NULL,  AUTO, true)

my current initialisation is

gw.begin(incomingMsg, MY_NODEID, false)

because it currently does not act as a repeater.

Would

gw.begin(incomingMsg, MY_NODEID, true)

turn this node into a working repeater ?

Most of the time this node is idle. Every five minutes it reads temperature and humidity and sends it off to the controller. A few times per day it turns some switch on or off. My guess is that the additional workload for repeating messages would not be too high.

Thank you very much for your input.
Cheers
Josh

@Yveaux said:

@joshmosh You cannot have multiple gateways in a single MySensors network. The node-ID of the gateway is always hardcoded to 0.
If you want to run multiple networks, each should have a unique RF24_CHANNEL & RF24_BASE_RADIO_ID combination. For best results make sure to have a separate RF24_CHANNEL for each network, and don't use directly adjacent channels.

@Yveaux
Thank you for this piece of information - I was not aware of this fact.
My idea was to reduce cost and parts count for sensors by using ESPs instead of nRF plus Arduino. Since I have Domoticz as controller, there is pehaps no need for an additional gateway, because Domoticz can handle TCP-attached sensors. Of course this would require to use WiFi instead of nRF24 as underlying transport for MySensors. My interpretation of some of hek's contributions is that he is working on it for realisation in version 1.6.