Troubleshooting

@Soloam that's some great code, mind if I copy it for my nodes? // Ah, wait, that's blocking code isn't it. Not technically, with the wait() function. But it would stop the rest of my node from running until the process is complete?

@electrik Yes, I drilled a 6.5mm hole, just big enough for the SMA connector to fit through and then screwed the antenna back on. Because the plate sits inbetween the radio and antenna, and touches the outside of the SMA, it is connected to ground.

@tekka I see. Thanks for explaining.

Finally fixed as detailed here https://forum.mysensors.org/topic/10138/repeater-node-causing-problems-solved/25

Hi all I solved this issue, this is the solution: I am using wait with additional parameter to wait 1000ms OR for a specific data packet from fhem. This works well! Now i don't need to write into EEPROM, after reboot the node is requesting actual status of the relays from fhem. //request status of Relais 1 request(CHILD_ID_Rel1, V_WATT,0); wait(1000,1,2); //request status of Relais 2 request(CHILD_ID_Rel2, V_WATT,0); wait(1000,1,2); Another "enhancement": I am using the Power readings to set/reset relays and i use the status reading to get the actual status back. I guess this was the initial logic of the fhem modul, but as power only produce a "1" as setpoint, i changed it to "on,off", equal the Power reading. The primitive setup in fhem looks like thios: defmod MYSENSOR_100 MYSENSORS_DEVICE 100 attr MYSENSOR_100 DbLogExclude .* attr MYSENSOR_100 IODev mysensors attr MYSENSOR_100 mapReading_armed3 3 armed attr MYSENSOR_100 mapReading_armed4 4 armed attr MYSENSOR_100 mapReading_armed5 5 armed attr MYSENSOR_100 mapReading_level4 4 level attr MYSENSOR_100 mapReading_level5 5 level attr MYSENSOR_100 mapReading_power1 1 power attr MYSENSOR_100 mapReading_power2 2 power attr MYSENSOR_100 mapReading_status1 1 status attr MYSENSOR_100 mapReading_status2 2 status attr MYSENSOR_100 mapReading_tripped3 3 tripped attr MYSENSOR_100 mapReading_tripped4 4 tripped attr MYSENSOR_100 mapReading_tripped5 5 tripped attr MYSENSOR_100 mode node attr MYSENSOR_100 requestAck 1 attr MYSENSOR_100 room mysensor attr MYSENSOR_100 setReading_power1 on,off attr MYSENSOR_100 setReading_power2 on,off attr MYSENSOR_100 setReading_status1 on,off attr MYSENSOR_100 setReading_status2 on,off attr MYSENSOR_100 showtime 1 attr MYSENSOR_100 timeoutAlive 240 attr MYSENSOR_100 verbose 5 setstate MYSENSOR_100 alive setstate MYSENSOR_100 2019-04-22 10:54:10 R_RSSI_from_Parent -89 setstate MYSENSOR_100 2019-04-22 10:54:09 R_RSSI_to_Parent -82 setstate MYSENSOR_100 2019-04-22 10:54:11 R_TX_Powerlevel_Pct 100 setstate MYSENSOR_100 2019-04-22 10:54:11 R_TX_Powerlevel_dBm 13 setstate MYSENSOR_100 2019-04-22 10:54:12 R_Uplink_Quality -89 setstate MYSENSOR_100 2019-04-20 21:20:19 SKETCH_NAME Klingelmodul setstate MYSENSOR_100 2019-04-20 21:20:19 SKETCH_VERSION 1.1 setstate MYSENSOR_100 2019-04-22 11:01:15 heartbeat last setstate MYSENSOR_100 2019-04-22 11:01:14 level4 -93 setstate MYSENSOR_100 2019-04-22 11:01:15 level5 -88 setstate MYSENSOR_100 2019-04-20 21:20:19 parentId 0 setstate MYSENSOR_100 2019-04-21 22:49:37 power1 on setstate MYSENSOR_100 2019-04-20 21:32:44 power2 on setstate MYSENSOR_100 2019-04-22 11:01:15 state alive setstate MYSENSOR_100 2019-04-21 22:49:37 status1 1 setstate MYSENSOR_100 2019-04-20 21:32:45 status2 1 setstate MYSENSOR_100 2019-04-22 10:48:49 tripped3 off tripped3 is my Input from the Doorbell. Ok, guys, 1000 thanks for your help! BR Uwe

