Echolo is already integrated with many device types, and most fall under one of the integration types in the list below:
"integration": "s1" "integration": "echolo" "integration": "milesight" "integration": "oem" / "F4FD" "integration": "geotab" / "750200C664FF0B" "integration": "touch"
If Echolo has created a custom integration for your device or device type, we will assign it an integration name. For example, if your new device is called “Widget 3000, “ we will create an integration name similar to
widget3000. Once this is created, you can create device profiles and add Rule Delivery Profiles.
Auto vs. Rule Delivery
Device Profiles have an option called
serviceType; when; when creating a new profile, the API will automatically assign
Rule Delivery (
rule_delivery) DEFAULT: Only used with the Rule’s API; if set to
rule_delivery,items matching this profile will only be sent to the Delivery Methods when all the Rule Conditions are met.
Auto Delivery (
auto_delivery): This is much like it sounds; it will automatically deliver the parsed data based on your integration type directly to your Delivery Methods.
"serviceType": "rule_delivery" "serviceType": "auto_delivery"
If using a device where the distance from the Hub is essential, setting the
configuredRssi reading will provide a more accurate distance measurement from the API. The way to configure this is to establish a device ~5 feet away from a Hub in the IoT Dashboard, watch that device, and note down three or more RSSI readings. Then, take the RSSI readings and create an average. This number should always be harmful, and taking more readings will make better-configured RSSI and distance measurements.