@Homer :blush: :blush: I take care to say Good morning Sir, and Thank you Sir... You never know when it comes back to bite my tail.

I had a unique challenging experience recently, where I needed urgent help and posted my issue here on the forum without much luck. When I didnt get help I resorted to AI, and I got the help I needed immediately. I didn't have to pay a dime for the services. in less than 1hour, I had all my issues resolved and everything working fine again.

I started with Googles Gemini. but progressed to Microsoft s CoPilot.

I just treated AI like you would an individual, introducing my issues and requesting for specific help with code and step by step guidance, I then shared Log Outputs and it refined its analysis and supplied the needed code. It was a highly rewarding experience for me. I even proceeded to giving it some challenging projects that I have been working on and it solved all of them.

So if you are a mere moonlighting tinkerer like me, someone who doesn't necessarily want to be an expert in these things. If you just want the fix the issue and not border with the need to understand the technicalities, use AI. I recommend MS CoPilot, as it simplifies everything and keeps you in the loop. Germini tends to run round in circles after a while. In fact at one point it gave up and told me it couldn't solve the issue, but I pressed it on by requesting that it tries other solutions. When I find it straying away, I constrained it by asking specifics. At the end, I got exactly what I wanted.

What is the future of a forum like this one with AI. Is MySensors looking to deploy AI with Chat Bots to help out with inquiries here? How long before people discover that they have an expert by their side all along?

What do you think?

Once again I am replying myself... :confounded: :confounded: :confounded: :confounded:

What that clearly shows is that people are either too busy to help, or they are tired of people like me, asking obvious questions that have been treated so many times elsewhere on this same discussion forum. Again, that is not their fault - most people here are volunteers and they all have pressing issues to deal with other than solving your problem!

Goodnews, Is that I have solved all my problems,:blush: :blush: not without help from an expert though. I know you all want to know Where did I find help? An expert versed in MySensors, Linux, C++, Domoticz and MQTT? ... you will never believe where I found help.

...

... wait for it

...

Right here on the internet! And I didn't have to pay a dime for his services. in less than 1hour, I had all my issues resolved and everything working fine again. Who hlped me?

Artificial Intelligence AKA AI - I started with Googles Gemini. but progressed to Microsoft s CoPilot.

Just treated AI like an individual, introducing my issues and requesting for specific help with code and step by step guidiance, I then shared Log Outputs and it refined its analysis and supplied the needed code. It was a highly rewarding experience for me. I even proceeded to giving it some challenging projects that I have been working on and it solved all of them.

So if you are a mere moonlighting tinkerer like me, someone who doesn't necessarily want to be an expert in these things. If you just want the fix the issue and not border with the need to understand the technicalities, use AI. I recommend MS CoPilot, as it simplifies everything and keeps you in the loop. Germini tends to run round in circles after a while. In fact at one point it gave up and told me it couldn't solve the issue, but I pressed it on by requesting that it tries other solutions. When I find it straying away, I constrained it by asking specifics. At the end, I got exactly what I wanted.

Food for thought, What would the future of forums like this be with AI at our finger tips and beck? :face_with_thermometer:

Thanks @nagelc at least I know I am not blinking in the dark...

Again, I am replying myself... :confused:

I spent long hours looking through the whole thing. I have a kind vague diagnosis: I replaced the Sleep(1000); in the loop with wait(0); to keep the node perpetually awake ensuring it doesn't miss out on the GW's responds - but this didn't make a difference.

I also ensured both Node and GW were running the same MS version. That also didn't change anything. for now, I know that;

• My nodes are successfully transmitting "Find Parent Request" messages.
• My Gateway is successfully receiving their messages.
• My Gateway is then attempting to respond to the Nodes.
• However, Nodes are not receiving (or acknowledging) those responses from the gateway, leading to the "NO REPLY" on the node and "NACK:0" on the gateway.
• Power is not an issue
• Hardware is also not an issue as I have swooped 2 other NRF24's (making it a total of 3 radios) and I still get the same result
• I have even looked online to see if anyone has had a similar challenge after upgrading to Bullseye, but I can find any.

