Home · Community report
Make a shared shopping list
Make a shared shopping list. Keep household groceries in one place.
What you can get
What it is
Shared list setup
A shared grocery list organized so household members can add and check off items.
It came back right when
- An item added on any device appears on the others within a stated time.
- A checked-off item stays checked off and does not return on the next sync.
- The credential used is scoped to the list and nothing else.
- The setup steps are written down well enough for someone else to repeat them.
- Nothing was installed or authenticated on your behalf.
The checks are editorial, not from the source.
- Map what existsStops for your approval
Current list, who edits it, which devices matter.
- Choose the authorityStops for your approval
One system wins; deletions follow it.
- Write the steps
Setup instructions and scoped credentials you place yourself.
- Test as a householdStops for your approval
Every device, every operation, timed.
Editorial, not from the source
Works when
- You already run Home Assistant and are comfortable maintaining it.
- One system can be named as the authoritative list.
- You will test with throwaway items before the household depends on it.
Does not work when
- You want a shared list without running any infrastructure.
- Both systems must accept edits and neither can be authoritative.
- Nobody in the household can fix it when an API changes.
Make a shared shopping list: setup template
| Piece | Decision | Tested |
|---|---|---|
| [Authoritative list] | [Which system wins] | [Deletion test passed] |
| [Credential] | [Scope: list only] | [Placed by you] |
| [Devices] | [Who adds and checks off] | [Each one tried] |
The source case
On X, @v01dp1r4t3 says that because the Amazon Alexa app is unstable, he had Muse create a syncing dashboard artifact using Home Assistant to bridge between them, and that he now has a stable shortcut on his home screen to the family's shared shopping list. An image is attached. The post does not show the configuration, say how the sync works, or report how it has held up since, and nothing here has been run by this directory.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Since the @AmazonAlexa app is unstable, I had @Muse create a syncing dashboard artifact using @home_assistant to handle the go between. Now I finally have a stable shortcut on my home screen to our families shared shopping list.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Home Assistant setup, Which list is authoritative today, Who needs to add and check off items. Acts Prepares the configuration and the steps. Does not install, authenticate or change your home automation setup. Source community report, checked 2026-09-18.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Home Assistant setup
- Which list is authoritative today
- Who needs to add and check off items
Connected
- Your own hub, and whichever list app the household already uses
Approved by you
- Scoped credentials that you create and place yourself
- No authorization to hold or use household hub tokens
How to try it
Editorial, not from the source
- Say what already exists: which list is the real one today, who adds to it, and on which devices it has to work.
- Decide which system holds the authoritative list. A sync between two systems that both accept edits needs a rule for what happens when both change.
- Ask for the setup to be written down as steps you perform, including where any token or credential goes and what access it grants.
- Test with a throwaway item from each person's device before the household relies on it.
Decide which list is the real one
The hard part of a shared list is not moving items, it is deciding who wins. If two systems both accept edits, an item deleted in one will come back from the other, and a list that resurrects deleted items stops being used within a week. Name one system as authoritative and let the rest mirror it. Say which devices genuinely have to work: a shortcut on one phone is not a household list, and the person most likely to be standing in the shop is the one whose device matters most. Write down what exists today, because the current list has a habit of continuing to exist alongside the new one.
Keep the credential small
A home automation hub holds tokens that can do far more than manage groceries. When a bridge asks for access, create a credential scoped to the list alone, place it yourself, and record where it lives so it can be rotated later. Nothing about a shopping list justifies a token that can unlock a door, disarm an alarm or read a camera feed. The same applies to whatever the other end is: a household app account is usually attached to a person, and sharing it broadly to make a list work is a trade worth noticing before rather than after. Ask for the setup as instructions you perform, not as actions taken for you.
Test it like a household, not like a demo
Add a throwaway item from each person's device, check it off from a different one, delete it from a third, and watch what the others do. Note how long propagation takes, because a list that syncs in four minutes is useless at the checkout. Expect breakage: consumer app APIs change without notice, and integrations built on them stop working at moments nobody chose. That is not an argument against building it, but it is an argument for writing down the steps well enough that anyone in the house can rebuild it, rather than leaving the household list dependent on whoever set it up remembering how.
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
- This is a home-automation integration, not a feature. It depends on your own Home Assistant instance and on APIs that change without notice.
- Tokens for a household hub are broad. A shopping-list bridge should not hold credentials that can open a door, disarm an alarm or read cameras.
- Sync conflicts are the normal failure mode: an item deleted on one device reappearing from the other is what makes a shared list stop being trusted.
- One attributed report of a working setup does not establish that it keeps working, or that it can be reproduced on your hardware.
Stop and check
Editorial, not from the source
- Before it starts: name the authoritative list and the devices that must work.
- Before any credential is created: confirm its scope is limited to the list.
- Before the household switches: test add, check off and delete from each person's device.
If it goes wrong
Editorial, not from the source
- Deleted items come back
- Name one system as authoritative and make the other follow it; two-way sync without a winner will resurrect deletions indefinitely.
- The list stops syncing after an app update
- Expect this. Keep the setup steps written down so the bridge can be rebuilt, and check the integration after major updates.
- The shortcut works for one person only
- Test from each household member's own device and account; a setup validated on the builder's phone regularly fails for everyone else.
Common questions
Why does one list have to be authoritative?
Because deletions need a winner. Two systems that both accept edits will keep reviving items each other removed, and that is the single most common reason a shared list gets abandoned.
What access should the bridge have?
Only the list. A hub token that can also control locks, alarms or cameras is far more access than groceries require, and it is worth scoping before anything is connected.
Will this keep working?
Unknown. It depends on consumer app APIs that change without notice. Write the setup down so it can be rebuilt, and check it after major app updates.
How do I test it properly?
From each household member's own device: add, check off and delete a throwaway item and see what the other devices do, and time how long propagation takes.
Can it set this up for me?
Not as written here. It prepares the configuration and the steps; installing, authenticating and placing credentials stay with you, because that is where the access decisions are.
Next in Home
Get recurring task recommendations — ask your own agent to check for relevant updates.