Welcome to Cordnewyork
Cordnewyork is the home page of CORD New York, a community organization based in New York. The site also collects short articles and updates spanning technology, lifestyle, and travel. Use the menu on the left to jump to specific sections, or scroll down for the latest posts.
Within these pages you will find notes on CORD NYC's past events, profiles of the Leadership Advisory Board, and a growing archive of newsroom-style features published under the Cordnewyork byline.
Five Things You'll Find Here
- WordPress-powered news and notes from the CORD NYC desk.
- An events archive covering community activities in and around New York.
- Profiles of the Leadership Advisory Board members who guide the organization.
- Reports on the impact of community projects, including food drives and walkathons.
- Reader-friendly technology and travel write-ups, refreshed on a rolling basis.
Why Siri Cannot Set a HomePod Sleep Alarm with a Custom Wake-Up Track
Asleep in Sydney, Brisbane or Hobart, plenty of Australians swear by a spoken request: wake me at half five, play the test-drive song. On a HomePod, the alarm appears, the tone that sounds is one of Apple's built-in noises, and the requested track never arrives at the right moment. The frustration is consistent across households because the failure is structural rather than a hardware fault.
The assistant can reliably create an alarm, and it can reliably start a song. What it cannot do is bind an arbitrary song from a personal music library to the moment the alarm fires. That specific wake-up sound remains tied to a fixed set of tones chosen inside the Home app on an iPhone, and natural language has no path to that setting.
Several things compound the problem: how precisely the request is transcribed, whether the speaker has a usable connection to Apple's servers, and how consistently the command is phrased. Better language models, on-device processing and tighter device integration could narrow the gap over time, yet the audio library boundary remains the hardest part.
What actually happens when you ask Siri for a sleep alarm
The HomePod carries a dedicated alarms and timers domain, and plain instructions inside that domain work well. "Set an alarm for 6:15" registers cleanly, appears in the Home app, syncs through iCloud and sounds at the right hour even when the internet connection drops.
The trouble starts when a modifier joins the request. Phrases such as "with the Foo Fighters track playing" or "using the slow piano version" get parsed either as a label attached to the alarm, so the alarm appears with a strange name, or as a second instruction to play something immediately. Either way, the wake-up source stays whatever tone was already configured.
A further limitation sits underneath: the wake-up sound is an enumerated choice within the alarm system, not a free-text pointer into the Music library. A song title is not a valid value for that field. Even flawless recognition of every word in the request would not let the assistant populate it, because the required feature does not exist yet.
Where Australian speech recognition loses the thread
Australian English is unusual for a reason that matters here. Melbourne, Adelaide and western Sydney are full of speakers whose first language was Greek, Italian, Mandarin, Punjabi or Arabic, and those speakers often code-switch mid-sentence. A two-part command spoken quickly, half-awake, carries a much higher error rate than a single verb and a time.
Homophones cause a specific family of errors. A closely related case, where the system showed a failure to distinguish note and know in a dictated reminder, illustrates the pattern: one misheard sound becomes a silently wrong action rather than an error message. The same substitution inside an alarm request can produce a reminder about waking up, or an alarm set to the wrong hour.
Phrasing habits matter as well. "Wake me at six fifteen" and "set an alarm for a quarter past six" travel through completely different parsing paths, and adding a request for music at the end increases the chance that the wake-up clause itself is absorbed into something else. Reminders, timers and alarms remain separate intents in most households, and mixing them muddies the result.
Why a named wake-up track complicates everything
Matching a track by name is harder than it looks. "Yellow" could be Coldplay, the Beyonce cover, a podcast episode or a local band. The assistant has to disambiguate title, artist, version and recording type, and if the track lives in a purchased or personal library, it must reach the right account and library index before playback begins.
That step is also where the wake-up request quietly collapses. The alarm system and the media player are separate subsystems, and joining them requires a binding feature that has never shipped for HomePod. The best the assistant can manage is to schedule an alarm and, separately, begin playing music now, which is worse than a refusal because the owner may believe the request succeeded.
Bandwidth is rarely the obstacle at this point. A page as light as online blackjack practice mode loads instantly over the same domestic connection in seconds. The bottleneck is interpretation and device integration, not throughput, which is why better networks alone will not fix the request.
The Australian setting for networks, law and routines
HomePods reach Australian households at roughly four hundred to four hundred and fifty dollars, sold through Apple Stores in Sydney and Melbourne, JB Hi-Fi and Amazon Australia, and almost always configured by an iPhone nearby. Connectivity varies sharply across the country. In metropolitan areas NBN fixed wireless and Telstra or Optus 5G handle voice requests comfortably; in regional New South Wales, inland Queensland and parts of Western Australia, blackspots leave a command stalled before it ever reaches Apple's servers, while a locally stored alarm still rings.
Regulation adds context for anyone weighing voice data. The Privacy Act 1988 and the Australian Privacy Principles govern how voice recordings and synced data are handled, and repairability has become a live policy issue after Victoria's right to repair legislation and comparable moves in New South Wales and South Australia. The Australian Consumer Law guarantees also apply to these purchases.
Daily habits finish the picture. Australians shift clocks in the first Sunday of October and the first Sunday of April, and households routinely re-check sleep alarms in the fortnight either side. Shared flats complicate the audio step further, where a wake-up tone loud enough for one sleeper is hostile to the rest of the house.
The practical differences come down to a few variables:
| Method | Requires an iPhone | Custom wake-up track | Functions without internet | Handles varied accents |
|---|---|---|---|---|
| Voice request to Siri on HomePod | No | No | No | Partly |
| Alarm editor in the Home app | Yes | Built-in tones only | Yes | Not applicable |
| Siri on an iPhone | Yes | No | Partly | Partly |
| Third-party clock app with audio library | Yes | Yes | Yes | Not applicable |
| Alexa or Google speaker | No | Limited | No | Partly |
Workarounds worth trying tonight
A few request patterns behave far better than others, and testing them during daylight hours reveals the limits quickly.
- "Set an alarm for 6:15" spoken plainly, with the speaker already awake and listening.
- "Set a timer for ten minutes," which is fast and dependable for cooking and laundry tasks.
- "What time is my first alarm," used as a verification step after any complicated request.
- "Remind me to take the bins out," since reminder phrasing is often parsed more accurately than alarm phrasing.
The more durable fixes involve doing the audio work yourself.
- Create the alarm in the Home app and choose a tone, then set the volume so it wakes one sleeper in a share house.
- Keep a backup alarm on an iPhone, especially across the October and April daylight-saving changes.
- Download the track to the speaker or phone beforehand so playback does not depend on mobile data at dawn.
- Note the exact wording that worked so the same phrase can be repeated on a bad night.
Siri still earns its place in Australian homes for alarms, timers and reminders, and Apple's language models keep getting sharper. The gap is narrower than it was, yet a named wake-up track remains a hardware and software boundary rather than a wording problem. Cord New York tracks the same failures in detail on Cord New York, and readers are welcome to send in the exact phrase their speaker misheard so the next test covers it.
Need a Hand Navigating?
If you are looking for something specific, the left-hand menu leads you to the main sections: About Us, Join Us, Past Events in New York, Impact of CORD, and the CORD NY Leadership page. The Donate page is the place to support the organization financially.
Ask a Question
Use the form below to send a note to the editorial team. We read every message.
What Readers Say
The events archive is the easiest way to follow what CORD NYC has been doing over the years. Clean and to the point.
— Recent visitorI appreciate having the leadership profiles alongside the community news. It keeps the people behind the work visible.
— Site readerThe technology and travel write-ups are a nice surprise on a community-focused site.
— Subscriber