An Android MQTT client with Tasker automation integration for connecting to brokers and triggering actions.
mqttclpro is an Android MQTT client application that integrates with Tasker for automation. It allows users to connect to MQTT brokers, subscribe to topics, and automate actions—like publishing messages or triggering events—based on MQTT messages. The app solves the problem of bridging IoT communication with mobile device automation on Android.
Android users and developers who work with MQTT protocols and want to automate device actions using Tasker, such as IoT enthusiasts, home automation hobbyists, or developers building mobile-integrated IoT solutions.
Developers choose mqttclpro for its seamless Tasker integration, enabling complex automation workflows without custom coding. Its focus on Android-specific automation and straightforward topic management sets it apart from generic MQTT clients.
MQTT Client for android with tasker support
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables seamless automation by allowing Tasker actions to publish MQTT messages or trigger events on message receipt, with support for Tasker variables in topics and payloads, as detailed in the integration instructions.
Users can add or remove topics easily through the app interface, simplifying subscription management for dynamic IoT workflows.
Messages are automatically saved for later reference, preventing data loss even after app restarts, as mentioned in the feature list.
Provides intents for other apps to connect to brokers and publish messages programmatically, with code examples given in the README for interfacing.
SSL/TLS encryption is labeled as experimental in the README, indicating it may be unreliable for secure production use and is a planned feature for improvement.
The app lacks notifications for real-time message alerts, limiting immediate feedback for automation triggers, though it's noted as 'coming soon' in the README.
The README admits the app 'might be rough around the edges,' suggesting potential bugs, incomplete features, or a less polished user experience.