If repeating counter of 1 then it could be a device powering up & TXing once then either deep-sleeping/resetting and restarting @ count = 1 again or perhaps running off energy scavenging - TEG, Solar, Vibration, etc. - taking ~10 mins to accumulate enough charge to TX once, exhausting and then waiting to recharge…even a duff battery might do that if it’s chemistry recovers enough to then restart b4 collapsing again. though that wont likely continue for long before battery totally dies?!
The Idea of TEG as source for short TX was one I have been thinking about/playing around with on LP radio for years…put TEG with radio enabled sensor on say radiator in cold room…Initiate boiler/pump which runs & heats radiator…starts to generate charge…powers temp sensor with radio, tx result…power down sensor/radio and wait for more charge build up…rinse & repeat…as room warms frequency of tx will fall as TEG temp diff reduces and takes longer to build charge, if room warm enough based on temp sens data or even just the fact of the TX event switch of boiler/pump etc. Similarly using vibration harvester for monitoring machinery (motors/pumps etc) - stay quiet for months/years then as bearings start to degrade vibration increases causing TX that then triggers preventative maintenance!
Signal strength suggests you are getting this from a distance or poss a unit set to TX at low power (we don’t all need top ‘shout’ at +14dbm !) - perhaps to conserve any scavenged energy and reduce time between TX’s as threshold of stored charge to achieve TX would be lower if running TX at say 0dbm or -6 or whatever…
When I look at payloads on my gateway console I often see info on Network /Net ID /Region - can you see anything similar? Mine shows between Dev Addr field and Physical Payload field. e,g. something like :-
Network: Experimental nodes
Net ID: 0x00
…do you see anything similar for more clues?