Added Bluetooth support being usable as Trigger as well as Action
While this on the one hand gives the opportunity to send data via Bluetooth to OTDT being a Trigger, it is possible to establish a OTDT to OTDT communication using Bluetooth on the other hand.
Maybe having Bluetooth (object) messages being a Trigger for OTDT is a fine thing in some situations (or sending messages via Bluetooth to other devices as an Action), establishing an "internal" communication between 2 (or even more) instances of OTDT results in a wide bunch of opportunities.
Theoretically you could span an own “internal” network within an enitity and therefore share data to check if things are doubled or to concentrate communications to central infrastructure and even more.