Troubleshooting

@msebbe reinstall my vcc library: https://forum.mysensors.org/topic/186/new-library-to-read-arduino-vcc-supply-level-without-resistors-for-battery-powered-sensor-nodes-that-do-not-use-a-voltage-regulator-but-connect-directly-to-the-batteries

This is output from Serial Gateway with Debug turned on: 0;0;3;0;9;gateway started, id=0, parent=0, distance=0 0;0;3;0;14;Gateway startup complete. 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=15,pt=2,l=2,sg=0:1 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:1 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:0171638 0;0;3;0;9;verify fail 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:01C94B5 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=6,pt=1,l=1,sg=1:0 97;255;3;0;6;0 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:01E5044 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=11,pt=0,l=18,sg=1:Sensebender Mot 97;255;3;0;11;Sensebender Motion 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:0127A06 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=12,pt=0,l=5,sg=1:1.3.1 97;255;3;0;12;1.3.1 And this is with DEBUG and DEBUG_SIGNING turned on: 0;0;3;0;9;gateway started, id=0, parent=0, distance=0 0;0;3;0;14;Gateway startup complete. 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=15,pt=2,l=2,sg=0:1 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=15,pt=2,l=2,sg=0,st=ok:1 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:01B45E7 SIM: 015F593B6382705C14D1165A91896D854A8336D1 MSG: 61002E0011FF312E352E34 CNC: 01B45E76EEFF4F7F35A50615EBA02F23ECA22B336B6008C39BAAAAAAAAAAAAAA HMAC: CA16F9C17D683DE7074FEE542CF8B26F41200DCB4AA70072BF96CB6DAE78C5D1 SNOK: 0116F9C17D683DE7074FEE542CF8B26F41200DCB 0;0;3;0;9;verify fail 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:01E7FED SIM: 010D119CDCF58D40871D2BE7F9DF050CF2D10F956E3D5C69 MSG: 61000E2306FF00 CNC: 01E7FED0F1F7A2BFC3B8CF302DF6077DA5BC74DF6388C54F8EAAAAAAAAAAAAAA HMAC: 670D119CDCF58D40871D2BE7F9DF050CF2D10F956E3D5C6967D5DA168E46CEAC SOK 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=6,pt=1,l=1,sg=1:0 97;255;3;0;6;0 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:01E5A12 SIM: 01B22062689F9E MSG: 610096030BFF53656E736562656E646572204D6F74696F6E CNC: 01E5A122848F72F8A4D2D18F979904FDB389DC6980BD8493AAAAAAAAAAAAAAAA HMAC: 28B22062689F9E3ECC79E3E5CAD58827D1DA38C88C4DE87974C1E05CE8C8068D SOK 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=11,pt=0,l=18,sg=1:Sensebender Mot 97;255;3;0;11;Sensebender Motion 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=16,pt=0,l=0,sg=0: 0;0;3;0;9;send: 0-0-97-97 s=255,c=3,t=17,pt=6,l=25,sg=0,st=ok:011B6BD SIM: 017ABA174BDC2555F1A4BB1E2CFE844937C86442 MSG: 61002E030CFF312E332E31 CNC: 011B6BD4E168AD907C4F8596A93D78FFF19A39E39144BB3DE6AAAAAAAAAAAAAA HMAC: E67ABA174BDC2555F1A4BB1E2CFE844937C864424509AF34FA335C677A953BE7 SOK 0;0;3;0;9;read: 97-97-0 s=255,c=3,t=12,pt=0,l=5,sg=1:1.3.1 The verify fail message is consistent always there which I hardly believe can be from transmission errors?

@Dave-Dan Haven't tried it with a ethernet gw yet, as I'm using a serial gw. But there are some posts here on the forum regarding the use of node red, some of them also with hints on using ethernet gw. Use Node-Red to Allow Multiple Connections to Ethernet Gateway MyController+Domoticz at same time? nodered "injected" between domoticz and mysensors

It is working! ;D ...thank you very much! Now i understand a little bit more with MySensors ;)

@knipex what was the mistake?

It look like the issue come from the dev branch : https://forum.mysensors.org/topic/1728/uno-ethernet-shield-radio-init-fail-solved/2 Is there something i can do ?

@hek Yes, as I gathered, but I have too many sensors on 1.5.1 and don't want to upgrade them to 2.0 while its not an official release. I posted it because there are probably others on 1.5.1 with the problem, but can't find a fix. Cheers...

