[Michele Ferrari]

Dears,
I have the same problem. But it not work even if I try to reboot the MDOT 🙁
I’m in outside with clear sky.
I’ve done the same test with another MDOT, but nothing chages

[Michele Ferrari]

Hi,
I have a similar problem. I have a class C actuator device.
I have done a nodered flow in which I send a turn On command, with “ack” flag set on true.
I think that the packet ACK was lost, and I continue to receive duplicated messages from the actuator.
This is the slice of the log.

13:46:2:896|DEBUG| Received packet
================================
000   80 03 00 00 00 80 d9 01
008   7d 5e 1a 44 b8 ce 8c 3e
010   23 50 ed 36 e0

13:46:2:896|DEBUG| Rx on 868300000, rssi: -93 snr: 70
13:46:2:896|DEBUG| Received frame: type: Confirmed Up
13:46:2:897|DEBUG| Packet received from Node 00:00:00:03  GW 00:80:00:00:a0:00:05:8d  (127.0.0.1)  Seq# 1d9
13:46:2:898|DEBUG| Expecting packet SeqNo: 000001d9
13:46:2:898|DEBUG| Check for dup: 01d9 == 01d9
13:46:2:899|DEBUG| MIC Check: 50ed36e0 == 50ed36e0
13:46:2:899|INFO| SeqNo: 0009474c PrevSeqNo: 000001d9 Duplicate: yes

I can’t understand
13:46:2:899|INFO| SeqNo: 0009474c PrevSeqNo: 000001d9 Duplicate: yes

Watching packet bytes sequence nr is 01d9, and the expected one is 01d9.
I can’t understand 0009474c.

I’ve tried to rejoin the device, sequence number restart from 0, but always the message 0009474c is displayed.

I’ve tried to restart both network server and mosquitto, but nothing change.
I’ve also tried to send a mosquitto_pub -n -t /lora/<actuator EUI>/clear, but nothing change.

I’ve searched inside .db file, but I cannot find 0009474c anywhere.

To fix it, I have to unregister and register again the device.

Can someone help me with this strange issue?

Michele

[Author]

Posts