> For the complete documentation index, see [llms.txt](https://rhiot.gitbook.io/rhiotdocumentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rhiot.gitbook.io/rhiotdocumentation/index-8.md).

# Releases notes

## 0.1.3 (currently in progress)

## 0.1.2  (2015-10-22)

* Deprecated BU353 component on the behalf of the GPSD component [#232](https://github.com/rhiot/rhiot/issues/232)
* Added GPS client coordinates type converter [#213](https://github.com/rhiot/rhiot/issues/213)
* Fixed: BU353 returns "FileNotFoundException: /dev/ttyUSB0 (Device or resource busy)" [#210](https://github.com/rhiot/rhiot/issues/210)
* Rhiot now supports reading Spring Boot application.properties file [#226](https://github.com/rhiot/rhiot/issues/226)
* Renamed com.github.camellabs.iot.vertx.camel.GroovyCamelVerticle to io.rhiot.vertx.camel.GroovyCamelVerticle [#207](https://github.com/rhiot/rhiot/issues/207)
* Moved camel-kura component from com.github.camellabs to io.rhiot package [#195](https://github.com/rhiot/rhiot/issues/195)
* Device detection is performed in parallel [#218](https://github.com/rhiot/rhiot/issues/218)
* Added "scan" command to the deployer [#217](https://github.com/rhiot/rhiot/issues/217)
* Deployer now allows to specify customized fat jar [#216](https://github.com/rhiot/rhiot/issues/216)
* Deployer now downloads the same gateway version as deployer version [#215](https://github.com/rhiot/rhiot/issues/215)
* Deployer now detects devices from multiple interfaces [#214](https://github.com/rhiot/rhiot/issues/214)
* Deployer now scans OSX network interfaces [#202](https://github.com/rhiot/rhiot/issues/202)
* Device Cloudlet MongoDB connection now timeouts faster [#191](https://github.com/rhiot/rhiot/issues/191)
* Add [Webcam camel component](https://github.com/rhiot/rhiot/issues/239), thx [@levackt](https://github.com/levackt) [#238](https://github.com/rhiot/rhiot/issues/239)

## 0.1.1  (2015-09-15)

* Changed project name from *Camel Labs* to *Rhiot*
* Added [Dockerized Rhiot Cloud](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#dockerized-rhiot-cloud) [#160](https://github.com/rhiot/rhiot/issues/160).
* Added [device management cloudlet](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#device-management-cloudlet) [#114](https://github.com/rhiot/rhiot/issues/114).
* Added web UI (aka [Cloudlet Console](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#device-management-web-ui) [#129](https://github.com/rhiot/rhiot/issues/129).
* Created [Rhiot Cloud demo site](http://rhiot.net) [#155](https://github.com/rhiot/rhiot/issues/155).
* Added [camel-gps-bu353](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#camel-gps-bu353-component) component [#93](https://github.com/rhiot/rhiot/issues/93).
* Migrated [Gateway](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#camel-iot-gateway) core from Spring Boot to Vert.x [#141](https://github.com/rhiot/rhiot/issues/141)  [#120](https://github.com/rhiot/rhiot/issues/120).
* [Gateway should start Jolokia REST API on port 8778, not 8080](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#monitoring-gateway-with-jolokia) [#143](https://github.com/rhiot/rhiot/issues/143).
* Releasing [Gateway](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#camel-iot-gateway) core and application artifacts separately [#126](https://github.com/rhiot/rhiot/issues/126).
* Renamed `camellabs.iot.gateway.heartbeat.rate property` to `camellabs_iot_gateway_heartbeat_rate` [#124](https://github.com/rhiot/rhiot/issues/124).
* Gateway [deletes logs after N megabytes limit is exceeded](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#gateway-logger-configuration) [#104](https://github.com/rhiot/rhiot/issues/104)  [#95](https://github.com/rhiot/rhiot/issues/95).
* Gateway [reads properties from the `/etc/default/camel-labs-iot-gateway`](https://github.com/rhiot/rhiot/blob/master/docs/readme.md#configuration-of-the-gateway)  [#98](https://github.com/rhiot/rhiot/issues/98).

## 0.1.0  (2015-06-02)

* Initial version of the Camel based [IoT field gateway](https://github.com/rhiot/rhiot/tree/master/iot#camel-iot-gateway)
* Raspbian [installation scripts](https://github.com/rhiot/rhiot/tree/master/iot#installing-gateway-on-the-raspbian) for the Camel IoT Gateway
* [Heartbeats support](https://github.com/rhiot/rhiot/tree/master/iot#device-heartbeats) for the Camel IoT Gateway (including logging, MQTT and LED signals)
* [Camel Kura WiFi component](https://github.com/rhiot/rhiot/tree/master/iot#camel-kura-wifi-component)
* [Camel Tinkerforge component](https://github.com/rhiot/rhiot/tree/master/iot#camel-tinkerforge-component)
* [Camel Pi4j component](https://github.com/rhiot/rhiot/tree/master/iot#camel-pi4j-component)
* [Camel PubNub component](https://github.com/rhiot/rhiot/tree/master/iot#camel-pubnub-component)
* Alpha version of the [Cloudlets](https://github.com/rhiot/rhiot/tree/master/iot#cloudlets) backend services, currently including [Geofencing Cloudlet](https://github.com/rhiot/rhiot/tree/master/iot/cloudlet/geofencing) and [Hawt.io-based UI plugin for it](https://github.com/rhiot/rhiot/tree/master/iot/cloudlet/geofencing)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rhiot.gitbook.io/rhiotdocumentation/index-8.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.