Cayenne seems to be not decoding the positioning information of the Abeeway micro tracker. Abeeway sent me a payload decoder for the tracker, but they claim the problem is on Cayenne.
This is the decoder code from Abeeway, maybe Cayenne can check the outcome ?
function Decoder(bytes, port) {
/*
Example decoder for some Netvox sensors with The Things Network
sorry, I am a beginner. But what I can do, is giving you access to my TTN account to take a look for yourself. As I am carrying the device along, there should be some payloads now
I’ll change the password on Friday, so you have some time.
It would also be nice, if you could integrate the Zenner smoke detector. I found a payload decoder in the net and added it to my TTN account, but there’s no single Zenner product on Cayenne and Zenner doesn’t care.
dont share your personal details in the public forum. On your TTN console, open your device and go in the data tab. When your device will publish data, it will show the payload. copy and share it here.
the Zenner team has to submit their device to be integrated with cayenne.
The messages you sent is beacon messages, we’d need at least one valid GPS message to be able to verify. A GPS message sends GPS coordinates. It usually only works outside where there is GPS coverage. Are you testing it inside or outside?
The tracker should be able to do tracking indoors by using Bluetooth and WiFi. According to the manufacturer it is also possible to send data to the tracker, but I have no idea how to do that.
It sends every uplink twice with a 5 seconds delay.
Later indoors I got this:
032CB298000B1E78DF04490C05 abn TTN decodes here Latitude and Longitude data in “fields”.
So if the data is correct, the position should be Tente (Wermelskirchen) Germany.
Correction, later in the evening I got data points. One every hour. I wonder why it didn’t sent WiFi or Bluetooth datapoints during daytime, but this maybe a matter of configuration. I’ll take a look into the device.
I think it’s a WiFi payload and not a GPS payload ( especially as at my working place a GPS signal can’t be received). According to the handbook the tracker sends a WiFi position after wakeup and than a position every 5 minutes.
On the TTN I get a upload every 5min, as stated, but it is not a GPS position. If I understand the handbook correctly, WiFi and Bluetooth have priority over GPS.
So here are some payloads from indoors GPS free tracking, that should contain a wifi position:
Yes I see, but what about indoor tracking ? The device is able to get positions when no GPS is available, e.g. if a thief put it into the basement. this should be done by using WiFi or Bluetooth:
The handbook states:
Whatever the chosen geolocation policy, the first position is always a WIFI one, sent immediately after the beginning of the motion. The FW v1.7-3 enables the deactivation of this WIFI payload and replace it by a geoloc_start. This capability is configurable via config_flag parameter.
On “features” the handbook says:
Used geolocation technologies
✓ GPS: Precise outdoor position.
✓ Low power GPS: Get quick position outdoors and daylight indoor conditions.
✓ WIFI: Position indoors and urban area.
✓ BLE: Position indoors
So, I would expect positioning indoors. But what I got during a hiking day was coordinates twice with 5min deviation and nothing else. Not a single position during an afternoon in the garden and today absolutely no position on a whole working day indoors.
I think, something must be wrong. During hiking I carried a LGT-92 with me, that sent a position every 5min, as expected, meaning that LoRa was available. At least it is availabe in the garden, only 10 meters away from the access point, but Abeeway sent no positioning at all.
Where is the error ? Just a wrong configuration or somehow lost data ?
What Wiktor of Alliot wrote is:
"One thing to note is that by default the device will only send location data when it detects motion. So if it is just sat on a desk it will only send the heartbeat messages you see. Also by default, it will attempt to sniff wifi networks and send those if it finds enough of them nearby, if that fails then it will try GPS location. "
So I think, that GPS positioning works with Cayenne, but WiFi payloads don’t, making the tracker useless with Cayenne every time a WiFi is present and that is most of the time. WiFi has priority over GPS positioning.
Yes, I understand. There is an onlinedecoder availabe at Abeeway: https://nano-things.net/abeeway-demo/decode
I see, that in WiFi mode currently no position data is sent. That’s what you call a beacon message. So it needs configuration and I have to find out, how to do that.
Does Cayenne support adowling from TTN to the tracker somehow ?