If I dont get expert help soon, my next plan is to consult AI... but that would be another day.

I need to rest my poor head... :bow:

Okay I tried again to set VERBOSE on a node and get the output and

 16 MCO:BGN:INIT REPEATER,CP=RNNRA---,FQ=16,REL=255,VER=2.3.2
27 TSM:INIT
28 TSF:WUR:MS=0
29 RF24:INIT:PIN,CE=9,CS=10
32 RF24:SBY
33 RF24:WBR:REG=0,VAL=14
39 RF24:WBR:REG=3,VAL=3
43 RF24:WBR:REG=4,VAL=95
45 RF24:WBR:REG=5,VAL=76
47 RF24:WBR:REG=6,VAL=37
49 RF24:WBR:REG=29,VAL=4
51 RF24:RBR:REG=29,VAL=4
54 RF24:RBR:REG=6,VAL=37
56 RF24:RBR:REG=5,VAL=76
58 RF24:WBR:REG=2,VAL=2
60 RF24:WBR:REG=1,VAL=0
62 RF24:WBR:REG=28,VAL=3
65 RF24:FRX
66 RF24:FTX
67 RF24:WBR:REG=7,VAL=112
69 TSM:INIT:TSP OK
71 TSM:INIT:STATID=5
73 RF24:WBR:REG=2,VAL=3
75 RF24:WBR:REG=1,VAL=1
77 RF24:STL
78 RF24:WBR:REG=0,VAL=15
80 RF24:WBR:REG=10,VAL=5
82 TSF:SID:OK,ID=5
84 TSM:FPAR
86 RF24:SPL
87 RF24:WBR:REG=0,VAL=14
90 RF24:OWP:RCPT=255
92 RF24:WBR:REG=10,VAL=255
94 RF24:WBR:REG=16,VAL=255
96 RF24:TXM:TO=255,LEN=7
99 RF24:FTX
100 RF24:WBR:REG=4,VAL=80
104 RF24:WBR:REG=7,VAL=112
107 ?RF24:TXM:MAX_RT
108 RF24:FTX
110 RF24:WBR:REG=4,VAL=95
112 RF24:STL
113 RF24:WBR:REG=0,VAL=15
116 RF24:WBR:REG=10,VAL=5
118 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2125 !TSM:FPAR:NO REPLY
2127 TSM:FPAR
2128 RF24:SPL
2129 RF24:WBR:REG=0,VAL=14
2132 RF24:OWP:RCPT=255
2135 RF24:WBR:REG=10,VAL=255
2138 RF24:WBR:REG=16,VAL=255
2140 RF24:TXM:TO=255,LEN=7
2143 RF24:FTX
2144 RF24:WBR:REG=4,VAL=80
2149 RF24:WBR:REG=7,VAL=112
2151 ?RF24:TXM:MAX_RT
2153 RF24:FTX
2155 RF24:WBR:REG=4,VAL=95
2157 RF24:STL
2158 RF24:WBR:REG=0,VAL=15
2161 RF24:WBR:REG=10,VAL=5
2163 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4171 !TSM:FPAR:NO REPLY
4173 TSM:FPAR
4174 RF24:SPL
4176 RF24:WBR:REG=0,VAL=14
4178 RF24:OWP:RCPT=255
4180 RF24:WBR:REG=10,VAL=255
4184 RF24:WBR:REG=16,VAL=255
4186 RF24:TXM:TO=255,LEN=7
4189 RF24:FTX
4190 RF24:WBR:REG=4,VAL=80
4195 RF24:WBR:REG=7,VAL=112
4197 ?RF24:TXM:MAX_RT
4199 RF24:FTX
4201 RF24:WBR:REG=4,VAL=95
4203 RF24:STL
4204 RF24:WBR:REG=0,VAL=15
4207 RF24:WBR:REG=10,VAL=5
4209 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6217 !TSM:FPAR:NO REPLY
6219 TSM:FPAR
6220 RF24:SPL
6222 RF24:WBR:REG=0,VAL=14
6224 RF24:OWP:RCPT=255
6226 RF24:WBR:REG=10,VAL=255
6230 RF24:WBR:REG=16,VAL=255
6232 RF24:TXM:TO=255,LEN=7
6235 RF24:FTX
6236 RF24:WBR:REG=4,VAL=80
6241 RF24:WBR:REG=7,VAL=112
6243 ?RF24:TXM:MAX_RT
6245 RF24:FTX
6247 RF24:WBR:REG=4,VAL=95
6249 RF24:STL
6250 RF24:WBR:REG=0,VAL=15
6253 RF24:WBR:REG=10,VAL=5
6255 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8263 !TSM:FPAR:FAIL
8264 TSM:FAIL:CNT=1
8266 TSM:FAIL:DIS
8268 TSF:TDI:TSL
8269 RF24:SLP
8271 RF24:WBR:REG=0,VAL=12

