Troubleshooting

So, now I have the same problem with a 5V pro clone. With normal bootloader: the board gets stuck in a loop with flashing LED when i try to reboot it. With MYSBootloader (1.3.0-beta.4 or 1.3.0-beta.3): unable to upload a new sketch using the FTDI cable node doesn't seem to get recognized properly by the GW or the controller. I see it's contiously sending "mysensors-out/10/255/4/0/0 FFFFFFFFFFFFFE400102" messages on MQTT, which I think is when it's checking for a new firmware, but nothing on the serial monitor. This makes it impossible to upload a new sketch OTA. Any ideas on how to troubleshoot?

Found the answer after searching most of the day!! https://forum.mysensors.org/topic/5716/solved-w5100-ethernet-gateway-with-nrf24-stable-mysensors-2-1-0-problem Thanks

Thank you so much! Well, I just made the first order for components and I have installed a test enviroment for HomeAssistant on a spare ARMBIAN board I had. I'll keep reading the forum and try to prepare myself..then I hope to be back with more practical questions :-p Thank you again for your precious help!

@blacksheepinc It is a watchdog reset, thats fix. But idk if it's software or hardware. The booting init (baud rate 115000) says it is hardware reset, but system_get_rst_info() says it is Software watchdog reset. Which is probably not true, because it resets it's GPIO states.

@mpp - No, the voltage regulator is engaged when providing power to RAW and regulates the voltages down from whatever you input to 5v. Therefore you can remove it when providing a stable power source to VCC. What happens though is that there is a drain/leakage of current even when you provide power to VCC. Therefore its good to remove it. Edit: Therefore... I love my Swedenglish...

I have one mega2560+w5100 too running with gw sketch and a bunch of sensors, so you are good to go

Great work @Rene046! Thanks for sharing your finished sketch.

It's a little complex but not bad! :+1: :D

I never got a 100% solution. I finally tried enough times. I think I turned it on with no Ethernet plugged in, let it boot, plugged in Ethernet and pressed the reset button. It may be the other way around, but it definitely involved having to use the reset button. Hope it helps, I may try to power cycle mine later and get a better procedure.

Arduino does not require a lot of current so it could have been an issue with wiring or the charger wasn't very stable

It works from an Arduino UNO clone; It's a connection error Thanks @gohan @mfalkvidd for your kind help.

I had the problem you describe, an ip address which was not the one it should be, usually a different one after each reset, sometimes with parts of the address recognisable as parts of the one I was expecting. I too tried a different W5100 module, different arduino, different connecting wires. No better. Then I found the answer, which was to supply the W5100 with 3.3v rather than the 5v I had been using. This fixed the problem completely. It is very odd that supplying the module with 5v stops it working properly, I can't explain it. It has an onboard AMS117 to convert the supply voltage to the 3.3v the chip needs. Whatever the reason though, it does fix the problem. I have two W5100 modules and neither will work properly if supplied with 5v. Both work perfectly on 3.3v. I see the instructions for the Mysensors ethernet gateway show the module supplied with 3.3v so I guess when I thought I knew better I was wrong! Hope this helps.

@gohan I missed the * in the wiring of the PA radio and wired it to the GPIO 3.3V pin; I had assumed that since the gateway was getting the one node solidly/all the time and the other nodes not at all, there must have been an issue other than power. I must say, the power issue is mentioned often enough on MySensors.org that I should have tried that solution a long time ago. Thanks again.

Trying to figure out what is wrong can be a fun challenge, and a great learning experience. I have found it mainly tedious and frustrating though, so I've decided to just throw away troublesome parts (as long as they cost less than a few dollars). :)

Dallas sensors are good. Well for incubator DHT22 should be fine, I just don't like DHT because they tend to jump values around, but yes a secondary monitor is nice to prevent roasted chicks :D

@Koresh that seems likely. I can't think of a legit way to use all those constant transmissions over the entire band. It certanly doesn't adhere to any duty cycle limitation.

@gohan said in New CHILD ID after reprogramming: #define MY_NODE_ID 5 aha MY_NODE_ID, instead of CHILD_ID :+1:

I tried with two different Dallas Onewire and checked out the library at github. Have build these sensors before but got -127 all the time. Just adding this here if it pops up alof of people having issues...