Closed jas-williams closed 2 years ago
It looks like the ingest validator needs tweaking as it seems hotspots are reporting a seen RSSI outside the bounds of -130
if hotspot_rssi < -130 or hotspot_rssi > 0 do
{:error, "Invalid Uplink RSSI for Hotspot: #{hotspot_name}"}
else
if hotspot_snr < -40 or hotspot_snr > 40 do
{:error, "Invalid Uplink SNR for Hotspot: #{hotspot_name}"}
else
{:ok, hotspot}```
I think we can pull the floor down to -141dBm
per https://www.semtech.com/products/wireless-rf/lora-core/sx1302cssxxxgw1.
Some uplinks are rejected with invalid RSSI is the bounds now invalid due to hotspot RSSI changes?
I am seeing a few rejected mappers uplinks the error looks like
req" }, { "category": "uplink", "data": { "integration": { "id": "b73f2b98-af92-48a3-97a6-44e63dd3eeb1", "name": "coverage-mapping", "status": "error" }, "res": { "body": "{\"error\":[\"Invalid Uplink RSSI for Hotspot: low-cloth-jaguar\"]}", "code": 400, "headers": { "CF-Cache-Status": "DYNAMIC", "CF-RAY": "6e7bbebca9e17b55-LAX", "Cache-Control": "max-age=0, private, must-revalidate", "Connection": "keep-alive", "Content-Length": "63", "Content-Type": "application/json; charset=utf-8", "Date": "Sun, 06 Mar 2022 14:22:42 GMT", "Expect-CT": "max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\"",
Has hotspot firmware changes broken something ?
This is the actual RSSI reported
hotspots": [ { "channel": 2, "frequency": 868.5, "hold_time": 866, "id": "112Xs2xknWxND1dNpUCPwmoocq4ZKHeLFQ3wjmfVNfhz8A1zjjqJ", "lat": 51.18132649222927, "long": -2.5383151597028974, "name": "low-cloth-jaguar", "reported_at": 1646576559738, "rssi": -134, "snr": -17.799999237060547, "spreading": "SF10BW125", "status": "success" }