One solution - refer to: [https://forum.mysensors.org/topic/3894/esp8266-unexpected-crash-or-reset](link url)

Thank you both for your answers. With so many parameters to play with, it was not easy to understand what was wrong.. But I think I finally got a way do get my hardware working :) Here are my findings : I thought I got RFM73 version of NRF24-like radios. They look like like here and here. After checking and connecting all VCC and GND together, switch radios and arduinos... I got them suddenly working with Mysensors development librairies, then back to silence without apparent reason... Indeed like @mark_venn suggested, I went back to stable librairies and try so set a static ID. Worked well... until it went back to silence again ! Then, following @mfalkvidd advice, I realised that flashing the eeprom_clear sketch solved my all my problems ! My summary : Ensure that your 3.3V power supply is strong enough. Ensure that your arduino, radios and sensors are sharing the same GND and VCC. Use development librairies from github Flash eeprom_clear before flashing your mysensor sketches Then gatewaySerial and relayActuator should be able to communicate "out of box", mean you'll monitor some lines like this on the gateway serial : 0;255;3;0;9;read: 0-0-0 s=255,c=3,t=15,pt=0,l=2,sg=0: Thanks again for your help, now I can start to play :)

The cable probably has a built-in 1 port USB hub then (actually two hubs if it is according to the specs since the maximum cable length between two usb hubs also is 5m). However, the cable will probably not be able to provide full power unless the cable also has a separate power supply.

Well, it is working with a new nrf with a 10 uf cap soldered on. Can't understand why swapping for a known good one didn't work but puting in a new one did. The annoyances of building your own stuff I suppose. I will use the original one in something else and see if I can persuade it to work.

@bogdan there are no signed messages in that log (sg=0). If you want signed messages, you need to tell your node to require signed messages. What settings have you enabled in your sketch in addition to enabling signing and whitelisting? Enabling signing just tells your sketch that it can sign messages, it does not mean that the node will require others to sign messages sent to it.

I saw a commit to the DEV repo so I did a git pull this morning, started arduino and recompiled and flashed. It's working. Immediately! The fixed ip-adress was there and the the serial monitor displayed nicely the debug and node messages. The mosquitto broker receives the info which I can see using the mosquitto_sub command. It beats me, as I can't imagine the yesterday evening commit fixed it, but I'm glad it works. For reference: This morning I used the 2.2.0 esp8266 board managers version.

@hek: Thanks! It's working now. I was confused by another issue, a call to requestTime in the setup routine which seems not going out.

Great work @Ddawme, thanks for reporting back

look into installing yamon3 on your dd-wrt I have 2 of the r7000 - great routers.

i had this issue the other day too when i restarted my gateway and controller (Ethernet Gateway powered by RPi Domoticz Controller). I had to go and find and restart each of my nodes. it was rather annoying. Is there a way to broadcast somekind of remote restart command? even if the Nodes dont broadcast to the gateway, maybe the Nodes can listen for a restart command?

The RPI loses routing information when restarting (this needs to be fixed!!). So you node must send something, for routing information to re-appear. I would suggest you let your RGB node wake up every 10 second or so and do a sendHeartbeat() or some other information like temperature.

Thanks @AWI for the reply. I thought I was sending values based on the above code with the following: //Misc. variables unsigned long SLEEP_TIME =60000UL; // Sleep time between reads (in milliseconds) int sleepcycle=1; // Counter to count the amout of time not sending data int humoffset=2; // only data is send if humidity is changed for this amout int tempoffset=1.0; // only data is if temperature is changed for this amout int gwsendtimout=20; // each 20*sleep_time (20 minutes) data will be send The Temp and Humidity in the sketch is quite honestly of lower importance to me as the PIR. I believe ( please correct me if I am wrong ), but the sensor should only report every 20 minutes, and only if a temp changes by a degree or humidity changes by 2 correct? The PIR, and sensor should sleep as often as possible, but based on motion in the vicinity of the sensor, should trigger an action immediately, and based on that, could send the temp and hum readings at the same time, OR every 20 minutes if there is a change... Thanks @AWI comments welcome.

Looks like your installation of the MySensors libraries is incomplete. Try reinstalling using the instructions at https://www.mysensors.org/about/arduino#installing-the-sensor-libraries