search

Milesight-IoT / SensorDecoders

https://www.milesight.com
GNU General Public License v3.0
138 stars 64 forks source link

CT101 uplink stop after report interval from 1 hour to 5 min #52

Open Sleeper67 opened 1 month ago

Sleeper67 commented 1 month ago

Hi there,

I changed my device (CT101) Uplink interval from 3600s to 300s via downlink and now the device has stopped sending uplinks.

Any idea why it would stopped?

Had the uplinks also recently stop on one of our EM320-TH-915M, which was sending confirmed uplinks

we're running Chirpstack v4.9.0

image

Milesight-IoT commented 1 month ago

According to your screenshot, you have set FF 8E 01 2C 01, which means that the data will be reported after 300 minutes.

Milesight-IoT commented 1 month ago

Due to lack of other context, it is not possible to determine why EM320-TH has stopped transmitting. You can check the device's network status, reporting interval, and whether there is sufficient power using Milesight ToolBox.

Milesight ToolBox :

Sleeper67 commented 1 month ago

According to your screenshot, you have set FF 8E 01 2C 01, which means that the data will be reported after 300 minutes.

Thanks for the reply, I'll change my encoder code to suit for consistency

My assumption was that the encoder would stay consistent and use the same units for setting the reporting interval. Since the encoder for the EM320-TH uses seconds, I expected the encoder for the CT101 to use seconds as well when configuring the report_interval.

Sleeper67 commented 1 month ago

Due to lack of other context, it is not possible to determine why EM320-TH has stopped transmitting. You can check the device's network status, reporting interval, and whether there is sufficient power using Milesight ToolBox.

Milesight ToolBox :

The EM320-TH has stopped sending join request as far as I can tell, unfortunately the device is far from us.

image