So after plugging this into the Phaser - I can read the log output.

8264 TSM:FAIL:CNT=1             // means Disable transport
8266 TSM:FAIL:DIS               // means Set transport to sleep

see that the Node is disabling the Transport, and turning off the NRF24. So how do I wake it up? Does this have to do with the Interrupt? IRQ Pin and all that?

Help please, Help @buxtronix everyone! Anyone!!

Thanks for your response @buxtronix . Please indulge me cos I am not an expert. I am just a tinkerer who dared to build this project and enjoyed it for years now.

The Software on the Node side remained as is. I haven't touched any of them after the Bullseye Operating System was installed.

Concerning the your debug suggestion, I have defined Verbose [ verbose=debug ] in the /etc/mysensors.conf. Does this address what you meant or should I do more.

The only things that has changed is that I changed Serial gateway from --my-serial-pty=/dev/ttyUSB020 which I couldn't select in Domoticz, so I changed it to --my-serial-port=/dev/ttyAMA0 and ./Configured with that. Could this be the culprit? If so, do I need to revisit each node to point things to the ttyAMA0 virtual Serial Port?

Lastly, how can I deal with the eeprom? Perhaps that is where the real problem stopping me from selecting the default ttyUSB020 serial port. What will happen if I erased the epprom. Will it return to the default when i make and install?

Five years ago, during the pandemic, I upgraded my Nano - MySensors Serial Gateway to a all-in-one Raspberry Pi running MySensors - Domoticz and Mosquitto Broker. I faced a challenge and got help from many kind hearted users here.. I have been using the Gateway and Nodes without incidence until last week, when I happened to upgrade the OS from Buster - Bullseye

regrettably, everything seem to stop working. I have tried without luck to get everything working again. I have uninstalled and successfully reinstalled Domoticz, MQTT, but MySensors continue to not acknowledge the registration of all nodes. I need some serious help. here is a brief of my setup.

• Rasberry Pi 3. MySensors Gateway - Running Domotics and Mosquitto MQTT.
• I used the Development branch for my git clone
• I configured with

./configure --my-transport=rf24 --my-gateway=serial --my-serial-is-pty --my-serial-port=/dev/ttyAMA0 --my-rf24-irq-pin=15 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18 --my-rf24-ce-pin=22

• I enabled SPI in the Raspi.config
• I ran Make and Make Install
• My log from tail -f /var/log/syslog shows

Jul 15 16:19:32 IoTGateway mysgw[328]: TSF:MSG:BC
Jul 15 16:19:32 IoTGateway mysgw[328]: TSF:MSG:FPAR REQ,ID=2
Jul 15 16:19:32 IoTGateway mysgw[328]: TSF:CKU:OK,FCTRL
Jul 15 16:19:32 IoTGateway mysgw[328]: TSF:MSG:GWL OK
Jul 15 16:19:32 IoTGateway mysgw[328]: !TSF:MSG:SEND,0-0-2-2,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:MSG:READ,3-3-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:MSG:BC
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:MSG:FPAR REQ,ID=3
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:PNG:SEND,TO=0
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:CKU:OK
Jul 15 16:19:58 IoTGateway mysgw[328]: TSF:MSG:GWL OK
Jul 15 16:19:58 IoTGateway mysgw[328]: !TSF:MSG:SEND,0-0-3-3,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0

