forked from jomjol/AI-on-the-edge-device
-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat!: Rework result post-processing and publishing (REST, MQTT, InfluxDB) #57
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Slider0007
changed the title
Refactor result post-processing and result publishing (MQTT, InfluxDB)
Refactor result post-processing and related result publishing (MQTT, InfluxDB)
Aug 11, 2023
Slider0007
changed the title
Refactor result post-processing and related result publishing (MQTT, InfluxDB)
Refactor result post-processing and publishing (MQTT, InfluxDB)
Aug 11, 2023
Slider0007
changed the title
Refactor result post-processing and publishing (MQTT, InfluxDB)
Refactor result post-processing and publishing (REST, MQTT, InfluxDB)
Aug 11, 2023
Slider0007
changed the title
Refactor result post-processing and publishing (REST, MQTT, InfluxDB)
feat!: Rework result post-processing and publishing (REST, MQTT, InfluxDB)
Sep 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
preValue
name variants tofallbackValue
in code and WebUIReturnValue
sActualValue
ReturnRawValue
sRawValue
ErrorMessageText
sValueStatus
ReturnPreValue
sFallbackValue
ReturnRateValue
sRatePerMin
ReturnChangeAbsolute
sRateperProcessing
timeStamp
sTimeProcessed
lastvalue
sTimeFallbackValue
PreValueOkay
isFallbackValueValid
ErrorMessage
in code and WebUIUse FallbackValue
delcare as expert parameter, because usage is strongly recommended (active by default)1. Result value behaviour:
2. Value status (legacy name: ErrorMessageText)
no error
000 Valid
No data to substitude N
E90 No data to substitude N
Neg. Rate: ...
E91 Rate negative
Rate too high: ...
E92 Rate too high (<)
Rate too high: ...
E93 Rate too high (>)
3. Indication of rate deviation
E91 rate negative
. Fallback Value can be used to cover this circumstance and provide still a validactual value
.Note: Timestamp of fallback value is going to be updated.
E91 Rate negative
is only debug level, because it doesn't hurt.Rate too high
(rate > max. rate threshold) status is splitted into two states, negative and positive deviation.E91 Rate negative
, using the fallback value, but additionally can be used for diagnostic purpose (e.g. automatically save respective images (feature, not implemented yet)Note: Timestamp of fallback value is going to be updated.
actual value - fallback value / time difference
between now and the last modification of fallback valueactual value - fallback value
(time difference is processing interval, therefore the rate per processing is equal to the absolute difference between two valid readings)4. InfluxDBv1 + InfluxDBv2
Exception: If actual value cannot be converted to a number (e.g. N replacement not possible) no publish will be triggered
5. MQTT result publishing:
value
actual_value
raw
raw_value
error
value_status
changeabsolut
/rate_per_digitalization_round
rate_per_processing
rate
rate_per_min
timestamp
timestamp_processed
json
topic6. REST API
/SetPreValue
/set_fallbackvalue
/value
(due to renaming)type=error
type=status
->
/value?all=true&type=status
->
/value?all=true&type=status&numbersname=main
BEGIN_COMMIT_OVERRIDE
feat!: Rework result post-processing and publishing (REST, MQTT, InfluxDB)
refactor!: Changed MQTT topic names
refactor!: Renamed REST API /value option: error -> status
refactor!: Adapted data log structure (value status only status number)
refactor!: Rename of
preValue
name variants tofallbackValue
in code and WebUIfix(webui): Config: Remove unused parameter
ErrorMessage
in code and WebUIrefactor(webui): Overview: Show round counter in separate line
feat(webui): Data Graph: Add Raw value + refactor
chore(webui): Config: Parameter
Use FallbackValue
delcare as expert parameterEND_COMMIT_OVERRIDE