@neo-mod To me, the log seems to indicate that the radio connection is not working. If the HW is identical (with capacitor on the radio power connection) then I can see two causes: Faulty nRF24. Try switching the radion module Distance between node 2 and GW too far or something blocking the radio transmission. Try moving node closer to GW.

Thank you for your quick response. I changed every wire and even tried it with another sensor - still the same problem. The voltage at the pi is 3.3V. I noticed that the problem occured after I changed the pull-up resistor of the 1-wire bus from 4k7 to 2k2 (before that everything worked as intended). Is there any intern pull-up resistor that I need to change or turn off/on?

Awesome!

I'm still keen to know if there is a way to call up any logs to check why things don't work, but at this stage I've been able to get the node to work again as it should. All I needed to do was give it more power.

Imo all these messages are addressed to the GW. See https://www.mysensors.org/build/parser. Destination "0" stands for the gateway. The log parser may also help to understand what is behind your other post here. The repeater node imo just acts as kind of sniffer and puts everything that's received to serial out, regardless if repeater functionality is necessay or not.

I've created a lot of devices on Arduino Nano's with soft signing. You have to learn how to manage memory, and then it works great. A gateway on a nano with nothing in the code except it being a gateway, that should work fine. I've never seen that error message when I used the SIMPLE SECURITY option. Low memory warning might also not really be a problem in practise. If your sketch is empty, then there may not be much to worry about: there are no functions in your code that suddenly need a lot of memory. The only question then is how much MySensors needs which isn't globally defined. I don't know the answer to that, but someone else might. In the end I'd say: test it. If all seems to work ok, then there's really not a problem.

@rado-mori Please see this for answer of how mysensors work..... https://www.mysensors.org/about/network If you can make this so what you want then you are in luck. But you will be wasting time to make a system that is not mysensors enabled if you want it to be in the future. As for controller may I suggest you try https://mycontroller.org/#/home

Oh - and a side note as it seems to have slipped between the lines. I'm testing with the module on USB power, and the IR LED it always ON - it should only be on in small bursts when transmitting. And the second I disable MySensors library the sensor behaves like it is supposed to do.

@canossa That's useful to know, I am finding it to be hit and miss with this setup too. Seem to randomly lose messages going back to my MQTT gateway (most annoying for door triggers!). i'll try adding in an additional power supply to the 3.3v line and see if that helps out with stability.

My understanding is that Myscontroller can only talk to the gateway, so if the node is not connecting to the gateway it will be invisible to Myscontroller. I am trying to resolve a similar situation, where I've burnt MysBootloader to a Arduino Pro Mini and it is not connecting to the gateway.

@elcheekytico said in Node unable to find parent: Ok, Really dumb, I had MY_RFM69_IRQ_PIN connected to the radio's RESET instead of DI00. I was grasping at straws and went to re-do my antenna because they were about 3mm too short when I noticed the mis-wiring. Once I fixed that swapped 3.3v and Ground and troubleshot that for a minute before I realized it. Before trying to fix the antenna I thought maybe since I didn't have a sensor defined the battery level data wasn't enough.The node is now talking to the controller with the MockMySensors sketch. Thanks for your help guys. I cleared eeprom and went back to my battery sketch and all is well.

So here's the latest. I checked and the PI was already set to static ip and not dhcp reservation. However, I made 2 changes and have been ok for 3 days now. i changed ports on the switch. Not sure if it mattered, but i have plenty. this is the one I think may have more impact. Since it seemed the carrier was dropping, but coming back, I started wondering if maybe something was triggering an auto renegotiation for nic speed. So I went in to the switch and have it hard set to 100 FULL instead of auto. I still have the debug running and gonna let this run for quite some time just to make sure im feeling it's ok.