Troubleshooting

@arthur I took the liberty to press the code block button (looks like this: </> ) to make the output more readable. It looks like your /usr/include/linux/types.h file is damaged. This is what the top of that file looks on my system: pi@raspberrypi:~ $ head /usr/include/linux/types.h #ifndef _LINUX_TYPES_H #define _LINUX_TYPES_H #include <asm/types.h> #ifndef __ASSEMBLY__ #include <linux/posix_types.h> Could you post yours?

As you also suspect I think the gateway is rebooting at a regular interval. In my experience this can be due to two causes. Either due to a bug that was present in an older core arduino firmware version or due to the gateway doesn't get enough power to handle sending of messages. Sending messages requires more power than receiving messages. How did you program the gateway, ie what software and what version of software did you use? How do you power the gateway? Do you use the recommended capacitor close to the radio? See this post for info on arduino core versions with the bug: https://forum.mysensors.org/topic/6257/ethernet-gateway-home-assitant/4 It was solved in version 1.6.18.

After upgrading Wemos from 2.3.0 to 2.4.0-RC2 version, OTA works well know :smiley:

Just replace the chinese clone with a real Nordic Semiconductor module and all problems are gone!

Looks like we finally have the tools to keep spam out of the forum after upgrade. This means a little more wait time for new users to get their posts accepted. But I think it's worth it to keep the evil spammers out.

I had the gateway reboot problem since 2.1.1. After initial startup, the gateway would keep rebooting after receiving messages from nodes. After a while it seems to stabilize. I tried 2.2.0-rc.1 as you suggested and I don't see that problem any more. Thank you!

@rozpruwacz :) Actually, I considered that as the fallback solution but I do not want to increase complexity if there is a robust, simple solution.

@Johandelange I didn't look closely enough at the logs, but I think @mfalkvidd may be right. You may need to assign the node IDs manually in your code if you are using MQTT. The 47uf capacitors might be a little high, but may still work fine. On my radio nodes I typically use 4.7uf, but your situation could be different. It does seem to be working for you.

Fixed here: https://github.com/mysensors/MySensors/issues/1007

It for shore is. And what is even more strange is that adding a new manually assigned IP now is working. Can't explain it. The router is a Asus RT-AC66U.

@martijn13 great! Tanks for reporting back.

Thanks @mfalkvidd Unfortunately that ruins my theory as to what I’m observing. I will keep experimenting.

@Mister_ik make sure you're using mySensors 2.2.x development branch, as it contains some fixes for sleeping with interrupts.

Thanks so much for the suggestions!. I've changed the nrf module with another one and now I've got 4.60uA in sleep... now I'm very satisfied! Ciao Gianluca

I found the problem. In an unrelated part of the sketch I was doing an analogue read from an input set up as a digital output. This apeared to generate some sort of error state that fouled up the interface between teh Arduino and the RFM69. After removing the offending statements everything works fine.

@micmuec Again, I would suggest a HIGH-HIGH trigger just in case something goes wrong, to prevent overflow.

@nelsonov Great! There is no need to create an issue. If there is anything to discuss, we can discuss in the pull request thread. Maybe call it something like "Add MY_DEBUGDEVICE to redirect debug output"

@sineverba great that you got it working. Yes, signing require a solid radio link. It is not so much a matter of "signing is not working" but rather "radio is not working".

@vanjsy Use the sketch here - you can use it as is (change ssid and pwd of course) or add the missing pieces to yours.