By the way the hardware is still the same as before

please forgive my poor soldering skills.

What am I doing wrong? Why wont the Gateway accept the Parent requests from the Nodes? Please can someone help - Calling on the experts that have helped me in the past @mfalkvidd @hek @electrik @TheoL @eiten save a grieving soul :cold_sweat:

@zookazim so sorry I haven't been on here in years. I actually left the IoT nodes for a while. I was running into so many issues. To answer your question... not sure if it's still required or even relevant.

@mfalkvidd so how do I change the title to reflect "SOLVED"?

I have good news. I used a small prototype board for everything. made sure no line was more than 6 inches long. I soldered (My soldering sucks!) the capacitator right next to the radio and Bahm! Domoticz picked up all powered devices. :grinning:

Lessons learnt, keep length of your wires short, nRf24 MUST have a decent capacitator to smoothen out power. Don't rely on GPIO pins to power it, use a regulator. Though help may come from all and sundry, its all up to you to check their suggestions... Thanks all for helping me.

I can finally retire my Nano-Serial Gateway! Wont be upgrading for a long time to come :sneezing_face:

@eiten l think it's A+ it has Wifi and l run it "headless" with my old Nano Gateway connected to the 1 USB. But I'll looking forward to getting the Pi to work as both Gateway and Controller.

I want to use a prototype board and drop the long lines. Plus I'll also bring the cap closer to the nrf24 to see if that helps.

@nono8223 I've this same problem... stock for days. I tried powering the radio directly with a 3.3volts regulator and capciator between GND and 3.3V pin of the nrf24 but still no luck.

I don't want to duplicate posts but the details of my issue can by found here
@Eme said in MySensors Raspberry Pi Gateway + Domotics Controller:

Please someone help me...

@eiten Don't know if the Pi model matters. I used a Pi Model A with wifi.

@eiten Yes what does that mean in English: :blush:

@eiten based on the suggestions "leaning towards" powering the rf24 from you and @mfalkvidd l fed the radio a regulated 3.3 with LD33V and l also brought the capacitator near the radio... yet I still cant register the nodes.

Pls what does "TSF:CKU:OK:FCTRL" mean?

Thanks @eiten I thought I already shared that. I just hooked Node 5 to the laptop to get its log...

 
 __  __       ____
|  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
|_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
        |___/                      2.3.2

