What does !TSP:MSG:PVER mismatch mean?



  • I have a DHT11 running for about 2 weeks now and suddenly the GW says the following lines over and over again:
    What does that mean?

    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    

  • Admin

    https://ci.mysensors.org/job/Verifiers/job/MySensorsArduino/branch/development/Doxygen_HTML/group__MyTransportgrp.html

    You seem to have some serious problems with your radio the data in the log looks corrupted. I.e. t=101...



  • It happens to me with an amplified version of nrf24. i change the module and works fine



  • I restarted the sensor and it now works like a charm, haven't done anything to it.
    I have to wait another two weeks to see if it happens again

    Thanks @hek for the link ( I was looking for that the other day)



  • 0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    0;255;3;0;9;TSP:MSG:READ 101-101-101 s=101,c=5,t=101,pt=3,l=12,sg=1:25957
    0;255;3;0;9;!TSP:MSG:PVER mismatch
    

    This started today again and if I read the values correctly its a sensor with ID 101?

    What I can find I can decode this:
    TSF:MSG:READ,sender-last-destination,s=%d,c=%d,t=%d,pt=%d,l=%d,sg=%d:%s
    s=sensor ID
    c=command
    t=msg type
    pt=payload type
    l=length
    sg=signing flag

    But I can't find what the values mean.

    The other problem is that I do not have a sensor with id 101! I think this is something else that is messing with my radio.


  • Admin

    The radio looks seriously broken or underpowered. I've seen similar results when trying to use an amplified radio (with high PA level) and supplying it with too little power.



  • You mean the gateway I suppose? The radio is a NFR24L01+ with PA and LNA. a cap (right now the UNO is power by a computer USB port)


  • Admin

    Try lowering pa -level

    #define MY_RF24_PA_LEVEL RF24_PA_LOW
    or 
    #define MY_RF24_PA_LEVEL RF24_PA_MIN
    


  • Thanks, I try it



  • Hello,

    I am having exactly the same issue with 2.0, works fine with 1.5.

    Using Arduino Mini Pro 5v - I do not have a Decoupling-Capacitor cause it hasnt been needed for 1.5 will that really be needed with 2.0?


  • Mod

    @Daniel-Eriksson said:

    Using Arduino Mini Pro 5v - I do not have a Decoupling-Capacitor cause it hasnt been needed for 1.5 will that really be needed with 2.0?

    Yes. Decoupling was needed for 1.5 as well, but in some cases people were lucky and it happened to work anyway. Being lucky can work with 2.0 as well, but relying on luck for your home automation is not recommended.



  • @mfalkvidd Ah ok, then I just have to wait for the stuff :) Thanks!


Log in to reply
 

Looks like your connection to MySensors Forum was lost, please wait while we try to reconnect.