Home · Community report
Turn on a lamp through Home Assistant
A creator posting as ShojiGarden on TikTok reports connecting Home Assistant to Muse with an access token and switching on a living room lamp with one sentence. This page sets out the token, connection and single-light test, with the security checks the caption leaves out.
What you can get
What it is
A working one-light connection
One living room light switched on by a plain sentence through a smart home connection you set up and can revoke, not a whole-home automation or security setup.
It came back right when
- Your dashboard shows the named light switched on
- No other device changed state
- The token appears in your profile under a name you recognise
The checks are editorial, not from the source.
- Prepare
A running smart home server and its address
- Ask and review
Check that your instance is reachable at the address you plan to give, and decide whether exposing it outside your home network is acceptable to you.
- Check the result
Your dashboard shows the named light switched on
The source case
@jeanwcharles, in a TikTok caption signed ShojiGarden, describes linking their smart home server to Meta Muse in three steps: creating a long-lived access token in the user profile, adding their server as a connected device in Muse with the home's address and the token, and then asking it to turn on the living room light. By their account, a lamp turned on from that one sentence. The caption does not show which lamp or integration was involved, how the address was exposed to Muse, what Muse replied, or whether any other device was tried.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Create a long-lived access token in your Home Assistant profile — you can revoke it anytime
Source excerpt
Add Home Assistant as a connected device in Meta Muse: paste your home's address and the token. Just once
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring A running smart home server and its address, A long-lived access token created in your user profile, The exact name of the light you want to control. Source community report, checked 2026-11-03.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- A running smart home server and its address
- A long-lived access token created in your user profile
- The exact name of the light you want to control
How to try it
Editorial, not from the source
- Check that your instance is reachable at the address you plan to give, and decide whether exposing it outside your home network is acceptable to you.
- In your user profile, create a long-lived access token with a clear name such as the agent's name, and copy it once.
- Add your server as a connected device in Muse, pasting the address and token into the connection screen rather than into a chat message.
- Ask Muse to list the lights it can see before giving any command, and match each name to the entity on your dashboard.
- Send a single command for one light, then confirm on the dashboard that the state changed.
- If you stop using the connection, delete the token in your profile so the access ends.
What the ShojiGarden caption describes
The post is billed as episode 1 of a series called Our Discoveries. The caption lists three steps: make a long-lived access token in the user profile, add the server as a connected device in Muse by pasting the home's address and the token, then ask: "Turn on the living room light." The author says a lamp came on with "No remote, no switch."
That is the whole account. The caption gives no reply text from Muse, no entity name and no detail on how the address was reachable, so treat it as a short walkthrough rather than a record of how the connection behaves over time.
Keeping the access token under control
Long-lived access tokens are created from the user profile page and are shown only once. As general practice, give each token a name that says which service holds it, so you can find and delete it later; the caption itself notes you can revoke it anytime.
A token carries the permissions of the user who made it. If your main account is an administrator, some people create a separate non-admin user for outside services; that is a general choice, not something the source describes. Never paste the token into an ordinary chat message or a screenshot.
Testing one light before anything else
Start with a lamp, because a wrong command costs nothing. Ask for a list of visible lights first, then name one exactly as your dashboard labels it, and check the dashboard after the command. Only after that works would it make sense to try a second device, and anything that controls entry or heat deserves a separate decision.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- The caption does not show the Muse reply, the entity, or any log confirming the light changed; what appears on screen in the video is not described in the caption.
- Only one device, a living room light, is reported. Nothing in the source covers locks, heating, scenes or automations.
- The source does not say whether the address was a local or remote URL, or what security setup was used.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
If it goes wrong
Editorial, not from the source
- Muse cannot reach your server address
- Check that the address works from outside your home network, if that is how you set it up, and that the URL includes the right port and https.
- The wrong light turns on, or none does
- Ask for the list of entities it sees and use the exact name your dashboard shows; rename the entity there if two names are similar.
- You think the token was exposed
- Delete it in your user profile right away, create a new one and add the connection again.
Common questions
Can Meta Muse control smart home devices?
One creator reports adding their server as a connected device in Muse and turning on a living room light with one sentence. The post shows no reply or logs, and this guide has not reproduced it.
Where do I get a long-lived access token?
Long-lived access tokens are created in your user profile. The token is shown once, so copy it straight into the connection screen.
How do I cut off access later?
Delete the token in your user profile. The caption says the token can be revoked anytime; removing the connection in Muse as well is a sensible extra step.
Does this work for locks or heating?
The source only reports a living room light. Nothing in it covers other device types, so test and approve those separately if you try them.
Next
Related to this task
More in Home
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.