You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ARM: 1CPU, 512MB RAM, 8GB disk space, network connection, Raspberry Pi OS (based on Debian 12) | Debian 12 operating system;
In some cases of Raspberry Pi when using internal WiFi and bluetooth, you should connect internal WiFi on 5GHz, because on 2,4GHz there may be a problem with connection stability (sharing same antenna).
Update your system and then install following packages:
Put blood pressure monitor in pairing mode by pressing Bluetooth button for 3-5 seconds, You will see a flashing "P" on monitor;
Run second scriptomron/omron_pairing.sh find device starting with “BLEsmart_”, select ID and press Enter, wait for pairing:
$ /home/robert/export2garmin-master/omron/omron_pairing.sh
===============================================
Export 2 Garmin Connect v2.2 (omron_pairing.sh)
===============================================
27.11.2024-12:56:16 SYSTEM * BLE adapter check if available
27.11.2024-12:56:38 SYSTEM * BLE adapter hci0(00:00:00:00:00:00) working, go to pairing
2024-11-27 12:56:38,688 - omblepy - INFO - Attempt to import module for device hem-7361t
To improve your chance of a successful connection please do the following:
-remove previous device pairings in your OS's bluetooth dialog
-enable bluetooth on you omron device and use the specified mode (pairing or normal)
-do not accept any pairing dialog until you selected your device in the following list
Select your Omron device from the list below...
+----+-------------------+-------------------------------+------+
| ID | MAC | NAME | RSSI |
+----+-------------------+-------------------------------+------+
| 0 | 00:00:00:00:00:00 | BLESmart_0000025828FFB232E019 | -74 |
+----+-------------------+-------------------------------+------+
Enter ID or just press Enter to rescan.
Complete data in "omron_omblepy_mac" parameter which is related to MAC address of Omron device (read during pairing, MAC column);
Configuration file contains many other options, check descriptions and use for your configuration.
Third script is import_data.sh has implemented debug mode, you can verify if everything is working properly, just execute it from console:
$ /home/robert/export2garmin-master/import_data.sh
=============================================
Export 2 Garmin Connect v2.5 (import_data.sh)
=============================================
18.07.2024-16:56:01 SYSTEM * Path to temp files: /dev/shm/
18.07.2024-16:56:01 SYSTEM * Path to user files: /home/robert/export2garmin-master/user/
18.07.2024-16:56:01 SYSTEM * BLE adapter is ON in export2garmin.cfg file, check if available
18.07.2024-16:56:01 SYSTEM * BLE adapter hci0(00:00:00:00:00:00) working, check if temp.log file exists
18.07.2024-16:56:01 SYSTEM * temp.log file exists, go to modules
18.07.2024-16:56:07 MISCALE * Module is OFF in export2garmin.cfg file
18.07.2024-16:56:07 OMRON * Module is ON in export2garmin.cfg file
18.07.2024-16:56:07 OMRON * omron_backup.csv file exists, checking for new data
18.07.2024-16:56:07 OMRON * Importing data from a BLE adapter
18.07.2024-16:56:39 OMRON * Prepare data for omron_backup.csv file
18.07.2024-16:56:40 OMRON * Calculating data from import 1721314552, upload to Garmin Connect
18.07.2024-16:56:40 OMRON * Data upload to Garmin Connect is complete
18.07.2024-16:56:40 OMRON * Saving calculated data from import 1721314552 to omron_backup.csv file
If there is an error upload to Garmin Connect, data will be sent again on next execution, upload errors and other operations are saved in temp.log file:
To run it at system startup in an infinite loop, create a file sudo nano /etc/systemd/system/export2garmin.service enter previously searched path to import_data.sh and include "User" name:
You can check if export2garmin service works sudo systemctl status export2garmin.service or temporarily stop it with command sudo systemctl stop export2garmin.service.
2.3.4. How to increase BLE range
Purchase a cheap USB bluetooth adapter:
5.0/5.1 (tested on RTL8761B chipset, manufacturer Zexmte, works with Miscale and Omron module);
5.3 (tested on ATS2851 chipset, manufacturer Zexmte, works with Miscale module, does not work with Omron module).
Bluetooth adapter should have a removable RP-SMA antenna;
You will have option to change if standard RP-SMA antenna included with bluetooth adapter gives too little range;
If you are using a virtual machine, assign bluetooth adapter from tab Hardware > Add: USB device > Use USB Vendor/Device ID > Choose Device: > Passthrough a specific device (tested on Proxmox VE 8.3);
RTL8761B chipset requires driver (for Raspberry Pi OS skip this step), install Realtek package and restart virtual machine:
sudo apt install -y firmware-realtek
sudo reboot
If you are using multiple BLE adapters, select appropriate one by HCI number or MAC address (recommended) and set in user/export2garmin.cfg file;
Use command sudo hciconfig -a to locate BLE adapter, and then select type of identification:
By HCI number, set parameter "ble_adapter_hci";
By MAC address, set parameter "ble_adapter_switch" to "on" and specify MAC addres in parameter "ble_adapter_mac".
Sample photo with test configuration, on left Raspberry Pi 0W, on right server with virtual machine (stronger antenna added):