Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add field-mask to dezem.yml #82

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions dezem.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,10 @@ create-downlink-api-key: false
base-url: https://m2m.dezem.de/services/import/lorawan/data-1.php
paths:
uplink-message: /
field-mask:
- end_device_ids.dev_eui
- received_at
- up.uplink_message.decoded_payload
- up.uplink_message.rx_metadata
- up.uplink_message.settings.data_rate.modulation.lora.spreading_factor
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend receiving the full data rate. It is not unheard of that you may receive uplinks which are LoRa modulated at 500KHz or 250KHz, and LoRa is not the only modulation available in LoRaWAN.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the Input. You are right. I've discussed it with the team. For now, we want to keep the template as proposed in this PR as this is the use case that usually applies for us and we want to reduce the payload size.
And... it's just a template. If someone creates a Webhook based on the this template, the person can easily alter the field mask in the GUI.

- up.uplink_message.frm_payload