vhm24-realtime

Ingest and distribute real-time VendHub machine telemetry via WebSocket streams.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jamsmac/VHM24 --skill vhm24-realtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vhm24-realtime
Source: https://github.com/jamsmac/VHM24/tree/main/skills/vhm24-realtime
Command: npx skills add https://github.com/jamsmac/VHM24 --skill vhm24-realtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VendHub Realtime patterns address the need to handle live telemetry, WebSocket streams, and distributed updates for vending machines, enabling real-time visibility and responsive alerts.

Core Features & Use Cases

  • WebSocket-based telemetry streams and room-based subscriptions for per-machine or global updates.
  • Live map integration and online/offline monitoring with alerting.
  • Client and server examples to bootstrap real-time dashboards and notification systems.

Quick Start

Use the provided server and client patterns to bootstrap a real-time telemetry workflow for VendHub machines, starting from the example server.ts and client.ts.

Frequently Asked Questions about vhm24-realtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement real-time telemetry streaming for IoT devices using WebSocket and Redis pub/sub?

Real-time telemetry streaming uses WebSocket handlers and Redis-backed publish/subscribe channels to ingest and distribute live machine data. It enables room-based subscriptions so clients receive per-machine or global updates instantly across a distributed network.

What is the best way to build a live map dashboard with online and offline status monitoring?

Building a live map dashboard relies on client hooks that subscribe to WebSocket telemetry streams and render updates in real time. The server-side handlers broadcast online and offline status changes, enabling responsive alerting and continuous visibility.

How do I set up WebSocket room-based subscriptions for distributed vending machine networks?

WebSocket room-based subscriptions group clients by specific machine channels using Redis pub/sub for message distribution. Clients join designated rooms to receive targeted telemetry updates, allowing granular per-machine monitoring or broader global network visibility.

Can I use Redis publish/subscribe to handle live telemetry ingestion and alerting without extra dependencies?

Redis publish/subscribe handles live telemetry ingestion and alerting natively by routing messages through WebSocket servers to subscribed clients. This architecture supports distributed updates and online/offline monitoring without requiring additional external message brokers.

Why use WebSocket streams instead of HTTP polling for real-time vending machine telemetry and notifications?

WebSocket streams maintain persistent connections for immediate telemetry push, unlike HTTP polling which introduces latency. Combined with Redis pub/sub, WebSockets deliver instant alerts and live map updates, reducing server load and ensuring responsive dashboards.

What do I need to bootstrap a real-time telemetry workflow for distributed machine monitoring?

Bootstrapping a real-time telemetry workflow requires server-side WebSocket handlers and Redis pub/sub configuration, starting from provided server and client examples. These patterns establish the data streams and client hooks needed to render live dashboards.