[SOLVED] TSF:MSG:PVER,0!=2

[alowhum]

I'm getting a weird error. The forum only has one other thread about PVER, and that says "your radio might be broken". But

• I tried three radios (one with capacitor), and all give the error.
• Tried low and min power levels.
• Also tried two sketches, and both give the error.
• tried decoupling sensors and a button. No change.
• I'm using it in a Nano Expansion board that gets 2A 12v power. I also tried powering it from just USB.

Details:
NRF24
MySensors 2.2

More debug data:

0 MCO:BGN:INIT REPEATER,CP=RNNRA---,VER=2.2.0
4 TSM:INIT
4 TSF:WUR:MS=10000
12 TSM:INIT:TSP OK
13 TSM:INIT:STATID=40
15 TSF:SID:OK,ID=40
17 TSM:FPAR
18 TSM:FPAR:STATP=0
20 TSM:ID
21 TSM:ID:OK
22 TSM:UPL
25 TSF:MSG:SEND,40-40-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
34 TSF:MSG:READ,0-0-40,s=255,c=3,t=25,pt=1,l=1,sg=0:1
39 !TSF:MSG:PVER,0!=2
2032 TSM:UPL
2034 TSF:MSG:SEND,40-40-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
2042 TSF:MSG:READ,0-0-40,s=255,c=3,t=25,pt=1,l=1,sg=0:1
2048 !TSF:MSG:PVER,0!=2
4042 TSM:UPL
4044 TSF:MSG:SEND,40-40-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
4051 TSF:MSG:READ,0-0-40,s=255,c=3,t=25,pt=1,l=1,sg=0:1
4057 !TSF:MSG:PVER,0!=2
6052 TSM:UPL
6054 TSF:MSG:SEND,40-40-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
6062 TSF:MSG:READ,0-0-40,s=255,c=3,t=25,pt=1,l=1,sg=0:1
6067 !TSF:MSG:PVER,0!=2
8064 !TSM:UPL:FAIL
8065 TSM:FPAR
8067 TSM:FPAR:STATP=0
8069 TSM:ID
8070 TSM:ID:OK
8071 TSM:UPL
8074 TSF:MSG:SEND,40-40-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=OK:1
8081 TSF:MSG:READ,0-0-40,s=255,c=3,t=25,pt=1,l=1,sg=0:1
8086 !TSF:MSG:PVER,0!=2```

[gohan]

Could also be cheap Chinese crappy clones

[alowhum]

I found the solution: clear the eeprom.

I had used the nodes with the MY_SIGNING_SIMPLE_PASSWD feature. Apparently when you use security on a node, the security measures stay in place.

[alowhum]

For anyone finding this: today I seemed to have the same issue, with cleared eeprom and with a test network made with two of the great red eByte radio modules.

I read elsewhere on the forum it might be a memory issue.