Node unable to get ID from gateway. [2.2.0]

[rejoe2]

@suresh-mali said in Node unable to get ID from gateway. [2.2.0]:

10053 !TSF:SID:FAIL,ID=0

Did you use the standard arduino Clean-EEPROM-Sketch or the one that comes with MySensors? The first writes "00" in EEPROM, the later "FF".
For analysing this kind of trouble also the https://www.mysensors.org/build/parser is a very valueable tool.

[Suresh Mali]

@rejoe2 I have used the Mockmysensor example sketch from Mysensors.

[rejoe2]

@suresh-mali said in Node unable to get ID from gateway. [2.2.0]:

I also cleared EEPROM

The question was: how did you do this? There are - as already mentionned - two sketches available, but only one works ;-) .

[Suresh Mali]

@rejoe2 oh, I am sorry. I use the sketch from EEPROM Lib in Arduino. Not from MySensors. I am doing it right?

[rejoe2]

@suresh-mali No, this is the one writing zero's. Use the one that comes with mysensors (or assign an ID manually in your sketch, this may lead directly to a working node).

[Suresh Mali]

@rejoe2 Will try that. I did tried assigning ID manually, but that did not work.

[Suresh Mali]

@rejoe2 I tried as suggested. Cleared EEPROM using the sketch from MySensors example folder, tried auto ID assignment and also predefined ID. None seems to work.

This is the log when no ID is assigned.

16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.2.0
25 TSM:INIT
26 TSF:WUR:MS=0
33 TSM:INIT:TSP OK
35 TSM:FPAR
37 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2046 !TSM:FPAR:NO REPLY
2049 TSM:FPAR
2051 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4059 !TSM:FPAR:NO REPLY
4061 TSM:FPAR
4063 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

Log when Node is assigned ID:

16 MCO:BGN:INIT NODE,CP=RNNNA---,VER=2.2.0
25 TSM:INIT
26 TSF:WUR:MS=0
33 TSM:INIT:TSP OK
35 TSM:INIT:STATID=254
37 TSF:SID:OK,ID=254
39 TSM:FPAR
75 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2083 !TSM:FPAR:NO REPLY
2085 TSM:FPAR
2121 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4129 !TSM:FPAR:NO REPLY
4131 TSM:FPAR
4167 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6175 !TSM:FPAR:NO REPLY
6177 TSM:FPAR
6213 TSF:MSG:SEND,254-254-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8221 !TSM:FPAR:FAIL
8222 TSM:FAIL:CNT=1
8224 TSM:FAIL:DIS
8226 TSF:TDI:TSL

Please advice if there anything that could help me understand the issue and fix it.
Thanks alot.

[rejoe2]

@suresh-mali said in Node unable to get ID from gateway. [2.2.0]:

!TSM:FPAR:FAIL

Seems like there is either a problem in the RF part (node could have a defect transmitter) or your controller is not accepting new nodes. This is partly controller specific, eg. in FHEM you have to set the GW to "inclusion mode" AND have to activate a feature called "autocreate".

[Suresh Mali]

@rejoe2 I have already tried 2 different RF modules, the known good ones. So RF can be ruled out. I am running it with Domoticz, usually I don't have to change any setting, on presentation the node is shown in Domoticz and I just add it to my UI. Also tried the option Allow discovery for 5 mins in Domoticz that did not work either. So kind of lost here as to what's happening.

[rejoe2]

@suresh-mali So then last ideas could be the gw version: is it also 2.2.0?
What kind of RF are you using - if it's nRF24 and you are already using the recommended caacitor, the MySensors lib version really could make a difference. For other RF modules, you may have a look at recent changes (RFM69 new driver).

Beside that I'm also running out of ideas.

[Suresh Mali]

@rejoe2 I am using 2.2.0 on both gateway and node. Using NRF24L01+ with Caps . Strangely one of my node running on 2.1.0 is able to communicate with the gateway. Let's hope Mods have some answers. Appreciate your efforts and time.
Thanks

[Suresh Mali]

Any Moderator or Admin here who can help me, please.

[mfalkvidd]

@suresh-mali I have moderator privileges. What do you need help with?

[Suresh Mali]

@mfalkvidd I have hit a dead end. The issue described in the thread is stii not resolved. Any advice on what can help figure out the issue would be helpful.

Thanks

[mfalkvidd]

@suresh-mali ah. Sorry, my moderator privileges did not include divine knowledge. I have no idea what could be the problem.

[DirkB19]

Not sure if it is the same problem, but looking similar ?

1. I upgrade my MQTT gateway to 2.2.0 (from 2.1.0), all working ok with my 2.1.0 sensor nodes
2. I upgrade the first sensor node to 2.2.0, and I get TSM:INIT:TSP FAIL messages on the node.
3. I downgrade the first sensor node back to 2.1.0 and it works again like a charm ...

Did I miss something ? Is this a bug in 2.2.0 ? Do I need to change config ?
Best regards,
DirkB