Comments (7)
It's seems too overhead to call the API for obtain the AppEUI on every RX packet.
So, I propose put the AppEUI in topic as: application/[applicationID]/app/[appEUI]/node/[devEUI]/rx.
It allows create simple handlers for parsing different data formats.
Makes sense?
from chirpstack-application-server.
Hi @ymkins I think there has been some misunderstanding what the AppEUI
actually means (I think the LoRaWAN specs was not really clear on this in previous versions).
Latest specs (1.0.2):
19 6.1.2 Application identifier (AppEUI)
20 The AppEUI is a global application ID in IEEE EUI64 address space that uniquely identifies
21 the entity able to process the JoinReq frame.
22 The AppEUI is stored in the end-device before the activation procedure is executed.
So it shouldn't be used to distinguish the payload format that you're using. E.g. two different AppEUI
values could still have the same purpose (e.g. sensing the temperature). Also, two equal AppEUI
values could do something completely different (as they will probably be bound to a vendor). When you have control over the node, you could of course use the AppEUI
to define which payload should be handled how.
Therefore the ApplicationID was introduced, so that you can define which nodes are serving which purpose.
from chirpstack-application-server.
Well, I agree with that two equal AppEUI values could do something completely different, as we can't control vendors).
I saw in the "Update MQTT handler so that it uses name of app and node" 249fe86 the "application/[applicationName]/node/[nodeName]/rx" schema. But in the "Update docs and changelog. Add app description in migration" 2b05632 there is the "application/[applicationID]/node/[devEUI]/rx" schema.
The ApplicationID depends on the registration process. It can be troubled to have the same ApplicationIDs on different environments.
@brocaar, what about ApplicationName?
from chirpstack-application-server.
Yes, the initial approach was to use names for both the application and node. However, the issue is that these names are mutable (thus can break any integration you made), where using the ApplicationID
and devEUI
are static. You can still change the names of your applications and nodes without breaking any integrations.
from chirpstack-application-server.
So, if we want provide integrations with the consistent ApplicationID on different environments, we can change the starting value of the id sequence in DB on deployment.
Something like ALTER SEQUENCE application_id_seq RESTART WITH 10000;
It allows consistent static values for applications with deferred registering.
Thanks.
from chirpstack-application-server.
Another option to have reserved ids after deployment, just create with API few application records for future using.
from chirpstack-application-server.
So, no more sense to have ApplicationName and NodeName with restricted values because of ApplicationDescription and NodeDescription. Isn't it?
from chirpstack-application-server.
Related Issues (20)
- MQTT Integration forces me to use client-certificate? HOT 2
- Postgres connection drop
- AS923-2 shows as EU868 in Application server v3.17.6 HOT 2
- Application server features
- HTML file not found HOT 2
- Improve manual gateway location positioning HOT 1
- Join Request/Accept shown in LoRaWAN Frames but no Join event in Device Data
- Downlink frame-counter (network)* can not +1
- Swagger docs misleading on "id" field
- AMQP Integration doesn't reestablish connection if channel was closed
- Changing service profile of application does not change devices' service profile in network database HOT 3
- Make GlobalSearch accessible also for authorization with API-Keys HOT 3
- Autoclear the Frame counter in ABP mode HOT 2
- enqueue downlink payload error: create device-queue item error: rpc error: code = InvalidArgument desc = device security-context out of sync (code: 13) HOT 1
- Strange data payload after doing unwise restoration HOT 2
- We encountered a problem when sending data using multicast
- How can I integrate HTTP with chirpstack? The link https://www.chirpstack.io/docs/chirpstack/integrations/http.html provides the code, but are there any instructions to use this code in chirpstack? Basically using the HTTP integration feature, I need to retrieve the data sent by the end devices and store it in a file. HOT 1
- OIDC - Email is missing on login
- "Validation errors" when editing existing Javascript CODEC: Chirpstack v4.5.1
- AWS SNS integration could perform some input validation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chirpstack-application-server.