Product Library / Security Systems & Alarms
Research profile · last verified 2026-07-19X-Sense XP0A-MR Interconnected Smart Smoke & CO Alarm
Exactly which product this is[1]
- Model number
- XP0A-MR
- Generation
- Link+ Pro
- Region this page covers
- US
- Also sold or listed as
- X-Sense XP0A-MR31 · X-Sense Link+ Pro combination alarm
“Not established” means we have not sourced that detail yet — not that the product has no model number, generation or regional variant. We publish the gap rather than filling it.
Compatibility
| Ecosystem | Support | The catch |
|---|---|---|
| Amazon Alexa | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[8] | Genuinely unresolved. An "X-Sense Home Security" Alexa skill exists, but X-Sense's own site never names Alexa on any smoke or CO product page and its product search returns nothing for "alexa" — the one X-Sense product marketed as Alexa-compatible is a different security-system line. The skill listing itself could not be read to confirm whether alarm events reach Alexa. |
| Google Home | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[8] | X-Sense names neither Google Home nor SmartThings on the pages we could read; its site refuses automated reading, so this is unconfirmed. |
| Apple Home | Doesn't workVerified: does not work with this ecosystem[8][21] | X-Sense's own site search returns zero products for "homekit". The CSA certified-products registry, which returned zero X-Sense entries as of 2026-07-19, now lists six Matter-certified products from X-Sense Innovations Co., Ltd. (re-checked 2026-08-27) — all six for a Matter bridge called SBS0A, certified as Device Type Aggregator (Primary Device Type ID 0x000E), and all six for a different model number from the SBS50 base station this alarm requires. X-Sense's own certified listing states that bridge carries its RF child devices (868/915 MHz) into Amazon Alexa, Google Home, Apple Home, SmartThings and Home Assistant, so a route into Apple Home now exists for some X-Sense hardware. What is not established is that it exists for THIS product: nothing read states that XP0A-MR pairs with SBS0A, that SBS0A is shipping, or that it replaces SBS50, and no "Smoke CO Alarm" device type is certified for X-Sense at all. This alarm's Apple route is unestablished as of this check. |
| SmartThings | InconclusiveWe researched this and the evidence doesn't settle it — the catch explains why[8] | X-Sense names neither Google Home nor SmartThings on the pages we could read; its site refuses automated reading, so this is unconfirmed. |
| Home Assistant | PartialPartial support — see the catch[8][15][22] | X-Sense itself now ships this route: its app release notes for version 1.34.0 (January 2026) say the SBS50 base station now supports 'Connect to Home Assistant', covering every smoke, CO, combination and heat alarm connected to it, which this alarm is once it is paired to the base station it already needs. Read 'official' precisely: the maker provides it, not Home Assistant. Home Assistant publishes no X-Sense integration of its own, so there is no page from its side describing what appears in Home Assistant or what you can do with it. That is why this stays partial: 'seamlessly integrated' is the maker's phrase, not a list of what a buyer gets. An older community add-on, which signs into X-Sense's cloud with a second shared account, still exists alongside it. Whether the maker's route runs over your home network or through X-Sense's cloud is not stated anywhere.In Home Assistant you also need: a X-sense hub |
? 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: PROPRIETARY-RF-915MHZ[1][2][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]
You can tell it to
Not established — we could not confirm this from vendor documentation
It reports
Not established — we could not confirm this from vendor documentation
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: Inconclusive — we read the vendor's own setup material and it does not say either way. Treat it as unanswered rather than as a no.
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][3]
- Batteries: 1× CR123A 3V lithium, replaceable, pre-installed — expect roughly 60 months per set
- Works without the internet: Inconclusive — we read the vendor's own material and it does not answer this either way. 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. The alarm's only everyday radio is X-Sense's own 915 MHz link, which connects the alarms to each other and to the SBS50 base station. There is no Wi-Fi in the alarm and your phone never talks to it directly; X-Sense's manual describes Bluetooth for setup only.
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, which X-Sense has not established for this model. Whether they reach Google Home or SmartThings is unconfirmed either way: X-Sense names neither on the pages we could read.
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 →
33 numbered sources· read them in the source's own words
- [1] X-Sense's own product pages at x-sense.com, read from the store's machine-readable product data, 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 — Read on the maker's own site, verified 2026-07-19Backs: Product identity, Price, Maintenance, Market availability, Protocols
- [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. — Read on the maker's own site, verified 2026-07-19Backs: Required hub or bridge, Protocols
- [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. — Read on the maker's own site, verified 2026-07-19Backs: Maintenance
- [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, verified 2026-07-19
- [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 — Checked a certification register, verified 2026-07-19Backs: Protocols
- [6] Searched the regulator's own recall database at saferproducts.gov by product name and by recall title for X-Sense and XSense — zero results. Control queries returned live data (a 2025 smoke-alarm recall; 10 results for 'Sense'), so the empty result is a tested negative rather than a failed search. Recorded because a life-safety record should state this rather than leave it open. — Read a public regulatory filing, verified 2026-07-19
- [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., verified 2026-07-19
- [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 on the evidence of the other side of the integration: home-assistant.io has no X-Sense integration, and the working path is a community-built add-on that signs in to X-Sense's cloud. — Read on the maker's own site, verified 2026-07-19Backs: Amazon Alexa compatibility, Google Home compatibility, Apple Home compatibility, SmartThings compatibility, Home Assistant compatibility
- [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 (refused), x-sense.com/products/xp0a-mr (refused), and the device.report mirror of the XP0A-MR combination alarm manual (refused). 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., verified 2026-08-09Backs: Protocols
- [10] x-sense.com storefront and Protect+ plan page both live; connected line still expanding (XP0J-iA published 2026-05-22), verified 2026-07-19Backs: Service status
- [11] X-Sense's own XP0A-MR product page (x-sense.com), re-read 2026-08-21 — replacing an earlier placeholder that carried no source at all — Read on the maker's own site, verified 2026-08-21
- [12] x-sense.com refuses our reader — 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 can be had. — Read on the maker's own site, verified 2026-08-20Backs: CapabilitiesChecked 2026-08-20. This page no longer lets us re-check it automatically, so that date is where this fact stands.
- [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. — Re-checked this against its sources, verified 2026-08-20
- [14] ⊕ THE OPENING CLAUSE OF THIS ENTRY IS WITHDRAWN 2026-08-22 — see the correction about this host's refusal appended at the end of this list. It read the host handing over the page on 2026-08-21 as the host having stopped refusing us. Under our own rule on access refusals that inference is wrong: www.x-sense.com's robots file disallows AI crawlers as a class, and a server handing over bytes cannot speak to that. The observation itself is untouched and still stands on this record — the same address did serve the page 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 search that returned nothing, 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 read. — Read on the maker's own site, verified 2026-08-22
- [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. THE OTHER SIDE OF THE INTEGRATION, CONTROLLED: home-assistant.io publishes no X-Sense integration — it has no page at /integrations/xsense/ or /integrations/x_sense/, 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. — Read on the maker's own site, verified 2026-08-22Backs: Home Assistant compatibility
- [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. — Read on the maker's own site, verified 2026-08-22Backs: Service status, Research status
- [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., verified 2026-08-22
- [18] ⛔ www.x-sense.com REFUSES US under our own rule on access refusals, and the refusal has nothing to do with whether the server answers: 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 catch-all 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 this host handing over the page on 2026-08-21 was mistaken for recovery: serving the bytes says the server answered, while its robots file says who may ask. Nothing was read from the host to establish this — reading its robots file is the permission check itself, not a read of the site., verified 2026-08-22
- [19] Routes attempted for the held correction, in the order our own plan set them out. (a) REGISTRY: fccid.io (its robots file, read 2026-08-26, answered, and its catch-all group allows us with 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 have all refused us before and are recorded as such. — Checked a certification register, verified 2026-08-26Seller's spec sheet, checked 2026-08-26This fact comes from a retailer or review specification listing rather than from the manufacturer. Last checked 2026-08-26.
- [20] The X-Sense Home Security App Store listing, seller "X-sense USA LLC", re-read 2026-08-26 on a host whose robots file permits us (checked the same day: the catch-all group allows the path, with 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.", verified 2026-08-26Backs: Subscription
- [21] csa-iot.org certified-product detail page for X-Sense's SBS0A Matter base station, read 2026-08-27 and RE-READ the same day as a check. 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. — Checked a certification register, verified 2026-08-27Backs: Apple Home compatibility
- [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., verified 2026-08-27Backs: Subscription, Service status, Research status, Home Assistant compatibility
- [23] Two sources open on the same day for other facts: www.x-sense.com/robots.txt (read 2026-08-27; the same nine AI-crawler tokens — ClaudeBot, GPTBot, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended, meta-externalagent, CloudflareBrowserRenderingCrawler — are still each disallowed from the whole site, and our reader'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., verified 2026-08-27
- [24] Record-keeping entry. The entry covering this record's ecosystem answers and dated 2026-07-19 (immediately above the 2026-08-09 Bluetooth test entry) carried no address for what was read, and no note saying why. It has now been labelled as one where the host refuses us: no wording was changed, no fact moved, and its own 2026-07-19 date is untouched, matching the labelling-only convention this record already used on 2026-08-20. Our own list of entries missing an address drops this one at the same time. — Re-checked this against its sources, verified 2026-08-27
- [25] www.x-sense.com/robots.txt, re-read 2026-08-28 during a routine re-verification round. Unchanged from the 2026-08-22 and 2026-08-27 reads: ClaudeBot, GPTBot, Google-Extended, CCBot, Bytespider, Amazonbot, Applebot-Extended and meta-externalagent are all disallowed from the whole site, with a "Content-Signal: search=yes,ai-train=no,use=reference" line on the permissive catch-all group. This record's product page is still excluded under our own rule on access refusals, whatever the server itself would answer., verified 2026-08-28
- [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 of this record's no-support answers cannot carry an absence marker, so the next round does not work it out again., verified 2026-08-30
- [27] An owner ruling of 2026-08-24, recorded in this project's decision log, applied to the record on 2026-09-01., verified 2026-09-01
- [28] the record's own customer-facing prose fields as they stood before 2026-09-05 (no new external read), verified 2026-09-05
- [29] We do not read www.x-sense.com: it excludes AI crawlers as a class, recorded when that was observed on 2026-08-26, so the maker's own product page for the XP0A-MR is closed to us and a refusal is never worked around. The App Store listing already cited on this record proves an iOS app exists and says nothing about Android, so recording the phone platforms as iOS alone would assert an absence the listing does not support — the same call batch 7 made on this record. All three fields stay as they are. Reopening condition: X-Sense changes its robots policy, or a first-party PDF is published on a host that has not refused us., verified 2026-09-10
- [30] This record's 2026-08-27 and 2026-08-28 conduct entries, re-read 2026-09-12 against our own register of hosts that have refused us, which records www.x-sense.com as refusing us on policy as an AI crawler, first observed 2026-08-26. No X-Sense host was requested on 2026-09-12., verified 2026-09-12
- [31] Read 2026-09-12: fccid.io/2AU4DDCG/User-Manual/User-manual-7239555, apps.apple.com/us/app/x-sense-home-security/id1568666708, csa-iot.org/csa_product/base-station/ ('The SBS0A Matter Base Station connects to the cloud via Wi-Fi through a router and communicates with various child devices via a private RF network (868/915 MHz)'). Not read, because X-Sense's site excludes AI crawlers as a class, observed 2026-08-26: every www.x-sense.com address this record cites., verified 2026-09-12
- [32] FCC equipment authorization 2AU4DDCG, read 2026-09-12 on the fccid.io mirror of the FCC record: grantee X-Sense Innovations Co., Ltd. (2AU4D), Equipment Class "Smoke and Carbon Monoxide Alarm", product code DCG, Operating Frequencies "915.295 MHz — Original Equipment — 2024-04-11" (the only range listed), rule part 15C, TCB scope "A1: Low Power Transmitters below 1 GHz". The grant's User Manual exhibit (document 7239555) carries the Document Title "F.1.05.XP0A12_,XP0A-MR11_…_US美规_V1.0_20240315", which is the filing naming this model. Control from the same grantee on the same search: 2AU4DDCS, "WI-FI Combination Smoke and Carbon Monoxide Alarm", lists "2412-2462 MHz, 2402-2480 MHz". — Checked a certification register, verified 2026-09-12Seller's spec sheet, checked 2026-09-12This fact comes from a retailer or review specification listing rather than from the manufacturer. Last checked 2026-09-12.
- [33] No page was read for this entry. It records why two answers on this record moved from a stated no to unconfirmed. Both rested on one 2026-07-19 note whose entire evidence was that a search of X-Sense's own site returned nothing for Google Home and nothing for SmartThings. An empty search result is a product of how we read the site, not something X-Sense published, so it cannot carry a no — the more so here, because X-Sense's site now refuses automated reading and the pages we can still reach say nothing either way. The older note keeps its wording. Apple Home on this record was read and deliberately left alone: its answer rests on the certified-products registry check of 2026-08-27, which is a different kind of evidence., verified 2026-09-16
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.