search

Estimote / Android-Fleet-Management-SDK

Estimote Fleet Management SDK for Android
https://developer.estimote.com
MIT License
836 stars 451 forks source link

Low network EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 #295

Closed rajeshkanna777 closed 5 years ago

rajeshkanna777 commented 5 years ago

Prerequisites

Basic information

Estimote SDK version: [1.4.1]

Android devices affected: [Nokia 6.1]

Android OS version affected: [Android OS version Oreo 8.0.0]

Beacon hardware version: [G1.12] Firmware Version 4.12.0 Hardware Version G1.12

Description

EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: LINK_NETWORK_WEB_LINK_ID Reason: Invalid value 0 for LINK_NETWORK_WEB_LINK_ID

[Description of the issue]

(Optional) Steps to reproduce:

  1. [First Step]
  2. [Second Step]
  3. [and so on...]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Logs and code

 W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: DARK_TO_SLEEP_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.089 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: DARK_TO_SLEEP_THRESHOLD Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.091 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: CONDITIONAL_BROADCASTING Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.094 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: FLIP_TOO_SLEEP_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.096 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: MOTION_ONLY_ADVERTISING_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.098 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: SMART_POWER_MODE_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.101 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: TEMPERATURE_OFFSET Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.103 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: EDDYSTONE_CONFIGURATION_SERVICE_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.105 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: NFC_DATA Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.110 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: MOTION_ONLY_ADVERTISING_DELAY Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.112 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: MAGNETOMETER_CALIBRATION_DATA Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.115 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: SHAKE_TO_CONNECT_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.117 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: NEAR_TO_CONNECT_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.119 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: LINK_NETWORK_TX_POWER Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.121 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: LINK_NETWORK_ENABLE Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.123 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: LINK_NETWORK_ADVERTISING_INTERVAL Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.125 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: LINK_NETWORK_MEASUREMENT_PERIOD Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
2018-09-20 18:55:43.126 16099-16099/com.wrkspot.onboard.vdeploy.dev W/EstimoteSDK: DeviceCloudSyncEngine$2.onFailure:122 Unable to synchronise setting: UTC_TIME Reason: Not connected to [88b88d060ffe1a274550c34c6be10219]
heypiotr commented 5 years ago

[Cleaning up stale issues following the rebranding of Estimote SDK to Estimote Fleet Management SDK]

Feel free to re-open this issue if the problem still persists with the latest version of the SDK, and affects the fleet management APIs (BulkUpdater, connecting to beacons and changing settings, etc.).

At a quick glance, this looks like maybe you're disconnecting from the beacon a bit too soon. If that's the case, you can try to delay the disconnection a bit. If you do re-open, can you also post your code?