> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/selected-salto-rfnet-related-products-obsolescence-march-2026.md).

# Selected Salto RFnet-related products obsolescence - March 2026

**For All Regions**

#### Notification![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Salto will discontinue several RFnet-related products due to continued supply chain challenges for key components and the overall migration towards **BLUEnet.**&#x20;

#### Key Dates![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

**Moving forward, Salto will not receive any more orders for these discontinued items.**&#x20;

* **End of Aftersales**  (Extensions of existing projects): December 31, 2026&#x20;
* **End of Repairs and Spare Parts**  (RMNs): December 31, 2029&#x20;

#### Impacted Units & Alternative Products![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

The basic reference structure of these products is provided below.&#x20;

***Note:** Please note that RFnet escutcheons and cylinders can only communicate with RFnet gateways and/or nodes. If transitioning to BLUEnet, the door hardware will need to change as well for online use.*&#x20;

<table data-header-hidden><thead><tr><th width="139"></th><th width="277"></th><th></th></tr></thead><tbody><tr><td><strong>Category:</strong></td><td><strong>Product Affected by EOL:</strong></td><td><strong>Alternative Product:</strong></td></tr><tr><td><strong>Gateways</strong></td><td><p><strong>RFnet Gateway:</strong> </p><p>GATEWAYx<strong>2</strong>C </p><p>GATEWAYx<strong>2</strong>CUS </p></td><td><p><strong>BLUEnet Gateway:</strong> </p><p>GATEWAYx<strong>3</strong>C </p><p>GATEWAYx<strong>3</strong>CUS </p></td></tr><tr><td><p><strong>Nodes</strong></p><p> </p></td><td><p><strong>RFnet Node:</strong></p><p>RFNODE </p><p>RFNODEx </p></td><td><p><strong>BLUEnet Node:</strong></p><p>RFNODE<strong>3</strong> </p><p>RFNODE<strong>3</strong>x </p></td></tr><tr><td><p><strong>Tester</strong></p><p> </p></td><td><p><strong>RF Tester:</strong></p><p>RFTESTERW01 </p></td><td><p><em>No Salto alternative</em></p><p> </p></td></tr><tr><td><strong>Antenna Kit</strong> </td><td><p><strong>RFnet Antenna Kit:</strong> </p><p>RFMODULEW0x </p></td><td><p><em>No Salto alternative</em></p><p> </p></td></tr></tbody></table>

#### Questions![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Please direct questions to your local Gallagher representative.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/product-advisories/current-advisories/readers-credentials-and-locks/selected-salto-rfnet-related-products-obsolescence-march-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
