This post is manually migrated from Ruuvi’s old feedback page.
Otso: can you expand what you mean.
Seems that description was not moved from the original issue:
"In some cases it would be beneficial to being able to define which Ruuvi sensors (or other nearby Bluetooth broadcast transmitters) to forward via HTTP/MQTT. Some reasons:
- Data plan and/or bandwidth of Gateway’s internet connection is limited and too many Ruuvi or other BLE devices around
- Gateway is pushing data to a 3rd party server and unnecessary incoming data is causing extra load and requires additional filtering
- A 3rd party server is used and use case requires Gateway to stay quiet by default and send any data only if a certain predefined BLE device(s) comes in the range of the Gateway
Both an inclusion and exclusion list would be helpful