Troubleshooting

The capacitor is probably the best option to solve stability issues on nrf24

@alowhum There are some changes in V_TEXT type in latest builds. Read this: https://forum.mysensors.org/topic/9340/domoticz-v_text-sensor-now-bidirectional

Cheap clones are often a pain. Look on the store links on mysensors.org, the most expensive ones are the ones I have and work perfectly with my rpi3

@scalz Sorry, your changes fixed my OP problem with the compile errors. I forgot to follow up noting the TSP INIT fails and switching back to the old driver :(

@mfalkvidd I never thought of that, but that could indeed be the case. In domoticz there is no data timeout configured. So still cant explain why domoticz is reconnecting. @electrik i am not using MQTT with the gateway. I use still the 2.3.0 board.

As temporary workaround, you can reserve the ip you want assigned on the dhcp server configuration (I'd guess it is your wifi router)

@mfalkvidd ha thanks, I've found one of your forum post where you discuss about a code you did, and I now better understand CHILD_ID. Everything working perfectly now, thanks a lot!

How did it go?

@gohan well, switching the gateway sketch is easy to do but my node-red is based on mqtt sensors...

@hard-shovel @igork hi guys, I've just come across this thread. Not sure if you got the problem solved, if not, please let me know or open an issue on the NodeManager's github page. Thanks!

there is also the isTransportReady function that you could check before runnig any other code and if it retrns false just skip everthing and go to sleep.

Im using an 18650. currently it's sitting around 3.9v. Do you have a link to the proper "mysensors" way of handling watch dog? Im not opposed to trying it. Especially if it gets hung up trying to do something then maybe the WDT while it's awake may help.

Hi, thanks for your help, that´s the solution!!

damn it, that did the trick!! Just haven´t noticed... Thx for your superfast support!!

If you want there is mycontroller that is compatible with mqtt and supporta firmware update

@boresexpress indeed that is a common issue, but it is well known and documented that some clones are inferior and a common source for issues. But if they work for you, that's just great :)

I dont' know if it may apply to you but take a look https://forum.mysensors.org/topic/5174/solved-non-healing-tsm-msg-len-error-hours-into-run

@sindrome73 You say you don't think the problem is with MYSbootloader, and you think the problem is with the .HEX files that write the new Bootloader. Those .HEX files are MYSbootloader. Channel 76 is hard-coded in them. You can’t get round this by changing anything in your controller. If you want to create and load MYSbootloader .HEX files for a different channel then you need to modify the configuration files you mention, then compile new .HEX files. That is not a simple task, it involves multiple steps including the installation of various tools. My advice would be to get FOTA working using the default channel 76 before trying anything else.

fac13 about 2 hours ago I realized I should have added a wait after the initialization, like this: - void preHwInit() { MY_DEBUGDEVICE.begin(115200); while(!MY_DEBUGDEVICE){}; } With that included, my sketch works without needing the architecture code mod. Putting the same code in before() doesn't work. Thanks for your help.

@alexsh1 Sorry, didn't have access to my hardware lab, so got thrown off by other projects. The upcoming weekend will probably go with looking at old nasty php code, fixing issues in a 7 year old project I made for a former employer.. / Thomas