Product Library / Security Systems & Alarms

X-Sense XP0A-MR Interconnected Smart Smoke & CO Alarm

Compiled by SmartHomeWorkflow Research · X-Sense · Security Systems & Alarms · ~$49.99 (about $50 is X-Sense's list price for a single alarm, from our 2026-07-19 research, and it is never treated as a live price. A later, more precise reading was withdrawn because it came from a page X-Sense had asked automated readers not to load, and the big US retailers do not allow our checks either, so no permitted route confirms the exact figure today)

Compatibility

? Inconclusive means we researched that ecosystem and the evidence doesn’t settle it — the catch says why, and the sources are listed below. It is a statement about the available evidence, never a verdict on the product. A Setup Check researches your exact setup where the official sources don’t answer.

Protocols: WIFI · BLUETOOTH^[3][5][9]

Needs before it works: The separately sold X-Sense SBS50 base station ($22.99), for anything smart. The alarm itself has no Wi-Fi radio, so app notifications, remote silencing and the CO readout all reach the internet through the base station, and a single alarm does not come with one. The trade-off, in X-Sense's own words: connecting the alarms to the base station means you 'lose the customizable wireless network', and the whole-network test stops working.^[2]

What it can do^[12][14]

Checked 2026-08-24: the only vendor surface (x-sense.com) refuses AI-class crawlers under fetch-conduct R-1; capabilities cannot be established without reading it. Ruled as done-by-absence, 16 #448.

Listed capabilities are what we could establish from vendor documentation. An ability missing here is unestablished — not necessarily absent.

Subscription reality^[20][22]

? Works without a subscription: Not established — no source we accept has addressed fees for this product in either direction.

Vendor account required: Not established — we have not sourced this yet.

Unknown, and here is why. This record used to say nothing about the alarm or the app is paywalled, but that rested on a page X-Sense had asked automated readers not to load, so it could not stand. What we could check instead (2026-08-26) is the X-Sense app's App Store listing: the app is free, and it names two paid offerings, Protect+ (24/7 fire dispatch in the US) and AI Smart Alerts. The release notes describe AI Smart Alerts as sending text and phone-call alerts when the alarm triggers after you subscribe, which is a paid tier gating a way of being told about a fire. Whether that counts as a separate service or a gated feature is a judgement we could not settle from a permitted source, so the value stays unknown. What would close it: X-Sense's own plan-comparison page, or a statement of what the free tier keeps.

Maintenance reality^[1]

• Batteries: 1× CR123A 3V lithium, replaceable, pre-installed — expect roughly 60 months per set
• Works without the internet: Not established — we have not sourced this yet. It does not mean the product fails without the internet.
• X-Sense's own spec table gives 5 years of battery life on the wireless interconnected network but 3–5 years when connected to the base station — running it as a smart alarm costs battery life. Hard 10-year sensor end-of-life from date of manufacture; at expiry the alarm beeps three times a minute with a spoken replacement warning that can be silenced for only 22 hours. Photoelectric smoke plus electrochemical CO; sounder ≥85 dB at 10 ft.

Security updates

No security-update support date is on record for this model yet. We haven't yet checked whether X-Sense publishes one, so this is a gap in our research — not a statement about the manufacturer.

The catch

The base station and the alarm-to-alarm network are mutually exclusive, in X-Sense's own words: connect the alarms to the base station and "you'll receive app notifications but lose the customizable wireless network"; choose the network instead and you lose app notifications. Base-station mode also drops the interlinked test — holding the test button checks only that one unit, so there is no whole-network test — and the app shows only the alarm that triggered, not the others. On top of that, the base station is required for anything smart and is not in the box with a single alarm.

Who it's for

Households that want interlinked smoke and CO alarms with phone alerts and no subscription, and are content to live in the X-Sense app. Not a fit for anyone expecting the alarms to appear in Apple Home, Google Home or SmartThings — none of the three are supported.

Sources & method

Numbered sources below back the facts marked with the matching number above. This is a research profile: compiled from manufacturer documentation, certification registries, and published testing — we state facts, not verdicts, and we have not physically tested this unit. How we work →

1. [1] x-sense.com product endpoints and the XP0A-MR user manual PDF (doc US F.1.05.XP0A03 V1.0, dated 2024-06-07) — $49.99 list / $34.99 sale for the single alarm, $139.99 / $97.99 for the XP0A-MR31 kit; 915.275 MHz Link+ Pro interlink; CR123A cell; 10-year replacement — vendor-page and manual research, verified 2026-07-19
   Backs: Product identity, Price, Maintenance, Market availability
2. [2] X-Sense's own product tag taxonomy separates three architectures: this model is 'Base Station Interconnected (App)', where the ALARM HAS NO WI-FI RADIO and reaches the internet only through the separately sold SBS50 base station ($22.99), which is not in the box with a single alarm. The sibling SC07-WX is the inverse — Wi-Fi in the alarm, no interlink at all. Recorded because the two are easily confused and the trade-off is the point of the record. — vendor-page research, verified 2026-07-19
   Backs: Required hub or bridge
3. [3] 'wifi' is recorded for the system's internet path even though the radio lives in the required SBS50 rather than in the alarm; 'bluetooth' is setup-only per manual p.4. The 915 MHz proprietary Link+ Pro interlink is deliberately NOT forced into a taxonomy value — it has no standard equivalent and is described in the record instead. — vendor-page research, verified 2026-07-19
   Backs: Protocols
4. [4] XP0A-MR manual p.1, verbatim: "You can only connect a device to one of them at a time... If you connect them to the base station, you'll receive app notifications but lose the customizable wireless network" and "the interlinked test function is not supported by the base station"; troubleshooting table p.23 confirms the app shows only the initiating alarm — manual research, verified 2026-07-19
5. [5] csa-iot.org certified-products search returns 'No Entries Found' for x-sense and no X-Sense entity appears in its company list; a control query for 'smoke' returned 8+ results, confirming the search itself works — registry research (control-tested), verified 2026-07-19
   Backs: Protocols
6. [6] Queried the regulator's own API (saferproducts.gov RestWebServices/Recall) on ProductName and RecallTitle for X-Sense and XSense — zero results. Control queries returned live data (a 2025 smoke-alarm recall; 10 results for 'Sense'), so the null result is a tested negative rather than a failed search. Recorded because a life-safety record should state this rather than leave it open. — regulator-source research (control-tested), verified 2026-07-19
7. [7] The manual p.1 states X-Sense combination alarms "conform with regulatory requirements, including UL 217 and UL 2034 standards." That is 'conform with', not 'UL Listed', and no UL file number is published. The distinction is preserved deliberately — for a life-safety device, restating a conformance claim as a listing would be a fabrication. — manual research, verified 2026-07-19
8. [8] Google, Apple and SmartThings are absence from X-Sense's own product search and every product page (zero results for each term). Alexa is left unknown because a skill exists but could not be read and X-Sense never names Alexa on this line — a calibrated unknown rather than a guess in either direction. Home Assistant is partial per the counterparty side: home-assistant.io has no X-Sense integration, and the working path is a community HACS component authenticating against X-Sense's cloud. — vendor-page and counterparty-source research, verified 2026-07-19
   Backs: Amazon Alexa compatibility, Google Home compatibility, Apple Home compatibility, SmartThings compatibility, Home Assistant compatibility
9. [9] Attempted 2026-08-09, all refused: x-sense.com/products/interlinked-smart-wi-fi-smoke-and-carbon-monoxide-detector-with-voice-alerts-x-sense-xp0a-mr31 (HTTP 403), x-sense.com/products/xp0a-mr (HTTP 403), and the device.report mirror of the XP0A-MR combination alarm manual (HTTP 403). Web access was control-tested as live at session start and multiple other vendor hosts answered normally in the same session, so the refusal is this host's, not ours. The existing 2026-07-19 note citing manual p.4 is left in place unchanged as the prior read it is. — primary-source verification attempt, verified 2026-08-09
   Backs: Protocols
10. [10] x-sense.com storefront and Protect+ plan page both live; connected line still expanding (XP0J-iA published 2026-05-22) — migrated hand stamp, verified 2026-07-19
    Backs: Service status
11. [11] X-Sense's own XP0A-MR product page (x-sense.com), re-read 2026-08-21 — replacing the BQ-131 migration placeholder that carried no source at all — vendor-page research, verified 2026-08-21
12. [12] `x-sense.com` refuses our fetches with HTTP 403 — first noted in the hundred-and-sixtieth session and re-confirmed 2026-08-20 — and it is the only source this record cites. No first-party capability statement is reachable. — vendor + ecosystem-documentation research (BQ-187 capabilities population), verified 2026-08-20
    Backs: Capabilities
13. [13] No source was read for this entry. It records an edit so the edit is not silent, per the freshness guard's own instruction. — provenance URL backfill (BQ-212 tranche 8) — labelling pass, no re-verification, verified 2026-08-20
14. [14] ⊕ THE OPENING CLAUSE OF THIS ENTRY IS WITHDRAWN 2026-08-22 — see the fetch-conduct correction appended at the end of this list. It read the 2026-08-21 HTTP 200 as the host having stopped refusing us. Under fetch-conduct R-1 that inference is wrong: www.x-sense.com's robots.txt disallows AI crawlers as a class, and an HTTP status cannot speak to that. The observation itself is untouched and still stands on this record — the same URL did return HTTP 200 on 2026-08-21. What the withdrawal changes is the reason this record's capabilities are unrecorded: an access refusal we are honouring, together with the evidence judgement set out here. What was read on 2026-08-22: x-sense.com/robots.txt (verbatim: "User-agent: ClaudeBot" followed by "Disallow: /", under a "User-agent: *" group reading "Content-Signal: search=yes,ai-train=no,use=reference" and "Allow: /"), plus a re-reading of the X-Sense evidence already cited on this record — the XP0A-MR product page feature list and model comparison quoted in the 2026-08-21 entry, the XP0A-MR manual, the CSA certified-products null result, and home-assistant.io's integrations index. Nothing in any of them states what an automation can tell this alarm to do or what it reports to one, and no new vendor page was fetched. — vendor + ecosystem-documentation research (BQ-187 capabilities population), verified 2026-08-22
    Backs: Capabilities
15. [15] X-Sense's own version history for the X-Sense Home Security app, published by "X-sense USA LLC" on Apple's App Store and read 2026-08-22. Version 1.34.0, dated 2026-01-21, verbatim: "The SBS50 base station now supports “Connect to Home Assistant.” You can complete the SBS50 base station’s “Connect to Home Assistant” setup through the functional settings in HA, allowing all smoke alarms, CO alarms, combination alarms, and heat alarms connected to your SBS50 base station to be seamlessly integrated into the Home Assistant platform." The listing's 26 version entries run to 1.42.1 dated 2026-08-20. COUNTERPARTY SIDE, CONTROLLED: home-assistant.io publishes no X-Sense integration — /integrations/xsense/ and /integrations/x_sense/ both return HTTP 404, and the integrations index (697,047 bytes, read 2026-08-22) contains zero occurrences of "xsense" or "x-sense" against 10 for "govee", 13 for "aqara" and 3 for "lutron_caseta", so the index is demonstrably an instrument that names vendors and this is a filtered negative rather than a failed search. — vendor release-note and counterparty-documentation research (control-tested), verified 2026-08-22
    Backs: Home Assistant compatibility
16. [16] The X-Sense Home Security app's App Store listing, seller "X-sense USA LLC", read 2026-08-22. Its version history carries 26 dated releases, the most recent being 1.42.1 on 2026-08-20 and 1.42.0 on 2026-08-18, with a continuous cadence back through 1.41.1 (2026-07-27), 1.41.0 (2026-07-16, "Protect+ has been upgraded with more ways to help protect your home"), 1.40.0 (2026-06-15), 1.39.0 (2026-05-11, "Radon alarm is now available"), 1.38.0 (2026-04-20), 1.37.1 (2026-03-30), 1.36.0 (2026-02-02), 1.34.0 (2026-01-21) and 1.33.0 (2025-12-01). The listing's in-app purchases still carry the Protect+ plan ("24/7 fire dispatch") and an AI Smart Alerts subscription. The SBS50 base station — the hub this record establishes is mandatory for any smart function — is named as actively gaining features in the 1.34.0 notes. — vendor release-note research, verified 2026-08-22
    Backs: Service status, Research status
17. [17] The same App Store listing read for the two entries above, assessed against the advance-on-touch fields. It publishes release notes, an in-app-purchase list and a privacy summary; it publishes no setup procedure, no radio specification, no support-period statement and no automation entity list. — advance-on-touch assessment (BQ-107 decision 7), verified 2026-08-22
18. [18] ⛔ www.x-sense.com REFUSES US under fetch-conduct R-1, and the refusal is INDEPENDENT OF HTTP STATUS: its robots.txt, read 2026-08-22, names nine AI-crawler tokens and disallows each of them — ClaudeBot, GPTBot, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended, meta-externalagent and CloudflareBrowserRenderingCrawler. Our own agent falls through to a permissive `*` group carrying "Content-Signal: search=yes,ai-train=no,use=reference", which is exactly the shape the rule was ruled on, and nine named tokens is well past its two-token threshold. That is why the HTTP 200 this host returned on 2026-08-21 was mistaken for recovery: a status code says the server handed over bytes, while robots.txt says who may ask. Nothing was fetched from the host to establish this — reading robots.txt is the compliance check itself, not a read of the site. — fetch-conduct compliance check — robots.txt only; no X-Sense page was fetched, rendered or reached through a mirror, verified 2026-08-22
19. [19] Routes attempted for the held correction, in the order BQ-243 pre-made them. (a) REGISTRY: fccid.io (robots.txt read 2026-08-26 — HTTP 200, the `*` group allows us, no AI-class exclusion) lists X-Sense Innovations under grantee code 2AU4D with 61 filings. Exactly one carries an XP0A user manual on the 915 MHz family: FCC ID 2AU4DDCG, Frequency Range 915.295 MHz, document 7239555, titled "F.1.05.XP0A12_,XP0A-MR11_...V1.0_20240315". (b) PLATFORM LISTING: the X-Sense Home Security App Store listing, re-read 2026-08-26 — it publishes release notes, in-app purchases and a privacy summary, and says nothing about alarm interconnection behaviour. (c) RETAILER: Home Depot, Lowe's, Walmart and Amazon are all registered refusals in `hostConduct`. — registry research (FCC filing) + platform listing — BQ-243 permitted-route pass, verified 2026-08-26
20. [20] The X-Sense Home Security App Store listing, seller "X-sense USA LLC", re-read 2026-08-26 on a host whose robots.txt permits us (checked the same day: `*` group allows the path, no AI-class exclusion). The listing states the app is "Free", and its release notes name two paid offerings. Protect+, in the description: "our Protect+ Plan is available in the United States. It provides 24/7 fire dispatch to fully protect your life, family, and property. Learn more about Protect+ Plan in the app." AI Smart Alerts, in release 1.38.0: "We have launched the AI Smart Alerts feature in the United States, Germany, and the United Kingdom. After subscribing, users will receive SMS/phone call alerts when the alarm is triggered." — platform-listing research (R-2 route: the vendor host refuses us, an independent platform's listing does not), verified 2026-08-26
    Backs: Subscription
21. [21] csa-iot.org certified-product detail page for X-Sense's SBS0A Matter base station, read 2026-08-27 and RE-READ 2026-08-27 in the post-run review. Six certificates, all Company "X-Sense Innovations Co., Ltd.", Program "Matter", Device Type **Aggregator** (Primary Device Type ID 0x000E): CSA264EAMAT55106-24, CSA264EBMAT55107-24, CSA264ECMAT55108-24, CSA264EDMAT55109-24, CSA264EEMAT55110-24, CSA264EFMAT55111-24. Certified Date 08/14/2026 · Family ID FAM226498 · Product ID 0x1001 · Vendor ID 0x165F · Specification Version 1.5 · Transport Interface Wi-Fi, Bluetooth · Firmware 1.1.0 · Hardware 0.2 · Family SKU SBS0A/ZASXS00224WUC, variant SBS0A/ZASXS00223BUK. The listing states verbatim that the bridge "connects to the cloud via Wi-Fi through a router and communicates with various child devices via a private RF network (868/915 MHz), presenting the status of these child devices to third-party ecosystems as Matter devices", that it "functions as a MatterBridge (gateway/bridge)", and that its Supported Ecosystems (Multi-Administrator/Multi-Fabric) are "Amazon Alexa, Google Home, Apple Home, Samsung SmartThings, Home Assistant". No "Smoke CO Alarm" device type is certified for X-Sense. — registry research (control-tested — the same search returned live, non-X-Sense results for other keywords in the same session), verified 2026-08-27
    Backs: Apple Home compatibility
22. [22] The X-Sense Home Security App Store listing, seller "X-sense USA LLC", re-read 2026-08-27. Verbatim, matching the 2026-08-22/2026-08-26 reads word for word: Protect+ — "our Protect+ Plan is available in the United States. It provides 24/7 fire dispatch to fully protect your life, family, and property"; AI Smart Alerts — "After subscribing, users will receive SMS/phone call alerts when the alarm is triggered." Version history's most recent entry is still 1.42.1 dated Aug 20, matching the 2026-08-22 read — no release has shipped in the intervening five days. The 1.34.0 Home Assistant release note quoted on this record (2026-08-22 entry) was re-confirmed present in the same version history. — platform-listing research (R-2 route, re-read), verified 2026-08-27
    Backs: Subscription, Service status, Research status, Home Assistant compatibility
23. [23] Two sources open this pass for other facts: www.x-sense.com/robots.txt (fetched 2026-08-27; the same nine AI-crawler tokens — ClaudeBot, GPTBot, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended, meta-externalagent, CloudflareBrowserRenderingCrawler — are still each given `Disallow: /`, and the fetch tool's own summary independently confirmed the "AI training" restriction and named-bot blocks without being asked to) and the App Store listing re-read in the entry above. — advance-on-touch assessment (BQ-107 decision 7, reconfirmation), verified 2026-08-27
24. [24] The entry tagged `claims: integrations.*` and dated 2026-07-19 (immediately above the 2026-08-09 bluetooth-test entry in this array) carried no `url` and no `urlGap`, flagged in `tools/provenance-url-baseline.json`. It has now been given `urlGap: "host-refuses"` — no `source` text was changed, no field value moved, and this entry's own `verified` date does not touch that entry's `verified: "2026-07-19"`, matching the labelling-only convention this record already used on 2026-08-20 (id `bq212-t8-x-sense-xp0a-mr-2026-08-20`). The corresponding row in `tools/provenance-url-baseline.json` is removed in the same pass. — provenance URL backfill — labelling pass, no re-verification, verified 2026-08-27
25. [25] www.x-sense.com/robots.txt, re-read 2026-08-28 (BQ-107 batch 44). Unchanged from the 2026-08-22/08-27 reads: ClaudeBot, GPTBot, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended and meta-externalagent are all `Disallow: /`, with a `Content-Signal: search=yes,ai-train=no,use=reference` line on the permissive `*` group. This record's product page is still fetch-conduct R-1 excluded, independent of any HTTP status the host might return. — fetch-conduct compliance check — robots.txt only; no X-Sense page was fetched, rendered or reached through a mirror, verified 2026-08-28
26. [26] Record-keeping entry. No source was read for it: no page on www.x-sense.com was requested, because the host's standing refusal is the answer. It records why three `none` cells on this record cannot carry an absence marker, so the next pass does not re-derive it. — internal, verified 2026-08-30
27. [27] Owner ruling 16 #448, recorded in docs/decisions/2026-08-24-DECISIONS-SITTING-RULINGS.md (R-8), applied to the record on 2026-09-01 as BQ-210's decision-7 pre-step. — ruling applied to a record; no new source read, verified 2026-09-01
28. [28] the record's own customer-facing prose fields as they stood before 2026-09-05 (no new external read) — consumer-translation pass (07 §2A.12) — customer-facing prose rewritten to the three-layer rule; NO FIELD VALUE, LEVEL, PATH OR TRANSPORT CHANGED. The research trail that used to sit inside those fields is preserved here verbatim., verified 2026-09-05

Compatibility and lifecycle information reflects the last-verified date above and can change without notice (firmware updates, cloud-service changes, discontinuations). It is provided as-is, for information — verify with the manufacturer before purchasing. Spot an error? Tell us and we'll fix it. Full terms: Terms of Service.

Check it against YOUR setup →