> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/s2gw-installation-manual/s2-sensor-types.md).

# S2 sensor types

Version 2.05 handles the S2 sensor types presented in the table below.

S2GW defines the S2 type basing on the node answer to GetSwHwRadio request and assigns the converter used to calculate the readings accordingly.

There are some S2 types which are not handled by S2GW. 

If the answer from the node contains unknown S2 type, the message to B3 contains "Sensor type not supported!".

<table><thead><tr><th width="110">S2 type</th><th width="74">Index</th><th width="411">Sensor converter</th><th>B3 type</th></tr></thead><tbody><tr><td> 0</td><td> 2</td><td>HeraeusBBD6220.HeraeusBBD6220TemperatureValueConverter </td><td>9301</td></tr><tr><td> 2</td><td> 3</td><td>HeraeusBBD6220.HeraeusBBD6220HumidityValueConverter </td><td> 9304 </td></tr><tr><td> 3 </td><td> 4</td><td>HeraeusBBD6220.HeraeusBBD6220CO2ValueConverter </td><td> 9306</td></tr><tr><td> 9</td><td> </td><td>GalaxyR.GalaxyRTempValueConverter</td><td> 9301 </td></tr><tr><td> 10</td><td> </td><td> GalaxyR.GalaxyRCO2ValueConverter</td><td> 9306 </td></tr><tr><td> 16</td><td></td><td> DallasValueConverter DS18S20</td><td> 9301 </td></tr><tr><td> 40</td><td> </td><td> DallasValueConverter DS18B20</td><td>9301 </td></tr><tr><td> 55</td><td> </td><td> AnalogueValueConverter</td><td> 9302 </td></tr><tr><td> 56</td><td> </td><td> AnalogueValueConverter</td><td> 9302 </td></tr><tr><td> 57</td><td> </td><td> AnalogueValueConverter</td><td>9302 </td></tr><tr><td> 83</td><td> 0</td><td> SHT75ValueConverter.ValueType.Humidity</td><td> 9304 </td></tr><tr><td>83</td><td> 1</td><td> SHT75ValueConverter.ValueType.Temperature</td><td> 9301 </td></tr><tr><td>100</td><td> </td><td> PT100ValueConverter</td><td> 9301 </td></tr><tr><td> 101</td><td></td><td> PT1000ValueConverter</td><td> 9301 </td></tr><tr><td> 102</td><td> </td><td> PT100V2ValueConverter </td><td>9301 </td></tr><tr><td> 105</td><td> </td><td> TwinMissionValueConverter </td><td> 9301 </td></tr><tr><td> 106</td><td> </td><td> S2408iValueConverter </td><td> 9305 </td></tr><tr><td> 107 </td><td> 0</td><td> Memmert.MemmertTempValueConverter </td><td>9301 </td></tr><tr><td> 107 </td><td>1</td><td>Memmert.MemmertCO2ValueConverter </td><td>9306 </td></tr><tr><td> 107</td><td>2 </td><td>Memmert.MemmertHumidityValueConverter </td><td>9304 </td></tr><tr><td> 108 </td><td>0 </td><td>SHERAcell150.SHERAcell150TempValueConverter </td><td>9301 </td></tr><tr><td> 108 </td><td>1 </td><td>SHERAcell150.SHERAcell150CO2ValueConverter </td><td>9306 </td></tr><tr><td>108 </td><td>2</td><td>SHERAcell150.SHERAcell150O2ValueConverter </td><td>9306 </td></tr><tr><td>109 </td><td>0 </td><td>Innova.InnovaTempValueConverter </td><td>9301 </td></tr><tr><td>109 </td><td>1 </td><td>Innova.InnovaRpmValueConverter </td><td>9306 </td></tr></tbody></table>

The readings are sent to B3 with B3 type in the XML.

| B3 sensor                 | B3 type |
| ------------------------- | ------- |
| Temperature               | 9301    |
| Analogue input            | 9302    |
| Humidity                  | 9304    |
| High Precision Temp 2408i | 9305    |
| Concentration             | 9306    |


---

# 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.boomerang3.com/s2gw-installation-manual/s2-sensor-types.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.