Data from another node



  • We are currently getting data from another node. Its ascii :
    #,PLANT1,200716103320,0000.0,000197,0000.0,0000.0,000000,000057,;#,PLANT1,200716103921,0000.0,000209,0000.0,0000.0,000000,000061,

    We get a very similar string every 12 minutes
    which is defenitly not ours. And the data our node is sending does not get to our backend. Can you please fix this asap?

    IMEI: deleted by admin
    Subscription: deleted by admin


  • Deutsche Telekom IoT

    That’s annoying!

    How often do you expect data from this device?
    And are you using coap or UDP?



  • We send data every hour via UDP to the TM-NL message server. We just turned the node off and swapped the simcard for a TM-DE one so we can continue testing. The issue started somewhere in the night, the first wrong data we saw was around 1am


  • Deutsche Telekom IoT

    Thanks, we’ll look into it


  • Deutsche Telekom IoT

    I can confirm that is not data from another node. We have some problems on a VPN tunnel in our network. And we’re looking for a solution.



  • It sure looks like log data… either from another node or from something internal in your systems.
    i converted a few more lines (they are in reverse order, sorry)
    200717081007 (2nd segment of first line) = 2020-07-18 08:10:07 = when we got the package. something is logging every 6 minutes and sending 2*6 values every 12 minutes.

    #,PLANT1,200717080405,0000.0,000060,0000.0,0000.0,000000,000010,;#,PLANT1,200717081007,0000.0,000067,0000.0,0000.0,000000,000013,
    #,PLANT1,200717075202,0000.0,000069,0000.0,0000.0,000000,000014,;#,PLANT1,200717075803,0000.0,000060,0000.0,0000.0,000000,000010,
    #,PLANT1,200717073958,0000.0,000044,0000.0,0000.0,000000,000003,;#,PLANT1,200717074559,0000.0,000060,0000.0,0000.0,000000,000007,
    #,PLANT1,200717072754,0000.0,000018,0000.0,0000.0,000000,-00003,;#,PLANT1,200717073356,0000.0,000025,0000.0,0000.0,000000,-00001,
    #,PLANT1,200717071551,0000.0,000011,0000.0,0000.0,000000,-00005,;#,PLANT1,200717072152,0000.0,000013,0000.0,0000.0,000000,-00003,
    #,PLANT1,200717070347,0000.0,000006,0000.0,0000.0,000000,-00006,;#,PLANT1,200717070950,0000.0,000009,0000.0,0000.0,000000,-00003,
    #,PLANT1,200717065143,0000.0,000006,0000.0,0000.0,000000,-00006,;#,PLANT1,200717065745,0000.0,000006,0000.0,0000.0,000000,-00004,
    #,PLANT1,200717063940,0000.0,000004,0000.0,0000.0,000000,-00006,;#,PLANT1,200717064542,0000.0,000004,0000.0,0000.0,000000,-00006,
    #,PLANT1,200717062736,0000.0,000002,0000.0,0000.0,000000,-00008,;#,PLANT1,200717063338,0000.0,000002,0000.0,0000.0,000000,-00008,
    #,PLANT1,200717061532,0000.0,000000,0000.0,0000.0,000000,-00012,;#,PLANT1,200717062134,0000.0,000002,0000.0,0000.0,000000,-00010,
    #,PLANT1,200717060328,0000.0,-00000,0000.0,0000.0,000000,-00009,;#,PLANT1,200717060931,0000.0,-00000,0000.0,0000.0,000000,-00014,
    #,PLANT1,200717055125,0000.0,-00000,0000.0,0000.0,000000,-00010,;#,PLANT1,200717055727,0000.0,-00000,0000.0,0000.0,000000,-00009,


  • Deutsche Telekom IoT

    @rhalflex

    do you see a difference now?



  • No change. Got this at 12:59 :
    #,PLANT1,200717125323,0000.0,000148,0000.0,0000.0,000000,000045,;#,PLANT1,200717125924,0000.0,000137,0000.0,0000.0,000000,000043,


  • Deutsche Telekom IoT

    We’re still working on it., sorry that it is taking so much time 😞



  • Yesterday (the 20th) at 11:21 we got the last regular package. After that from 11:26 - 12:44 we got something thats not ascii:
    11:26 : 0a23481d381f0e0c0462004223481d003862155ff827e309be4c7db51da7c061155f738f0129094cacaf1eab105d155f410000c6094c79b51da7c061155f208e01d5084223481d007462155ff827d709be4223481d00b062155ff927cc09be4223481d00ec62155ff927cb09be4c7db51da0ec62155f738f012d094c79b51da7ec62155f208e01d9084223481d002863155ff827b809bee506

    11:26 : 0a23481d381f0e14046200f3ff

    11:50 : 480a060800101a180d2a24090847a16b7301000018901c25000000002d0000c04032026c693a02131542048e1c8d1c4a0f3836373732343033303039313531335a0708b10110631864

    11:53 : 86010a060800101a180d326209c311a46b73010000103c1dcd4c9e412250e8ed82400d288340895481401cdd8040891d814079608240e82f8340e41f8140faf48240e78a82400bc37d40796b824030bd82402f7b8240fd3384400a1b7e4078fd8140520881400c8e8240796082404a0f3836373732343033303039313531335a0708b5011063184a

    12:13 : 86010a060800101a180d3262091061b66b73010000103c1dcd4c9e4122501b3581406a1c844030448240e42d80408acd814031918240b15c8340c25b8240d63e8340f87381400a208240f71b814030de824049fd854020b383400c0a8240d4c881400d288340400181409e9a82404a0f3836373732343033303039313531335a0708ad0110631850

    12:33 : 86010a060800101a180d3262097bb0c86b73010000103c1dcdcc9d41225030f27d40eab97f404619844054fa8140349684409ffd8240f9238240d47b81401cfe804076928040e75e8240aede8040ade98040c3d48240c4957f40d291814041a68140e8cc824040178140f6ad80404a0f3836373732343033303039313531335a0708b10110631868

    and it has been quiet since. I have not tested yet if our own data comes through yet. and wont be able for a while as the node shipped to the customer with a TMDE sim.



  • And we got 1 more at 23:47 : 232c504c414e54312c3230303731363033343330352c303030302e302c2d30303030302c2c303030302e302c303030302e302c3030303030302c2d30303031302c2c2c2c2c2c2c2c2c2c3b232c504c414e54312c3230303731363033343930372c303030302e302c2d30303030302c2c303030302e302c303030302e302c3030303030302c2d30303031302c2c2c2c2c2c2c2c2c2c


Log in to reply