deveui on Mdot not sent to Conduit

[John Greene]

Payloads from one of our mdots is not transmitting to our AEP Conduit with the proper “deveui.” It is coming through with all zeroes. Following is a payload:

{“tmst”:4067837668,”time”:”2019-03-14T23:20:50.346076Z”,”chan”:5,”rfch”:1,”freq”:912.9,”stat”:1,”modu”:”LORA”,”datr”:”SF10BW125″,”codr”:”4/5″,”lsnr”:10.5,”rssi”:-74,”opts”:”03070307″,”size”:0,”fcnt”:1,”cls”:0,”port”:1,”mhdr”:”80e5953c00a40100″,”data”:””,”appeui”:”37-49-f3-c7-d6-e5-9e-61″,“deveui”:”00-00-00-00-00-00-00-00″,”ack”:true,”adr”:true,”gweui”:”00-80-00-00-a0-00-0a-1b”,”seqn”:1}

The same binary works fine (ie, the deveui goes through) on other mdots. Any ideas as to why the deveui is being transmitted with zeroes? It is entirely possible that we accidentally did something to the mdot that might have messed with its configuration. Is there any way to restore the mdot to factory settings and/or create a deveui to match the one on the identifying tag?

[Jason Reiss]

Looks like flash was erased.
Go to https://support.multitech.com

[Author]

Posts