fix: load DB sensor type ranges in HTTP/MQTT ingestion paths (KI-81)

fix: load DB sensor type ranges in HTTP/MQTT ingestion paths #81

Merged

wasabi opened 2 days ago

Summary

Ensures HTTP and MQTT ingestion paths use DB-loaded sensor type ranges instead of hardcoded defaults only.

Changes

HTTP receiver now loads ranges from DB via get_sensor_type_ranges() with fallback to defaults
MQTT subscriber now loads ranges from DB with fallback to defaults
Removed dead validate_reading() wrapper from sensor_ingester (double-validation)

Tests

8 tests for range loading, fallback behavior, and dead code removal.

Commits were merged into target branch

fix: load DB sensor type ranges in HTTP/MQTT ingestion paths

- HTTP receiver now loads ranges from DB via get_sensor_type_ranges()
- MQTT subscriber now loads ranges from DB with fallback to defaults
- Remove dead validate_reading() wrapper from sensor_ingester
- Add 8 tests for range loading and fallback behavior

2 days ago

f5e33daa

wasabi merged 2 days ago
Login to comment

Submitter	wasabi
Target	main
Source	fix/field-ingestion-ranges

Jobs

Merge Strategy

Create Merge Commit

Watchers (1)

Reference

pull request KI-81