Comments (1)
The device IDs you used in step 3 are somewhat outside of Astarte specification: they are "Extended device IDs" and, as stated in the Astarte Documentation:
Astarte accepts Device IDs longer than 128 bit, which are then truncated to 128 bit internally. This behaviour exists for compatibility reasons but it's not supported and will likely change in future releases - hence, refrain from using anything which is not a 128-bit Device ID.
This means that fVjW5ZscQI6u1P-eoDO1jgw
, fVjW5ZscQI6u1P-eoDO1jga
etc... do collide internally on the original fVjW5ZscQI6u1P-eoDO1jg
, i.e. all their data is stored on fVjW5ZscQI6u1P-eoDO1jg
, and similarly they are deleted as fVjW5ZscQI6u1P-eoDO1jg
. This is an intended behaviour to maintain compatibility, but in future releases they will not be allowed anymore.
Notice also that if you run astartectl utils device-id validate
, you will already get that extended IDs are not valid as an answer:
$ astartectl utils device-id validate fVjW5ZscQI6u1P-eoDO1jgw
fVjW5ZscQI6u1P-eoDO1jgw is not a valid Astarte Device ID
$ astartectl utils device-id validate fVjW5ZscQI6u1P-eoDO1jg
Valid
from astarte.
Related Issues (20)
- Astarte microservices should expose a version endpoint HOT 1
- Metrics: expose the number of bytes sent by Trigger Engine
- Metrics: expose the number of calls to Astarte services API, aggregated by realm
- Metrics: expose cumulative device connection time by Realm
- Metrics: cumulative device connection time persistence
- AppEngine queries on group devices do not work if the group name contains a forward slash '/' HOT 3
- Astarte Pairing API (swagger) contains incorrect examples HOT 1
- Wrong match on json decode error
- Wrong pat match failed `DatabaseQuery.call`
- Empty arrays properties sent as `null` upon reconnection. HOT 1
- Representing a history of status changes HOT 1
- [meta] Allow multiple Astarte instances to share the same database HOT 2
- Support volatile triggers on all devices
- DUP: do not crash on device process initialization
- The device registration limit prevents re-registration of already existing devices
- Binaryblob and datetime properties sent as incorrect types upon reconnection.
- Message unacked when Trigger Engine failes to connect to the target HOT 1
- Server datastreams with explicit timestamp transmitted with no timestamp HOT 1
- Realm Management: consistency in queries is incoherent
- [Housekeeping] Provide realm auto deletion functionality HOT 1
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 astarte.