@turquoisebay/mqtt 0.1.16 → 0.1.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +5 -0
- package/README.md +0 -32
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,11 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [0.1.17] - 2026-02-03
|
|
9
|
+
|
|
10
|
+
### Docs
|
|
11
|
+
- Remove HA/Kuma examples from README
|
|
12
|
+
|
|
8
13
|
## [0.1.16] - 2026-02-03
|
|
9
14
|
|
|
10
15
|
### Docs
|
package/README.md
CHANGED
|
@@ -9,10 +9,8 @@ MQTT channel plugin for [OpenClaw](https://github.com/openclaw/openclaw) — bid
|
|
|
9
9
|
## Features
|
|
10
10
|
|
|
11
11
|
- 🔌 **Bidirectional messaging** — subscribe and publish to MQTT topics
|
|
12
|
-
- 🏠 **Home automation ready** — integrates with Home Assistant, Mosquitto, EMQX
|
|
13
12
|
- 🔁 **Robust reconnection** — recovers from broker restarts and cold starts
|
|
14
13
|
- 🔒 **TLS support** — secure connections to cloud brokers
|
|
15
|
-
- 📊 **Service monitoring** — receive alerts from Uptime Kuma, healthchecks, etc.
|
|
16
14
|
- ⚡ **QoS levels** — configurable delivery guarantees (0, 1, 2)
|
|
17
15
|
|
|
18
16
|
## Installation
|
|
@@ -94,36 +92,6 @@ If you want to publish custom text via CLI, use the `message` tool:
|
|
|
94
92
|
openclaw agent --message "Send MQTT: Temperature is 23°C"
|
|
95
93
|
```
|
|
96
94
|
|
|
97
|
-
## Use Cases
|
|
98
|
-
|
|
99
|
-
### Service Monitoring
|
|
100
|
-
|
|
101
|
-
Pair with [Uptime Kuma](https://github.com/louislam/uptime-kuma) to receive alerts:
|
|
102
|
-
|
|
103
|
-
1. Configure Uptime Kuma notification → MQTT
|
|
104
|
-
2. Set topic to `openclaw/inbound`
|
|
105
|
-
3. OpenClaw receives and can act on alerts
|
|
106
|
-
|
|
107
|
-
### Home Assistant Integration
|
|
108
|
-
|
|
109
|
-
```yaml
|
|
110
|
-
# Home Assistant configuration.yaml
|
|
111
|
-
mqtt:
|
|
112
|
-
sensor:
|
|
113
|
-
- name: "OpenClaw Status"
|
|
114
|
-
state_topic: "openclaw/outbound"
|
|
115
|
-
|
|
116
|
-
automation:
|
|
117
|
-
- trigger:
|
|
118
|
-
platform: mqtt
|
|
119
|
-
topic: "home/alerts"
|
|
120
|
-
action:
|
|
121
|
-
service: mqtt.publish
|
|
122
|
-
data:
|
|
123
|
-
topic: "openclaw/inbound"
|
|
124
|
-
payload: "{{ trigger.payload }}"
|
|
125
|
-
```
|
|
126
|
-
|
|
127
95
|
## Security
|
|
128
96
|
|
|
129
97
|
**Important:** Any client that can publish to the inbound topic has full access to your OpenClaw agent. Treat MQTT as a **trusted channel only** (restricted broker, auth, private network). If you need untrusted access, add a validation layer before publishing to `openclaw/inbound`.
|