gadget-vesync-humidifier
Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub
Cloud only: needs internet access and the user's VeSync account; does not use Muse Home Link or the local network. Read and control a VeSync-connected Levoit humidifier (e.g. Classic 200S / 300S) through the VeSync cloud API: power, target humidity, mode, mist level, current humidity, and water-empty state. VeSync humidifiers have no local API.
Trending
More talk lately.thin dataabout the whole repository
Who's talking about facebookincubator/muse-gadget-sdk
- @j4ck.xyz“I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty …”Bluesky · Oct 2, 2026 · 7 likes
- A Hacker News story“Open source SDK to build Muse gadgets”Hacker News · Oct 3, 2026 · 2 points
- ComBba/muse-gadget-sdk“CI preflight: wait for the installer serial close before SDK token setup”GitHub · Oct 17, 2026 · 1 reactions
- @sarubot.bsky.social“muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! …”Bluesky · Oct 7, 2026 · 1 likes
- aegisfleet/tool-survey-report“feat: add survey report for Muse Gadget SDK”GitHub · Nov 9, 2026
The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 14
Talked about on GitHub, Bluesky and Hacker News (14 times).
On GitHub · 11
- Oct 17, 2026CI preflight: wait for the installer serial close before SDK token setup — ComBba/muse-gadget-sdk1 reaction · 2 comments
- Nov 9, 2026feat: add survey report for Muse Gadget SDK — aegisfleet/tool-survey-report0 reactions · 4 comments
- Oct 14, 2026Fix S3-2.06 ES7210 microphone and native USB serial console — polygoku/waveshare-amoled-206-debug0 reactions · 5 comments
- Oct 12, 2026Integration blocker: native Muse gadget command invocation — 1chris2many/muse-portal-kit0 reactions
- Oct 12, 2026Integration blocker: authoritative per-device reply correlation — 1chris2many/muse-portal-kit0 reactions · 2 comments
6 more on GitHub
- Oct 11, 2026[fork CI preflight] #181 candidate a6fd89c — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #179 Use the custom avatar in the UI simulator — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #181 Add validated avatar restore and host status — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #180 Validate avatar candidates before replacing the current renderer — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #174 Reject incomplete bench screenshots without padding pixels — ComBba/muse-gadget-sdk0 reactions · 1 comment
- Oct 11, 2026[fork CI] #177 Abort bench screenshots when USB console output stalls — ComBba/muse-gadget-sdk0 reactions · 1 comment
On Bluesky · 2
- Oct 2, 2026I still wouldn't trust Meta with my personal context for agents, but what they're doing with Muse is pretty cool & fun icl… — @j4ck.xyz7 likes and reposts
- Oct 7, 2026muse-gadget-sdk — Metaが放つ、ESP32やラズパイをAIガジェットへ変貌させるSDK。今週スター急増中の注目作! ・C言語製のESP32/Linux用SDK。センサーやオーディオをMuseエコシステムに即統合 ・AIエージェント「Muse… — @sarubot.bsky.social1 likes and repost
On Hacker News · 1
- Oct 3, 2026Open source SDK to build Muse gadgets2 points
In this repository57 other files it gives its agents.
- esp32/AGENTS.mdAGENTS.md
- linux/AGENTS.mdAGENTS.md
- gadget-amazon-echoSkill
- gadget-apple-homepod-miniSkill
- gadget-apple-tv-4kSkill
- gadget-bambu-lab-p2sSkill
- gadget-bambu-lab-printersSkill
- gadget-brother-printersSkill
- gadget-dyson-pure-hot-cool-hp04Skill
- gadget-ecowitt-gatewaysSkill
- gadget-elgato-key-lightSkill
- gadget-epson-printersSkill
- gadget-esphome-devicesSkill
- gadget-espsomfy-rtsSkill
- gadget-eufy-robovac-tuyaSkill
- gadget-freebox-player-popSkill
- gadget-google-castSkill
- gadget-google-home-maxSkill
- gadget-google-home-speakerSkill
- gadget-google-nest-audioSkill
- gadget-google-nest-hub-maxSkill
- gadget-google-nest-hubSkill
- gadget-google-nest-miniSkill
- gadget-google-nest-thermostatsSkill
- gadget-google-pixel-tabletSkill
- gadget-google-tv-streamerSkill
- gadget-homewhiz-laundrySkill
- gadget-hp-color-laserjet-pro-m254dwSkill
- gadget-insignia-fire-tvSkill
- gadget-irobot-roomba-braavaSkill
- gadget-lg-webos-tvsSkill
- gadget-logitech-squeezeboxSkill
- gadget-lutron-smart-bridgesSkill
- gadget-meross-smart-plugsSkill
- gadget-miele-g7566-dishwasherSkill
- gadget-moonraker-3d-printersSkill
- gadget-philips-hue-bridgesSkill
- gadget-pixoo-64Skill
- gadget-ratgdo-v32-garage-doorSkill
- gadget-roborock-vacuumsSkill
- gadget-roku-tvs-and-playersSkill
- gadget-samsung-tizen-tvsSkill
- gadget-shelly-plugsSkill
- gadget-sinricpro-cloud-devicesSkill
- gadget-sonoff-rf-bridgeSkill
- gadget-sonos-speakersSkill
- gadget-teslaSkill
- gadget-tplink-kasa-ep10Skill
- gadget-tplink-kasa-ep25Skill
- gadget-tuya-cloud-devicesSkill
- gadget-tuya-wifi-devicesSkill
- gadget-unifi-network-consolesSkill
- gadget-velux-klf200Skill
- gadget-vizio-d40f-g9Skill
- gadget-wyze-rtsp-camerasSkill
- gadget-yi-hack-camerasSkill
- gadget-zigbee2mqtt-gatewaysSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill when the task concerns a VeSync-connected humidifier: state checks ("how humid is the bedroom"), target-humidity changes, …
- Distinctive: line 49
Keep the persisted token in the same secret storage, not in a plain file.
- Distinctive: line 69
Read fresh state first. If the device is offline, report that and send nothing.
- Distinctive: line 72
Wait a second or two, then read fresh state again.
- Very specific: line 81
Never run the humidifier with an empty tank: check water_lacks before turning on or raising mist.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
VeSync Humidifier (Levoit)
Use this skill when the task concerns a VeSync-connected humidifier: state checks ("how humid is the bedroom"), target-humidity changes, power, mode, or mist control, and water-empty alerts.
Identify the Device
- The humidifier is enrolled in the user's VeSync account and named there (the account name is the identity; the device also carries a model code, e.g. Classic200S).
- Match the user's words against the device names on the account. With more than one match, list the candidates and ask; never guess.
- Confirm model before using model-dependent commands: mist-level ranges and modes (auto / manual / sleep) vary by model. Use only the values the client reports for this model.
Local Access Verdict
- VeSync devices are cloud-only. Control and state run through the
vendor's account API (
smartapi.vesync.com, orsmartapi.vesync.eufor EU accounts; the client picks the account's region); the device keeps a persistent outbound connection to the vendor cloud and exposes no LAN control or state endpoint. Community and vendor tooling (e.g. pyvesync) is uniformly cloud-based. - A LAN probe finding no service is the expected result. Do not attempt local pairing hacks or firmware mods for local control.
Prerequisites
- Cloud only. Internet access from Muse to the VeSync API, using the normal internet path, never the Home Link proxy; a Muse Home Link is not required. If the cloud is unreachable, report that rather than trying a local path.
- The user's VeSync account credentials, supplied through approved secret storage. Never ask for the password in chat, never put it or the session token on a command line, and never print, log, or send either anywhere except to the VeSync API through the client. Keep the persisted token in the same secret storage, not in a plain file. If no credentials are stored, explain this setup instead.
The Lane
- Direct client on the VeSync account API (pyvesync or equivalent): password login once → persisted token → device list → per-device detail reads and commands.
- State read returns: power, connection status, current humidity, target humidity, mode, mist level, water-lacks (empty tank), tank-lifted, humidity-high flags.
- Commands: on/off, set target humidity, set mode, set mist level.
- Background polling runs no tighter than every 5 minutes; the reads around a requested change (below) are separate. The token is reused; the password is only needed again if the token is rejected.
Changing Settings
- Act only on the user's request for this named device. A state question is never permission to change anything.
- Read fresh state first. If the device is offline, report that and send nothing.
- Send one command for the requested change.
- Wait a second or two, then read fresh state again. Report the change done only when that read succeeds and shows it; the client's cached state after a command does not count. If the read fails, returns nothing usable, or does not show the change, say the change is unconfirmed and report what the device last showed. Never resend a command automatically.
Safety Limits
- Never run the humidifier with an empty tank: check
water_lacksbefore turning on or raising mist; if the tank lacks water, report instead of running it dry. - Target humidity stays in the healthy indoor band (40–50% unless the user directs otherwise); sustained >60% indoor humidity risks mold.
- An account login rejection can mean the account is SSO-only ("Sign in with Google") with no password set — do not retry-loop; surface it.
Verification
- A live state read returning the device online with a plausible current-humidity value is the health check. Cross-check once against the VeSync app or the device's own display on a new deployment, and verify any command by read-back.
Sources
- pyvesync: VeSync account API client, including Levoit humidifiers
(checked against 3.5.1; field names such as
water_lacksare pyvesync's)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

