# Backend: MQTT(s)

You can configure relaying data to MQTT server:

<figure><img src="https://1423309131-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LsPjfnhNj3v37AZtF-d%2Fuploads%2Fgit-blob-0554607c6cddb77cc65a76e28d96c03a588dcb04%2FScreenshot%20from%202023-12-19%2021-36-28.png?alt=media" alt=""><figcaption></figcaption></figure>

You can choose the data format - raw data received from Bluetooth sensors or decoded data for Ruuvi sensors:

<figure><img src="https://1423309131-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LsPjfnhNj3v37AZtF-d%2Fuploads%2Fgit-blob-56e50ae79772528786941a83d6cf7bfde1afc283%2FScreenshot%20from%202023-12-19%2021-37-49.png?alt=media" alt=""><figcaption></figcaption></figure>

By default, data received from Bluetooth sensors is retransmitted over MQTT immediately, but if you have a lot of sensors you may want to limit the data flow. In order to do this you can set a sending interval:

<figure><img src="https://1423309131-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LsPjfnhNj3v37AZtF-d%2Fuploads%2Fgit-blob-056dd2685454e2854b744c7edccc6b225a32a043%2FScreenshot%20from%202023-12-13%2009-14-51.png?alt=media" alt=""><figcaption></figcaption></figure>

It also supports MQTT client authentication via SSL by enabling the upload of a client certificate and its associated private key, ensuring secure and verified client-server communication. You can use a server SSL Certificate if you want to be independent of public Certificate Authorities (CAs) or if you have deployed a self-signed certificate on the HTTPS server, giving you greater control and customization over your security infrastructure:

<figure><img src="https://1423309131-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LsPjfnhNj3v37AZtF-d%2Fuploads%2Fgit-blob-6fc10df6c9d1c7c417d2464801633bf43d0f7ffe%2FScreenshot%20from%202023-12-13%2009-10-23.png?alt=media" alt=""><figcaption></figcaption></figure>