16 MCO:BGN:INIT REPEATER,CP=RNNRA---,FQ=16,REL=255,VER=2.3.2
27 MCO:BGN:BFR
28 TSM:INIT
29 TSF:WUR:MS=0
36 TSM:INIT:TSP OK
38 TSM:INIT:STATID=5
40 TSF:SID:OK,ID=5
41 TSM:FPAR
46 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
764 TSF:MSG:READ,2-2-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
770 TSF:MSG:BC
1880 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
1884 TSF:MSG:BC
2053 !TSM:FPAR:NO REPLY
2055 TSM:FPAR
2059 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2810 TSF:MSG:READ,2-2-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
2816 TSF:MSG:BC
3924 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
3930 TSF:MSG:BC
4066 !TSM:FPAR:NO REPLY
4068 TSM:FPAR
4072 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4845 TSF:MSG:READ,2-2-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
4850 TSF:MSG:BC
5971 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
5977 TSF:MSG:BC
6079 !TSM:FPAR:NO REPLY
6081 TSM:FPAR
6085 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6887 TSF:MSG:READ,2-2-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
6892 TSF:MSG:BC
8008 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
8013 TSF:MSG:BC
8092 !TSM:FPAR:FAIL
8093 TSM:FAIL:CNT=1
8095 TSM:FAIL:DIS
8097 TSF:TDI:TSL
18099 TSM:FAIL:RE-INIT
18101 TSM:INIT
18107 TSM:INIT:TSP OK
18109 TSM:INIT:STATID=5
18112 TSF:SID:OK,ID=5
18114 TSM:FPAR
18118 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20059 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
20064 TSF:MSG:BC
20125 !TSM:FPAR:NO REPLY
20127 TSM:FPAR
20131 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
22094 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
22099 TSF:MSG:BC
22140 !TSM:FPAR:NO REPLY
22142 TSM:FPAR
22147 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
24135 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
24140 TSF:MSG:BC
24155 !TSM:FPAR:NO REPLY
24157 TSM:FPAR
24161 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
26169 !TSM:FPAR:FAIL
26170 TSM:FAIL:CNT=2
26172 TSM:FAIL:DIS
26174 TSF:TDI:TSL
36177 TSM:FAIL:RE-INIT
36179 TSM:INIT
36186 TSM:INIT:TSP OK
36188 TSM:INIT:STATID=5
36191 TSF:SID:OK,ID=5
36193 TSM:FPAR
36197 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
38204 !TSM:FPAR:NO REPLY
38206 TSM:FPAR
38210 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
38228 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
38234 TSF:MSG:BC
40218 !TSM:FPAR:NO REPLY
40220 TSM:FPAR
40224 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
40258 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
40263 TSF:MSG:BC
42232 !TSM:FPAR:NO REPLY
42234 TSM:FPAR
42238 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
42304 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
42309 TSF:MSG:BC
44247 !TSM:FPAR:FAIL
44249 TSM:FAIL:CNT=3
44250 TSM:FAIL:DIS
44252 TSF:TDI:TSL
54255 TSM:FAIL:RE-INIT
54257 TSM:INIT
54263 TSM:INIT:TSP OK
54265 TSM:INIT:STATID=5
54268 TSF:SID:OK,ID=5
54270 TSM:FPAR
54275 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
56282 !TSM:FPAR:NO REPLY
56284 TSM:FPAR
56288 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
56393 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
56398 TSF:MSG:BC
58296 !TSM:FPAR:NO REPLY
58298 TSM:FPAR
58302 ?TSF:MSG:SEND,5-5-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
58434 TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
58439 TSF:MSG:BC
59362 TSF:MSG:READ,2-2-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
59367 TSF:MSG:BC

It still cant find the Gateway, and I see it reads Node 7 and 2 request for registration too.

Hello @mfalkvidd , l am a fan! I very honoured to have you look into my issue... to answer your questions...

No it's another Rf24 but from the same batch as the one on the nano Gateway and all my nodes. I still have a spare one lying around. I'll try it see if it makes any difference.

The Rf24 is powered directly from the Pi with a 220uf cap connected next to GPIO pins as described in the official Rasberry Pi Gateway guide. I'll post a picture of the setup.

Everything is still on the fly with Dupont cables and Leds on a bread board until everything works well.

Concerning proximity of nodes to Gateway and if I've moved them from their original place. Besides the Gateway now lying on my desk, all my nodes are still in their place around the hose. Node ID 2 is the Sprinkler from my kitchen downstairs (over 10 metres away between concrete walls) Node ID 7 is the Gate node outside the house (about 9 meters from my desk) and Node ID 5 which didn't show in the log (probably disconnected at the time) is right next to the PiGateway.

Thanks for your response @Yveaux , l did notice 3 nodes at the time, but perhaps it didn't show on the portion of the log l shared. Yes l had been using a USB serial gateway attached to a Pi3 for over 2 years. I have tried my best to stay away from the "Bleeding Edge" of technology by staying with a stable version that has worked for me. I've been on MySenosors Ver 2.1.1 for a very long time. Just thought to update and Bahm! I'm in trouble. Can't connect to several nodes. Luckily MQTT still works, but all my MySensors nodes are down.

Please someone help me...