BLE Tasker Plugin
500+
Téléchargements
Tout public
info
À propos de l'application
This is a plugin for Tasker that allows controlling a BLE device from Tasker.
Supported BLE chips:
- Nordic Semiconductor nRF51822 (vendor id: 6E400001-B5A3-F393-E0A9-E50E24DCCA9E)
- Texas Instruments CC254x (vendor id: 0000FFE0-0000-1000-8000-00805F9B34FB)
- Microchip RN4870/1 (vendor id: 49535343-FE7D-4AE5-8FA9-9FAFD205E455)
- Telit Bluemod (vendor id: 0000FEFB-0000-1000-8000-00805F9B34FB)
There is the option to use other chips with different characteristics, given that the BLE protocol is relatively simple. To do this you can configure your own vendor id, with a single read characteristic and single write characteristic in the Connect Action.
Current functionality:
Connect (Action)
This is used to connect to a BLE device, you need to run this Action before before the other commands can be used. You have to supply the MAC address of your device in the configuration. If the connection is lost to the BLE device (for example if the BLE device turns off), the plugin will try to reconnect indefinitely, until you run the Disconnect Action. This Action starts the plugin running in the Foreground (with a notification)
Disconnect (Action)
Disconnect from the BLE device (also stops the foreground service of the plugin)
Send Message (Action)
Send a message (String) to your BLE device. The message is sent to the device you are connected to through the Connect Action.
Receive Message (Event)
This event is triggered if you are connected to the BLE device through the Connect Action and the BLE device sends a message. The message is captured in the local %message variable in the Task you attach to the event.
Connection State (State)
This State activates if there is an active connection and inactivates when the connection is lost. If the BLE device is shut down, the connection is lost and this will inactivate. If the BLE device turns on again and the connection re-establishes, this becomes active again.
Supported BLE chips:
- Nordic Semiconductor nRF51822 (vendor id: 6E400001-B5A3-F393-E0A9-E50E24DCCA9E)
- Texas Instruments CC254x (vendor id: 0000FFE0-0000-1000-8000-00805F9B34FB)
- Microchip RN4870/1 (vendor id: 49535343-FE7D-4AE5-8FA9-9FAFD205E455)
- Telit Bluemod (vendor id: 0000FEFB-0000-1000-8000-00805F9B34FB)
There is the option to use other chips with different characteristics, given that the BLE protocol is relatively simple. To do this you can configure your own vendor id, with a single read characteristic and single write characteristic in the Connect Action.
Current functionality:
Connect (Action)
This is used to connect to a BLE device, you need to run this Action before before the other commands can be used. You have to supply the MAC address of your device in the configuration. If the connection is lost to the BLE device (for example if the BLE device turns off), the plugin will try to reconnect indefinitely, until you run the Disconnect Action. This Action starts the plugin running in the Foreground (with a notification)
Disconnect (Action)
Disconnect from the BLE device (also stops the foreground service of the plugin)
Send Message (Action)
Send a message (String) to your BLE device. The message is sent to the device you are connected to through the Connect Action.
Receive Message (Event)
This event is triggered if you are connected to the BLE device through the Connect Action and the BLE device sends a message. The message is captured in the local %message variable in the Task you attach to the event.
Connection State (State)
This State activates if there is an active connection and inactivates when the connection is lost. If the BLE device is shut down, the connection is lost and this will inactivate. If the BLE device turns on again and the connection re-establishes, this becomes active again.
Date de mise à jour
La sécurité, c'est d'abord comprendre comment les développeurs collectent et partagent vos données. Les pratiques concernant leur confidentialité et leur protection peuvent varier selon votre utilisation, votre région et votre âge. Le développeur a fourni ces informations et peut les modifier ultérieurement.
Aucune donnée partagée avec des tiers
En savoir plus sur la manière dont les développeurs déclarent le partage
Aucune donnée collectée
En savoir plus sur la manière dont les développeurs déclarent la collecte
Nouveautés
- Received messages can now be decoded as bytes and hexadecimal, as well as UTF-8 text
- Messages to send can now be encoded as bytes and hexadecimal, as well as UTF-8 text
- Messages to send can now be encoded as bytes and hexadecimal, as well as UTF-8 text
Assistance de l'appli
À propos du développeur
Stein Laurens Overtoom
bleapp@overtoom.email
Netherlands
