@torfinn RESOLVED:
Hi ! I had problem with properly registering on the gateway ( due to chips was used on old version earlier ). After finding this post I tried the https://www.mysensors.org/build/debug#clearing-eeprom and it fixed problem. Looking at 40uA sleeping now 
@mortommy Hi ! I decided to go with 2.1.1 on new sensors but still have the old 1.5.4 gw running. Had to change frequency to #define MY_RF24_CHANNEL 125 as the 2.1.1 sensors also registered partialy ( temp not humidity ) on the old 1.5 gw.
Also tried out #define MY_REPEATER_FEATURE Disabled this seems to do the opposite what i thought. Radio is never turned off ie. 17mA drain.
Added the following to try the lower the init etc. and it improves a little.
#define MY_REGISTRATION_FEATURE Disabled
#define MY_REGISTRATION_RETRIES 1
I think its a serious flaw that if the gw for any case locks up our sensors will drain the battery until it's back online again.
This should give you a description in domoticz: present(0, S_TEMP,"A-DS18S20");
I dont know about the child id but the unit id will be the same as the number you present them with.
I dont get the whole scope of your setup but I would just have domoticz control the relays based on whatever calc you do on the temps.
Anyone got this to work with the MYSBootloader ( ref. #define MY_RF24_CE_PIN 10 #define MY_RF24_CS_PIN 9 ).
If you have working .HEX please post it.
@zen85 Thanks I got it to work but if I add #define MY_DEBUG_VERBOSE_RF24 i still get RBR:REG=23, VAL=17 filling the console....
Hi ! Got a couple of these. Hard to say if its + chip ( but I guess not ). Anyway I am not able to get them running a simple test sketch. Only get RBR:REG=23, VAL=17
@mortommy Hi ! I decided to go with 2.1.1 on new sensors but still have the old 1.5.4 gw running. Had to change frequency to #define MY_RF24_CHANNEL 125 as the 2.1.1 sensors also registered partialy ( temp not humidity ) on the old 1.5 gw.
Also tried out #define MY_REPEATER_FEATURE Disabled this seems to do the opposite what i thought. Radio is never turned off ie. 17mA drain.
Added the following to try the lower the init etc. and it improves a little.
#define MY_REGISTRATION_FEATURE Disabled
#define MY_REGISTRATION_RETRIES 1
I think its a serious flaw that if the gw for any case locks up our sensors will drain the battery until it's back online again.
@torfinn RESOLVED:
Hi ! I had problem with properly registering on the gateway ( due to chips was used on old version earlier ). After finding this post I tried the https://www.mysensors.org/build/debug#clearing-eeprom and it fixed problem. Looking at 40uA sleeping now
Hi ! Just wanted to add that this also solved it for me. I had problem with properly registering on the gateway ( due to chips was used on old version earlier ). After finding this post I tried the https://www.mysensors.org/build/debug#clearing-eeprom and it fixed problem. Looking at 40uA sleeping now
@mar.conte Hi ! Have the same problem with mysensor and NRF24l01. Tried to pull down both pins 4,5 (INT1/2) and even tried just to sleep(10000) without success. My circuit uses 17mA sending and 3,5mA when its supposed to sleep ???
Could it be board related ? I am using Arduino 1.8.1. I tried compiling with Ardino Pro / ATmega 328p 8Mhz as stock setup and now using both bootloader and setup from here: https://github.com/MCUdude/MiniCore/blob/master/README.md#boards-manager-installation
I was just thinking that maybe some of the command in the mysensors library are disabled if it detects another board setting ?
Also anyone know if the pin 2 / IRQ should be used ? Its not connected in my project could it be that mysensors is awakened by this ?
Thank's for your feedback.
Did you use the usual gw.sleep command on 1.5.4 or any other lowpower libraries ?