wpsignal

<p>WordSocket sends realtime events from your WordPress site to connected browsers.<br />
When content changes: a post is published, a comment is approved, an option is updated: the plugin pushes the event to subscribers instantly via WebSocket (with SSE fallback).</p>
<p>On WordPress 7.0+, WordSocket also registers as a WebSocket-based Yjs sync provider for realtime collaborative editing in the block editor, replacing the default HTTP polling transport with a low-latency WebSocket connection.</p>
<p>WPSignal is an independent service and is not affiliated with or endorsed by the WordPress project.</p>
<p><strong>Features:</strong></p>
<ul>
<li>One-click automatic connection via the WPSignal dashboard (no API key required)</li>
<li>Manual connection via API key for advanced setups</li>
<li>Disconnect button with inline confirmation, removes the site from the server immediately</li>
<li>WebSocket-first with automatic SSE fallback</li>
<li>Per-site JWT signing secrets: each site’s connection tokens are cryptographically isolated</li>
<li>AES-256-GCM encrypted event payloads: the WPSignal relay receives ciphertext only and never has access to plaintext message content</li>
<li>Admin toggle to disable the collaboration provider and fall back to WordPress HTTP polling</li>
<li>Built-in triggers for post updates and custom post types</li>
<li>Custom trigger builder: map any WordPress action hook to a realtime event</li>
<li>Public JavaScript API (<code>window.WPS</code>) for themes and plugins to share the connection</li>
<li>Extensible connection token: <code>wpsignal_token_channels</code> and <code>wpsignal_token_channel_prefixes</code> filters let other plugins add channels and namespace permissions to the JWT without modifying core</li>
<li>Admin explorer page with live event log, publish form, and token inspector</li>
<li>Short-lived JWTs (5 min) with automatic refresh</li>
</ul>
<p><strong>How it works:</strong></p>
<ol>
<li>Install the plugin and connect to the WPSignal service.</li>
<li>When content changes in WordPress, the plugin encrypts and publishes an HMAC-signed event to the WPSignal server.</li>
<li>The server pushes the ciphertext to all browsers subscribed to that channel.</li>
<li>The browser decrypts the payload and dispatches <code>wpsignal:*</code> DOM events. The relay never sees plaintext content.</li>
<li>On WordPress 7.0+, the block editor uses the same WebSocket connection for collaborative editing with no extra configuration.</li>
</ol>
<h4>Third-Party Service</h4>
<p>This plugin connects to the <strong>WPSignal service</strong> at api.wpsignal.io for the following operations:</p>
<ul>
<li><strong>Site registration</strong>: when you connect in the admin (via the automatic one-click flow or by entering an API key manually), the plugin registers your site with the server and receives credentials.</li>
<li><strong>Event publishing</strong>: when a trigger fires (e.g. a post is saved), the plugin sends an encrypted, HMAC-signed HTTP request to the server.</li>
<li><strong>Realtime connections</strong>: logged-in users’ browsers connect to the server via WebSocket or SSE to receive events.</li>
</ul>
<p>Event payloads are AES-256-GCM encrypted before leaving WordPress. The WPSignal server relays ciphertext and never has access to plaintext message content. Data is delivered in realtime and is <strong>not persisted</strong> on the server.</p>
<ul>
<li><a href="https://wpsignal.io/terms" rel="nofollow ugc">Terms of Service</a></li>
<li><a href="https://wpsignal.io/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/yS1roK49HEQ?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>Open Source</h3>
<p><a href="https://github.com/wpsignal/wordsocket" rel="nofollow ugc">https://github.com/wpsignal/wordsocket</a></p>


WordSocket

WebSocket relay for WordPress. Realtime events plus a Yjs sync provider for WordPress 7.0 collaborative editing. No polling, no custom server.

POTAR

<p>MQTT-Plug brings live MQTT data directly into WordPress using secure WebSocket connections.<br />
It is designed for developers, IoT experimenters, and small production deployments that want real-time visibility without building a custom frontend.</p>
<p>Unlike traditional MQTT tools, MQTT-Plug focuses on <strong>embedding live data into WordPress pages, posts, and dashboards</strong>, while keeping credentials safe and configuration simple.</p>
<h3>Key Features</h3>
<ul>
<li>Connect to MQTT brokers over WS/WSS</li>
<li>Live message stream and event log</li>
<li>Topic-based subscriptions</li>
<li>Shortcode-driven embeds</li>
<li>Works with public or authenticated dashboards</li>
<li>Designed for modern MQTT backends (Mosquitto, EMQX, HiveMQ, The-Link-Builders, managed brokers)</li>
<li>No external Node services required</li>
<li>Lightweight; no tracking, no telemetry, no lock-in</li>
</ul>
<p>MQTT-Plug is infrastructure-agnostic. You control your broker, topics, and data flow.</p>
<h3>Configuration</h3>
<p>In <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> MQTT-Plug</strong>, configure:</p>
<ul>
<li>Broker host</li>
<li>WebSocket port</li>
<li>TLS / secure connection (WSS)</li>
<li>Username and password (if required)</li>
<li>Base topic or subscription filter</li>
<li>Debug logging (optional)</li>
</ul>
<p>All credentials are stored using WordPress options and are never exposed to public users unless explicitly enabled.</p>
<h3>Usage</h3>
<p>Basic shortcode:</p>
<p>[mqtt_plug]</p>
<p>Optional attributes:</p>
<ul>
<li><code>height="520px"</code> – set container height</li>
<li><code>class="custom-class"</code> – add a CSS hook</li>
<li><code>mode="observer"</code> – server-fed or read-only views (if enabled)</li>
</ul>
<p>Example:</p>
<p>[mqtt_plug height=”600px” class=”iot-dashboard” mode=”observer”]</p>
<h3>Security Notes</h3>
<ul>
<li>Public pages should <strong>not</strong> use live credentials.</li>
<li>Use observer or server-fed modes for public dashboards.</li>
<li>Always prefer WSS when exposing MQTT over the internet.</li>
<li>Rotate credentials regularly for production systems.</li>
</ul>
<p>MQTT-Plug does not open inbound ports on WordPress and does not proxy MQTT traffic through the server unless explicitly configured.</p>
<h3>License</h3>
<p>GPLv2 or later.</p>
<h3>Credits</h3>
<p>Developed by <strong>Michael Winchester</strong><br />
For documentation and updates, visit <a href="https://meshplug.michaelwinchester.com/" rel="nofollow ugc">https://meshplug.michaelwinchester.com/</a></p>


MQTT-Plug

Real-time MQTT dashboards inside WordPress. Connect securely over WebSocket (WS/WSS) and visualize live IoT data, logs, and events.

WordSocket vs MQTT-Plug