scrapCount
ScrapCount messages are sent whenever a product is to be marked as scrap.
2 minute read
Topic
ia/<customerID>/<location>/<AssetID>/scrapCount
ia.<customerID>.<location>.<AssetID>.scrapCount
Usage
Here a message is sent every time products should be marked as scrap. It works as follows: A message with scrap and timestamp_ms is sent. It starts with the count that is directly before timestamp_ms. It is now iterated step by step back in time and step by step the existing counts are set to scrap until a total of scrap products have been scraped.
Content
timestamp_ms
is the unix timestamp, you want to go back fromscrap
number of item to be considered as scrap.
- You can specify maximum of 24h to be scrapped to avoid accidents
- (NOT IMPLEMENTED YET) If counts does not equal scrap, e.g. the count is 5 but only 2 more need to be scrapped, it will scrap exactly 2. Currently, it would ignore these 2. see also #125
- (NOT IMPLEMENTED YET) If no counts are available for this asset, but uniqueProducts are available, they can also be marked as scrap.
JSON
Examples
Ten items where scrapped:
{
"timestamp_ms":1589788888888,
"scrap":10
}
Schema
{
"$schema": "http://json-schema.org/draft/2019-09/schema",
"$id": "https://learn.umh.app/content/docs/architecture/datamodel/messages/scrapCount.json",
"type": "object",
"default": {},
"title": "Root Schema",
"required": [
"timestamp_ms",
"scrap"
],
"properties": {
"timestamp_ms": {
"type": "integer",
"default": 0,
"minimum": 0,
"title": "The unix timestamp you want to go back from",
"examples": [
1589788888888
]
},
"scrap": {
"type": "integer",
"default": 0,
"minimum": 0,
"title": "Number of items to be considered as scrap",
"examples": [
10
]
}
},
"examples": [
{
"timestamp_ms": 1589788888888,
"scrap": 10
},
{
"timestamp_ms": 1589788888888,
"scrap": 5
}
]
}
Producers
- Typically Node-RED
Consumers
Last modified April 17, 2023: build: version 0.9.13 (6cb0a01)