1.0Abeewayhttps://www.abeeway.com/fr/Franz Lavruthttps://www.abeeway.com/fr/author/franz/rich600338<blockquote class="wp-embedded-content" data-secret="I2KaYfOtpB"><a href="https://www.abeeway.com/fr/faq/">FAQ</a></blockquote><iframe sandbox="allow-scripts" security="restricted" src="https://www.abeeway.com/fr/faq/embed/#?secret=I2KaYfOtpB" width="600" height="338" title="« FAQ » — Abeeway" data-secret="I2KaYfOtpB" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"></iframe><script> /*! This file is auto-generated */ !function(d,l){"use strict";l.querySelector&&d.addEventListener&&"undefined"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i<o.length;i++)o[i].style.display="none";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute("style"),"height"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):"link"===t.message&&(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document); //# sourceURL=https://www.abeeway.com/wp-includes/js/wp-embed.min.js </script> https://www.abeeway.com/wp-content/uploads/2021/10/Abeeway-app-FAQ_01-responsive.png800339Abeeway Mobile APP – FAQ Abeeway Mobile APP – FAQ Permissions Mobile app gets stuck at permissions page Abeeway app needs Bluetooth and location permissions to be set as “Allow all the time”. This is because the mobile app is connecting to the tracker over Bluetooth and sending phone positions to the backend on behalf of the tracker. App needs location and Bluetooth permissions even when it is in background. Note: The screenshot above is for the App settings page on Android 10. For other Android/iOS versions, the screen might be different. Adding a tracker I cannot find my tracker when I try to search it to add to my account ? You can’t find the tracker as its probably not advertising. Please ensure the following are true: The MCU/Application Firmware is above 2.2.x The Bluetooth firmware version is above 3.3.x The trackers are flashed with this config file (The config file depends on the tracker type and region) Note: If you are running Abeeway Mobile Version 1.0.2 and below, it is important to run MCU Firmware 2.2.x.  For Abeeway Mobile App Version > 1.0.2, it is important to run MCU Firmware >= 2.3.x on the tracker.   The mobile app version can be found from the Abeeway Mobile app main menu (See screenshot below. The mobile app version in the example below is 1.0.2): For Micro Tracker/Smart Badge: Restart the tracker with long button press. The tracker will advertise itself for 10 minutes to allow pairing with the tracker. The tracker will beep with advertisement melody if the operation was successful. (See here for how to restart the tracker with button sequence). If the tracker does not play advertisement melody even though the firmware/config file is correct, it is because it is bonded. See below for instructions on how to remove Bluetooth bond on the tracker For Compact Tracker: Activate the Bluetooth with the magnet sequence (see here for the sequence)  For ANY Tracker: Send the downlink ff020b0064 on LoRaWAN downlink port = 2. The tracker will advertise itself for 100 seconds to allow pairing with the phone. You can change the duration of advertisement using Abeeway Driver (see section: Start and Stop BLE advertisement) How do I remove Bluetooth bond on the tracker? The Bluetooth bond on the tracker can be removed in one of the following ways: With the button sequence (easiest): MCU Firmware 2.2.x and below. Ensure the tracker is switched off with the long button press, followed by the button sequence <1 long press , 6 short press, 1 long press>, then switch on the tracker with long press. The tracker will beep with advertisement melody if the operation was successful (This is applicable only to Micro Tracker/Smart Badge) MCU Firmware 2.3.x and above. Hold the button for more than 14 sec to enter ESC sequence. The tracker will play melody indicating the fact that special sequence can be started. Once inside the special sequence, do the following: 1 click, 1 click, 1x press (between 1 – 4 sec). If the sequence is successful, the tracker will play Bluetooth advertisement melody indicating the Bluetooth bond is removed for about 10 minutes (which is the default configuration). (This is applicable only to Micro Tracker/Smart Badge) Sending the LoRaWAN downlink ff0202 on downlink port = 2 to the Abeeway tracker Using CLI with the tracker connected over USB port. The tracker can be connected to USB port and then communicate it with serial tool like Tera term. Once connected to Tera term, enter the password “123” as this is the default password to interact with the tracker. Then type “ble clear” to clear the Bluetooth bond on the tracker. For more information, please refer to CLI user guide. I get this message « Error connecting to the tracker » when I add the tracker to my account? This issue happens due to the Bluetooth connectivity. Please do the following steps and try again to add the tracker: Step 1: Remove the Bluetooth bond from the phone.  The Bluetooth bond on the phone can be easily removed by clicking on “FORGET” button on the Abeeway tracker. Abeeway devices always start with prefix ABW followed by last 9 digits of LoRa DEVEUI. DEVEUI can be found on the back of the sticker on the tracker. Note: The screenshot above is for Android 9. The procedure to remove the Abeeway tracker from phone’s Bluetooth device will be different for iOS or other Android phones. Step 2: Remove Bluetooth bond on the tracker The Bluetooth bond on the tracker can be removed in one of the following ways: With the button sequence (easiest): MCU Firmware 2.2.x and below. Ensure the tracker is switched off with the long button press, followed by the button sequence <1 long press , 6 short press, 1 long press>, then switch on the tracker with long press. The tracker will beep with advertisement melody if the operation was successful (This is applicable only to Micro Tracker/Smart Badge) MCU Firmware 2.3.x and above. Hold the button for more than 14 sec to enter ESC sequence. The tracker will play melody indicating the fact that special sequence can be started. Once inside the special sequence, do the following: 1 click, 1 click, 1x press (between 1 – 4 sec). If the sequence is successful, the tracker will play Bluetooth advertisement melody indicating the Bluetooth bond is removed for about 10 minutes (which is the default configuration). (This is applicable only to Micro Tracker/Smart Badge) Sending the LoRaWAN downlink ff0202 on downlink port = 2 to the Abeeway tracker Using CLI with the tracker connected over USB port. The tracker can be connected to USB port and then communicate it with serial tool like Tera term. Once connected to Tera term, enter the password “123” as this is the default password to interact with the tracker. Then type “ble clear” to clear the Bluetooth bond on the tracker. For more information, please refer to CLI user guide. Step 3: Trigger the tracker to advertise itself over Bluetooth For Micro Tracker/Smart Badge: Restart the tracker with long button press. The tracker will advertise itself for 10 minutes to allow pairing with … Continuer la lecture «  »