Tuya Opens Meta's Muse Agent to Cloud-Connected Smart Homes

Tuya Smart announced on November 12, 2026 that Meta's Muse AI agent can now query and control devices in a user's Tuya account through cloud APIs — no local device keys, no shared network, no firmware changes. The delivery vehicle is an open-source skill called gadget-tuya-cloud-devices, and it exists today as a plain Markdown file.

That's the whole trick. Muse supplies the conversational and agent capabilities. Tuya supplies the connectivity to what the company says is a platform spanning more than 3,000 smart-hardware categories across more than 200 countries and regions. One caveat worth pinning early: those figures describe Tuya's platform broadly, not devices specifically verified to work with Muse.

What does the skill actually do?

The new skill adapts Tuya's existing tuya-smart-control skill to the Muse Gadgets specification. In practice, it targets hardware users already own — lights, outlets, air conditioners, cameras and sensors connected to their Tuya cloud account.

That's a deliberate departure from the direction Meta's own Muse Gadgets project has taken so far. Meta's open-source SDKs support add-on hardware: ESP32 boards, Raspberry Pi and other Linux systems. Tuya skipped that route entirely. Instead of building another device for Muse, the company pointed the agent at the installed base.

The timing matters for the agent market. Every major AI assistant is racing to become the interface through which people control their homes. An integration that reaches millions of already-deployed devices — rather than hobbyist boards — gives Muse a practical foothold it didn't have before.

How does cloud access replace per-device setup?

A single free API key authenticates every request. The two characters after the key's sk- prefix identify the account's data center and automatically select one of seven regional endpoints. That removes manual endpoint configuration, a recurring friction point for smart-home integrators.

Users also skip local-key setup entirely. Under the old local approach, a key could become invalid whenever a device was re-paired, forcing the whole configuration process to be repeated.

Before the skill generates any command, it reads the device's Thing Model — a standardized description of supported properties, read/write permissions, value ranges and increments. Tuya's API documentation recommends reading that model before issuing commands. The payoff is generality: one skill can handle different product categories without a separate adaptation for each model. When a model-specific or local-control skill already exists, requests route there first.

What can users control — and what's off-limits?

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. But those subscriptions demand 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 runs trigger-action automations — with user confirmation required.

The guardrails are explicit. Event-triggered notifications go only to the user, via SMS, voice call, email or app push, and at least 30 minutes must pass between alerts. When several devices match a request, the skill lists their rooms and asks for confirmation. It refuses to command offline devices or write to read-only properties. After issuing a command, it reads status back one to two seconds later before confirming success.

Hard limits remain. Door-lock control, live video, firmware upgrades, network configuration, device pairing and removal, and complex data types are all excluded — and directed to the Tuya app instead. The API key lives only in request headers, is never echoed into conversations, and can reach only devices in the user's own account.

Is the integration finished?

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

The upstream status is even less settled. 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 is merged, the Muse Gadgets repository does not hold the authoritative copy. Tuya's own tuya-smart-control remains the canonical skill.

There's also a geographic boundary: Muse is currently available only in the United States and Canada.

Could this spread beyond Muse?

Tuya thinks so. Users can grab the adaptation from Tuya's GitHub repository and request a free API key. Developers can go further — the underlying skill follows the SKILL.md format, so other agents that support that format can reuse it. Tuya argues this portability could let brands expose connected devices to more agent ecosystems without building a separate integration for each one.

That claim points at the broader stakes. If skills written once can serve multiple agent platforms, device makers gain a cheaper path into the assistant economy, and the choice of agent becomes less locked to the choice of hardware.

For now, the release extends Muse's potential reach beyond purpose-built hardware and toward devices already installed in homes. Its practical scope stays bounded by trial API restrictions and a pull request still sitting in review — how fast Meta merges it will determine whether this becomes a mainstream control path or stays a developer curiosity.