Hi,
I have recently added a few T Beam devices to my ttn mapping application. To my surprise, when I view the advanced map and specify a device name I see mapping in another continent, along side the mapping that device has done. I was of the thought that device ID’s should be unique - is this not the case or is something broken?
Cheers,
Adrian
Application IDs are globally unique. Devices IDs within an application. Requiring globally unique device names (which is what the IDs are used for most of the time) would create a headache as there are many thousands of devices.
That all makes sense - but what doesn’t, is how, even with id/name/address re-use, a user could see information from someone else’s node. They shouldn’t (directly or by aid of TTN servers) have access to the keys needed to validate or decode it, and it doesn’t seem to make sense that the network would even offer them raw encrypted data for a node that isn’t theirs. The only logical way I can think of to get the raw feed for other people’s nodes is when that flows through or is also picked up by one’s own gateway, which shouldn’t happen for a node on another continent.
Is there some other piece of the puzzle that explains this?
That could be an issue with TTNmapper. Have you checked the TTNmapper service agreement on the subject? @jpmeijers
The TTN back-end does not allow access to any of the information you mentioned.
Sounds like what you are saying is that users have configured TTN to push their mapping node data to an additional non-core (and perhaps even 3rd party?) service that’s perhaps not keeping it distinct by user.
If the goal is crowdsourcing a community map of coverage that may not be entirely inappropriate as an idea, though seems like it can generate confusion.
That is right, TTNmapper is a third party service and data from a node is only forwarded to it if the application owner adds TTNmapper integration to the application or if the user runs an app on a smartphone to map.
So sending data to the service is a deliberate decision made by the application owner.
This issue has already been mentioned in the past - it’s TTN Mapper filtering by name and not by hw Id, thus with some mixed data when you want to look to your own tracker only.