Closed johanstokking closed 6 years ago
I think that Collos has three algorithm for resolving location. So I think that update events need not only location but also algorithm.
In V2 we have only one location per device in the registry.
Do note that the idea of Collos is that it resolves the best possible; in the order of WiFi, LoRa TDOA to LoRa RSSI. It is only for debugging purposes to have multiple endpoints enabled, but this is not supported in our device registry.
Some notes for @Sypheos:
dev.ChangedFields()
encoding/json
!) for consistency with what grpc-gateway returns. OK, I understand. We are interested only in TDOA. I think that RSSI is TDOA's preliminary exercise.
If you use the Lora Wifi
recipe, you'll get the fallback automatically. Just don't pass WiFi; https://apiportal.preview.collos.org/docs/services/localization-lora-recipes/operations/59e9b2a367ba551b780cd259?
OK, I understand.
What topic does this event send to ?
@toruuetani It will be part of the updated management event, see https://github.com/TheThingsNetwork/ttn/tree/develop/mqtt#management-events
OK, thanks.
@toruuetani Device data event now contain location PR #715 is merged
@Sypheos Great ! I'm looking forward to evaluate this feature.
I expect this to be deployed to production early next week 👍
OK, I will wait for update. Thank you !
How is progress?
The updates are currently being rolled out. All regions with ttn-
prefix are already updated.
This is a feature request for the backend.
Publish (at least) location as part of the device events.
This is especially relevant for the Collos integration, which updates the device registry and triggers a device update event. If we add the device's location as part of the payload, applications can subscribe to location updates through MQTT.
Data is
nil
, see https://github.com/TheThingsNetwork/ttn/blob/develop/core/handler/manager_server.go#L228