Innovation & Tech

Tuya Links Meta's Muse to Smart Homes via Cloud APIs

Tuya's open-source skill lets Meta's Muse control lights, cameras and sensors already in users' homes via cloud APIs — one free key, no firmware changes, pending Meta's review.

By Grace Kim

4 min read

Tuya Connects Meta’s Muse to Smart Home Devices Through Cloud APIs
Tuya Connects Meta’s Muse to Smart Home Devices Through Cloud APIsgeralt / pixabay

What's News

  • Tuya announced the gadget-tuya-cloud-devices skill for Meta's Muse on November 12, 2026.
  • The skill uses one free API key selecting one of seven regional endpoints — no local keys or firmware changes.
  • Tuya's platform spans 3,000+ smart-hardware categories across 200+ countries and regions.
  • Camera videos via Muse are capped at 60 seconds; alerts require at least 30 minutes between notifications.
  • The skill sits in Meta's review queue as pull request #61; all Tuya APIs remain trial-phase.

Tuya Smart announced on November 12, 2026 an open-source skill that lets Meta's Muse AI agent query and control smart home devices through cloud APIs — no local device keys, no shared network, no firmware changes.

The skill, formally named gadget-tuya-cloud-devices, adapts Tuya's existing tuya-smart-control skill to the Muse Gadgets specification as a plain Markdown file. Muse supplies the conversational and agent capabilities. Tuya supplies the device connectivity.

Tuya reports its platform covers more than 3,000 smart-hardware categories across more than 200 countries and regions. Those figures describe Tuya's platform, not devices verified to work with Muse.

How does it differ from Meta's own hardware path?

Meta's Muse Gadgets project enables add-on hardware through open-source SDKs supporting ESP32 boards and Raspberry Pi or other Linux systems. Tuya skipped that route. Instead of building another device for Muse, the skill addresses lights, outlets, air conditioners, cameras and sensors already connected to a user's cloud account.

The practical effect: Muse's reach extends beyond purpose-built gadgets toward hardware already installed in homes.

What replaces per-device setup?

A single free API key authenticates requests. The two characters following its sk- prefix identify the account's data center and select one of seven regional endpoints, removing manual endpoint configuration. That matters because local-key setup has a known pain point: a key becomes invalid when a device is re-paired, forcing users to repeat the configuration.

Before generating any command, the skill reads the device's Thing Model — a standardized description of supported properties, read/write permissions, value ranges and increments. The API documentation recommends reading the model before issuing commands. One skill can then handle different product categories without a separate adaptation per model, and requests route first to a model-specific or local-control skill when one already exists.

What can Muse actually do?

Supported interactions include:

  • listing homes, rooms and devices
  • renaming devices
  • changing switches, brightness, temperature or mode
  • checking weather and energy statistics
  • capturing camera snapshots or videos of up to 60 seconds

Real-time subscriptions use WebSocket events for property changes and online/offline status. Those subscriptions require an always-online Linux device. Tuya describes a Raspberry Pi connected through the Muse Gadgets Linux SDK, where Muse can deploy a resident program that receives events and executes user-confirmed trigger-action automations.

Notifications face hard limits. Event-triggered alerts go only to the user via SMS, voice call, email or app push, with at least 30 minutes between alerts.

What safeguards constrain the agent?

The control path keeps physical devices protected. When several devices match a request, the skill lists their rooms and asks for confirmation. It does not command offline devices or write read-only properties. It reads status back one to two seconds after a command before confirming success.

Several functions stay off-limits entirely. Door-lock control, live video, firmware upgrades, network configuration, device pairing or removal, and complex data types are excluded and directed to the Tuya app. The API key is used only in request headers, never echoed into conversations, and can access only devices in the user's own account.

What's still pending?

The underlying Tuya repository is MIT-licensed but labels every currently available API endpoint as trial-phase, subject to rate limits, call quotas and other usage restrictions.

The upstream review is also unfinished. Tuya's Muse adaptation directory says the skill was submitted to Meta's project as pull request #61 and remains in review. Until that submission merges, the Muse Gadgets repository does not hold the authoritative copy; tuya-smart-control remains canonical in Tuya's repository.

Muse is currently available in the United States and Canada. Users can obtain the adaptation from Tuya's GitHub repository and request a free API key. Developers can reuse the underlying skill with other agents that support the SKILL.md format — portability Tuya says could let brands expose connected devices to more agent ecosystems without building a separate integration for each agent.

Until Meta merges pull request #61 and Tuya's trial APIs stabilize, the skill's reach into millions of installed devices remains a promise bounded by rate limits and an open review queue.

Source: unite.ai

Share this article:

More from Grace Kim

Grace Kim

Show full bio

Market editor covering people, launches and day-to-day practice in entrepreneurship, startups and venture funding at Business Bearings.

1,985 articles

Related articles

« Previous articleNext article »