Showing preview only (2,909K chars total). Download the full file or copy to clipboard to get everything.
Repository: blynkkk/blynkkk.github.io
Branch: master
Commit: f914dc98a161
Files: 497
Total size: 2.4 MB
Directory structure:
gitextract_308jsc33/
├── Amendments.md
├── AppExport.md
├── BlynkFirmware.md
├── BlynkMainOperations.md
├── BlynkProtocol.md
├── BlynkServer.md
├── CNAME
├── FAQ.md
├── GettingStarted.md
├── HardwareSetUps.md
├── Implementing.md
├── IntroAndDownloads.md
├── License.md
├── Links.md
├── OTA.md
├── README.md
├── Roadmap.md
├── SUMMARY.md
├── Security.md
├── Sharing.md
├── SupportedHardware.md
├── Troubleshooting.md
├── Widgets-RU.md
├── Widgets.md
├── amendments.md
├── api/
│ ├── README.md
│ ├── api_getlastweekdata.md
│ ├── events-api.md
│ └── external_api.md
├── appexport.md
├── blynkfirmware.md
├── blynkmainoperations.md
├── blynkprotocol.md
├── blynkserver.md
├── css/
│ └── style.css
├── en/
│ ├── README.md
│ ├── api/
│ │ └── README.md
│ ├── infra/
│ │ └── backup_policy_FAQ.md
│ └── product/
│ ├── README.md
│ └── product-template-settings/
│ ├── README.md
│ ├── dashboard.md
│ ├── datastreams/
│ │ ├── README.md
│ │ ├── datastream_alias.md
│ │ ├── datastream_automation.md
│ │ ├── datastream_datatype.md
│ │ ├── datastream_default_value.md
│ │ ├── datastream_deicmals.md
│ │ ├── datastream_feedback.md
│ │ ├── datastream_invalidate.md
│ │ ├── datastream_min_max.md
│ │ ├── datastream_name.md
│ │ ├── datastream_save_raw.md
│ │ ├── datastream_sync.md
│ │ └── datastream_virtual_pin.md
│ ├── events/
│ │ ├── README.md
│ │ ├── event_code.md
│ │ ├── event_name.md
│ │ ├── event_notification.md
│ │ ├── event_notification_period.md
│ │ └── event_online_offline.md
│ ├── general-settings/
│ │ ├── README.md
│ │ ├── product_manufacturer.md
│ │ └── product_offline_ignore_period.md
│ └── metadata.md
├── en-product/
│ ├── create-new-product.md
│ ├── dashboard/
│ │ └── chart.md
│ ├── datastreams/
│ │ ├── README.md
│ │ ├── datastream-alias.md
│ │ ├── datastream-data-type.md
│ │ ├── datastream-invalidate-value.md
│ │ ├── datastream-min-max-values.md
│ │ ├── datastream-name.md
│ │ ├── datastream-save-raw-data.md
│ │ ├── datastream-virtual-pin.md
│ │ ├── decimals-formatting.md
│ │ ├── default-value.md
│ │ ├── expose-to-automation.md
│ │ ├── sync-with-the-latest-server-value.md
│ │ └── wait-for-confirmation-from-the-device.md
│ ├── events/
│ │ ├── README.md
│ │ ├── events-code.md
│ │ ├── events-name.md
│ │ ├── events-notification-period.md
│ │ ├── events-notification.md
│ │ └── events-online-offline.md
│ ├── general-settings/
│ │ ├── README.md
│ │ ├── manufacturer.md
│ │ └── offline-ignore-period.md
│ ├── metadata.md
│ ├── mobile-app-ui.md
│ └── web-dashboard.md
├── faq.md
├── firmware-api/
│ ├── README.md
│ └── disable-widgets-in-the-app.md
├── firmware-api-1/
│ └── disable-widgets-in-the-app.md
├── gettingstarted.md
├── google-code-prettify/
│ ├── CHANGES.html
│ ├── COPYING
│ ├── Makefile
│ ├── README.html
│ ├── examples/
│ │ └── quine.html
│ ├── js-modules/
│ │ ├── combinePrefixPatterns.js
│ │ ├── externs.js
│ │ ├── extractSourceSpans.js
│ │ ├── extractSourceSpans_test.html
│ │ ├── js_include.pl
│ │ ├── numberLines.js
│ │ ├── numberLines_test.html
│ │ ├── prettify.js
│ │ ├── recombineTagsAndDecorations.js
│ │ ├── recombineTagsAndDecorations_test.html
│ │ ├── regexpPrecederPatterns.pl
│ │ └── run_prettify.js
│ ├── src/
│ │ ├── lang-apollo.js
│ │ ├── lang-basic.js
│ │ ├── lang-clj.js
│ │ ├── lang-css.js
│ │ ├── lang-dart.js
│ │ ├── lang-erlang.js
│ │ ├── lang-go.js
│ │ ├── lang-hs.js
│ │ ├── lang-lisp.js
│ │ ├── lang-llvm.js
│ │ ├── lang-lua.js
│ │ ├── lang-matlab.js
│ │ ├── lang-ml.js
│ │ ├── lang-mumps.js
│ │ ├── lang-n.js
│ │ ├── lang-pascal.js
│ │ ├── lang-proto.js
│ │ ├── lang-r.js
│ │ ├── lang-rd.js
│ │ ├── lang-scala.js
│ │ ├── lang-sql.js
│ │ ├── lang-tcl.js
│ │ ├── lang-tex.js
│ │ ├── lang-vb.js
│ │ ├── lang-vhdl.js
│ │ ├── lang-wiki.js
│ │ ├── lang-xq.js
│ │ ├── lang-yaml.js
│ │ ├── prettify.css
│ │ ├── prettify.js
│ │ └── run_prettify.js
│ ├── styles/
│ │ ├── demo.html
│ │ ├── desert.css
│ │ ├── doxy.css
│ │ ├── index.html
│ │ ├── sons-of-obsidian.css
│ │ └── sunburst.css
│ ├── tests/
│ │ ├── debug-ie-compat-matrix.html
│ │ ├── ie-newline-copy-paste.html
│ │ ├── large_input_test.html
│ │ ├── prettify_test.html
│ │ ├── prettify_test_2.html
│ │ ├── run_prettify_test.html
│ │ ├── test_base.js
│ │ └── test_styles.css
│ └── tools/
│ ├── closure-compiler/
│ │ ├── COPYING
│ │ ├── README
│ │ ├── amd-externs.js
│ │ ├── compiler.jar
│ │ └── console-externs.js
│ ├── cut-release.sh
│ ├── googlecode_upload.py
│ ├── lang-handler-aliases.sh
│ └── yui-compressor/
│ ├── LICENSE.TXT
│ ├── README
│ └── yuicompressor-2.4.4.jar
├── hardwaresetups.md
├── http.md
├── https-api/
│ ├── api_getlastweekdata.md
│ ├── events-api.md
│ └── external_api.md
├── implementing.md
├── index.html
├── introanddownloads.md
├── license.md
├── links.md
├── mobile/
│ ├── README.md
│ ├── accelerometer.md
│ ├── barometer.md
│ ├── ble.md
│ ├── bluetooth.md
│ ├── bridge.md
│ ├── button.md
│ ├── datastreams.md
│ ├── device_selector.md
│ ├── device_tiles.md
│ ├── email.md
│ ├── eventor.md
│ ├── gauge.md
│ ├── gps_streaming.md
│ ├── gps_trigger.md
│ ├── graph.md
│ ├── gravity.md
│ ├── humidity.md
│ ├── image.md
│ ├── joystick.md
│ ├── labeled_value.md
│ ├── labeled_value_display.md
│ ├── lcd.md
│ ├── led.md
│ ├── level_display.md
│ ├── light.md
│ ├── map.md
│ ├── menu.md
│ ├── music_player.md
│ ├── notification.md
│ ├── numberInput.md
│ ├── number_input.md
│ ├── proximity.md
│ ├── report.md
│ ├── rgb.md
│ ├── rtc.md
│ ├── ru/
│ │ ├── accelerometer.md
│ │ ├── barometer.md
│ │ ├── ble.md
│ │ ├── bluetooth.md
│ │ ├── bridge.md
│ │ ├── button.md
│ │ ├── device_selector.md
│ │ ├── device_tiles.md
│ │ ├── email.md
│ │ ├── eventor.md
│ │ ├── gauge.md
│ │ ├── gps_streaming.md
│ │ ├── gps_trigger.md
│ │ ├── graph.md
│ │ ├── gravity.md
│ │ ├── humidity.md
│ │ ├── image.md
│ │ ├── joystick.md
│ │ ├── labeled_value.md
│ │ ├── labeled_value_display.md
│ │ ├── lcd.md
│ │ ├── led.md
│ │ ├── level_display.md
│ │ ├── light.md
│ │ ├── map.md
│ │ ├── menu.md
│ │ ├── music_player.md
│ │ ├── notification.md
│ │ ├── numberInput.md
│ │ ├── number_input.md
│ │ ├── proximity.md
│ │ ├── report.md
│ │ ├── rgb.md
│ │ ├── rtc.md
│ │ ├── segmentedSwitch.md
│ │ ├── segmented_control.md
│ │ ├── slider.md
│ │ ├── step.md
│ │ ├── styled_button.md
│ │ ├── super_chart.md
│ │ ├── table.md
│ │ ├── tabs.md
│ │ ├── temperature.md
│ │ ├── terminal.md
│ │ ├── textInput.md
│ │ ├── text_input.md
│ │ ├── time_input.md
│ │ ├── timeinput.md
│ │ ├── timer.md
│ │ ├── twitter.md
│ │ ├── value_display.md
│ │ ├── video.md
│ │ └── webhook.md
│ ├── segmentedSwitch.md
│ ├── segmented_control.md
│ ├── slider.md
│ ├── step.md
│ ├── styled_button.md
│ ├── super_chart.md
│ ├── table.md
│ ├── tabs.md
│ ├── temperature.md
│ ├── terminal.md
│ ├── textInput.md
│ ├── text_input.md
│ ├── time_input/
│ │ ├── README.md
│ │ └── untitled-1.md
│ ├── time_input.md
│ ├── timeinput.md
│ ├── timer.md
│ ├── twitter.md
│ ├── value_display.md
│ ├── video.md
│ └── webhook.md
├── mobile-app/
│ └── untitled.md
├── new/
│ └── en/
│ ├── product_categories.md
│ ├── product_hotspot_prefix.md
│ └── product_template_ids.md
├── ota.md
├── roadmap.md
├── ru/
│ ├── Amendments.md
│ ├── AppExport.md
│ ├── BlynkFirmware.md
│ ├── BlynkMainOperations.md
│ ├── BlynkProtocol.md
│ ├── BlynkServer.md
│ ├── FAQ.md
│ ├── GettingStarted.md
│ ├── HardwareSetUps.md
│ ├── Implementing.md
│ ├── IntroAndDownloads.md
│ ├── License.md
│ ├── Links.md
│ ├── OTA.md
│ ├── README.md
│ ├── Roadmap.md
│ ├── Security.md
│ ├── Sharing.md
│ ├── SupportedHardware.md
│ ├── Troubleshooting.md
│ ├── Widgets.md
│ ├── amendments.md
│ ├── appexport.md
│ ├── blynkfirmware.md
│ ├── blynkmainoperations.md
│ ├── blynkprotocol.md
│ ├── blynkserver.md
│ ├── faq.md
│ ├── gettingstarted.md
│ ├── hardwaresetups.md
│ ├── http.md
│ ├── implementing.md
│ ├── introanddownloads.md
│ ├── license.md
│ ├── links.md
│ ├── ota.md
│ ├── readme.md
│ ├── roadmap.md
│ ├── ru.md
│ ├── security.md
│ ├── sharing.md
│ ├── supportedhardware.md
│ ├── troubleshooting.md
│ └── widgets.md
├── scripts/
│ ├── flatdoc.js
│ ├── legacy.js
│ └── script.js
├── security.md
├── sharing.md
├── supportedhardware.md
├── table.css
├── themes/
│ ├── blynk.css
│ └── prism.css
├── troubleshooting.md
├── untitled/
│ ├── README.md
│ ├── accelerometer.md
│ ├── archive/
│ │ ├── README.md
│ │ ├── bad-request-github.md
│ │ ├── joystick.md
│ │ └── super_chart.md
│ ├── barometer.md
│ ├── ble.md
│ ├── blob/
│ │ ├── README.md
│ │ ├── master.md
│ │ ├── menu/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-1.md
│ │ ├── proximity.md
│ │ ├── styled_button/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io.md
│ │ ├── textinput.md
│ │ └── timeinput/
│ │ ├── README.md
│ │ └── blynkkk-blynkkk.github.io-2.md
│ ├── bluetooth.md
│ ├── blynkkk-blynkkk.github.io/
│ │ ├── README.md
│ │ └── gps_trigger.md
│ ├── blynkkk-blynkkk.github.io-1/
│ │ ├── README.md
│ │ └── rtc.md
│ ├── blynkkk-blynkkk.github.io-2/
│ │ ├── README.md
│ │ └── eventor.md
│ ├── blynkkk-blynkkk.github.io-3/
│ │ ├── README.md
│ │ └── email.md
│ ├── blynkkk-blynkkk.github.io-4/
│ │ ├── README.md
│ │ └── tabs.md
│ ├── blynkkk-blynkkk.github.io-5/
│ │ ├── README.md
│ │ └── map.md
│ ├── blynkkk-blynkkk.github.io-6/
│ │ ├── README.md
│ │ └── ble.md
│ ├── blynkkk-blynkkk.github.io-7/
│ │ ├── README.md
│ │ └── device_tiles.md
│ ├── blynkkk-blynkkk.github.io-8/
│ │ ├── README.md
│ │ └── temperature.md
│ ├── blynkkk-blynkkk.github.io-9/
│ │ ├── README.md
│ │ └── value_display.md
│ ├── bridge.md
│ ├── build-software-better-together/
│ │ ├── README.md
│ │ └── video.md
│ ├── button.md
│ ├── commit/
│ │ ├── README.md
│ │ ├── change-float-to-double-41-b1f1a43.md
│ │ ├── gauge.md
│ │ └── music_player.md
│ ├── commits/
│ │ ├── README.md
│ │ ├── blynkkk-blynkkk.github.io.md
│ │ ├── light.md
│ │ └── time_input.md
│ ├── device_selector.md
│ ├── device_tiles.md
│ ├── email.md
│ ├── eventor.md
│ ├── find/
│ │ ├── README.md
│ │ ├── blynkkk-blynkkk.github.io.md
│ │ ├── image.md
│ │ └── terminal.md
│ ├── gauge.md
│ ├── gps_streaming.md
│ ├── gps_trigger.md
│ ├── graph.md
│ ├── gravity.md
│ ├── humidity.md
│ ├── image.md
│ ├── joystick.md
│ ├── labeled_value.md
│ ├── labeled_value_display.md
│ ├── lcd.md
│ ├── led.md
│ ├── level_display.md
│ ├── light.md
│ ├── map.md
│ ├── menu.md
│ ├── music_player.md
│ ├── network/
│ │ ├── README.md
│ │ ├── blynkkk-blynkkk.github.io.md
│ │ ├── numberinput.md
│ │ └── slider.md
│ ├── notification.md
│ ├── number_input.md
│ ├── numberinput.md
│ ├── proximity.md
│ ├── pull/
│ │ ├── README.md
│ │ ├── change-float-to-double-by-earlold-pull-request-41.md
│ │ ├── text_input.md
│ │ └── webhook.md
│ ├── report.md
│ ├── rgb.md
│ ├── rtc.md
│ ├── ru.md
│ ├── segmented_control.md
│ ├── segmentedswitch.md
│ ├── slider.md
│ ├── step.md
│ ├── styled_button.md
│ ├── super_chart.md
│ ├── table.md
│ ├── tabs.md
│ ├── temperature.md
│ ├── terminal.md
│ ├── textinput.md
│ ├── timeinput.md
│ ├── timer.md
│ ├── tree/
│ │ ├── README.md
│ │ ├── accelerometer/
│ │ │ ├── README.md
│ │ │ └── new.md
│ │ ├── barometer.md
│ │ ├── bluetooth/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-4.md
│ │ ├── blynkkk-blynkkk.github.io.md
│ │ ├── bridge.md
│ │ ├── button/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-3.md
│ │ ├── device_selector.md
│ │ ├── gps_streaming.md
│ │ ├── graph/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-6.md
│ │ ├── gravity/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-5.md
│ │ ├── humidity/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-1.md
│ │ ├── labeled_value.md
│ │ ├── labeled_value_display.md
│ │ ├── lcd.md
│ │ ├── led.md
│ │ ├── level_display.md
│ │ ├── master.md
│ │ ├── notification.md
│ │ ├── number_input/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io.md
│ │ ├── report.md
│ │ ├── rgb.md
│ │ ├── segmented_control/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io-2.md
│ │ ├── segmentedswitch.md
│ │ ├── step.md
│ │ ├── table/
│ │ │ ├── README.md
│ │ │ └── blynkkk-blynkkk.github.io.md
│ │ ├── timer.md
│ │ └── twitter.md
│ ├── twitter.md
│ ├── value_display.md
│ ├── video.md
│ └── webhook.md
├── widgets-ru.md
└── widgets.md
================================================
FILE CONTENTS
================================================
================================================
FILE: Amendments.md
================================================
#Blynk Amendments
###Tell every maker about Blynk
No pressure. Just do it. Now.
###Make your idea work without Blynk
Blynk can be easily integrated in almost any project. But before that - make it work **without** it. After you are sure that you can get all the sensor data or can control things from the code – integrate Blynk and make it even more awesome.
###Use search
We are always happy to chat and help, but remember - every time you ask the question that was answered many many times before that, Blynk Team is not building a new widget or new cool feature. So:
- google before asking
- use search on our forum, it works really well
- check Instructables
###Always wrap your code
Though shalt not post code without ```wrapping it```
================================================
FILE: AppExport.md
================================================
# App Export
## Firmware for ESP8266, NodeMCU, BlynkBoard, etc.
#### Prepare development environment
1. Install [Arduino IDE](https://www.arduino.cc/en/Main/Software)
2. Install [Blynk Library](https://github.com/blynkkk/blynk-library/releases/latest) and restart Arduino IDE
3. Install [ESP8266 core for Arduino](https://github.com/esp8266/Arduino#installing-with-boards-manager)
4. For Windows / OS X, you may need to install USB-Serial drivers according to your converter:
- СP2102: https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx
- FTDI (FT232, etc): http://www.ftdichip.com/Drivers/VCP.htm
- *TODO: Link to drivers for CH340 and PL2303.*
5. If your board has a NeoPixel RGB LED, install [Adafruit NeoPixel](https://github.com/adafruit/Adafruit_NeoPixel) library from Library Manager
#### Build your Firmware
1. Open our example in Arduino IDE: ```File -> Examples -> Blynk -> Provisioning -> Blynk_ESP8266```
2. Open ```Settings.h``` tab.
3. Configure your firmware:
* ```BOARD_NAME``` - ...
* ```BOARD_VENDOR``` - ...
* ```PRODUCT_WIFI_SSID``` - ...
#### Upload firmare
1. Select your board type: ```Tools -> Board -> [Your Board]```
2. Select your port: ```Tools -> Port -> [...]```
3. Verify and Upload!
Note that for Blynk Board, you can select board type ```NodeMCU 1.0```.
================================================
FILE: BlynkFirmware.md
================================================
#Blynk Firmware
## Configuration
### Blynk.begin()
The easiest way to configure Blynk is to use ```Blynk.begin()```:
```cpp
Blynk.begin(auth, ...);
```
It has multiple parameters for different hardware models and it also depends on the type of connection. Follow the example sketches for your specific hardware model.
What happens inside of ```Blynk.begin()``` function:
1. Connection to the network (WiFi, Ethernet, ...)
2. Call of ```Blynk.config(...)``` to set Auth Token, Server Address, etc.
3. Attempts to connect to the server once (can block for more than 30s)
If your shield/connection type is not supported yet - you can implement it by yourself. [Here are some examples](https://github.com/blynkkk/blynk-library/tree/master/examples/More/ArduinoClient).
### Blynk.config()
```config()``` allows you to manage network connection. You can set up your connection type (WiFi, Ethernet, ...) by yourself, and then call:
```cpp
Blynk.config(auth, server, port);
```
or just
```cpp
Blynk.config(auth);
```
**NOTE: After ``` Blynk.config(...) ``` is called, your hardware is not yet connected to the server.**
It will try to connect while until it hits first instance of ``` Blynk.run() ``` or ``` Blynk.connect() ```routine.
To skip connecting to the server or to disconnect manually, call ``` Blynk.disconnect() ``` after configuration.
Use ```connectWiFi``` to conveniently set up WiFi connection:
```cpp
Blynk.connectWiFi(ssid, pass);
```
To connect to open WiFi networks, set pass to an empty string (```""```).
## Connection management
There are several functions to help with connection management:
### Blynk.connect()
This functions will continue trying to connect to Blynk server.
Returns `true` when connected, `false` if timeout have been reached.
Default timeout is 30 seconds.
```cpp
bool result = Blynk.connect();
bool result = Blynk.connect(timeout);
```
### Blynk.disconnect()
Disconnects hardware from Blynk server:
```cpp
Blynk.disconnect();
```
### Blynk.connected()
Returns `true` when hardware is connected to Blynk Server, `false` if there is no active connection to Blynk server.
```cpp
bool result = Blynk.connected();
```
### Blynk.run()
This function should be called frequently to process incoming commands and perform housekeeping of Blynk connection.
It is usually called in ``` void loop() {} ```.
This command can be initiated it in other places of your code unless you run out of heap memory (in the cascaded functions with local memory).
For example, it is not recommended to call ``` Blynk.run() ``` inside of the ```BLYNK_READ ``` and ``` BLYNK_WRITE ``` functions on low-RAM devices.
## Digital & Analog pins control
Blynk library can perform basic pin IO (input-output) operations out-of-the-box:
digitalRead
digitalWrite
analogRead
analogWrite (PWM or Analog signal depending on the platform)
No need to write code for simple things like LED, Relay control and analog sensors. Just choose a corresponding Pin in Blynk app and control it directly with no additional code
## Virtual pins control
Virtual Pins is a way to exchange any data between your hardware and Blynk app.
Think about Virtual Pins as channels for sending any data. Make sure you differentiate Virtual Pins from physical GPIO
pins on your hardware. Virtual Pins have no physical representation.
Virtual Pins are commonly used to interface with other libraries (Servo, LCD and others) and implement custom logic.
The device can send data to the App using ```Blynk.virtualWrite(pin, value)``` and receive data from the App using ```BLYNK_WRITE(vPIN)```. Read below
#### Virtual Pin data types
All Virtual Pin values are always sent as Strings and there are no practical limits on the data that can be sent.
However, there are certian limitations on the hardware side when dealing with numbers. For example, the integer on Arduino
is 16-bit, allowing range -32768 to 32767.
To interpret incoming data as Integers, Floats, Doubles and Strings use:
```cpp
param.asInt();
param.asFloat();
param.asDouble();
param.asStr();
```
You can also get the RAW data from the param buffer:
```cpp
param.getBuffer()
param.getLength()
```
### Blynk.virtualWrite(vPin, value)
**NOTE: Use BlynkTimer when you use this command to send data. Otherwise your hardware will be disconnected from the server**
Send data in various formats to Virtual Pins.
```cpp
// Send string
Blynk.virtualWrite(pin, "abc");
// Send integer
Blynk.virtualWrite(pin, 123);
// Send float
Blynk.virtualWrite(pin, 12.34);
// Send multiple values as an array
Blynk.virtualWrite(pin, "hello", 123, 12.34);
// Send RAW data
Blynk.virtualWriteBinary(pin, buffer, length);
```
Calling ```virtualWrite``` attempts to send the value to the network immediately.
**Note:** For virtual pins with numbers > 127, the `V128` syntax is not available.
Please use plain virtual pin number, for example:
```cpp
Blynk.virtualWrite(128, "abc");
```
## BlynkTimer
It's important to send data in intervals and keep the void loop() as clean as possible.
`BlynkTimer` allows you to send data periodically with given intervals not interfering with Blynk library routines
`Blynk Timer` inherits [SimpleTimer Library](http://playground.arduino.cc/Code/SimpleTimer), a well known and widely used library to time multiple events on hardware.
`BlynkTimer` is included in Blynk library by default and there is no need to install SimpleTimer separately or include `SimpleTimer.h`
- A single `BlynkTimer` object allows to schedule up to 16 timers
- Improved compatibility with boards like `Arduino 101`, `Intel Galileo`, etc.
- When a timer struggles to run multiple times (due to a blocked `loop`), it just skips all the missed intervals, and calls your function only once. This differs from `SimpleTimer`, which could call your function multiple times in this scenario.
For more information on timer usage, please see: http://playground.arduino.cc/Code/SimpleTimer
And here is a BlynkTimer [example sketch](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushData/PushData.ino#L30).
Please also remember that a single ```BlynkTimer``` can schedule many timers, so most probably you need only one instance of BlynkTimer in your sketch.
### BLYNK_WRITE(vPIN)
```BLYNK_WRITE``` is a function called every time device gets an update of Virtual Pin value from the server (or app):
To read the received data use:
```cpp
BLYNK_WRITE(V0)
{
int value = param.asInt(); // Get value as integer
// The param can contain multiple values, in such case:
int x = param[0].asInt();
int y = param[1].asInt();
}
```
**`BLYNK_WRITE` can't be used inside of any loop or function. It's a standalone function.**
**Note:** For virtual pins with numbers > 127, please use `BLYNK_WRITE_DEFAULT()` API
### BLYNK_READ(vPIN)
```BLYNK_READ``` is function called when device is requested to send it's current value of Virtual Pin to the server. Normally, this function should contain ```Blynk.virtualWrite``` call(s).
```cpp
BLYNK_READ(V0)
{
Blynk.virtualWrite(V0, newValue);
}
```
**Note:** For virtual pins with numbers > 127, please use `BLYNK_READ_DEFAULT()` API
### BLYNK_WRITE_DEFAULT()
Redefines the handler for all pins that are not covered by custom ```BLYNK_WRITE``` functions.
```cpp
BLYNK_WRITE_DEFAULT()
{
int pin = request.pin; // Which exactly pin is handled?
int value = param.asInt(); // Use param as usual.
}
```
### BLYNK_READ_DEFAULT()
Redefines the handler for all pins that are not covered by custom ```BLYNK_READ``` functions.
```cpp
BLYNK_READ_DEFAULT()
{
int pin = request.pin; // Which exactly pin is handled?
Blynk.virtualWrite(pin, newValue);
}
```
### BLYNK_CONNECTED()
Use this function when you need to run certain routine when hardware connects to Blynk Cloud or private server. It's common to call sync functions inside of this function.
```cpp
BLYNK_CONNECTED() {
// Your code here
}
```
### BLYNK_APP_CONNECTED()
This function is called every time Blynk app client connects to Blynk server.
```cpp
BLYNK_APP_CONNECTED() {
// Your code goes here
}
```
**Note: Ennable this feature in Project Settings first:**
<img src="images/app_connected_setting.png" style="width: 200px; height:360px"/>
[Example](https://github.com/blynkkk/blynk-library/blob/master/examples/More/AppConnectedEvents/AppConnectedEvents.ino)
### BLYNK_APP_DISCONNECTED()
This function is called every time the Blynk app disconnects from Blynk Cloud or private server.
```cpp
BLYNK_APP_DISCONNECTED() {
// Your code here
}
```
**Note: Enable this feature in Project Settings first:**
<img src="images/app_connected_setting.png" style="width: 200px; height:360px"/>
[Example](https://github.com/blynkkk/blynk-library/blob/master/examples/More/AppConnectedEvents/AppConnectedEvents.ino)
### Blynk.syncAll()
Requests all stored on the server latest values for all widgets. All analog/digital/virtual pin values and states will be set to the latest stored value. Every virtual pin will generate BLYNK_WRITE() event.
```cpp
BLYNK_CONNECTED() {
Blynk.syncAll();
}
```
### Blynk.syncVirtual(vPin)
This command updates individual Virtual Pin to the latest stored value on the server. When it's used, a corresponding ```BLYNK_WRITE``` handler is called.
```cpp
Blynk.syncVirtual(V0);
```
To update multiple pins, use:
```
Blynk.syncVirtual(V0, V1, V6, V9, V16);
```
### Blynk.setProperty(vPin, "property", value)
This command allows [changing widget properties](#blynk-main-operations-change-widget-properties)
## Debugging
### #define BLYNK_PRINT
### #define BLYNK_DEBUG
To enable debug prints on the default Serial port add on the top of your sketch
**IMPORTANT: This should be the first line in your code**:
```cpp
#define BLYNK_PRINT Serial // Defines the object that is used for printing
#define BLYNK_DEBUG // Optional, this enables more detailed prints
```
Then enable Serial Output in setup():
```cpp
Serial.begin(9600);
```
Open Serial Monitor and you'll see the debug prints.
You can also use spare Hardware serial ports or SoftwareSerial for debug output (you will need an adapter to connect to it with your PC).
<span style="color:#D3435C;">**WARNING:** Enabling ```BLYNK_DEBUG``` will slowdown your hardware processing speed up to 10 times!</span>
### BLYNK_LOG()
When ```BLYNK_PRINT``` is defined, you can use ```BLYNK_LOG``` to print your logs. The usage is similar to ```printf```:
```cpp
BLYNK_LOG("This is my value: %d", 10);
```
On some platforms (like Arduino 101) the ```BLYNK_LOG``` may be unavailable, or may just use too much resources.
In this case you can use a set of simpler log functions:
```cpp
BLYNK_LOG1("Hello World"); // Print a string
BLYNK_LOG1(10); // Print a number
BLYNK_LOG2("This is my value: ", 10); // Print 2 values
BLYNK_LOG4("Temperature: ", 24, " Humidity: ", 55); // Print 4 values
...
```
## Minimizing footprint
To minimize the program Flash/RAM, you can disable some of the built-in functionality:
1. Comment-out ```#define BLYNK_PRINT``` to remove prints
2. Put on the top of your sketch:
```
#define BLYNK_NO_BUILTIN // Disable built-in analog & digital pin operations
#define BLYNK_NO_FLOAT // Disable float operations
```
## Porting, hacking
If you want to dive into crafting/hacking/porting Blynk library implementation, please also check [this documentation](https://github.com/blynkkk/blynk-library/tree/master/extras/docs).
================================================
FILE: BlynkMainOperations.md
================================================
# Blynk main operations
## Virtual Pins
Blynk can control Digital and Analog I/O Pins on you hardware directly. You don't even need to write code for it.
It's great for blinking LEDs, but often it's just not enough...
We designed Virtual Pins to send **any** data from your microcontroller to the Blynk App and back.
Anything you connect to your hardware will be able to talk to Blynk.
With Virtual Pins you can send something from the App, process it on microcontroller and then send it back to the smartphone. You can trigger functions, read I2C devices, convert values, control servo and DC motors etc.
Virtual Pins can be used to interface with external libraries (Servo, LCD and others) and implement custom functionality.
Hardware may send data to the Widgets over the Virtual Pin like this:
```cpp
Blynk.virtualWrite(pin, "abc");
Blynk.virtualWrite(pin, 123);
Blynk.virtualWrite(pin, 12.34);
Blynk.virtualWrite(pin, "hello", 123, 12.34);
```
For more information about virtual pins, [read this](/#blynk-firmware-virtual-pins-control)
## Send data from app to hardware
You can send any data from Widgets in the app to your hardware.
All [Controller Widgets](/#widgets-controllers) can send data to Virtual Pins on your hardware.
For example, code below shows how to get values from the Button Widget in the App
```cpp
BLYNK_WRITE(V1) //Button Widget is writing to pin V1
{
int pinData = param.asInt();
}
```
When you press a Button, Blynk App sends ```1``` On the second click - it sends ```0```
This is how Button Widget is set up:
<img src="images/button_virtual_1.png" style="width: 200px; height:360px"/>
Full example sketch: [Get Data](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/GetData/GetData.ino#L24)
### Sending array from Widget
Some Widgets (e.g Joystick, zeRGBa) have more than one output.
<img src="images/joystick_merge_mode.png" style="width: 200px; height:360px"/>
This output can be written to Virtual Pin as an array of values.
On the hardware side - you can get any element of the array [0,1,2...] by using:
```cpp
BLYNK_WRITE(V1) // Widget WRITEs to Virtual Pin V1
{
int x = param[0].asInt(); // getting first value
int y = param[1].asInt(); // getting second value
int z = param[N].asInt(); // getting N value
}
```
**Sketch:** [JoystickTwoAxis](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/JoystickTwoAxis/JoystickTwoAxis.ino#L24)
## Get data from hardware
There are two ways of pushing data from your hardware to the Widgets in the app over Virtual Pins.
### Perform requests by Widget
- Using Blynk built-in reading frequency while App is active by setting 'Reading Frequency' parameter to some interval:
<img src="images/frequency_reading_pull.png" style="width: 200px; height:360px"/>
```cpp
BLYNK_READ(V5) // Widget in the app READs Virtal Pin V5 with the certain frequency
{
// This command writes Arduino's uptime in seconds to Virtual Pin V5
Blynk.virtualWrite(5, millis() / 1000);
}
```
**Sketch:** [PushDataOnRequest](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushDataOnRequest/PushDataOnRequest.ino#L26)
### Pushing data from hardware
If you need to PUSH sensor or other data from your hardware to Widget, you can write any logic you want.
Just set the frequency to PUSH mode. Any command that hardware sends to Blynk Cloud is automatically stored on server
and you get this info either with [History Graph](/#widgets-displays-superchart) widget
or with [HTTP API](http://docs.blynkapi.apiary.io/#reference/0/pin-history-data/get-all-history-data-for-specific-pin).
<img src="images/frequency_reading_push.png" style="width: 200px; height:360px"/>
We recommend sending data in intervals and avoiding [Flood Error](https://docs.blynk.cc/#troubleshooting-flood-error).
You can use timers like [BlynkTimer](/#blynk-firmware-blynktimer).
Please read instructions inside this [example sketch](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushData/PushData.ino) for more details.
Here is how it can work:
```cpp
#include <SPI.h>
#include <Ethernet.h>
#include <BlynkSimpleEthernet.h>
char auth[] = "YourAuthToken"; // Put your token here
BlynkTimer timer; // Create a Timer object called "timer"!
void setup()
{
Serial.begin(9600);
Blynk.begin(auth);
timer.setInterval(1000L, sendUptime); // Here you set interval (1sec) and which function to call
}
void sendUptime()
{
// This function sends Arduino up time every 1 second to Virtual Pin (V5)
// In the app, Widget's reading frequency should be set to PUSH
// You can send anything with any interval using this construction
// Don't send more that 10 values per second
Blynk.virtualWrite(V5, millis() / 1000);
}
void loop()
{
Blynk.run(); // all the Blynk magic happens here
timer.run(); // BlynkTimer is working...
}
```
**Sketch:** [PushData](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushData/PushData.ino#L30)
## State syncing
### For hardware
If your hardware looses Internet connection or resets, you can restore all the values from Widgets in the Blynk app.
```cpp
BLYNK_CONNECTED() {
Blynk.syncAll();
}
//here handlers for sync command
BLYNK_WRITE(V0) {
....
}
```
The ```Blynk.syncAll()``` command restores all the Widget's values based on the last saved values on the server.
All analog and digital pin states will be restored. Every Virtual Pin will perform ```BLYNK_WRITE``` event.
**WARNING**: if pin is empty and wasn't initialized - hardware will not get any response for those pin during sync.
[Sync Hardware with App state](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/HardwareSyncStateFromApp/HardwareSyncStateFromApp.ino)
You can also update a single Virtual Pin value by calling ```Blynk.syncVirtual(V0)``` or you can update several pins with ```Blynk.syncVirtual(V0, V1, V2, ...)```.
You can also use server to store any value without widget. Just call ```Blynk.virtualWrite(V0, value)```.
[Storing single value on server](https://github.com/blynkkk/blynk-library/blob/master/examples/More/ServerAsDataStorage/ServerAsDataStorage_SingleValue/ServerAsDataStorage_SingleValue.ino)
[Storing multiple values on server](https://github.com/blynkkk/blynk-library/blob/master/examples/More/ServerAsDataStorage/ServerAsDataStorage_MultiValue/ServerAsDataStorage_MultiValue.ino)
### For app
If you need to keep your hardware in sync with Widgets' state even if app is offline use ```Blynk.virtualWrite```.
Imagine you have a LED Widget connected to the Virtual Pin V1 in the app, and a physical button attached to your hardware.
When you press a physical button, you would expect to see updated state of the LED Widget in the app.
To achieve that you need to send ```Blynk.virtualWrite(V1, 255)``` when a physical button gets pressed.
[Represent physical button state via LED widget with interrupts](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/ButtonInterrupt/ButtonInterrupt.ino)
[Represent physical button state via LED widget with polling](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/ButtonPoll/ButtonPoll.ino)
[Represent physical button state via Button widget with polling](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/SyncPhysicalButton/SyncPhysicalButton.ino)
## Control of multiple devices
Blynk app has support of multiple devices. That means you can assign any widget to specific device with own auth token.
For example - you may have button on V1 that controls wi-fi bulb A and another button on V1 that controls wi-fi bulb B. In order
to do this you need more than 1 device within your project. To achieve this please go to project settings and click on "Devices" section :
<img src="images/new_project_settings.png" style="width: 200px; height:360px"/>
You'll see list of devices :
<img src="images/list_of_devices.png" style="width: 200px; height:360px"/>
So you can add new device :
<img src="images/new_device.png" style="width: 200px; height:360px"/>
After above steps, every widget will have one more field "Target" :
<img src="images/widget_settings_devices.png" style="width: 200px; height:360px"/>
Now you need to assign widget to device and after that widget will control only this specific device.
That's it! Now you need to upload sketches with correct Auth Tokens to your hardware.
### Tags
Tags feature allows you to group multiple devices. Tags are very useful in case you want to control few devices with
1 widget. For example, imagine a case when you have 3 smart bulbs and you want to turn on all those bulbs with one
single click. You need to assign 3 devices to 1 tag and assign tag to button. That's it.
Tag widgets also support state syncing. So you can get state of widget from your hardware. However you can't update
state of such widgets from hardware.
## Devices online status
Blynk app has support for online statuses for multiple devices.
<img src="images/online_status.png" style="width: 200px; height:360px"/>
In ideal world when device closes tcp connection with some ```connection.close()``` - connected server will get notification
regarding closed connection. So you can get instant status update on UI. However in real world this mostly exceptional situation.
In majority of cases there is no easy and instant way to find out that connection is not active anymore.
That's why Blynk uses ```HEARTBEAT``` mechanism. With this approach hardware periodically sends ```ping``` command with predefined
interval (10 seconds by default, ```BLYNK_HEARTBEAT``` [property](https://github.com/blynkkk/blynk-library/blob/master/src/Blynk/BlynkConfig.h)).
In case hardware don't send anything within 10 seconds server waits additional 5 seconds and after that connection
assumed to be broken and closed by server. So on UI you'll see connection status update only after 15 seconds when it is
actually happened.
You can also change ```HEARTBEAT``` interval from hardware side via ```Blynk.config```. In that case ```newHeartbeatInterval * 2.3``` formula will be applied. So in case you you decided to set ```HEARTBEAT``` interval to
5 seconds. You'll get notification regarding connection with 11 sec delay in worst case.
## Project Settings
Every project has it's own settings:
- **Theme** - switch between the Light and Black Blynk Theme (Business accounts have wider choice);
- **Keep screen always on** - allows you to use the Blynk app without going to the sleep mode (usually all mobile devices do that);
- **Send app connected command** - with this option enabled the server will send "App Connected" and "App Disconnected" commands
to your hardware when your Blynk app goes online/offline. [Usage example](https://github.com/blynkkk/blynk-library/blob/master/examples/More/AppConnectedEvents/AppConnectedEvents.ino);
- **Do not show offline notifications** - right now, for debugging purposes, every time your hardware goes offline - the Blynk
Server will notify you with popup in the app about that. However, when debugging is not needed or the Blynk app is used only
via HTTP/S this notifications are meaningless. So this switch allows you to turn off this popups. Also this switch turns off
the Push notification "Notify when offline" option.
## Change Widget properties
Changing some of the widget properties from hardware side is also supported.
For example, you can change the color of LED widget based on a condition:
```
//change LED color
Blynk.setProperty(V0, "color", "#D3435C");
//change LED label
Blynk.setProperty(V0, "label", "My New Widget Label");
//change MENU labels
Blynk.setProperty(V0, "labels", "Menu Item 1", "Menu Item 2", "Menu Item 3");
```
[Set Property for single value field](https://github.com/blynkkk/blynk-library/blob/master/examples/More/SetProperty/SetProperty_SingleValue/SetProperty_SingleValue.ino)
[Set Property for multi value field](https://github.com/blynkkk/blynk-library/blob/master/examples/More/SetProperty/SetProperty_MultiValue/SetProperty_MultiValue.ino)
**NOTE : ** Changing these parameters work **only** for widgets attached to Virtual pins (analog/digital pins won't work).
Four widget properties are supported - ```color```, ```label```, ```min```, ```max``` for all widgets :
```label``` is string for label of all widgets.
```color``` is string in [HEX](http://www.w3schools.com/html/html_colors.asp) format (in the form: #RRGGBB,
where RR (red), GG (green) and BB (blue) are hexadecimal values between 00 and FF). For example :
```
#define BLYNK_GREEN "#23C48E"
#define BLYNK_BLUE "#04C0F8"
#define BLYNK_YELLOW "#ED9D00"
#define BLYNK_RED "#D3435C"
#define BLYNK_DARK_BLUE "#5F7CD8"
```
```min```, ```max``` - minimum and maximum values for the widget (for example range for the Slider).
This numbers may be float.
On firmware side, widget objects also support ```setLabel()``` and ```setColor()``` functions.
Widget specific properties:
**Button**
```onLabel``` / ```offLabel``` is string for ON/OFF label of button;
**Styled Button**
```onLabel``` / ```offLabel``` is string for ON/OFF label of button;
```onColor``` / ```offColor``` is string in HEX format for ON/OFF colors of the button;
```onBackColor``` / ```offBackColor``` is string in HEX format for ON/OFF colors of the button background.
**Music Player**
```isOnPlay``` is boolean accepts true/false.
```
Blynk.setProperty(V0, "isOnPlay", "true");
```
**Menu**
```labels``` is list of strings for Menu widget selections;
```
Blynk.setProperty(V0, "labels", "label 1", "label 2", "label 3");
```
**Video Streaming**
```cpp
Blynk.setProperty(V1, "url", "http://my_new_video_url");
```
**Step**
```cpp
Blynk.setProperty(V1, "step", 10);
```
**Image**
```cpp
Blynk.setProperty(V1, "opacity", 50); // 0-100%
```
```cpp
Blynk.setProperty(V1, "scale", 30); // 0-100%
```
```cpp
Blynk.setProperty(V1, "rotation", 10); //0-360 degrees
```
also, you can fully replace the list of images from the hardware:
```cpp
Blynk.setProperty(V1, "urls", "https://image1.jpg", "https://image2.jpg");
```
or you can change individual image by it index:
```cpp
Blynk.setProperty(V1, "url", 1, "https://image1.jpg");
```
You can also change widget properties via [HTTP API](http://docs.blynkapi.apiary.io/#).
## Limitations and Recommendations
- Don't put ```Blynk.virtualWrite``` and any other ```Blynk.*``` command inside ```void loop()```- it will cause
lot's of outgoing messages to our server and your connection will be terminated;
- We recommend calling functions with intervals. For example, use [BlynkTimer](/#blynk-firmware-blynktimer)
- Avoid using long delays with ```delay()``` – it may cause connection breaks;
- If you send more than 100 values per second - you may cause
[Flood Error](/#troubleshooting-flood-error) and your hardware will be automatically disconnected from the server;
- Be careful sending a lot of ```Blynk.virtualWrite``` commands as most hardware is not very powerful (like ESP8266)
so it may not handle many requests.
================================================
FILE: BlynkProtocol.md
================================================
# Blynk protocol
Blynk transfers binary messages with the following structure:
| Command | Message Id | Length/Status | Body |
|:-------------:|:-------------:|:---------------:|:--------:|
| 1 byte | 2 bytes | 2 bytes | Variable |
Message Id and Length are [big endian](http://en.wikipedia.org/wiki/Endianness#Big-endian).
Body has a command-specific format.
Command and Status definitions: [BlynkProtocolDefs.h](https://github.com/blynkkk/blynk-library/blob/master/Blynk/BlynkProtocolDefs.h)
Another protocol description can be found [here](https://github.com/blynkkk/blynk-server/blob/master/README_FOR_APP_DEVS.md#protocol-messages).
Typical Blynk library knows how to send(S)/process(P):
S BLYNK_CMD_LOGIN + auth token
SP BLYNK_CMD_PING
SP BLYNK_CMD_RESPONSE
SP BLYNK_CMD_BRIDGE
SP BLYNK_CMD_HARDWARE
S BLYNK_CMD_TWEET
S BLYNK_CMD_EMAIL
S BLYNK_CMD_PUSH_NOTIFICATION
## HARDWARE/BRIDGE command body
The body of these commands are encoded as a sequence of strings, separated by ```'\0'``` ([Null character](http://en.wikipedia.org/wiki/Null_character)).
Please note that the last value may be not Null-terminated.
In the following command examples ```\0``` chars are replaced with spaces.
### Pin mode
PinMode command is received by library after connection, or when a mobile application starts.
pm <pin> <mode>
pm <pin> <mode> <pin> <mode> <pin> <mode> ...
Mode:
* in - INPUT
* out - OUTPUT
* pu - INPUT_PULLUP
* pd - INPUT_PULLDOWN
### Digital pin operations
Digital write:
dw <pin> <val>
Digital read:
dr <pin>
### Analog pin operations
aw <pin> <val>
ar <pin>
### Virtual pin operations
vw <pin> <param0> <param1> <param2> <param3> ...
vr <pin>
### Other operations
info
TODO
## Developer notes
* Values in HW commands are plain text.
* In response to ```dr/ar``` command, library should send ```dw/aw``` command on the same pin and with the same message id.
* These situations should cause a connection drop, or reconnection attempt:
* Message with ```ID=0``` is received
* Message with unknown type is received
## Adding network interface
4 entities should be created to add a new network interface to Blynk:
1. Select connection interface that will be used for Blynk operation.
This should be something like http://www.arduino.cc/en/Tutorial/WebClient
Based on the API of the connection, create the **Transport**.
Some examples may be found in the Adapters folder:
* BlynkTransportSerial
* BlynkTransportCC3000
* BlynkArduinoClient - *can be reused, if possible*
2. Create **Blynk representative class**, which contains connection-specific helper functions (like begin).
Examples:
* BlynkEthernet
* BlynkSerial
* BlynkCC3000
* BlynkWildFire
* BlynkYun
3. Create **BlynkSimple*** header for your connection.
This constructs main **Blynk instance**, so the user (mostly) doesn't need to get into such details.
Examples:
* BlynkSimpleEthernet.h
* BlynkSimpleCC3000.h
* BlynkSimpleWifi.h
* BlynkSimpleUIPEthernet.h
4. Create a **simple example** for your platform ;)
### Example implementations
Use these to play with the protocol and understand the basics:
* [Pseudo-library in Python](https://github.com/blynkkk/blynk-library/blob/master/tests/pseudo-library.py)
* [Node.js + Espruino](https://github.com/vshymanskyy/blynk-library-js)
* [Arduino](https://github.com/blynkkk/blynk-library)
* [Particle Core](https://github.com/vshymanskyy/blynk-library-spark)
================================================
FILE: BlynkServer.md
================================================
# Blynk server
No longer supported
================================================
FILE: CNAME
================================================
docs.blynk.cc
================================================
FILE: FAQ.md
================================================
#FAQ
- I backed Blynk on Kickstarter. Where are my widgets and why the app is free?
> App is free because otherwise you would have to pay to download it. This is how AppStore and Google Play works.
> Current Blynk release has a limited amount of widgets. We decided to make them free for everyone until we implement store. After that, every widget will be paid. However every backer will get them for free (according to their pledge).
- What is Blynk Cloud?
> Blynk Cloud is a open-source software written on Java using plain TCP/IP and secured TCP/IP (for hardware that supports it) sockets and running on our server. Blynk iOS and Android apps connect to Blynk Cloud by default. Access is free for every Blynk user. We also provide a Private Server distribution for those who want to [install it locally](/#blynk-server).
- How much access to Cloud Blynk Server cost?
> It is free for every Blynk user.
- Can I run Blynk server locally?
> Yes. Those of you, who want extra security or don’t have internet connection, can install Local Blynk Server and run it in your own local network. Blynk Server is Open-Source and it takes less than few seconds to deploy. All the instructions and files are [here](/#blynk-server).
- What are the requirements to run Private Blynk Server?
> To run Private Blynk Server, all you need is Java Runtime Environment.
- Can I run Blynk server on Raspberry Pi?
> Yes, surely! [Here is instruction](/#blynk-server-how-to-run-local-blynk-server-launch-blynk-server-on-raspberry-pi).
- Does Blynk app work over Bluetooth?
> Yes. It is in beta right now.
- Does Blynk support Ethernet / Wi-FI / UART?
> Yes, all of them. See full list of [supported hardware](/#supported-hardware) and shields.
- I don't have any shield. Can I use Blynk with my computer?
> Yes, you can use Blynk just with a USB cable. There is a step-by-step [instruction](/#other-hardware-connect-over-usb) on how to do it.
- Can Blynk handle multiple Arduinos?
> Yes. There 3 ways right now :
> - add multiple devices to your project.
> - you may use same [Auth Token](/#getting-started-getting-started-with-application-auth-token) for different hardware. In that case you can control few hardwares from 1 dashboard.
> - you can do it using [Bridge functionality](/#widgets-other-bridge) which allows you to send messages from one hardware to another.
- Does Blynk server store sensor data when app goes offline?
> Yes, every command that hardware sends to server is stored. You could use [History Graph](/#widgets-displays-superchart) widget in order to view it.
- How many Virtual Pins I can use?
> It depends mostly on your hardware. Low-end hardware may use up to 32 Virtual Pins. More powerful (like ESP8266) can
> use up to 128 but it requires also BLYNK_USE_128_VPINS property in your sketch. [Example](https://github.com/blynkkk/blynk-library/blob/master/src/Blynk/BlynkConfig.h#L64).
- Why app requires all this permissions?
> http://help.blynk.cc/faq/blynk-android-permissions-explained
================================================
FILE: GettingStarted.md
================================================
#Getting Started
Let's get you started in 5 minutes (reading doesn't count!).
We will switch on an LED connected to your Arduino using the Blynk App on your smartphone.
Connect an LED as shown here:
<img src="images/Arduino_LED.jpg" style="width: 250px; height:350px"/>
##Getting Started With The Blynk App
###1. Create a Blynk Account
After you download the Blynk App, you'll need to create a New Blynk account. This account is separate from the accounts used for the Blynk Forums, in case you already have one.
We recommend using a **real** email address because it will simplify things later.
<img src="images/register_account.png" style="width: 200px; height:360px"/>
####Why do I need to create an account?
An account is needed to save your projects and have access to them from multiple devices from anywhere. It's also a security measure.
You can always set up your own [Private Blynk Server](/#blynk-server) and have full control.
###2. Create a New Project
After you've successfully logged into your account, start by creating a new project.
<img src="images/getting_started/create_project_button.png" style="width: 200px; height:360px"/>
###3. Choose Your Hardware
Select the hardware model you will use. Check out the [list of supported hardware](/#supported-hardware)!
<img src="images/getting_started/select_hardware.png" style="width: 200px; height:360px"/>
###4. Auth Token
**Auth Token** is a unique identifier which is needed to connect your hardware to your smartphone.
Every new project you create will have its own Auth Token. You'll get Auth Token automatically on your email after
project creation. You can also copy it manually. Click on devices section and selected required device :
<img src="images/getting_started/token_1.png" style="width: 200px; height:360px"/>
And you'll see token :
<img src="images/getting_started/new_device.png" style="width: 200px; height:360px"/>
<span style="color:#D3435C;">**NOTE:** Don't share your Auth Token with anyone, unless you want someone to have access to your hardware. </span>
It's very convenient to send it over e-mail. Press the e-mail button and the token will be sent to the e-mail address you used for registration.
You can also tap on the Token line and it will be copied to the clipboard.
Now press the **"Create"** button.
<img src="images/new_project.png" style="width: 200px; height:360px"/>
###5. Add a Widget
Your project canvas is empty, let's add a button to control our LED.
Tap anywhere on the canvas to open the widget box. All the available widgets are located here. Now pick a button.
**Widget Box**
<img src="images/widgets_box.png" style="width: 200px; height:360px"/>
**Drag-n-Drop** - Tap and hold the Widget to drag it to the new position.
**Widget Settings** - Each Widget has it's own settings. Tap on the widget to get to them.
<img src="images/button_settings.png" style="width: 200px; height:360px"/>
The most important parameter to set is **PIN** . The list of pins reflects physical pins defined by your hardware. If your LED is connected to Digital Pin 8 - then select **D8** (**D** - stands for **D**igital).
<img src="images/pin_selection.png" style="width: 200px; height:360px"/>
###6. Run The Project
When you are done with the Settings - press the **PLAY** button. This will switch you from EDIT mode to PLAY mode where you can interact with the hardware. While in PLAY mode, you won't be able to drag or set up new widgets, press **STOP** and get back to EDIT mode.
You will get a message saying "Arduino UNO is offline". We'll deal with that in the next section.
<img src="images/play_button.png" style="width: 200px; height:360px"/>
##Getting Started With Hardware
###How To Use an Example Sketch
You should by now have the Blynk Library installed on your computer. If not - [click here](/#downloads-blynk-library).
Example sketches will help you get your hardware online quickly and major Blynk features.
Open the example sketch according to the hardware model or shield you are using.
<img src="images/connection_type_sketch.png" style="width: 500px; height:217px"/>
Let's take a look at the example sketch for an [Arduino UNO + Ethernet shield](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
```cpp
#define BLYNK_PRINT Serial
#include <SPI.h>
#include <Ethernet.h>
#include <BlynkSimpleEthernet.h>
char auth[] = "YourAuthToken";
void setup()
{
Serial.begin(9600); // See the connection status in Serial Monitor
Blynk.begin(auth); // Here your Arduino connects to the Blynk Cloud.
}
void loop()
{
Blynk.run(); // All the Blynk Magic happens here...
}
```
###Auth Token
In this example sketch, find this line:
```cpp
char auth[] = "YourAuthToken";
```
This is the [Auth Token](/#getting-started-getting-started-with-application-4-auth-token) that you emailed yourself.
Please check your email and copy it, then paste it inside the quotation marks.
It should look similar to this:
```
char auth[] = "f45626c103a94983b469637978b0c78a";
```
Upload the sketch to the board and open Serial Terminal. Wait until you see something like this:
```
Blynk v.X.X.X
Your IP is 192.168.0.11
Connecting...
Blynk connected!
```
<span style="color:#24C48C" >**Congrats! You are all set! Now your hardware is connected to the Blynk Cloud!**</span>
##Blynking
Go back to the Blynk App, push the button and turn the LED on and off! It should be Blynking.
<img src="images/button_pressed.png" style="width: 200px; height:360px"/>
Check out [other example sketches](https://github.com/blynkkk/blynk-library/tree/master/examples).
Feel free to experiment and combine different examples together to create your own amazing projects.
For example, to attach an LED to a [PWM](http://www.arduino.cc/en/Tutorial/Fading)-enabled Pin on your Arduino, set the slider widget to control the brightness of an LED. Just use the same steps described above.
================================================
FILE: HardwareSetUps.md
================================================
# Hardware set-ups
## Arduino over USB (no shield)
If you don't have any shield and your hardware doesn't have any connectivity, you can still use Blynk – directly over USB :
1. Open [Arduino Serial USB example](https://github.com/blynkkk/blynk-library/blob/master/examples/Boards_USB_Serial/Arduino_Serial_USB/Arduino_Serial_USB.ino)
and change [Auth Token](/#getting-started-getting-started-with-application-4-auth-token)
```cpp
// You could use a spare Hardware Serial on boards that have it (like Mega)
#include <SoftwareSerial.h>
SoftwareSerial DebugSerial(2, 3); // RX, TX
#define BLYNK_PRINT DebugSerial
#include <BlynkSimpleStream.h>
// You should get Auth Token in the Blynk App.
// Go to the Project Settings (nut icon).
char auth[] = "YourAuthToken";
void setup()
{
// Debug console
DebugSerial.begin(9600);
// Blynk will work through Serial
Serial.begin(9600);
Blynk.begin(auth, Serial);
}
void loop()
{
Blynk.run();
}
```
2. Run the script which is usually located in ```/scripts``` folder:
- Windows:```My Documents\Arduino\libraries\Blynk\scripts```
- Mac ```User$/Documents/Arduino/libraries/Blynk/scripts```
**On Windows:**
Open cmd.exe
Write your path to blynk-ser.bat folder. For example:
```
cd C:\blynk-library-0.3.1\blynk-library-0.3.1\scripts
```
Run ```blynk-ser.bat``` file. For example : ```blynk-ser.bat -c COM4``` (where COM4 is port with your Arduino)
And press "Enter", press "Enter" and press "Enter"
**On Linux and Mac**:
Navigate to /scripts folder. For example:
```
cd User$/Documents/Arduino/libraries/Blynk/scripts
```
When inside this folder, run:
```
user:scripts User$ ./blynk-ser.sh
```
**Warning:** Do no close terminal window with running script.
In some cases you may also need to perform :
```
user:scripts User$ chmod +x blynk-ser.sh
```
You may need also to run it with ```sudo```
```
user:scripts User$ sudo ./blynk-ser.sh
```
This is what you'll see in Terminal app on Mac (usbmodem address can be different):
```
[ Press Ctrl+C to exit ]
/dev/tty.usbmodem not found.
Select serial port [ /dev/tty.usbmodem1451 ]:
```
Copy the serial port address: ```/dev/tty.usbmodem1451``` and paste it back:
```
Select serial port [ /dev/tty.usbmodem1451 ]: /dev/tty.usbmodem1451
```
After you press Enter, you should see an output similar to this:
```
Resetting device /dev/tty.usbmodem1451...
Connecting: GOPEN:/dev/tty.usbmodem1451,raw,echo=0,clocal=1,cs8,nonblock=1,ixoff=0,ixon=0,ispeed=9600,ospeed=9600,crtscts=0 <-> openssl-connect:blynk-cloud.com:9443,cafile=/Users/.../server.crt,nodelay
2015/10/03 00:29:45 socat[30438.2046857984] N opening character device "/dev/tty.usbmodem1451" for reading and writing
2015/10/03 00:29:45 socat[30438.2046857984] N opening connection to LEN=16 AF=2 45.55.195.102:9443
2015/10/03 00:29:45 socat[30438.2046857984] N successfully connected from local address LEN=16 AF=2 192.168.0.2:56821
2015/10/03 00:29:45 socat[30438.2046857984] N SSL connection using AES128-SHA
2015/10/03 00:29:45 socat[30438.2046857984] N starting data transfer loop with FDs [3,3] and [4,4]
```
<span style="color:#D3435C;">**NOTE:** Arduino IDE may complain with "programmer is not responding". You need to terminate script before uploading new sketch. </span>
Additional materials:
- [Tutorial: Control Arduino over USB with Blynk app. No shield required. Mac OS)](https://www.youtube.com/watch?v=fgzvoan_3_w)
- [How to control arduino (Wirelessly) with blynk via USB. Windows](https://www.youtube.com/watch?v=I_hgIj2FdPI)
- [Instructables: Control Arduino with Blynk over USB](http://www.instructables.com/id/Control-arduino-using-Blynk-over-usb/)
## Raspberry Pi
1. Connect your Raspberry Pi to the Internet and open it's console.
2. Run this command (it updates your OS package repository to include the required packages):
```
curl -sL "https://deb.nodesource.com/setup_6.x" | sudo -E bash -
```
3. Download and build Blynk JS library using npm:
```
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install build-essential
sudo apt-get install -g npm
sudo npm install -g onoff
sudo npm install -g blynk-library
```
4. Run Blynk test script (put your auth token):
```
blynk-client 715f8cafe95f4a91bae319d0376caa8c
```
5. You can write our own script based on [examples](https://github.com/vshymanskyy/blynk-library-js/tree/master/examples)
6. To enable Blynk auto restart for Pi, find ```/etc/rc.local``` file and add there:
```
node full_path_to_your_script.js <Auth Token>
```
Additional materials:
- [Instructables: Blynk on Javascript for Raspberry Pi, Intel Edison and others](http://www.instructables.com/id/Blynk-JavaScript-in-20-minutes-Raspberry-Pi-Edison)
- [Instructables: Use DHT11/DHT12 sensors with Raspberry Pi and Blynk](http://www.instructables.com/id/Raspberry-Pi-Nodejs-Blynk-App-DHT11DHT22AM2302/?ALLSTEPS)
**Note:** Instead of using Node.js, you can also build a C++ libarry version (same as Arduino, WiringPi-based) installation:
- [Library README for Linux](https://github.com/blynkkk/blynk-library/blob/master/linux/README.md)
- [Blynk Community Topic: How-To Raspberry Pi](https://community.blynk.cc/t/howto-for-raspberry-pi/332)
- [Video tutorial - Setting up Blynk and Raspberry Pi:](https://www.youtube.com/watch?v=iSG_8g6KyGE)
## ESP8266 Standalone
You can run Blynk directly on the ESP8266!
Install the latest ESP8266 library for Arduino using [this guide](https://github.com/esp8266/Arduino#installing-with-boards-manager).
**Example Sketch:** [ESP8266_Standalone](https://github.com/blynkkk/blynk-library/blob/master/examples/Boards_WiFi/ESP8266_Standalone/ESP8266_Standalone.ino)
Additional materials:
- [Instructables: ESP8266 ESP-12(Standalone)+ Blynk](http://www.instructables.com/id/ESP8266-ESP-12Standalone-Blynk-101)
- [Instructables: ESP8266-12 standalone Blynk lm35 temperature sensor](http://www.instructables.com/id/ESP8266-12-blynk-wireless-temperature-LM35-sensor/?ALLSTEPS)
[Step-by-Step Tutorial in Russian language](http://esp8266.ru/esp8266-blynk)
## NodeMCU
Please follow [this detailed instruction](https://github.com/blynkkk/blynk-library/tree/master/examples/Boards_WiFi/NodeMCU#instruction-for-nodemcu-setup).
Or watch [this Video tutorial](https://www.youtube.com/watch?v=FhS44hGk1Lc).
## Arduino + ESP8266 WiFi with AT commands
This connection type is not recommended for beginners.
If you would like to try it, please carefully read [this help topic](http://help.blynk.cc/hardware-and-libraries/arduino/esp8266-with-at-firmware)
**Note:** Some boards like Arduino UNO WiFi from Arduino.org, do not use AT commands (and do not provide relevant libraries), so this renders them unusable with Blynk.
## Particle
Blynk works with the whole family of Particle products: Core, Photon and Electron
1. Open [Particle Web IDE](https://build.particle.io/build).
2. Go to the libraries.
3. Search for **Blynk** in the Community Libraries and click on it
4. Open ```01_PARTICLE.INO``` example
5. Click "use this example"
6. Put your Auth Token here: ``` char auth[] = "YourAuthToken";``` and flash the Particle!
You can scan this QR code from the Blynk App and you'll get a ready-to-test project for **Particle Photon**. Just put your Auth Token into the ```01_PARTICLE.INO``` example.
<img src="images/Particle Demo1530733075.png" style="width: 300px; height:300px"/>
Additional materials:
- [Particle core + DHT22](https://www.hackster.io/gusgonnet/temperature-humidity-monitor-with-blynk-7faa51)
================================================
FILE: Implementing.md
================================================
# Implementing a Blynk HW client (library)
Currently we provide Arduino/C++ implementation of the library.
It is very extensible and modular, look at [the list of supported hardware](/#supported-hardware).
Adding new connection types and Arduino-compatible boards is easy.
TODO: Porting guide.
But some devices are programmed in other languages, like:
* Espruino, JavaScript, Node.JS
* MicroPython, Python
* NodeMCU, eLua
This document hints how to write a custom library.
## Blynk library main functions
* Provide easy-to use API
* Virtual pin handlers registration
* Provide comfortable wrappers for some widgets
* Manage connection
* Should support different connection type/hardware, if applicable
* Serialize/deserialize Blynk protocol
* Handle direct pin operations
* Should be portable across similar devices (or same technology/programming language), if possible
* Should detect and notify the user about [troubles](/#troubleshooting) where possible (especially Flood)
### Adding new HW board
Different boards can be added by creating JSON board description file.
```json
{
"name": "Arduino UNO",
"map": {
"digital": {
"pins": {
"D0": 0, "D1": 1, "D2": 2, "D3": 3, "D4": 4,
"D5": 5, "D6": 6, "D7": 7, "D8": 8, "D9": 9,
"D10": 10, "D11": 11, "D12": 12, "D13": 13
},
"ops": [ "dr", "dw" ]
},
"analog": {
"pins": {
"A0": 14, "A1": 15, "A2": 16, "A3": 17, "A4": 18, "A5": 19
},
"ops": [ "dr", "dw", "ar" ],
"arRange":[0, 1023]
},
"pwm": {
"pins": [
"D3", "D5", "D6", "D9", "D10", "D11"
],
"ops": [ "aw" ],
"awRange":[0, 255]
},
"virtual": {
"pinsRange": [ 0, 31 ],
"ops": [ "vr", "vw" ]
}
}
}
```
Look at the [full boards list](https://github.com/blynkkk/blynk-library/tree/master/boards_json).
You can send us your own board description file for review and App integration.
There may be a problem that you want to start testing your implementation, but your board is not listed int the Blynk App.
On Android, we now have a "Generic Board" specially for such purposes.
Unfortunately iOS does not have it yet.
Basically you can select UNO board and check how it works using just virtual pins.
Most digital pins will also work.
Analog IO/PWM will not work in general, until we add your board to the App.
================================================
FILE: IntroAndDownloads.md
================================================
# Intro
<h2 class="banner-header">🚨🚨🚨 IMPORTANT:</h2>
<p class="banner">
This documentation is for the LEGACY version of Blynk platform which is no longer supported and will be shut down.<br/>
You can sign up for the current version of Blynk platform <a href="http://blynk.cloud/dashboard/register">here</a>.<br/>
The new mobile apps can be downloaded from <a href="https://apps.apple.com/us/app/blynk-iot/id1559317868">App Store</a> and <a href="https://play.google.com/store/apps/details?id=cloud.blynk&hl=en&gl=US">Google Play</a>.<br/>
The actual Blynk documentation is <a href="https://docs.blynk.io/">here</a>.
</p>
If you want to continue with using unsupported verion of Blynk, check out Getting Started.
<br>
[Getting Started >](/#getting-started)
##How Blynk Works
Blynk was designed for the Internet of Things. It can control hardware remotely, it can display sensor data,
it can store data, vizualize it and do many other cool things.
There are three major components in the platform:
- **Blynk App** - allows to you create amazing interfaces for your projects using various widgets we provide.
- **Blynk Server** - responsible for all the communications between the smartphone and hardware.
You can use our Blynk Cloud or run your [private Blynk server](/#blynk-server) locally.
It's open-source, could easily handle thousands of devices and can even be launched on a Raspberry Pi.
- **Blynk Libraries** - for all the popular hardware platforms - enable communication with the server and
process all the incoming and outcoming commands.
Now imagine: every time you press a Button in the Blynk app, the message travels to ~~space~~ the Blynk Cloud,
where it magically finds its way to your hardware. It works the same in the opposite direction and
everything happens in a blynk of an eye.
<img src="images/architecture.png" style="width: 640px; height:478px"/>
##Features
* Similar API & UI for all supported hardware & devices
* Connection to the cloud using:
* WiFi
* Bluetooth and BLE
* Ethernet
* USB (Serial)
* GSM
* ...
* Set of easy-to-use Widgets
* Direct pin manipulation with no code writing
* Easy to integrate and add new functionality using virtual pins
* History data monitoring via SuperChart widget
* Device-to-Device communication using Bridge Widget
* Sending emails, tweets, push notifications, etc.
* ... new features are constantly added!
You can find [example sketches](https://github.com/blynkkk/blynk-library/tree/master/examples) covering basic Blynk Features.
They are included in the library. All the sketches are designed to be easily combined with each other.
##What do I need to Blynk?
At this point you might be thinking: **"Ok, I want it. What do I need to get started?"** – Just a couple of things, really:
####**1. Hardware**.
An Arduino, Raspberry Pi, or a similar development kit.
**Blynk works over the Internet.**
This means that the hardware you choose should be able to connect to the internet. Some of the boards, like Arduino Uno
will need an Ethernet or Wi-Fi Shield to communicate, others are already Internet-enabled: like the ESP8266, Raspberri Pi with WiFi dongle, Particle Photon or SparkFun Blynk Board. But even if you don't have a shield, you can connect it over USB to your
laptop or desktop (it's a bit more complicated for newbies, but we got you covered).
What's cool, is that the [list of hardware](/#supported-hardware) that works with Blynk is huge and will keep on growing.
####**2. A Smartphone**.
The Blynk App is a well designed interface builder. It works on both iOS and Android, so no holywars here, ok?
#Downloads
##**Blynk Apps for iOS or Android** <br>
[<img src="images/appstore-lrg.svg" alt="Drawing" style=" width: 158px; height:42"/>](https://itunes.apple.com/us/app/blynk-control-arduino-raspberry/id808760481?ls=1&mt=8) [<img src="https://play.google.com/intl/en_us/badges/images/apps/en-play-badge.png" alt="Drawing" style=" width: 158px; height:42px"/>](https://play.google.com/store/apps/details?id=cc.blynk)
##**Blynk Library** <br>
[Download The Blynk Library >](https://github.com/blynkkk/blynk-library/releases/latest)
In case you forgot, or don't know how to install Arduino libraries [click here](http://www.arduino.cc/en/guide/libraries).
================================================
FILE: License.md
================================================
# License
This project is released under The MIT License (MIT)
================================================
FILE: Links.md
================================================
#Links
* [Blynk site](https://www.blynk.cc)
* [Blynk community](https://community.blynk.cc)
* [Facebook](https://www.fb.com/blynkapp)
* [Twitter](https://twitter.com/blynk_app)
* [Blynk Library](https://github.com/blynkkk/blynk-library)
* [Blynk Examples](https://github.com/blynkkk/blynk-library/tree/master/examples)
* [Blynk Server](https://github.com/blynkkk/blynk-server)
* [Kickstarter campaign](https://www.kickstarter.com/projects/167134865/blynk-build-an-app-for-your-arduino-project-in-5-m/description)
================================================
FILE: OTA.md
================================================
#OTA
Blynk also supports over the air updates for - ESP8266, NodeMCU and SparkFun Blynk boards. OTA supported only
for the private servers and for the paid customers for now.
## How does it work?
- You need to use [regular sketch for exported apps](https://github.com/blynkkk/blynk-library/tree/master/examples/Blynk.Inject/Template_ESP8266);
- After you launched your hardware you are ready for OTA;
- You can trigger the firmware update for the specific hardware via it's token or for all hardware.
### Flow
1. User triggers OTA with one of below HTTPS request;
2. User provides within HTTPS request admin credentials and firmware binary file to update hardware with;
3. When hardware connects to server - server checks it firmware. In case, hardware firmware build date differs from
uploaded firmware, than server sends special command to hardware with url for the new firmware;
4. Hardware processes url with below [handler](https://github.com/blynkkk/blynk-library/blob/master/examples/Blynk.Inject/Template_ESP8266/OTA.h#L31):
```
BLYNK_WRITE(InternalPinOTA) {
//url to get firmware from. This is HTTP url
//http://localhost:8080/static/ota/FUp_2441873656843727242_upload.bin
overTheAirURL = param.asString();
...
}
```
5. Hardware downloads new firmware and starts flashing firmware;
## Trigger update for the specific hardware
```
curl -v -F file=@Template_ESP8266.ino.nodemcu.bin --insecure -u admin@blynk.cc:admin https://localhost:9443/admin/ota/start?token=123
```
- ```Template_ESP8266.ino.nodemcu.bin``` - is relative (or full) path to your firmware;
- ```--insecure``` flag for servers with self-generated certificates. You don't need this flag if you used Let's Encrypt or other trusted certificates;
- ```admin@blynk.cc:admin``` admin credentials to your server. This is default ones. Format is ```username:password```. You can change it in ```server.properties``` file;
- ```token``` is token of your hardware you want apply the firmware update to. The firmware update will be initiated only in case device is online;
## Trigger OTA for all devices
Update for all devices will be triggered only when they are connected to the cloud. You need to remove the token part for that.
```
curl -v -F file=@Template_ESP8266.ino.nodemcu.bin --insecure -u admin@blynk.cc:admin https://localhost:9443/admin/ota/start
```
In that case, OTA will be triggered right after device connected to the server. In case device is online firmware update
will be initiated only when device will be connected again.
## Trigger OTA for the specific user
In that case firmware update will be triggered for all devices of specified user.
```
curl -v -F file=@Template_ESP8266.ino.nodemcu.bin --insecure -u admin@blynk.cc:admin https://localhost:9443/admin/ota/start?user=pupkin@gmail.com
```
## Trigger OTA for specific user and project
In that case firmware update will be triggered for all devices of specified user within specified project.
```
curl -v -F file=@Template_ESP8266.ino.nodemcu.bin --insecure -u admin@blynk.cc:admin https://localhost:9443/admin/ota/start?user=pupkin@gmail.com&project=123
```
## Stop OTA
```
curl -v --insecure -u admin@blynk.cc:admin https://localhost:9443/admin/ota/stop
```
## How to make firmware
In order to make firmware in Arduino IDE - go to menu: Sketch -> Export compiled Binary.
*NOTE:* ESP8266 right now takes firmware only via HTTP. And not HTTPS.
================================================
FILE: README.md
================================================
# This documentation is no longer maintained and supported. Latest documentation is available here: https://docs.blynk.io
Blynk IoT Platform is a white-label, multi-tenant software solution that allows you to build personal and commercial IoT projects connected products.
With Blynk you can start with building a prototype or personal project and then scale it up to millions of commercial connected devices.
Blynk platform allows you to connect almost any electronics hardware to the Internet, start collectind data from devices, monitor and control them remotely from anywhere in the world
Data from devices can be stored, aggregated, and visualized in easy-to-build mobile and web applications.
Blynk is a real-time system where you can create outstanding experience for your end-customers and perform complex analytics
The four major components of the Blynk IoT Platform are:
* **Blynk.Cloud**
* **Blynk.Edgent**
* **Blynk.app**
* **Blynk.Console**
================================================
FILE: Roadmap.md
================================================
#Roadmap
We build Blynk based on Blynkers feedback but with limited resources we have to prioritize our features. At the moment list look like that:
- App Sharing (project sharing when other people can control your hardware, but can't modify your project); Free Beta
- App Sharing (project sharing when other people can control your hardware, but can't modify your project); Subscription based
- Bluetooth Low Energy support;
- Hardware state handling (changing physical button state changes Blynk application state);
- Hardware online/offlane state improvements (better indication for "is hardware online?", "is hardware offline?");
- Project space increase
- Direct Connect support (for WiFi);
- RTC widget;
- Design options for widgets (size, button with icons, etc);
- Phone sensors widgets (GPS, accelerometer);
- IP camera support;
- Customizable look and feel of the project
Under consideration:
- Home screen widget (to avoid opening App when you need only 1 button click);
- Haptic feedback (vibration) when touching widgets
================================================
FILE: SUMMARY.md
================================================
# Table of contents
* [What is Blynk](README.md)
## overview
* [Blynk Components](overview/blynk-components.md)
## Product <a id="en-product"></a>
* [What is a Product](en-product/create-new-product.md)
* [General Settings](en-product/general-settings/README.md)
* [Manufacturer](en-product/general-settings/manufacturer.md)
* [Offline Ignore Period](en-product/general-settings/offline-ignore-period.md)
* [Metadata](en-product/metadata.md)
* [Datastreams](en-product/datastreams/README.md)
* [Datastream Name](en-product/datastreams/datastream-name.md)
* [Decimals Formatting](en-product/datastreams/decimals-formatting.md)
* [Wait for confirmation from the device](en-product/datastreams/wait-for-confirmation-from-the-device.md)
* [Default Value](en-product/datastreams/default-value.md)
* [Expose to Automation](en-product/datastreams/expose-to-automation.md)
* [Sync with the latest server value](en-product/datastreams/sync-with-the-latest-server-value.md)
* [Datastream: Alias](en-product/datastreams/datastream-alias.md)
* [Datastream: Invalidate Value](en-product/datastreams/datastream-invalidate-value.md)
* [Datastream: Min/Max values](en-product/datastreams/datastream-min-max-values.md)
* [Datastream: Data Type](en-product/datastreams/datastream-data-type.md)
* [Datastream: Virtual Pin](en-product/datastreams/datastream-virtual-pin.md)
* [Datastream: Save Raw Data](en-product/datastreams/datastream-save-raw-data.md)
* [Events](en-product/events/README.md)
* [Events: Notification](en-product/events/events-notification.md)
* [Events: Code](en-product/events/events-code.md)
* [Events: Name](en-product/events/events-name.md)
* [System Events](en-product/events/events-online-offline.md)
* [Events: Notifications Limit](en-product/events/events-notification-period.md)
* [Web Dashboard](en-product/web-dashboard.md)
* [Mobile app UI](en-product/mobile-app-ui.md)
## Firmware API <a id="firmware-api-1"></a>
* [Disable Widgets in the App](firmware-api-1/disable-widgets-in-the-app.md)
## REST API <a id="https-api"></a>
* [Devices](https-api/external_api.md)
* [Events](https-api/events-api.md)
## Mobile App
* [Untitled](mobile-app/untitled.md)
================================================
FILE: Security.md
================================================
#Security
Blynk server has 5 ports open for different security levels.
* **80** - plain TCP connection for the hardware (no security)
* **8080** - plain TCP connection for hardware (no security)
* **443** - SSL/TLS connection for the Mobile Apps and hardware with SSL
* **9443** - SSL/TLS connection for the Mobile Apps and hardware with SSL
Hardware may select to connect to 443 (9443) or 80 (8080), depending on it's capabilities.
Connection between the app and the server is always is done through SSL/TLS, so it is always secured.
Connection between the hardware and server depends on your hardware capabilities.
## Use Local Blynk Server
Local Blynk Server is no longer supported.
## Use SSL gateway
Most platforms are not capable to handle SSL, so they connect to 80.
However, our [gateway script](https://github.com/blynkkk/blynk-library/blob/master/scripts/blynk-ser.sh) can be used to add SSL security layer to communication.
```bash
./blynk-ser.sh -f SSL
```
This will forward all hardware connections from 9443 port to the server via SSL gateway.
You can run this script on your Raspberry Pi, desktop computer, or even directly on your router!
**Note:** when using your own server, you should overwrite the bundled server.crt certificate, or specify it to the script using ```--cert``` switch:
```bash
./blynk-ser.sh -f SSL -s <server ip> -p 9443 --cert=<certificate>.crt
```
Flag ```-f SSL``` is enabled by default for USB communication so you don't have to explicit declare it.
**Note:** SSL is supported by the gateway only on Linux/OSX for now
If you want to skip SSL, and connect to TCP, you can also do that:
```bash
./blynk-ser.sh -t TCP
```
================================================
FILE: Sharing.md
================================================
#Sharing
Blynk offers two types of sharing your projects with other people:
- **Share access to your hardware.** Think about giving someone an App for your Project. They can't modify, but can control and see what's there.
- **Share your Project configuration.** Others will get a clone of your project by scanning a given QR link, but they won't be able to control your hardware. It's great for tutorials, instructables, etc.
## Shared access to your hardware
Imagine giving someone an App to control your Project.
- people you’ve shared your project with can’t modify anything. They can only use it
- you can update your app, change the layout, add widgets and it’s immediately synced to everyone
- you can revoke access at any moment
How it works:
- you send the QR code to your users (you can email, print, post to social media, do whatever you want)
- others download Blynk app, scan the QR code and your app opens for them ready to use. They don’t even need to login or create an account.
Go to your Project's Settings:
<img src="images/dash_settings_sharing.png" style="width: 200px; height:360px"/>
Click on "Generate Link" button :
<img src="images/dash_settings_sharing_generate.png" style="width: 200px; height:360px"/>
It will generate QR code you can share with others:
<img src="images/dash_public_sharing.png" style="width: 200px; height:360px"/>
That's it! Now **Exit the settings and press PLAY button.**
Another person would need to install Blynk app and scan QR code from the login screen (scanning from existing profile is not yet supported) ;
<img src="images/scan_qr.png" style="width: 200px; height:360px"/>
**NOTE:** Your Project should be active, don't forget to press Play button.
**WARNING:** Sharing costs 1000 energy and this energy is not recoverable even you didn't use sharing at all.
## Share your Project configuration
In case you want to share your Project's set up without giving access to your hardware (for example to make a tutorial or instructable)- follow the steps:
In Project's Settings go to **Clone** button.
<img src="images/clone.png" style="width: 200px; height:360px"/>
It will generate QR code you can share with anyone.
<img src="images/QR.png" style="width: 200px; height:360px"/>
Another person **should Log In to Blynk app** and press QR button in Projects gallery
<img src="images/QR_button_edit.png" style="width: 200px; height:360px"/>
After the scan, a new Project will be created, all the widgets, settings, layout will be cloned. Another person would need enough Energy Balance to clone your Project.
**Auth Token will be different!**. Nobody will get access to your hardware. They just get a copy of the layout and settings.
================================================
FILE: SupportedHardware.md
================================================
# Supported Hardware
**Attention!** This documentation is for the LEGACY version of Blynk platform which is no longer supported.
Please check out the [**new documentation**](https://docs.blynk.io)
Blynk supports more than 400 boards already, including support for Arduino, Particle, ARM mbed, TI Energia, MicroPython, Node.js, OpenWRT and many Single Board Computers. You can add your own connection types easily (see [these](https://github.com/blynkkk/blynk-library/tree/master/examples/More/ArduinoClient) examples for Arduino)!
## Platforms
- **Arduino** (https://github.com/blynkkk/blynk-library)
- Arduino MKR WiFi 1010
- Arduino MKR GSM 1400
- Arduino MKR NB 1500
- Arduino Uno, Duemilanove
- Arduino Nano, Mini, Pro Mini, Pro Micro, Due, Mega
- Arduino 101 (Intel Curie, with BLE)
- Arduino MKR1000
- Arduino Zero
- Arduino Yún (onboard WiFi and Ethernet, via Bridge)
- Arduino.org UNO WiFi
- Arduino MKR VIDOR 4000 (use the example for MKR WiFi 1010)
- Arduino UNO WiFi Rev.2 (use the example for MKR WiFi 1010)
- **Arduino-like**
- Blynk Board
- ESP8266 (Generic, NodeMCU, Witty Cloud, Huzzah, WeMos D1, Seeed Wio Link, etc.)
- ESP32 (WiFi, BLE)
- Nordic nRF51/nRF52 - based boards
- Teensy 3.2/3.1
- Blue Pill (STM32F103C)
- Realtek RTL8710 / Ameba via [RTLduino](https://github.com/pvvx/RtlDuino)
- BBC micro:bit
- LightBlue Bean *, soon*
- DFRobot Bluno
- RedBear Duo (WiFi, BLE)
- RedBearLab Blend Micro
- RedBearLab BLE Nano (v1 and v2)
- Seeed Tiny BLE
- Simblee BLE
- RFduino BLE
- The AirBoard (BLE-Link, RN-XV)
- Feather M0 WiFi
- Feather 32u4 BLE
- Intel Edison
- Intel Galileo
- Fishino Guppy, Uno, Mega
- TinyCircuits TinyDuino (CC3000)
- Microduino/mCookie Core, Core+, CoreUSB
- Wicked WildFire V2, V3, V4
- Digistump Oak
- chipKIT Uno32
- Alorium XLR8 (FPGA)
- LinkIt ONE (WiFi only)
- **Energia**
- Texas Instruments
- CC3220SF-LaunchXL
- CC3200-LaunchXL
- Tiva C Connected LaunchPad
- Stellaris LM4F120 LaunchPad
- MSP430F5529 + CC3100
- LaunchPad MSP432
- RedBearLab (CC3200, WiFi Mini)
- **Particle** https://github.com/vshymanskyy/blynk-library-spark)
- Core
- Photon
- Electron
- RPi
- SparkFun RedBoard
- RedBear Duo (WiFi & BLE)
- **ARM mbed** (https://developer.mbed.org/users/vshymanskyy/code/Blynk/)
- Seeed Tiny BLE
- RedBearLab BLE Nano
- BBC micro:bit
- STM32 Nucleo + Wiznet 5100 *, soon*
- **JavaScript** (Node.js, Espruino, Browsers) (https://www.npmjs.com/package/blynk-library)
- Regular PC with Linux / Windows / OS X
- Raspberry Pi (Banana Pi, Orange Pi, ...)
- BeagleBone Black
- Onion Omega
- Onion Omega 2
- Intel Galileo
- Intel Edison
- Intel Joule
- LeMaker Guitar
- LeMaker Banana Pro
- Samsung ARTIK 5
- PandaBoard, CubieBoard, pcDuino, Tessel 2
- VoCore, VoCore2 (OpenWRT + [Espruino package](https://github.com/vshymanskyy/OpenWRT-Espruino-packages))
- Espruino Pico
- ...
- **Python** (https://github.com/vshymanskyy/blynk-library-python)
- MicroPython
- Python 2
- Python 3
- **Lua** (https://github.com/blezek/blynk-esp)
- NodeMCU
## Arduino connection types
- USB (Serial), connected to your laptop or desktop
- **Ethernet**
- Arduino MKR ETH
- Arduino Ethernet Shield (W5100)
- Arduino Ethernet Shield 2 (W5500)
- SeeedStudio Ethernet Shield V2.0 (W5200)
- ENC28J60-based modules
- **WiFi**
- ESP8266 as WiFi modem (running original firmware)
- Arduino WiFi 101 Shield
- Arduino WiFi Shield
- WIZnet WizFi310
- Adafruit CC3000 WiFi Breakout / Shield
- RN-XV WiFly
- **Bluetooth Smart (BLE 4.0)**
- HM-10, HC-08
- DFRobot BLE-Link module
- Microduino/mCookie BLE
- RedBearLab BLE Mini
- nRF8001-based boards (Adafruit Bluefruit LE, etc.)
- **Bluetooth 2.0 Serial Port Profile (SPP)**
- HC-05, HC-06, ...
- **Cellular (GSM/3G/LTE)**
- SIMCom SIM800 series (SIM800A, SIM800C, SIM800L, SIM800H, SIM808, SIM868)
- SIMCom SIM900 series (SIM900A, SIM900D, SIM908, SIM968)
- A6/A7
- M590
- BG96
- GPRSbee
- Microduino GSM
- Adafruit FONA (Mini Cellular GSM Breakout)
- Adafruit FONA 800/808 Shield
## Made by Community
- [Marvell® EZ-Connect™ MW300/MW302](https://github.com/vshymanskyy/blynk-library-ez-connect)
- [WIZnet-W5500-EVB](http://instructables.com/id/WIZnet-W5500-EVB-and-Blynk-App-communication)
- [LabVIEW](https://github.com/juncaofish/NI-LabVIEWInterfaceforBlynk)
- [Node-RED](https://github.com/gablau/node-red-contrib-blynk-ws) (can be used as bridge to HTTP, TCP, UDP, MQTT, XMPP, IRC, OSC...)
## Problematic Boards
These boards are not supported and do not work out of the box:
- [Arduino Tian](http://www.arduino.org/products/boards/arduino-tian)
Here is a list of [**known library issues**](https://github.com/blynkkk/blynk-library/issues?q=is%3Aissue+label%3A"for+reference"+)
================================================
FILE: Troubleshooting.md
================================================
# Troubleshooting
## Connection
If you experience connection problems, follow these steps:
1. Check that your hardware, wires, cables and power supply are good quality, not harmed or damaged, etc.
Use high power USB cables and USB ports.
2. Check your wiring using the examples (TCP/HTTP Client or similar) **provided with your shield and hardware**.
* Once you understand how to manage connection, it's much easier to use Blynk.
3. Try running command ```telnet blynk-cloud.com 80``` from your PC, connected to the same network as your hardware.
You should see something like: ```Connected to blynk-cloud.com.```.
4. Try running Blynk default examples for your platform **without modifications** to see if it is working.
* Double-check that you have selected **the right example** for your connection type and hardware model.
* Our examples come with **comments and explanations**. **Read them carefully.**
* Check that your Auth Token is valid (copied from the App and **doesn't contain spaces, etc.**)
* If it doesn't work, try looking into [serial debug prints](/#enable-debug).
5. Done! Add your modifications and functionality. Enjoy Blynk!
***Note:*** when you have multiple devices connected to your network, they should all have different MAC and IP addresses. For example, when using 2 Arduino UNO with Ethernet shields, flashing default example to both of them will cause connection problems. You should use [manual ethernet configuration](https://github.com/blynkkk/blynk-library/blob/master/examples/Boards_Ethernet/Arduino_Ethernet_Manual/Arduino_Ethernet_Manual.ino) example.
## WiFi network connection
If you encounter WiFi connection problems, please check these pitfalls:
* You're trying to connect to "WPA & WPA2 Enterprise" network (often used in offices), and your shield does not support this security method
* Your WiFi network has a login page that requests entering an access token (often used in restaurants)
* Your WiFi network security disallows connecting alien devices completely (MAC filtering, etc)
* There is a firewall running. Default port for hardware connections is 80 (8080 on the Local Server).
Make sure it's open.
## Delay
If you use long ```delay()``` or send your hardware to sleep inside of the ```loop()``` expect connection drops and downgraded performance.
***DON'T DO THAT:***
```cpp
void loop()
{
...
delay(1000); // this is long delay, that should be avoided
other_long_operation();
...
Blynk.run();
}
```
***Note:*** This also applies to the BLYNK_READ & BLYNK_WRITE handlers!
***SOLUTION:***
If you need to perform actions in time intervals - use timers, for example [BlynkTimer](/#blynk-firmware-blynktimer).
## Flood Error
If your code frequently sends a lot of requests to our server, your hardware will be disconnected. Blynk App may show "Your hardware is offline"
When ```Blynk.virtualWrite``` is in the ```void loop```, it generates hundreds of "writes" per second
Here is an example of what may cause flood. ***DON'T DO THAT:***
```cpp
void loop()
{
Blynk.virtualWrite(1, value); // This line sends hundreds of messages to Blynk server
Blynk.run();
}
```
***SOLUTION:***
If you need to perform actions in time intervals - use timers, for example [BlynkTimer](/#blynk-firmware-blynktimer).
Using ```delay()``` will not solve the problem either. It may cause [another issue](/#delay). Use timers!
If sending hundreds of requests is what you need for your product you may increase flood limit on local server
and within Blynk library.
For local server you need to change ```user.message.quota.limit``` property within ```server.properties``` file :
#100 Req/sec rate limit per user.
user.message.quota.limit=100
For library you need to change ```BLYNK_MSG_LIMIT``` property within ```BlynkConfig.h``` file :
//Limit the amount of outgoing commands.
#define BLYNK_MSG_LIMIT 20
## Enable debug
To enable debug prints on the default Serial, add this on the top of your sketch **(it should be the first line
in your sketch)**:
```cpp
#define BLYNK_DEBUG // Optional, this enables lots of prints
#define BLYNK_PRINT Serial
```
And enable serial in ```void setup()```:
```cpp
Serial.begin(9600);
```
You can also use spare Hardware serial ports or SoftwareSerial for debug output (you will need an adapter to connect to it with your PC).
***Note:*** enabling debug mode will slow down your hardware processing speed up to 10 times.
## Geo DNS problem
Geo DNS issue is no longer a problem. It was solved in 2017.
## Reset password
On login screen click on "Forgot password?" label and than type your email and ```Send``` button.
You'll get instruction on your email.
### Android reset password flow
1. Open instruction email **from your smartphone or tablet**;
2. Click on "Reset now" button in your email;
3. Click on Blynk icon in below popup and reset the pass:
<img src="images/reset.png"/>
================================================
FILE: Widgets-RU.md
================================================
<h2 class="banner-header"> 🚨🚨🚨 ВАЖНО:</h2>
<p class="banner">
Эта документация предназначена для УСТАРЕВШЕЙ версии платформы Blynk, которая больше не поддерживается и будет закрыта.<br/>
Вы можете зарегистрироваться в текущей версии платформы Blynk <a href="http://blynk.cloud/dashboard/register">здесь</a>.<br/>
Новые мобильные приложения можно скачать с <a href="https://apps.apple.com/us/app/blynk-iot/id1559317868">App Store</a> и <a href="https://play.google.com/store/apps/details?id=cloud.blynk&hl=en&gl=US">Google Play</a>.<br/>
Текущая документация Blynk <a href="https://docs.blynk.io/">здесь</a>.
</p>
#Widgets
Widgets are interface modules. Each of them performs a specific input/ output function when communicating with the hardware.
There are 4 types of Widgets:
- **Controllers** - used to send commands that control your hardware
- **Displays** - used for data visualization from sensors and other sources;
- **Notifications** - send messages and notifications;
- **Interface** - widgets to perform certain GUI functions;
- **Other** - widgets that don't belong to any category;
Each Widget has it's own settings. Some of the Widgets (e.g. Bridge) just enable functionality and they don't have any settings.
## Common Widget Settings
### Pin Selector
This is one of the main parameters you need to set. It defines which pin to control or to read from.
<img src="images/pin_selection.png" style="width: 200px; height:360px"/>
**Digital Pins** - represent physical Digital IO pins on your hardware. PWM-enabled pins are marked with the ```~``` symbol
**Analog Pins** - represent physical Analog IO pins on your hardware
**Virtual Pins** - have no physical representation. They are used to transfer any data between Blynk App and your hardware.
Read more about Virtual Pins [here](/#blynk-main-operations-virtual-pins).
### Data Mapping
In case you want to map incoming values to specific range you may use mapping button:
<img src="images/display_edit_mapping.png" style="width: 200px; height:360px"/>
Let's say your sensor sends values from 0 to 1023. But you want to display values in a range 0 to 100 in the app.
When Data Mapping enabled, incoming value 1023 will be mapped to 100.
### SPLIT/MERGE
Some of the Widgets can send more than one value. And with this switch you can control how to send them.
- **SPLIT**:
Each of the parameters is sent directly to the Pin on your hardware (e.g D7). You don't need to write any code.
**NOTE:** In this mode you send multiple commands from one widget, which can reduce performance of your hardware.
Example: If you have a Joystick Widget and it's set to D3 and D4, it will send 2 commands over the Internet:
```cpp
digitalWrite(3, value);
digitalWrite(4, value);
```
- **MERGE:**
When MERGE mode is selected, you are sending just 1 message, consisting of array of values. But you'll need to parse it on the hardware.
This mode can be used with Virtual Pins only.
Example: Add a zeRGBa Widget and set it to MERGE mode. Choose Virtual Pin V1
```cpp
BLYNK_WRITE(V1) // There is a Widget that WRITEs data to V1
{
int r = param[0].asInt(); // get a RED channel value
int g = param[1].asInt(); // get a GREEN channel value
int b = param[2].asInt(); // get a BLUE channel value
}
```
### Decimals
Defines how many decimals you would like to see when moving a Slider.
When "No Fraction" is chosen, slider will only send integer values with no decimals.
"1 digit" means that values will look like 1.1, 1.2, ..., 2.0, etc.
### Send On Release
This option allows you to optimize data traffic on your hardware.
For example, when you move joystick widget, commands are streamed to the hardware, during a single joystick move
you can send dozens of commands. There are use-cases where it's needed, however creating such a load may lead to hardware overload and reset.
**Send On Release** is a recommended setting for majority of applications. This is also a default setting.
### Write interval
Similar to "Send on Release" option. However, it allows you to stream values to your hardware within certain interval. For example, setting **write interval** to 100 ms means that while you move the slider, only 1 value will be sent to hardware within 100 ms period.
This option is also used to optimize data traffic flow to your hardware.
### Color gradient
When you choose gradient, it affects the color of widget elements based on invoming values.
For example: You set Gauge Widget with Min and Max parameters of 0-100, and choose green-yellow-red gradient. When hardware sends:
- `10`, Gauge will change it's color to green color
- `50` will change Gauge to yellow color
- `80` will change Gauge to red color
There are 2 types of gradients you can choose from:
- Warm: Green - Orange - Red;
- Cold: Green - Blue - Violet;
##Controllers
### Кнопка (Button)
Кнопка может работать в двух режимах - в режиме переключателя (нажатие и отжатие посылает 1 сообщение) и в пуш режиме
(нажатие посылает команду и отжатие посылает команду). Кнопка позволяет послать любое число. По умолчанию кнопка шлет
0/1 (LOW/HIGH). В пуш режиме кнопка шлет 1 (HIGH) на нажатие и 0 (LOW) при отжатии.
Вы так же можете менять состояние кнопки с микроконтроллера. Например, включить кнопку на пине V1 можно так :
```cpp
Blynk.virtualWrite(V1, HIGH);
```
Так же можно поменять тексты в кнопке :
```cpp
Blynk.setProperty(V1, "onLabel", "Вкл");
```
```cpp
Blynk.setProperty(V1, "offLabel", "Выкл");
```
Название самой кнопки :
```cpp
Blynk.setProperty(V1, "label", "Моя кнопочка");
```
Или изменить ее цвет :
```cpp
//#D3435C - Blynk RED
Blynk.setProperty(V1, "color", "#D3435C");
```
В случае если микроконтроллер был перегружен, Вы всегда можете получить последнее состояние кнопки с сервера с помощью
фичи синхронизации состояния:
```cpp
//как только подключились
BLYNK_CONNECTED() {
//запросить информацию у сервера о состоянии пина V1
Blynk.syncVirtual(V1);
}
//этот метод будет вызыван после ответа сервера
BLYNK_WRITE(V1) {
int buttonState = param.asInt();
}
```
#### Кнопка на рабочем столе
Если Вы используете Android, то Вы можете добавить Blynk кнопку на рабочий стол. В этом случае кнопка будет работать по
протоколу HTTPS. Такого рода кнопки имеют определенные ограничения по функционалу в связи с ограничениями платформы Android.
Например, Вы не можете получить мгновенную синхронизацию состояния кнопки на рабочем столе с состоянием на микроконтроллере. Так как состояние кнопки на рабочем столе обновляется раз в 15 мин.
**Замечание:** Добавление виджета кнопки на рабочий стол стоит 100 энергии. Эта энергия не возвращается после удаления виджета.
Также такая кнопка будет работать на локальном сервере только если открыть порт 8080.
**Пример кода:** [Базовый пример](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
**Пример кода:** [Синхронизация состояния с физической кнопкой через прерывания](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/ButtonInterrupt/ButtonInterrupt.ino)
**Пример кода:** [Синхронизация состояния с физической кнопкой через поллинг](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/ButtonPoll/ButtonPoll.ino)
**Пример кода:** [Синхронизация состояния с физической кнопкой](https://github.com/blynkkk/blynk-library/blob/master/examples/More/Sync/SyncPhysicalButton/SyncPhysicalButton.ino)
### Слайдер (Slider)
Слайдер очень похож на потенциометр. Он позволяет посылать значения в диапазоне от минимального значения к максимальному.
Диапазон допустимых максимального и минимального значений определяется в приложении.
Вы так же можете менять состояние слайдера с микроконтроллера. Например, Вы можете изменить положение ползунка в слайдере :
```cpp
Blynk.virtualWrite(V1, 55);
```
Так же можно поменять текст в слайдере :
```cpp
Blynk.setProperty(V1, "label", "Мой слайдерок");
```
или изменить цвет :
```cpp
//#D3435C - Карсный цвет в кодирвке RGB
Blynk.setProperty(V1, "color", "#D3435C");
```
### Таймер (Timer)
Таймер запускает действия в определенное время. Даже если смартфон не в сети. По умолчанию время начала отправляет 1 (HIGH), время остановки отправляет 0 (LOW). Вы можете изменить это поведение на любые другие значения.
Вы можете изменить настройки Таймера в режиме «Запуска».
В последней версии Android также есть улучшенный таймер в виджете [Обработчик событий](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/eventor.md).
C [Обработчиком](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/eventor.md) событий вы можете назначить несколько таймеров на один и тот же пин, отправить любую строку/число, выбирать дни и часовой пояс.
Рекомендуется использовать виджет [Обработчик событий](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/eventor.md) поверх виджета Таймер.
Однако виджет Таймер по-прежнему подходит и для простых событий таймера.
**ПРИМЕЧАНИЕ:** Виджет таймера зависит от времени сервера, а не вашего телефона. Иногда время телефона может не соответствовать времени сервера.
**Пример кода:** [Таймер](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Timer/Timer.ino)
### Джойстик (Joystick)
Управление сервоприводом в 4 направлениях.
#### Параметры:
- **Раздельный** (SPLIT):
Каждый из параметров отправляется непосредственно на пин вашего оборудования (например, D7 и D8). Вам не нужно писать код.
**ПРИМЕЧАНИЕ:** В этом режиме вы отправляете несколько команд из одного виджета, что может снизить производительность вашего оборудования.
**Пример:** Если у вас есть виджет Джойстика и он настроен на D3 и D4, он отправит две команды через Интернет:
```cpp
digitalWrite(3, x);
digitalWrite(4, y);
```
- **Совмещенный** (MERGE):
Когда выбран режим MERGE, вы отправляете только 1 сообщение, состоящее из массива значений. Но вам нужно разобрать его на оборудовании устройства.
Этот режим можно использовать только с виртуальными пин-ами.
**Пример:** добавьте виджет Джойстика и установите его в режим "MERGE". Выберите виртуальный пин V1
```cpp
BLYNK_WRITE(V1) // Joystick assigned to V1
{
// получить x
int x = param[0].asInt();
// получить y
int y = param[1].asInt();
}
```
- **Поворт/Наклон** (Rotate on Tilt)
Когда это параметр включен, Джойстик будет автоматически вращаться, если вы будете использовать смартфон в горизонтальной положении.
- **Автовозврат** (Auto-Return)
Когда это парамтер выключен, ручка джойстика не вернется в центральное положение. Она останется там, где вы ее оставили.
### Отправка при Отжатии (Send On Release)
**Send On Release** доступно для большинства виджетов контроллеров и позволяет уменьшить трафик данных на ваше оборудование. Например, когда вы перемещаете виджет джойстика, команды непрерывно передаются на аппаратное устройство, во время одного движения джойстика вы можете отправлять десятки команд. Есть случаи, когда это необходимо, однако создание такой нагрузки может привести к зависанию или сбросу оборудования. Мы рекомендуем включить функцию **Send On Release** для большинства случаев, если вам не требуется мгновенная обратная связь. Эта опция включена по умолчанию.
### Интервал записи (Write interval)
Похоже на вышеуказанный вариант. Однако, позволяет вам передавать значения на ваше оборудование в через определенные интервалы времени. Например, установка интервала записи на 100 мс означает, что при перемещении ползунка на аппаратное обеспечение будет отправлено только 1 значение в течение 100 мс. Эта опция также используется для уменьшения трафика данных на ваше оборудовании.
**Пример кода:** [Джойстик две оси](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/JoystickTwoAxis/JoystickTwoAxis.ino)
### Шаговое управление (Step Control)
Шаговое управление похоже на две кнопки, назначенные одному пин-у. Одна кнопка увеличивает ваше значение на установленный шаг, а другая уменьшает его. Это очень полезно для случаев использования, когда вам нужно точно изменять ваши значения, но вы не можете достичь такой точности с помощью виджета [Cлайдера](https://github.com/blynkkk/blynkkk.github.io/tree/master/mobile/ru/slider.md).
**Отправить шаг (Send Step)** опция позволяет вам отправлять на оборудование каждый шаг нвместо фактического значения виджета.
**Зациклить значения (Loop value)** опция позволяет сбросить Шаговый виджет на начальное значение при достижении максимального.
Вы можете изменить значение Шагового виджета со стороны оборудования. Например:
```cpp
Blynk.virtualWrite(V1, val);
```
Вы можете изменить описание виджета со стороны оборудования с помощью кода:
```cpp
Blynk.setProperty(V1, "label", "Мой счетчик.");
```
Вы можете изменить шаг виджета со стороны оборудования:
```cpp
Blynk.setProperty(V1, "step", 10);
```
или изменить цвет:
```cpp
//#D3435C - Красный цвет в RGB кодировке
Blynk.setProperty(V1, "color", "#D3435C");
```
Вы также можете получить состояние виджета Шагового управления с сервера в случае, если ваше оборудование отключилось, с помощью функции Blynk.Sync:
```cpp
BLYNK_CONNECTED() {
Blynk.syncVirtual(V1);
}
BLYNK_WRITE(V1) {
int stepperValue = param.asInt();
}
```
##Displays
### Отображение значений (Value Display)
Отображает входящие данные с ваших датчиков или виртуальных пин-ов.
Может работать в двух режимах:
- режим PUSH (выберается в списке выбора частоты считывания);
- режим частоты считываний;
В режиме PUSH вы обновляете значения виджета со стороны оборудования с помощью кода:
```cpp
Blynk.virtualWrite(V1, val);
```
В этом режиме каждое сообщение, которое отправляет аппаратное устройство автоматически сохраняется на сервере. Режим PUSH не требует, чтобы приложение было онлайн или открыто.
В режиме частоты считывния вам необходимо выбрать интервал обновления данных, и приложение будет запускать события считывния с требуемой периодичностью.
Ваше приложение должно быть открыто и запущено для отправки запросов на оборудование. Вам не нужен код для аналоговых и цифровых выводов в даном случае. Однако для виртуальных выводов вам необходимо использовать следующий код:
```cpp
//вызывать из приложения
BLYNK_READ(V1)
{
//отправить в приложение
Blynk.virtualWrite(V1, val);
}
```
#### Отображение значений на рабочем столе
Вы также можете добавить виджет отображение значения на рабочий стол Android. В этом случае отображение значений работает по протоколу HTTPS.
Имейте в виду, что в режиме «Рабочий стол» отображение значений имеет несколько ограничений. Виджет будет обновлять свое состояние только один раз в 15 минут. Вы можете изменить это органичение через настройки виджета. Однако интервал обновления менее 15 минут не гарантируется.
Вы также можете изменить размер отображаемого значения на рабочем столе - просто сделайте длинный тап на виджете и измените его размер на необходимый.
**Примечание:** Добавление виджета на главный экран стоит 100 энергии. Эта энергия не возвращяется при удалении виджета.
**Примечание:** Виджеты рабочего стола для локальных серверов Blynk требуют открытия порта 8080.
**Пример кода:** [Базовый пример](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### Интервал записи (Write interval)
Опция позволяет вам передавать значения на ваше оборудование в через определенные интервалы времени. Например, установка интервала записи на 100 мс означает, что при перемещении ползунка на аппаратное обеспечение будет отправлено только 1 значение в течение 100 мс. Эта опция также используется для уменьшения трафика данных на ваше оборудовании.
**Пример кода:** [Базовый пример](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### Светодиод (LED)
Простой светодиод для индикации. Вам нужно отправить 0, чтобы выключить светодиод. И 255 для того, чтобы включить светодиод.
Или просто используйте Blynk API, как описано ниже:
```cpp
//регистрируемся на виртуальном пине 1
WidgetLED led1(V1);
led1.off();
led1.on();
```
Все значения от 0 до 255 изменяют яркость светодиода:
```cpp
WidgetLED led2(V2);
//установить яркость светодиода на 50%.
led2.setValue(127);
```
Вы также можете изменить цвет светодиода с помощью кода:
```cpp
//#D3435C - Красный в RGB формате
Blynk.setProperty(V1, "color", "#D3435C");
```
#### Светодиод на рабочем столе
Вы можете добавить виджет светодиод на рабочий стол Android. В этом случае светодиод работает через протокол HTTPS. Имейте в виду, что в режиме «Рабочий стол» виджет светодиода имеет некоторые ограничения. Светодиод будет обновлять свое состояние только один раз в 15 минут. Вы можете изменить этот интервал через настройки виджета. Однако интервал обновления менее 15 минут не гарантируется.
**Примечание:** Добавление виджета на рабочий стол стоит 100 энергии. Эта энергия не возвращается при удалении виджета.
**Примечание:** Виджеты рабочего стола для локальных серверов Blynk требуют открыть порт 8080.
**Пример кода:** [Базовый пример](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LED/LED_Blink/LED_Blink.ino)
### Указатель (Gauge)
Отличный визуальный способ отображения входящих числовых значений.
Может работать в 2 режимах:
- режим PUSH (выберается в списке выбора частоты считывания);
- режим частоты считываний;
В режиме PUSH вы обновляете значения указателя со стороны оборудования с помощью кода:
```cpp
Blynk.virtualWrite(V1, val);
```
В этом режиме каждое сообщение, которое отправляет аппаратное устройство автоматически сохраняется на сервере. Режим PUSH не требует, чтобы приложение было онлайн или открыто.
В режиме частоты считывния вам необходимо выбрать интервал обновления данных, и приложение будет запускать события считывния с требуемым периодичностью.
Ваше приложение должно быть открыто и запущено для отправки запросов на оборудование. Вам не нужен код для аналоговых и цифровых выводов в даном случае. Однако для виртуальных выводов вам необходимо использовать следующий код:
```cpp
//вызывать из приложения
BLYNK_READ(V1)
{
//отправить в приложение
Blynk.virtualWrite(V1, val);
}
```
#### Параметры форматирования
Указатель также имеет поле «Label» (Метка), которое позволяет использовать форматирование.
Предположим, ваш датчик отправляет число 12.6789 в приложение Blynk.
Поддерживаются следующие параметры форматирования:
```/pin/``` - отображает значение без форматирования (12.6789)
```/pin./``` - отображает значение без десятичной части (13)
```/pin.#/``` - отображает значение с одним десятичным знаком (12.7)
```/pin.##/``` - отображает значение с двумя десятичными знаками (12.68)
#### Другие опции
Вы также можете изменить метку прибора с помощью:
```cpp
Blynk.setProperty(V1, "label", "Мое значение метки");
```
или изменить цвет (кодировка RGB):
```cpp
//#D3435C - Красный цвет
Blynk.setProperty(V1, "color", "#D3435C");
```
**Пример кода:** [Светодиод](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### ЖК дисплей (LCD)
Это обычный ЖК-дисплей 16x2, "сделанный" на нашем секретном предприятии в Китае.
Виджет может работать в двух режимах:
- Простой (Simple)
- Расширенный (Advanced)
#### Простой режим (Simple)
В простом режиме ваш ЖК-виджет работает как обычный виджет с частотой чтения.
В режиме частоты считывания вам нужно выбрать интервал обновления данных, и приложение будет запускать события с требуемым интервалом. Ваше приложение должно быть открыто и запущено для отправки запросов на оборудование. В данном случае вам не нужен код для аналоговых и цифровых пин-ов. Однако для виртуальных пин-ов вам необходимо использовать следующий код:
```cpp
//вызываем из приложения
BLYNK_READ(V1)
{
//отправляем в приложение
Blynk.virtualWrite(V1, val);
}
```
В простом режиме ЖК-дисплей также поддерживает параметры форматирования.
#### Параметры форматирования
Предположим, ваш датчик отправляет число 12.6789 в приложение Blynk.
Поддерживаются следующие параметры форматирования:
```/pin/``` - отображает значение без форматирования (12.6789)
```/pin./``` - отображает значение без десятичной части (13)
```/pin.#/``` - отображает значение с одним десятичным знаком (12.7)
```/pin.##/``` - отображает значение с двумя десятичными знаками (12.68)
**Пример кода:** [ЖК дисплей простой режим - PUSH](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_SimpleModePushing/LCD_SimpleModePushing.ino)
**Пример кода:** [ЖК дисплей простой режим - 1 сек](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_SimpleModeReading/LCD_SimpleModeReading.ino)
#### Расширенный режим (Advanced)
Расширенный режим предназначен для опытных пользователей. Позволяет использовать специальные команды для управления ЖК-дисплеем.
#### Команды
Инициируем переменную ЖК-дисплея:
```cpp
WidgetLCD lcd(V1);
```
Отправим сообщение:
```cpp
lcd.print(x, y, "Ваше сообщение");
```
Где ```x``` - позиция символа (0-15), ``` y``` - номер строки (0 или 1),
Очистка ЖК-дисплея:
```cpp
lcd.clear();
```
**Пример кода:** [ЖК-дисплей расширенный режим](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_AdvancedMode/LCD_AdvancedMode.ino)
### Диаграмма (SuperChart)
Диаграмма используется для живой визуализации и хранения данных. Вы можете использовать виджет для логирования данных датчиков, бинарных событий и многого другого.
Чтобы использовать виджет Диаграмма, вам нужно будет передать данные с оборудования с желаемым интервалом, используя таймеры.
[Здесь приведен](https://examples.blynk.cc/?board=ESP8266&shield=ESP8266%20WiFi&example=GettingStarted%2FPushData) базовый пример передачи данных.
#### Взаимодействие:
- **Переключение между режимами текущий и временной** Нажмите диапазоны времени в нижней части виджета, чтобы изменить масштаб Диаграммы по времени.
- **Тап по легенде графиков** показать или скрыть поток данных.
- **Долги тап на графике** покажет метку времени и соответствующие значения.
- **Быстро проведите пальцем влево или вправо, чтобы увидеть предыдущие данные** впоследствии вы можете прокручивать данные назад и вперед в пределах заданного временного диапазона.
- **Полноэкранный режим** нажмите эту кнопку, чтобы открыть полноэкранный режим в альбомной ориентации.
Чтобы выйти из режима полного экрана, просто поверните телефон обратно в портретный режим. График должен вращаться автоматически. В полноэкранном режиме вы увидите X (время) и несколько шкал Y.
Полноэкранный режим можно отключить в настройках виджета.
- **Кнопка меню**
Кнопка меню откроет дополнительные функции:
- Экспорт в CSV
- Стереть данные на сервере
#### Настройки диаграммы:
- **Заголовок диаграммы (Chart Title)** общее наименование диаграммы.
- **Размер шрифта заголовка (Title Font Size)** выберите из 3 размеров шрифта.
- **Выравнивание заголовка (Title Alignment)** выберите выравнивание заголовка диаграммы. Этот параметр влияет на положение заголовка и легенды в виджете.
- **Показать ось X (время) (Show x-axis (time))** выберите настройку, если хотите показать шкалу времени внизу графика.
- **Автоматическое масштабирование для всех потоков данных (Override Auto Scaling for All Datastreams)** отключение этой опции позволит выполнить ручную настройку для оси Y (см. ниже).
- **Выбор масштаба времени (Time ranges picker)** Позволяет выбрать необходимые периоды (`15m`,` 30m`, `1h`,` 3h`, ...) и разрешение для вашего графика. Разрешение определяет, насколько подробные ваши данные. Прямо сейчас график поддерживает два типа разрешения: `standard` и `high`. Разрешение также зависит от выбранного периода. Например, `standard` разрешение для `1d` означает, что вы будете получать 24 значения в день (одно в час), а при `high` разрешении вы будете получать за` 1d` 1440 значений в день (одно в минуту).
- **Потоки данных (Datastreams)** добавить потоки данных (см. ниже, как настроить потоки данных).
#### Настройки потоков данных
Виджет поддерживает до 4 потоков данных.
Нажмите значок настроек потоков данных, чтобы открыть настройки.
**Дизайн (Design)** выберите доступные типы диаграмм:
- Линейная (Line)
- С областями (Area)
- Гистограмма (Bar)
- Бинарная (Binary) (приведение данных к двоичному виду)
**Цвет (Color)** выберите сплошные цвета или градиенты.
**Источник и ввод (Source and input)** - Вы можете использовать три типа источника данных:
**1. Виртуальный пин (Virtual Pin)** - выберите желаемое устройство и виртуальный пин для получения данных.
**2. Теги (Tags)** - диаграмма может агрегировать данные с нескольких устройств, используя встроенные функции агрегирования.
Например, если у вас есть 10 датчиков температуры, посылающих температуру с заданным интервалом, Вы можете отобразить среднее значение от 10 датчиков в виджете.
Использование тегов:
- **[Добавить Тэг](http://docs.blynk.cc/#blynk-main-operations-control-of-multiple-devices-tags)** на каждое устройство, с которого вы хотите агрегировать данные. Это можно сделать в настройках проекта Blynk.
- **Отправить данные в виртуальный пин (Push data to the same Virtual Pin)** на каждое устройство. (т.е. ```Blynk.virtualWrite (V0, temperature);```)
- **Выберите тег в качестве источника (Choose Tag as a source)** в виджете Диаграмма и используйте пин, куда поступают данные (т.е. V0)
**Добступные функции:**
- `SUM` будет суммировать все входящие значения в указанный виртуальный пин со всех устройств, помеченные выбранным тегом
- `AVG` будет вычислять среднее значение
- `MED` найдет среднее значение
- `MIN` будет вычислять минимальное значение
- `MAX` будет вычислять максимальное значение
**ВАЖНО: Теги не работают в режиме реального времени.**
**3. [Выбор устройства (Device Selector)](https://github.com/blynkkk/blynkkk.github.io/tree/master/mobile/ru/ device_selector.md)**
Если вы добавите виджет Выбор устройства в свой проект, вы можете использовать его в качестве источника данных для Диаграммы.
В том случае, когда вы меняете устройство, диаграмма будет автоматически обновляться.
#### Настройки оси Y (Y-Axis Settings)
Cуществует 4 режима масштабирования данных вдоль оси Y, активируется после отключения общей настройки виджета "Автоматическое масштабирование для всех потоков данных (Override Auto Scaling for All Datastreams)".
**1. Авто (Auto)**
Данные будут автоматически масштабироваться на основе минимальных и максимальных значений заданного периода времени. Это лучший вариант для начинающих.
**2. Минимальный/Максимальный (Min/Max)**
Когда выбран этот режим, шкала Y будет установлена на выбранные вами границы значений.
Например, если ваше оборудование отправляет данные со значениями от -100 до 100, вы можете установить эти границы и данные графика будут отображены полностью.
Вы также можете визуализировать данные в другом диапазоне. Допустим, входящие данные имеют значения в диапазоне 0-55, но вы хотели бы видеть только значения в диапазоне 30-50. Вы можете настроить диапазон, но если значения не соответствуют заданному масштабу оси Y, диаграмма будет обрезана.
**3. Процент от высоты (% of Height)**
Эта опция позволяет автоматически масштабировать входящие данные на виджете и размещать их так, как вы хотите.
В этом режиме вы устанавливаете процент высоты виджета на экране от 0% до 100%.
Если вы установите диапазон 0-100%, это будет полная автоматическая шкала. Независимо от того, в каком диапазоне поступают данные, он всегда будет масштабирован по всей высоте виджета.
Если вы установите его на 0-25%, то график будет отображаться только на 1/4 высоты виджета.
Этот параметр очень полезен для **Бинарной диаграммы** или для визуализации нескольких потоков данных на одной и той же диаграмме разными способами.
**4. Дельта (Delta)**
Пока данные остаются в пределах заданного значения дельты, график будет автоматически масштабироваться в этом диапазоне.
Если дельта превышает диапазон, график автоматически масштабируется до минимальных/максимальных значений указанного периода.
**Суффикс (Suffix)**
Здесь вы можете указать суффикс, который будет отображаться со значениями во время длительного тап на графике.
**Разрядность (Decimals)**
Определяет формат числовых значений, когда вы нажимаете и удерживаете палец на графике. Возможные варианты: #, #.#, #.##, и т.д.
**Соединиить отсуствующие точки графика (Connect Missing Data Points)**
Если этот переключатель включен, то Диаграмма соединит все точки, даже если данные частично отсуствуют.
Если для него установлено значение «ВЫКЛ», то вы увидите пропуски в случае отсутствия данных.
**Настройки Бинарной диаграммы (Binary Chart Settings)**
Этот тип диаграммы полезен для построения двоичных данных, например, когда устройство было включено или выключено, или когда было обнаружено движение или когда был достигнут определенный порог значений.
Вам необходимо указать точку **Перехода (FLIP)**, которая будет точкой, в которой входящие данные будут принимать состояние `ИСТИНА (TRUE)` или `ЛОЖЬ (FALSE)`.
Например, вы отправляете данные в диапазоне от 0 до 1023. Если вы установите `512` в качестве точки **Перехода (FLIP)**, то все, что выше `512` (исключая 512), будет записано как `ИСТИНА (TRUE)`, любое значение ниже `512` (включая 512) будет `ЛОЖЬ (FALSE)`.
Другой пример: если вы отправляете `0 и 1` и устанавливаете `0` в качестве точки **Перехода FLIP**, то `1` будет `ИСТИНА`, а `0` будет `ЛОЖЬ`.
**Маркеры состояния (State Labels):**
Здесь вы можете указать, как `ИСТИНА/ЛОЖЬ` должны отображаться на графике когда вы нажимаете и удерживаете палец.
Например, вы можете установить значение `ИСТИНА` как `Оборудование ВКЛ`, `ЛОЖЬ` как `Оборудование ВЫКЛ`.
### Видео трансляция (Video Streaming)
Простой виджет, который позволяет отображать прямой эфир и потокове видео. Виджет поддерживает протоколы RTSP (RP, SDP), HTTP/S прогрессивной потоковой передачи, HTTP/S прямого эфира. Для получения дополнительной информации, пожалуйста ознакомтесь с [официальной документацией Android](https://developer.android.com/guide/appendix/media-formats.html).
На данный момент команда Blynk не предоставляет потоковые серверы. Таким образом, вы можете осуществлять потоковую передачу непосредственно с ваше камеры или использовать сторонние сервисы, а также запустить собственны потоковый сервер (например, на оборудовании Raspberry).
Вы можете остановить/запустить видео поток, нажав на сам виджет.
Вы можете изменить URL-адрес видео потока с аппаратного устройства при помощи кода:
```cpp
Blynk.setProperty(V1, "url", "http://my_new_video_url");
```
### Индикатор уровня (Level Display)
Отображает входящие данные с ваших датчиков или виртуальных пин-ов. Отображение уровня очень похоже на индикатор выполнения процесса, это очень красивый и причудливый вид для индикации «выполненных» событий, например «уровня заряда батареи».
Вы можете обновить отображение значения с аппаратной стороны с помощью кода:
```cpp
Blynk.virtualWrite(V1, val);
```
Каждое сообщение, которое аппаратное устройство отправляет на сервер, автоматически сохраняется на сервере.
Режим PUSH не требует, чтобы приложение было онлайн или запущено.
**Пример кода:** [Пример PUSH](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushData/PushData.ino)
## Interface
### Вкладки (Tabs)
Единственная цель виджета Вкладки - расширить пространство вашего проекта.
Чтобы редактировать виджет Вкладок - просто нажмите на выбранную вкладку.
Вы можете перетаскивать виджеты между вкладками.
Из списка можно удалить только последнюю вкладку: чтобы удалить ее, проведите пальцем влево по ее названию в экране настроек виджета.
Максимальное количество вкладок на iOS составляет 4.
Максимальное количество вкладок на Android - 10.
Оставайтесь с нами для предстоящего редизайна виджета вкладок!
### Меню (Menu)
Виджет Меню позволяет отправлять команды на ваше оборудование на основе выборного списка, сделанного вами в пользовательском интерфейсе. Меню отправляет индекс выбранного элемента спика, а не саму строку. Отправляемый индекс начинается с 1. Он работает так же, как типовой элемент "Комбинированный список" ([ComboBox](https://ru.wikipedia.org/wiki/%D0%9A%D0%BE%D0%BC%D0%B1%D0%B8%D0%BD%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%BD%D1%8B%D0%B9_%D1%81%D0%BF%D0%B8%D1%81%D0%BE%D0%BA)).
Пример кода:
```cpp
BLYNK_WRITE {
switch (param.asInt()) {
case 1: { // Пункт 1
Serial.println("Выбран Пункт 1");
break;
}
case 2: { // Пункт 2
Serial.println("Выбран Пункт 2");
break;
}
}
}
```
Вы также можете назначить пункты меню со стороны оборудования с помощью кода:
```cpp
Blynk.setProperty(V1, "labels", "label 1", "label 2", "label 3");
```
**Пример кода:** [Меню](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Menu/Menu.ino)
### Ввод времени (Time Input)
Виджет Ввода времени позволяет вам выбрать время начала/окончания, день недели, часовой пояс, значения в формате до полудня/после полудня и отправить их на ваше оборудование. В настоящее время поддерживаются следующие форматы: ```ЧЧ:ММ``` и ```ЧЧ:ММ AM/PM```.
Аппаратное устройстов будет отсчитывать время пользовательского интерфейса в виде секунд дня (```3600 * часов + 60 * минут```) для запуска/остановки времения. Время, которое виджет отправляет оборудованию, является локальным временем пользователя.
Индексы по выбранных дней:
```
Понедельник - 1
Вторник - 2
...
Суббота - 6
Воскресенье - 7
```
Вы также можете изменить состояние виджета в интерфейсе пользователя. Смотрите ниже примеры кода.
**Пример кода:** [Простой Ввод времени для времени начала](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/SimpleTimeInput/SimpleTimeInput.ino)
**Пример кода:** [Расширенный Ввод времени](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/AdvancedTimeInput/AdvancedTimeInput.ino)
**Пример кода:** [Обновление Ввода времени в пользовательском интерфейсе](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/UpdateTimeInputState/UpdateTimeInputState.ino)
### Карта (Map)
Виджет Карты позволяет устанавливать точки/флажки на карте со стороны оборудования. Это очень полезный виджет, если у вас есть несколько устройств, и вы хотите отслеживать их позиции на карте.
Вы можете отправить точку на карту с помощью обычной команды виртуальной записи:
```cpp
Blynk.virtualWrite(V1, pointIndex, lat, lon, "Название");
```
Мы также создали оболочку, чтобы вы могли упростить использование виджета Карты.
Вы можете изменить метки флажков на оборудовании с помощью кода:
```cpp
WidgetMap myMap(V1);
...
int index = 1;
float lat = 51.5074;
float lon = 0.1278;
myMap.location(index, lat, lon, "Название");
```
Использование уникальных ```index``` позволяет вам переопределить существующее значение точки.
**Пример кода:** [Базовый пример Карты](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Map/Map.ino)
### Таблица (Table)
Табличный виджет удобен, когда вам нужно структурировать аналогичные данные в пределах одного графического элемента. Работает как обычная таблица.
Вы можете добавить строку в таблицу с помощью кода:
```
Blynk.virtualWrite(V1, "add", id, "Имя", "Значение");
```
Вы можете обновить строку в таблице с помощью кода:
```
Blynk.virtualWrite(V1, "update", id, "Новое имя", "Новое значение");
```
Чтобы выделить любой элемент в таблице, используйте его идентификатор:
```
Blynk.virtualWrite(V1, "pick", 0);
```
Чтобы выбрать/отменить выбор (сделать значок зеленым/серым) элемент в таблице, используйте его идентификатор:
```
Blynk.virtualWrite(V1, "select", 0);
Blynk.virtualWrite(V1, "deselect", 0);
```
Чтобы очистить таблицу используйте код:
```
Blynk.virtualWrite(V1, "clr");
```
Вы также можете обрабатывать другие действия из таблицы. Например, использовать строку таблицы в качестве кнопки переключения.
```
BLYNK_WRITE(V1) {
String cmd = param[0].asStr();
if (cmd == "select") {
// строка в таблице была выбрана.
int rowId = param[1].asInt();
}
if (cmd == "deselect") {
// строка в таблице была отменена.
int rowId = param[1].asInt();
}
if (cmd == "order") {
// когда строки в таблице переупорядочиваются
int oldRowIndex = param[1].asInt();
int newRowIndex = param[2].asInt();
}
}
```
**Примечание:** Максимальное количество строк в таблице равно 100. Когда вы достигнете предела, таблица будет работать как список FIFO (Первый пришел - первый ушел).
Это ограничение можно изменить, настроив свойство ```table.rows.pool.size``` в параметрах локального сервера.
**Пример кода:** [Простое использование таблицы](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Table/Table_Simple/Table_Simple.ino)
**Пример кода:** [Расширенное использование таблицы](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Table/Table_Advanced/Table_Advanced.ino)
### Селектор устройств (Device Selector)
Селектор устройств - это мощный виджет, который позволяет обновлять виджеты на основе одного активного устройства.
Этот виджет особенно полезен, когда у вас есть несколько устройств с аналогичной функциональностью.
Представьте, что у вас есть 4 устройства, и к каждому устройству подключен датчик температуры и влажности. Для отображения данных по всем 4 устройствам вам необходимо добавить 8 виджетов.
С помощью Селектора устройств вы можете использовать только 2 виджета, которые будут отображать температуру и влажность в зависимости от активного устройства, выбранного в Селекторе.
Все, что вам нужно сделать, это:
1. Добавить виджет Селектора устройств в проект
2. Добавить 2 виджета (например виджет отображения значений (Value Display Widget)), чтобы отобразить температуру и влажность
3. В настройках виджетов вы сможете назначить их на Селектор устройств (в разделе источника или цели)
4. Выйти из настроек, запустить проект
Теперь вы можете изменить активное устройство в Селекторе устройств и увидите, что значения температуры и влажности отражают обновленные данные для только что выбранного вами устройства.
**ПРИМЕЧАНИЕ:** Виджет вебхук ([Webhook](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/WebHook/WebHook_GET/WebHook_GET.ino)) пока не работает с Селектором устройств.
### Плитка устройств (Device Tiles)
Плитка устройств - это мощный виджет, очень похожий на виджет Селектора устройств (Device Selector), но с пользовательским интерфейсом. Позволяет отображать один пин с устройства на одну плитку.
Этот виджет особенно полезен, когда у вас есть несколько устройств с аналогичной функциональностью. Теперь вы можете группировать похожие устройства на одном макете (шаблоне).
## Sensors
### Акселерометр (Accelerometer)
Акселерометр один из [сенсоров движения](https://developer.android.com/guide/topics/sensors/sensors_motion.html),
который позволяет определить движение Вашего телефона в пространстве.
Он может пригодится для отслеживания таких событий как тряска, удар, поворот или наклон телефона. Концептуально, акселерометр определяет силу ускорения приложенную к вашему телефону.
Единица измерения - м/c^2 приложенная к каждой из осей ```x```, ```y```, ```z```.
Чтобы получить данные с сенсора нужно использовать следующий код :
```cpp
BLYNK_WRITE(V1) {
//сила ускорения, приложенная к оси x
int x = param[0].asFloat();
//сила ускорения, приложенная к оси y
int y = param[1].asFloat();
//сила ускорения, приложенная к оси z
int z = param[2].asFloat();
}
```
Акселерометр не работает при свернутом приложении.
### Барометр/Давление (Barometer/pressure)
Барометр один из сенсоров [окружающей среды](https://developer.android.com/guide/topics/sensors/sensors_environment.html)
и позволяет измерять атмосферное давление.
Измеряется в ```hPa``` (гПа) или ```mbar``` (мБар).
Чтобы получить данные с сенсора нужно использовать следующий код :
```cpp
BLYNK_WRITE(V1) {
//Давление в мБар
int pressure = param[0].asInt();
}
```
Барометр не работает при свернутом приложении.
### Гравитация (Gravity)
Гравитация - это своего рода [датчики движения](https://developer.android.com/guide/topics/sensors/sensors_motion.html), который позволяет обнаруживать движение вашего смартфона.
Полезно для мониторинга движения устройства, таких как наклон, встряхивание, вращение или качание.
Датчик силы притяжения выдает трехмерный вектор, указывающий направление и величину силы притяжения.
Измеряется в ```m/s^2``` силы притяжения, приложенной к оси ```x```, ```y```, ```z```.
Для того, чтобы принять данные от него, вам необходимо:
```cpp
BLYNK_WRITE(V1) {
//сила притяжения, приложенная к оси x
int x = param[0].asFloat();
//сила притяжения, приложенная к оси y
int y = param[1].asFloat();
//сила притяжения, приложенная к оси y
int z = param[2].asFloat();
}
```
**ВНИМАНИЕ:** Виджет гравитации не работает в фоновом режиме.
### Влажность (Humidity)
Влажность является своего рода [датчиком среды](https://developer.android.com/guide/topics/sensors/sensors_environment.html),
который позволяет измерять относительную влажность окружающей среды.
Измеряется в ```%``` - фактически это относительная влажность в процентах.
Для того, чтобы принять данные от датчика, вам необходимо:
```cpp
BLYNK_WRITE(V1) {
//Влажность в %
int humidity = param.asInt();
}
```
**ВНИМАНИЕ:** Влажность не работает в фоновом режиме.
### Свет (Light)
Свет - это своего рода [датчики окружающей среды](https://developer.android.com/guide/topics/sensors/sensors_environment.html), который позволяет измерять уровень освещенности (уровень внешней освещенности измеряется в люксах). В телефонах чаще всего используется для управления яркостью экрана.
Для того, чтобы принять данные этого виджета, вам необходимо:
```cpp
BLYNK_WRITE(V1) {
//уровень освещенности
int lx = param.asInt();
}
```
Виджет Свет не работает в фоновом режиме.
### Близость (Proximity)
Близость - это своего рода [датчики положения](https://developer.android.com/guide/topics/sensors/sensors_position.html)
это позволяет определить, насколько близко смартфон к лицу. Измеряется в ```cm``` (см) - расстояние от телефона до лица. Однако большинство этих датчиков возвращает только информацию FAR / NEAR.
Поэтому, возвращаемое значение будет ```0 / 1```. Где 0 / LOW = ```FAR``` (далеко), а 1 / HIGH = ``` NEAR``` (рядом).
Для того, чтобы принять данные из виджета, вам необходимо:
```cpp
BLYNK_WRITE(V1) {
// расстояние до объекта
int proximity = param.asInt();
if (proximity) {
// РЯДОМ
} else {
// ДАЛЕКО
}
}
```
Виджет близость не работает в фоновом режиме.
### Температура (Temperature)
Температура является своего рода [датчиком окружающей среды](https://developer.android.com/guide/topics/sensors/sensors_environment.html) который позволяет измерять температуру окружающего воздуха. Измеряется в ```°C``` - градусах Цельсия.
Для приема данных из виджета, необходимо использовать код:
```cpp
BLYNK_WRITE(V1) {
// температура в градусах цельсия
int celcius = param.asInt();
}
```
Виджет Температуры не работает в фоновом режиме.
### Триггер GPS (GPS Trigger)
Виджет Триггер GPS позволяет легко инициировать события, когда вы входите или выходите из географической зоны. Этот виджет будет работать в фоновом режиме и периодически будет проверять ваши координаты. Если ваше местоположение находится в пределах или вне указанной зоны (географическая зона выбирается на карте виджета), виджет отправит команду ```HIGH```/``` LOW``` на аппаратное устройство. Например, Триггер GPS назначен для пина ```V1```, и включена опция ```Trigger When Enter```. В этом случае, когда вы окажитесь в указанной географической зоне виджет вызовет событие ```HIGH```.
```cpp
BLYNK_WRITE(V1) {
int state = param.asInt();
if (state) {
//Вы вошли в зону
} else {
//Вы вышли из зоны
}
}
```
Подробнее о том, как работает GPS-виджет, вы можете прочитать [здесь](https://developer.android.com/guide/topics/location/strategies.html).
**ВНИМАНИЕ:** Виджет Триггер GPS работает в фоновом режиме.
### Поток GPS (GPS Streaming)
Полезно для мониторинга местонахождения смартфона получать данные о широте, долготе, высоте и скорости (скорость часто может быть 0, если смартфон не поддерживает ее измерение).
Чтобы принимать данные из этого виджета, вам необходимо:
```cpp
BLYNK_WRITE(V1) {
float latitude = param[0].asFloat();
float longitude = param[1].asFloat();
float altitude = param[2].asFloat();
float speed = param[3].asFloat();
}
```
или вы можете использовать подготовленную оболочку ```GpsParam``` :
```cpp
BLYNK_WRITE(V1) {
GpsParam gps(param);
//Печать лат/лон с 6 десятичными знаками
Serial.println(gps.getLat(), 7);
Serial.println(gps.getLon(), 7);
Serial.println(gps.getAltitude(), 2);
Serial.println(gps.getSpeed(), 2);
}
```
Поток GPS работает в фоновом режиме.
**Пример кода:** [Поток GPS](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/GPS_Stream/GPS_Stream.ino)
## Other
### Мост (Bridge)
Мост может быть использован для связи между устройствами (без участия приложения). Вы можете отправлять цифровые / аналоговые / виртуальные команды записи с одного устройства на другое, зная только токен авторизации. На данный момент виджет Мост не обязательно использовать в приложении (здесь он используется для указания того, что у нас есть такая функция).
**Вы можете использовать несколько мостов для управления несколькими устройствами.**
Виджет Мост использует виртуальный пин и превращает его в канал для управления другим устройством. Это означает, что вы можете контролировать любые виртуальные, цифровые или аналоговые пины целевого устройства. Будьте осторожны, не используйте пины типа ```A0, A1, A2 ...``` при обмене данными между различными типами устройств, так как в таких случаях Arduino Core может ссылаться на неверные пины.
Пример кода для устройства A, которое будет отправлять значения на устройство B:
```cpp
//Инициирует виджет Моста на V1 устройства A
WidgetBridge bridge1(V1);
...
void setup() {
Blynk.begin(...);
while (Blynk.connect() == false) {
// Ждем пока Blynk подключится
}
bridge1.digitalWrite(9, HIGH); // выставим триггер HIGH на D9 устройства B. Код на устройстве B не требуется
bridge1.analogWrite(10, 123);
bridge1.virtualWrite(V1, "hello"); // вам нужно написать код на устройстве B, чтобы получить это значение. См. ниже
bridge1.virtualWrite(V2, "value1", "value2", "value3");
}
BLYNK_CONNECTED() {
bridge1.setAuthToken("OtherAuthToken"); // токен с устройства B
}
```
**ВАЖНО:** при выполнении ```virtualWrite()``` с виджета Мост, устройство B должно обрабатывать входящие данные с устройства A.
Например, если вы отправляете значение с устройства A на устройство B, используя ```bridge.virtualWrite (V5)```, вам необходимо использовать свой обработчик на устройстве B:
```cpp
BLYNK_WRITE(V5){
int pinData = param.asInt(); //pinData variable will store value that came via Bridge
}
```
Имейте в виду, что ```bridge.virtualWrite``` не отправляет никаких значений в мобильное приложение. Для этого вам нужно вызвать ```Blynk.virtualWrite```.
**Пример кода:** [Мост](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Bridge/Bridge.ino)
### Обработчик событий (Eventor)
Виджет Обработчик событий позволяет создавать простые правила поведения или **события**.
Давайте рассмотрим типичный вариант использования: считывание температуры с датчика DHT и отправка push-уведомления, когда температура превышает определенный предел:
```cpp
float t = dht.readTemperature();
if (isnan(t)) {
return;
}
if (t > 40) {
Blynk.notify(String("Температура слишком высокая: ") + t);
}
```
С Обработчиком событий вам не нужно писать этот код. Все, что вам нужно, это отправить значение с датчика на сервер Blynk:
```cpp
float t = dht.readTemperature();
Blynk.virtualWrite(V0, t);
```
Не забывайте, что команды ```virtualWrite``` должны быть заключены в таймер и не должны использоваться в основном цикле ```loop```.
**ПРИМЕЧАНИЕ:** Не забудьте добавить виджет уведомлений в приложении.
Обработчик событий пригодится вам, когда нужно изменить условия на лету без повторной загрузки нового скетча на аппаратное обеспечение. Вы можете создать столько **событий**, сколько вам нужно. Обработчик событий также может быть запущен со стороны приложения. Вам просто нужно назначить виджет на тот же контакт, что и ваше событие в Обработчике событий.
Обработчик событий не постоянно отправляет события. Давайте рассмотрим простой пример, как показано выше ```if (temperature > 40) send notification```. Когда температура превышает 40 пороговых значений - отправляется уведомление. Если температура продолжает оставаться выше 40 никакие повторные действия не будут инициированы. Но если ```temperature``` опускается ниже порогового значения, а затем проходит его снова уведомление будет отправлено повторно (для уведомлений Обработчика событий нет ограничения отправки в течение 5 секунд).
Обработчик событий также поддерживает события таймера (Timer). Например, вы можете установить пин ```V1``` ON/HIGH в 21:00:00 каждую пятницу.
В Обработчике событий вы можете назначить несколько таймеров на один и тот же пин, отправить любую строку/число, выбрать день и часовой пояс.
Чтобы удалить созданное **событие**, пожалуйста, используйте сдвиг пальцем по экрану. Вы также можете перенести последний элемент самого события.
**Пример кода:** [Обработчик событий](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Eventor/Eventor.ino)
**ПРИМЕЧАНИЕ:** Виджет таймера зависит от времени сервера, а не вашего телефона. Иногда время телефона может не соответствовать времени сервера.
**ПРИМЕЧАНИЕ:** события запускаются только один раз при выполнении условия. Это означитает что [цепочка событий] (https://community.blynk.cc/t/eventor-behavior-bug-feature/20962) невозможна (однако она может быть включена в коммерческой версии).
### Часы реального времени (RTC)
Часы реального времени позволяют получать время с сервера. Вы можете предварительно выбрать любой часовой пояс в пользовательском интерфейсе, чтобы получить время на оборудование из нужной локали.
**Пример кода:** [Часы реального времени](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/RTC/RTC.ino)
### Bluetooth с низким энергопотреблением
Этот виджет позволяет включить блутзуз с низким энергопотреблением на вашем телефоне. На текущий момент виджет также
требует наличия интернет соединения (постараемся пофиксить в ближайшем будущем). Некоторые типы виджетов нельзя
использовать вместе с блутузом, например исторический граф, так как он требует чтобы данные отправлялись на сервер, чего
блутуз виджет не делает.
**Список поддерживаемых чипов и контроллеров:** [BLE](https://github.com/blynkkk/blynk-library/tree/master/examples/Boards_Bluetooth)
### Блютуз (Bluetooth)
Этот виджет позволяет включить блютуз на вашем телефоне. На текущий момент виджет также требует наличия интернет соединения (постараемся пофиксить в ближайшем будущем) и поддерживается только на Android.
Некоторые типы виджетов нельзя использовать вместе с блютузом, например исторический граф, так как он требует чтобы
данные отправлялись на сервер, чего блютуз виджет не делает.
**Список поддерживаемых чипов и контроллеров:** [BLE](https://github.com/blynkkk/blynk-library/tree/master/examples/Boards_Bluetooth)
### Музыкальный проигрыватель (Music Player)
Простой элемент интерфейса с 3 кнопками - имитирует интерфейс музыкального проигрывателя. Каждая кнопка отправляет свою команду на аппаратное устройство: ```play``` (воспроизвести), ```stop``` (стоп), ```prev``` (предыдущий), ```next``` (следующий).
Вы можете изменить состояние виджета в приложении с аппаратной стороны с помощью следующих команд:
```
Blynk.virtualWrite(Vx, "play");
Blynk.virtualWrite(Vx, "stop");
```
Вы также можете изменить состояние воспроизведение/остановка виджета с помощью следующего кода (эквивалент вышеупомянутых команд):
```Blynk.setProperty(V1, "isOnPlay", "false");```
**Пример кода:** [Музыкальный проигрыватель](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Player/Player.ino)
### Вебхук (Webhook)
Вебхук очень мощный виджет, который позволяет Вам легко интегрироватся с любыми сторонними сервисами. С его помощью
Вы можете слать любые HTTP/S запросы на любой сервер или устройство, которое имеет HTTP/S API (например, лампы Philips Hue).
Вебхук вешается на вирутальный пин и любая команда, которая приходит на этот пин будет вызывать срабатывание HTTP/S
запроса. Команды на такой виртуальный пин могут приходить как со стороны железа, так и со стороны приложения. То есть,
Вы можете слать любой HTTP запрос при нажатии кнопки в приложении, если эта кнопка на том же пине что и вебхук.
Вот простой пример, представьте, что Вы хотите слать данные с микроконтроллера не только в Blynk, но и в какой-то другой сервис,
например - Google Docs или в thingspeak.com. Раньше Вам для этого пришлось бы писать что-то вроде :
```cpp
WiFiClient client;
if (client.connect("api.thingspeak.com", 80)) {
client.print("POST /update HTTP/1.1\n");
client.print("Host: api.thingspeak.com\n");
client.print("Connection: close\n");
client.print("X-THINGSPEAKAPIKEY: " + apiKeyThingspeak1 + "\n");
client.print("Content-Type: application/x-www-form-urlencoded\n");
client.print("Content-Length: ");
client.print(postStr.length());
client.print("\n\n");
client.print(postStr);
}
```
С вебхуком этого больше делать не нужно. Достаточно лишь заполнить поля виджета в приложении и выполнить привычное:
```cpp
Blynk.virtualWrite(V0, value);
```
Где V0 - пин вебхук виджета.
В дополнение, Вы можете подставлять значение пина в URL:
```cpp
https://api.thingspeak.com/update?api_key=xxxxxx&field1=/pin/
```
или тело запроса :
```cpp
["/pin/"]
```
Так же можно отправлять несколько значений внутри одного пина (до 5) :
```/pin[0]/```,```/pin[1]/```, ```/pin[2]/```
Еще одна крутая штука - это возможность делать HTTP GET запросы на сервере и слать их результат на микроконтроллер.
Прелесть тут в том, что Вам не нужно для этого писать сложный код на микроконтроллере. Представьте, что Вам нужно
получить информацию о погоде от какого-то метио сервиса. Например, по такому запросу :
```http://api.sunrise-sunset.org/json?lat=33.3823&lng=35.1856&date=2016-10-01```
Вы можете вставить этот запрос в вебхук виджет, выбрать пин ```V0``` и написать :
```cpp
BLYNK_WRITE(V0){
String webhookdata = param.asStr();
Serial.println(webhookdata);
}
```
Теперь, каждый раз когда вы дергаете ```V0``` с помощью ```Blynk.virtualWrite(V0, 1)``` будет вызвана функция ```BLYNK_WRITE(V0)```.
**Замечание:** обычно HTTP запросы довольно большие, поэтому Вам, вероятно, нужно будет увеличить лимит на максимальную
длину сообщения на микроконтроллере ```#define BLYNK_MAX_READBYTES 1024```.
**Замечание:** наше облако так же имеет определенные лимиты для вебхука. Мы разрешаем слать только 1 запрос в секунду.
Это поведение можно изменить на локальном сервер через свойство ```webhooks.frequency.user.quota.limit```. Пожалуйста,
используйте вебхуки с умом. Многие веб ресурсы не способны обрабатывать даже 1 запрос в секунду.
**Замечание :** в случае если Ваш вебхук не выполнился 10 раз подряд - вебхук виджет будет остановлен. Чтобы восстановить
его работу - нужно открыть и закрыть виджет в режиме редактирования. Не выполненными считаются запросы у которых код ответа
не равен 200 или 302.
### Отчеты (Reports)
Функция виджета Отчеты заключается в настройке и разметке отчетов данных в формате CSV. Вы можете выбрать разовые или переодически запланированные отчеты.
Кроме того, в отчетах вы можете очистить все пользовательсике данные, собранные с ваших устройств.
Вам необходимо настроить начальные параметры в режиме редактирования, а затем уже в режиме воспроизведения вы сможете настроить сами отчеты.
#### Режим редактирования. Конфигурация ввода данных
В режиме редактирования (когда ваш проект остановлен) вы определяете потоки данных, которые вы хотели бы позже включить в отчет.
Виджет Отчеты предназначен для работы с виджетом [Плитка устройств (Device Tiles)](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/device_tiles.md). Если вы не используете плитки устройств, вы все равно можете выбрать одно устройство или группу устройств в качестве источника данных для отчетов.
Вы должны выбрать либо [Плитку устройств](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/device_tiles.md), либо одино устройство, либо группу устройств для отчета. Вы не можете объединить эти оба варианта.
#### Режим воспроизведения
После добавления исходных устройств и их потоков данных нажмите кнопку «Воспроизвести» и нажмите кнопку «Отчеты».
### Настройка отчетов
Каждый параметр отчета предполагает свои собственные настройки:
```Report name``` (Имя отчета) - дайте вашему отчету осмысленное имя.
```Data source``` (Источники данных) - выберите потоки данных, которые вы хотели бы включить в отчеты.
```Report Frequency``` (периодичность отчетов) - Определяет, как часто будут отправляться отчеты. Они могут быть разовыми и запланированными.
```one-time``` (Сейчас) - мгновенно сформирует отчет и отправит его на указанные адреса электронной почты. Нажмите на значок справа, чтобы отправить отчет.
Запланированные отчеты могут быть отправлены ```daily```/```weekly```/```monthly``` (ежедневно/еженедельно/ежемесячно).
```At Time``` (Время) установите время дня, когда отчет будет отправлен.
```Start```/```End``` (Качало/Конец) указывает дату начала и окончания оправки отчетов.
Для еженедельного отчета вы можете выбрать день недели, когда отчет должен быть отправлен.
Для ежемесячного отчета вы можете выбрать, отправку отчета в первый или последний день месяца.
```Recipients``` (Получатели) - укажите до 5 адресов электронной почты..
```Data resolution``` (Разрешение данных) определяет детализацию ваших отчетов. Поддерживаемые детализации: ```minute``` (ежеминутно), ```hourly``` (ежечасно) и ```daily``` (ежедневно).
Например, когда вы генерируете ежедневный отчет с детализацией в 1 минуту, вы получаете ```24 * 60 * 60``` единиц данных в вашем ежедневном отчете за каждый выбранный поток.
```Group data in reports by``` (Группировка данных в отчетах) - укажите выходной формат файла-(ов) CSV:
```Datastream``` (Поток) - вы получите один CSV файл для каждого потока данных.
```Device``` (Устройство) - вы получите один CSV-файл на каждое устройство. Каждый файл будет содержать все включенные потоки данных.
```Report``` (Отчет) - вы получите один CSV-файл для всех ваших устройств и всех ваших потоков данных.
```Timezone correction``` (Времненная зона) - укажите корректировку часового пояса, если вам нужно настроить дату и время отчета на определенный часовой пояс.
```Date and time format``` (Формат даты и времени) - определяет формат поля временной метки ваших данных.
Вы можете выбрать ```2018-06-21 20:16:48```, ```2018-06-21T20:16:48+03:00``` или другой поддерживаемый формат.
Существует особый формат ```Timestamp``` (Временная метка), которая отражает разницу между текущим временем и полуночью 1 января 1970 года UTC, измеряемую в миллисекундах.
После настройки отчета нажмите кнопку «ОК» в правом верхнем углу. Ваш отчет готов.
После настройки отчета вы увидите, когда запланирован следущий отчет ```Next```, а также увидите расписание для этого отчета.
После отправки отчета хотя бы один раз, вы можете увидеть дату его последней отправки ```Last```.
```Last``` (Последний) метка также содержит статус отправки отчета:
- ```OK``` (Успешно): отчет был сгенерирован и успешно отправлен Получателям;
- ```No Data``` (Нет данных): отчет не содержит данных за указанный период;
- ```Error``` (Ошибка): что-то пошло не так. Пожалуйста, свяжитесь со службой поддержки Blynk.
Отчеты будут генерироваться, даже если ваш проект не находится в активном (Play) режиме. Однако помните, неактивные проекты небудут генерировать данные.
**ПРИМЕЧАНИЕ:** все отчеты формируются в кодировке UTF-16. Пожалуйста, убедитесь, что при открытии файла отчета вы выбрали кодировку UTF-16 в вашем CSV-редакторе.
### Отчеты (Reports)
Функция виджета Отчеты заключается в настройке и разметке отчетов данных в формате CSV. Вы можете выбрать разовые или переодически запланированные отчеты.
Кроме того, в отчетах вы можете очистить все пользовательсике данные, собранные с ваших устройств.
Вам необходимо настроить начальные параметры в режиме редактирования, а затем уже в режиме воспроизведения вы сможете настроить сами отчеты.
#### Режим редактирования. Конфигурация ввода данных
В режиме редактирования (когда ваш проект остановлен) вы определяете потоки данных, которые вы хотели бы позже включить в отчет.
Виджет Отчеты предназначен для работы с виджетом [Плитка устройств (Device Tiles)](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/device_tiles.md). Если вы не используете плитки устройств, вы все равно можете выбрать одно устройство или группу устройств в качестве источника данных для отчетов.
Вы должны выбрать либо [Плитку устройств](https://github.com/blynkkk/blynkkk.github.io/blob/master/mobile/ru/device_tiles.md), либо одино устройство, либо группу устройств для отчета. Вы не можете объединить эти оба варианта.
#### Режим воспроизведения
После добавления исходных устройств и их потоков данных нажмите кнопку «Воспроизвести» и нажмите кнопку «Отчеты».
### Настройка отчетов
Каждый параметр отчета предполагает свои собственные настройки:
```Report name``` (Имя отчета) - дайте вашему отчету осмысленное имя.
```Data source``` (Источники данных) - выберите потоки данных, которые вы хотели бы включить в отчеты.
```Report Frequency``` (периодичность отчетов) - Определяет, как часто будут отправляться отчеты. Они могут быть разовыми и запланированными.
```one-time``` (Сейчас) - мгновенно сформирует отчет и отправит его на указанные адреса электронной почты. Нажмите на значок справа, чтобы отправить отчет.
Запланированные отчеты могут быть отправлены ```daily```/```weekly```/```monthly``` (ежедневно/еженедельно/ежемесячно).
```At Time``` (Время) установите время дня, когда отчет будет отправлен.
```Start```/```End``` (Качало/Конец) указывает дату начала и окончания оправки отчетов.
Для еженедельного отчета вы можете выбрать день недели, когда отчет должен быть отправлен.
Для ежемесячного отчета вы можете выбрать, отправку отчета в первый или последний день месяца.
```Recipients``` (Получатели) - укажите до 5 адресов электронной почты..
```Data resolution``` (Разрешение данных) определяет детализацию ваших отчетов. Поддерживаемые детализации: ```minute``` (ежеминутно), ```hourly``` (ежечасно) и ```daily``` (ежедневно).
Например, когда вы генерируете ежедневный отчет с детализацией в 1 минуту, вы получаете ```24 * 60 * 60``` единиц данных в вашем ежедневном отчете за каждый выбранный поток.
```Group data in reports by``` (Группировка данных в отчетах) - укажите выходной формат файла-(ов) CSV:
```Datastream``` (Поток) - вы получите один CSV файл для каждого потока данных.
```Device``` (Устройство) - вы получите один CSV-файл на каждое устройство. Каждый файл будет содержать все включенные потоки данных.
```Report``` (Отчет) - вы получите один CSV-файл для всех ваших устройств и всех ваших потоков данных.
```Timezone correction``` (Времненная зона) - укажите корректировку часового пояса, если вам нужно настроить дату и время отчета на определенный часовой пояс.
```Date and time format``` (Формат даты и времени) - определяет формат поля временной метки ваших данных.
Вы можете выбрать ```2018-06-21 20:16:48```, ```2018-06-21T20:16:48+03:00``` или другой поддерживаемый формат.
Существует особый формат ```Timestamp``` (Временная метка), которая отражает разницу между текущим временем и полуночью 1 января 1970 года UTC, измеряемую в миллисекундах.
После настройки отчета нажмите кнопку «ОК» в правом верхнем углу. Ваш отчет готов.
После настройки отчета вы увидите, когда запланирован следущий отчет ```Next```, а также увидите расписание для этого отчета.
После отправки отчета хотя бы один раз, вы можете увидеть дату его последней отправки ```Last```.
```Last``` (Последний) метка также содержит статус отправки отчета:
- ```OK``` (Успешно): отчет был сгенерирован и успешно отправлен Получателям;
- ```No Data``` (Нет данных): отчет не содержит данных за указанный период;
- ```Error``` (Ошибка): что-то пошло не так. Пожалуйста, свяжитесь со службой поддержки Blynk.
Отчеты будут генерироваться, даже если ваш проект не находится в активном (Play) режиме. Однако помните, неактивные проекты небудут генерировать данные.
**ПРИМЕЧАНИЕ:** все отчеты формируются в кодировке UTF-16. Пожалуйста, убедитесь, что при открытии файла отчета вы выбрали кодировку UTF-16 в вашем CSV-редакторе.
================================================
FILE: Widgets.md
================================================
#Widgets
Widgets are interface modules. Each of them performs a specific input/ output function when communicating with the hardware.
There are 4 types of Widgets:
- **Controllers** - used to send commands that control your hardware
- **Displays** - used for data visualization from sensors and other sources;
- **Notifications** - send messages and notifications;
- **Interface** - widgets to perform certain GUI functions;
- **Other** - widgets that don't belong to any category;
Each Widget has it's own settings. Some of the Widgets (e.g. Bridge) just enable functionality and they don't have any settings.
## Common Widget Settings
### Pin Selector
This is one of the main parameters you need to set. It defines which pin to control or to read from.
<img src="images/pin_selection.png" style="width: 200px; height:360px"/>
**Digital Pins** - represent physical Digital IO pins on your hardware. PWM-enabled pins are marked with the ```~``` symbol
**Analog Pins** - represent physical Analog IO pins on your hardware
**Virtual Pins** - have no physical representation. They are used to transfer any data between Blynk App and your hardware.
Read more about Virtual Pins [here](/#blynk-main-operations-virtual-pins).
### Data Mapping
In case you want to map incoming values to specific range you may use mapping button:
<img src="images/display_edit_mapping.png" style="width: 200px; height:360px"/>
Let's say your sensor sends values from 0 to 1023. But you want to display values in a range 0 to 100 in the app.
When Data Mapping enabled, incoming value 1023 will be mapped to 100.
### SPLIT/MERGE
Some of the Widgets can send more than one value. And with this switch you can control how to send them.
- **SPLIT**:
Each of the parameters is sent directly to the Pin on your hardware (e.g D7). You don't need to write any code.
**NOTE:** In this mode you send multiple commands from one widget, which can reduce performance of your hardware.
Example: If you have a Joystick Widget and it's set to D3 and D4, it will send 2 commands over the Internet:
```cpp
digitalWrite(3, value);
digitalWrite(4, value);
```
- **MERGE:**
When MERGE mode is selected, you are sending just 1 message, consisting of array of values. But you'll need to parse it on the hardware.
This mode can be used with Virtual Pins only.
Example: Add a zeRGBa Widget and set it to MERGE mode. Choose Virtual Pin V1
```cpp
BLYNK_WRITE(V1) // There is a Widget that WRITEs data to V1
{
int r = param[0].asInt(); // get a RED channel value
int g = param[1].asInt(); // get a GREEN channel value
int b = param[2].asInt(); // get a BLUE channel value
}
```
### Decimals
Defines how many decimals you would like to see when moving a Slider.
When "No Fraction" is chosen, slider will only send integer values with no decimals.
"1 digit" means that values will look like 1.1, 1.2, ..., 2.0, etc.
### Send On Release
This option allows you to optimize data traffic on your hardware.
For example, when you move joystick widget, commands are streamed to the hardware, during a single joystick move
you can send dozens of commands. There are use-cases where it's needed, however creating such a load may lead to hardware overload and reset.
**Send On Release** is a recommended setting for majority of applications. This is also a default setting.
### Write interval
Similar to "Send on Release" option. However, it allows you to stream values to your hardware within certain interval. For example, setting **write interval** to 100 ms means that while you move the slider, only 1 value will be sent to hardware within 100 ms period.
This option is also used to optimize data traffic flow to your hardware.
### Color gradient
When you choose gradient, it affects the color of widget elements based on invoming values.
For example: You set Gauge Widget with Min and Max parameters of 0-100, and choose green-yellow-red gradient. When hardware sends:
- `10`, Gauge will change it's color to green color
- `50` will change Gauge to yellow color
- `80` will change Gauge to red color
There are 2 types of gradients you can choose from:
- Warm: Green - Orange - Red;
- Cold: Green - Blue - Violet;
##Controllers
### Button
Works in push or switch modes. Allows to send ON and OFF (LOW/HIGH) values. Button sends 1 (HIGH) on press and sends 0 (LOW) on release.
<img src="images/button.png" style="width: 77px; height:80px"/>
<img src="images/button_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [BlynkBlink](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### Slider
Similar to potentiometer. Allows to send values between in a given MIN/MAX range.
<img src="images/slider.png" style="width: 77px; height:80px"/>
<img src="images/slider_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [BlynkBlink](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### Timer
Timer triggers actions at a specified time. Even if smartphone and app is offline. Start time sends 1 (HIGH). Stop time sends 0 (LOW).
Recent Android version also has improved Timer within Eventor widget.
With Eventor Time Event you can assign multiple timers on same pin, send any string/value, select days and timezone.
It is recommended to use Eventor over Timer widget.
However Timer widget is still suitable for simple timer events.
<img src="images/timer.png" style="width: 77px; height:80px"/>
<img src="images/timer_edit.png" style="width: 200px; height:360px"/>
**NOTE:** The timer widget rely on the server time and not your phone time. Sometimes the phone time may not match the server time.
**Sketch:** [Timer](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Timer/Timer.ino)
### Joystick
Control servo movements in 4 directions
####Settings:
- SPLIT/MERGE modes - read [here](/#widgets-common-widget-settings-splitmerge)
- **Rotate on Tilt**
When it's ON, Joystck will automatically rotate if you use your smartphone in landscape orientation
- **Auto-Return**
-
When it's OFF, Joystick handle will not return back to center position. It will stay where you left it.
<img src="images/joystick.png" style="width: 77px; height:80px"/>
<img src="images/joystick_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [JoystickTwoAxis](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/JoystickTwoAxis/JoystickTwoAxis.ino)
### zeRGBa
zeRGBa is a usual RGB color picker + brightness picker
#### Settings:
- **SPLIT**:
Each of the parameters is sent directly to the Pin on your hardware (e.g D7). You don't need to write any code.
**NOTE:** In this mode you send multiple commands from one widget, which can reduce performance of your hardware.
Example: If you have a zeRGBa Widget and it's set to D1, D2, D3 it will send 3 commands over the Internet:
```cpp
digitalWrite(1, r);
digitalWrite(2, g);
digitalWrite(3, b);
```
- **MERGE**:
When MERGE mode is selected, you send 1 message with an array of values inside. You would need to parse the message on the hardware.
This mode can be used with Virtual Pins only.
Example: Add a zeRGBa Widget and set it to MERGE mode. Choose Virtual Pin V1.
```cpp
BLYNK_WRITE(V1) // zeRGBa assigned to V1
{
// get a RED channel value
int r = param[0].asInt();
// get a GREEN channel value
int g = param[1].asInt();
// get a BLUE channel value
int b = param[2].asInt();
}
```
### Step Control
Step Control is used to set granular values with a given step
2 buttons are assigned to 1 pin. One button increments the value, another one decrements it.
**Send Step** option allows you to send step value to hardware instead of actual value of step widget.
**Loop value** option allows you to reset step widget to start value when maximum value is reached.
**Sketch:** [Basic Sketch](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
##Displays
### Value Display
Displays incoming data.
<img src="images/display.png" style="width: 77px; height:80px"/>
<img src="images/display_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [BlynkBlink](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
### Labeled Value
Displays incoming data in a formatted wayt. It is a better version of 'Value Display' where you can add suffixes and prefixes on the app side, with no coding on the hardware.
<img src="images/display.png" style="width: 77px; height:80px"/>
<img src="images/labeled_value_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [BlynkBlink](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
#### Formatting options
For example: your sensor sends vaule of 12.6789 to Blynk application.
Next formatting options are supported:
```/pin/``` - displays the value without formatting (12.6789)
```/pin./``` - displays the rounded value without decimal part (13)
```/pin.#/``` - displays the value with 1 decimal digit (12.7)
```/pin.##/``` - displays the value with two decimal places (12.68)
<img src="images/labeled_value_format_edit.png" style="width: 200px; height:360px"/>
### LED
A simple LED for indication. You need to send 0 in order to turn LED off. And 255 in order to turn LED on. Or just use
Blynk API as described below:
```cpp
WidgetLED led1(V1); //register to virtual pin 1
led1.off();
led1.on();
```
All values between 0 and 255 will change LED brightness:
```cpp
WidgetLED led2(V2);
led2.setValue(127); //set brightness of LED to 50%.
```
<img src="images/led.png" style="width: 77px; height:80px"/>
**Sketch:** [LED](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LED/LED_Blink/LED_Blink.ino)
### Gauge
Visual display of numeric values.
<img src="images/gauge.png" style="width: 77px; height:80px"/>
<img src="images/gauge_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [BlynkBlink](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/BlynkBlink/BlynkBlink.ino)
#### Formatting options
For example: your sensor sends vaule of 12.6789 to Blynk application.
Next formatting options are supported:
```/pin/``` - displays the value without formatting (12.6789)
```/pin./``` - displays the rounded value without decimal part (13)
```/pin.#/``` - displays the value with 1 decimal digit (12.7)
```/pin.##/``` - displays the value with two decimal places (12.68)
### LCD
This is a regular 16x2 LCD display made in our secret facility in China.
#### SIMPLE / ADVANCED MODE
#### Commands
You need to use special commands with this widget:
```
lcd.print(x, y, "Your Message");
```
Where x is a symbol position (0-15), y is a line id (0 or 1),
```
lcd.clear();
```
<img src="images/lcd.png" style="width: 77px; height:80px"/>
<img src="images/lcd_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [LCD Advanced Mode](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_AdvancedMode/LCD_AdvancedMode.ino)
**Sketch:** [LCD Simple Mode Pushing](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_SimpleModePushing/LCD_SimpleModePushing.ino)
**Sketch:** [LCD Simple Mode Reading](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/LCD/LCD_SimpleModeReading/LCD_SimpleModeReading.ino)
#### Formatting options
For example: your sensor sends vaule of 12.6789 to Blynk application.
Next formatting options are supported:
```/pin/``` - displays the value without formatting (12.6789)
```/pin./``` - displays the rounded value without decimal part (13)
```/pin.#/``` - displays the value with 1 decimal digit (12.7)
```/pin.##/``` - displays the value with two decimal places (12.68)
<img src="images/lcd_format_edit.png" style="width: 200px; height:360px"/>
### SuperChart
SuperChart is used to visualise live and historical data. You can use it for sensor data, for binary event logging and more.
To use SuperChart widget you would need to push the data from the hardware with the desired interval by using timers.
[Here is](https://examples.blynk.cc/?board=ESP8266&shield=ESP8266%20WiFi&example=GettingStarted%2FPushData) a basic example for data pushing.
#### Interactions:
- **Switch between time ranges and Live mode**
</br>Tap time ranges at the bottom of the widget to change time ranges
- **Tap Legend Elements** to show or hide datastreams
</br>
- **Tap'n'hold to view timestamp and corresponding values**
<img src="images/chart/tapnhold_charts.png" style="width: 300px; height:280px"/>
- **Quick swipe from left to right to reveal previous data**
<img src="images/chart/swipe_charts.png" style="width: 300px; height:280px"/>
Then you can then scroll data back and forward within the given time range.
- **Full Screen Mode**</br>
Press this button to open Full Screen view in landscape orientation:
<img src="images/chart/fullscreen_charts.png" style="width: 300px; height:280px"/>
Simply rotate the phone back to portrait mode. Chart should rotate automagically.
In full screen view you will see X (time) and multiple Y scales.
Full Screen Mode can be disabled from widget Settings.
- **Menu Button**</br>
Menu button will open additional functions:
- Export to CSV
- Erase Data on the server
<img src="images/chart/menu_charts.png" style="width: 300px; height:280px"/>
#### SuperChart Settings:
- Chart Title
- Title Font Size
You have a choice of 3 font sizes
- Title Alignment
Choose chart title alignment. This setting also affects Title and Legend position on the Widget.
- Show x-axis (time)
Select it if you want to show the time label at the bottom of your chart.
- Time ranges picker
Allows you to select required periods (`15m`, `30m`, `1h`, `3h`, ...) and resolution for your chart. Resolution
defines how precise your data is. Right now chart supports 2 types of resolution `standard` and `high`. Resolution also
depends on the selected period. For example, `standard` resolution for `1d` means you'll get 24 points per day (1 per hour),
with `high` resolution you'll get for `1d` 1440 points per day (1 per minute).
- Datastreams - add datastreams (read below how to configure datastreams)
#### Datastream Settings
Widget supports up to 4 Datastreams.
Press Datastream Settings Icon to open Datastream Settings.
<img src="images/chart/datastream_charts.png"/>
**Design:**
Choose available types of Chart:
- Line
- Area
- Bar
- Binary (anchor LINK to binary)
**Color:**
Choose solid colors or gradients
**Source and input:**
You can use 3 types of Data source:
**1. Virtual Pin**
Choose the desired Device and Virtual Pin to read the data from.
**2. Tags**
SuperChart can aggregate data from multiple devices using built-in aggregation functions.
For example, if you have 10 Temperature sensors sending temperature with the given period,
you can plot average value from 10 sensors on the widget.
To use Tags:
- **[Add Tag](/#blynk-main-operations-control-of-multiple-devices-tags)** to every device you want to aggregate data from.
- **Push data to the same Virtual Pin** on every device. (e.g. ```Blynk.virtualWrite (V0, temperature);```)
- **Choose Tag as a source** in SuperChart Widget and use the pin where the data is coming to (e.g V0)<br>
**Functions available:**
- **SUM**, will summarize all incoming values to the specified Virtual Pin across all devices tagged with the chosen tag
- **AVG**, will plot average value
- **MED**, will find a median value
- **MIN**, will plot minimum value
- **MAX** will plot maximum value
**☝️ IMPORTANT: Tags are not working in Live Mode.**
3. **[Device Selector](/#widgets-time-input-device-selector)**
If you add Device Selector Widget to your project, you can use it as a source for SuperChart.
In this case, when you change the device in Device Selector, chart will be updated accordingly
**Y-Axis Settings**
<br>There are 4 modes of how to scale data along the Y axis
1. *Auto*<br>
Data will be auto-scaled based on min and max values of the given time period. This is nice option to start with.
2. **Values**<br>
When this mode is selected, Y scale will be set to the values you choose.
For example, if your hardware sends data with values varying from -100 to 100, you can set the chart
to this values and data will be rendered correctly.
<img src="images/chart/yScale_manual_charts.png" style="width: 300px; height:212"/>
You may also want to visualize the data within some specific range.
Let's say incoming data has values in the range of 0-55, but you would like to see only values in the range 30-50.
You can set it up and if values are out of Y scale you configured, chart will be cropped
3. **% of Height**<br>
This option allows you to auto-scale incoming data on the widget and position it the way you want.
In this mode, you set up the percentage of widget height on the screen, from 0% to 100%.
<img src="images/chart/yheight2_charts.png" style="width: 300px; height:212px"/>
If you set 0-100%, in fact it's a full auto-scale. No matter in which range the data is coming,
it will be always scaled to the whole height of the widget.
If you set it to 0-25%, then this chart will only be rendered on 1/4 of the widget height:
<img src="images/chart/yheight2_manual_charts.png" style="width: 300px; height:212px"/>
This setting is very valuable for **Binary Chart** or for visualizing a few datastreams on the same chart in a different way.
<img src="images/chart/binary_charts.png" style="width: 300px; height:280px"/>
4. *Delta*<br>
While data stays within the given Delta value, chart will be auto-scaled within this range.
If delta exceeds the range, chart will be auto-scaled to min/max values of the given period.
**Suffix:**<br>
Here you can specify a suffix that will be shown during the Tap'n'hold
**Decimals**<br>
Defines the formatting of the graph value when you Tap'n'hold the graph. Possible options are: #, #.#, #.##, etc.
**Connect Missing Data Points**<br>
If this switch is ON, then SuperChart will connect all the dots even if there was no data
<img src="images/chart/datapoints1_charts.png" style="width: 300px; height:280px"/>
If it's set to OFF, then you will see gaps in case there was no data.
<img src="images/chart/datapoints2_charts.png" style="width: 300px; height:280px"/>
**Binary Chart Settings**<br>
This type of chart is useful to plot binary data, for example when unit was ON or OFF, or when motion was detected or when certain threshold was reached.
You need to specify a **FLIP** point, which is the point where incoming data will be turned into TRUE or FALSE state.
For example, you send the data in the range of `0 to 1023`. If you set `512` as a **FLIP** point, then everything above `512` (excluding 512) will be recorded as `TRUE`, any value below `512` (including 512) will be `FALSE`.
Another example, if you send `0 and 1` and set `0` as a **FLIP** point, then `1` will be `TRUE`, `0` will be `FALSE`
**State Labels:**<br>
Here you can specify how `TRUE/FALSE` should be shown in Tap'n'Hold mode.
For example, you can set to `TRUE` to "Equipment ON" label, `FALSE` to "Equipment OFF".
<img src="images/chart/binarylabel_charts.png" style="width: 300px; height:280px"/>
Superchart supports currently 2 types of granularity:
- Minute granularity - ```1h```, ```6h```, ```1d```;
- Hour granularity - ```1w```, ```1m```, ```3m```;
This means that minimum chart update interval is 1 minute for ```1h```, ```6h```, ```1d``` periods.
1 hour for ```1w```, ```1m``` and ```3m``` periods.
As Blynk Cloud is free to use we have a limit on how many data you can store. At the moment Blynk Cloud accepts
1 message per minute per pin. In case you send your data more frequently your values will be averaged. For example,
in case you send value ```10``` at 12:12:05 and than again ```12``` at 12:12:45 as result in chart you'll see
value ```11``` for 12:12.
In order to see data in chart you need to use either widgets with "Frequency reading" interval (in
that case your app should be open and running) or you can use ```Blynk.virtualWrite``` on hardware side. Every
```Blynk.virtualWrite``` command is stored on server automatically. In that case you don't need application to be up and running.
### Terminal
Displays data from your hardware. Allows to send any string to your hardware. Terminal always stores last 25 messages
your hardware had send to Blynk Cloud. This limit may be increased on Local Server with ```terminal.strings.pool.size```
property.
You need to use special commands with this widget:
```cpp
terminal.print(); // Print values, like Serial.print
terminal.println(); // Print values, like Serial.println()
terminal.write(); // Write a raw data buffer
terminal.flush(); // Ensure that data was sent out of device
terminal.clear(); // Erase all values in the terminal
```
<img src="images/terminal.png" style="width: 77px; height:80px"/>
<img src="images/terminal_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [Terminal](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Terminal/Terminal.ino)
### Video Streaming
Simple widget that allows you to display any live stream. Widget supports RTSP (RP, SDP), HTTP/S progressive streaming,
HTTP/S live streaming. For more info please follow [official Android documentation](https://developer.android.com/guide/appendix/media-formats.html).
At the moment Blynk doesn't provide streaming servers. So you can either stream directly from camera, use 3-d party
services or host streaming server on own server (on raspberry for example).
You can also change video url from hardware with:
```cpp
Blynk.setProperty(V1, "url", "http://my_new_video_url");
```
### Level Display
Level Display is very similar to progress bar, when you need to visualize a level betwen min/max value
To update Level Display from hardware side with code:
```cpp
Blynk.virtualWrite(V1, val);
```
Every message that hardware sends to server is stored automatically on server. PUSH mode doesn't require
application to be online or opened.
**Sketch:** [Push Example](https://github.com/blynkkk/blynk-library/blob/master/examples/GettingStarted/PushData/PushData.ino)
##Notifications
###Twitter
Twitter widget connects your Twitter account to Blynk and allows you to send Tweets from your hardware.
<img src="images/TwitterON.png" style="width: 77px; height:80px"/>
Example code:
```cpp
Blynk.tweet("Hey, Blynkers! My Arduino can tweet now!");
```
Limitations:
- you cant' send 2 tweets with same message (it's Twitter policy)
- only 1 tweet per 5 seconds is allowed
**Sketch:** [Twitter](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Twitter/Twitter.ino)
###Email
Email widget allows you to send email from your hardware to any address.
Example code:
```cpp
Blynk.email("my_email@example.com", "Subject", "Your message goes here");
```
It also contains ```to``` field. With this field you may define receiver of email in the app.
You may skip ```to``` field when you want to send email to your Blynk app login email:
```cpp
Blynk.email("Subject", "Your message goes here");
```
You can send either ```text/html``` or ```text/plain``` (some clients don't support ```text/html```) email.
You can change this content type of email in the Mail widget settings.
Additionally you may use ```{DEVICE_NAME}```, ```{DEVICE_OWNER_EMAIL}``` and ```{VENDOR_EMAIL}``` (for the local server)
placeholders in the mail for the ```to```, ```subject``` and ```body``` fields:
```cpp
Blynk.email("{DEVICE_OWNER_EMAIL}", "{DEVICE_NAME} : Alarm", "Your {DEVICE_NAME} has critical error!");
```
<img src="images/mail.png" style="width: 77px; height:80px"/>
Limitations:
- Maximum allowed email + subject + message length is 120 symbols. However you can increase this limit if necessary
by adding ```#define BLYNK_MAX_SENDBYTES XXX``` to you sketch. Where ```XXX``` is desired max length of your email.
For example for ESP you can set this to 1200 max length ```#define BLYNK_MAX_SENDBYTES 1200```. The
```#define BLYNK_MAX_SENDBYTES 1200``` must be included before any of the Blynk includes.
- Only 1 email per 5 seconds is allowed
- In case you are using gmail on the Local Server you are limited with 500 mails per day (by google). Other providers may have similar
limitations, so please be careful.
- User is limited with 100 messages per day in the Blynk Cloud;
**Sketch:** [Email](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Email/Email.ino)
###Push Notifications
Push Notification widget allows you to send push notification from your hardware to your device. Currently it also
contains 2 additional options:
- **Notify when hardware offline** - you will get push notification in case your hardware went offline.
- **Offline Ignore Period** - defines how long hardware could be offline (after it went offline) before sending notification.
In case period is exceeded - "hardware offline" notification will be send. You will get no notification in case hardware
was reconnected within specified period.
- **Priority** high priority gives more chances that your message will be delivered without any delays.
See detailed explanation [here](https://developers.google.com/cloud-messaging/concept-options#setting-the-priority-of-a-message).
**WARNING**: high priority contributes more to battery drain compared to normal priority messages.
<img src="images/push.png" style="width: 77px; height:80px"/>
Example code:
```cpp
Blynk.notify("Hey, Blynkers! My hardware can push now!");
```
You can also use placeholder for device name, that will be replaced on the server with your device name:
```cpp
Blynk.notify("Hey, Blynkers! My {DEVICE_NAME} can push now!");
```
Limitations:
- Maximum allowed body length is 120 symbols;
- Every device can send only 1 notification every 5 seconds;
**Sketch:** [PushNotification](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/PushNotification/PushNotification_Button/PushNotification_Button.ino)
###Unicode in notify, email, push, ...
The library handles all strings as UTF8 Unicode. If you're facing problems, try to print your message to the Serial and see if it works (the terminal should be set to UTF-8 encoding). If it doesn't work, probably you should read about unicode support of your compiler.
If it works, but your message is truncated - you need to increase message length limit (all Unicode symbols consume at least twice the size of Latin symbols).
###Increasing message length limit
You can increase maximum message length by putting on the top of your sketch (before Blynk includes):
```cpp
#define BLYNK_MAX_SENDBYTES 256 // Default is 128
```
## Interface
### Tabs
The only purpose of Tabs widget is to extend your project space. You can have up to 4 tabs.
Also you can drag widgets between tabs. Just drag widget on the label of required tab of tabs widget.
<img src="images/tabs_settings.png" style="width: 200px; height:360px"/>
### Menu
Menu widget allows you to send command to your hardware based on selection you made on UI. Menu
sends index of element you selected and not label string. Sending index is starts from 1.
It works same way as usual ComboBox element. You can also set Menu items
[from hardware side](/#blynk-main-operations-change-widget-properties).
<img src="images/menu_edit.png" style="width: 200px; height:360px"/>
Example code:
```
switch (param.asInt())
{
case 1: { // Item 1
Serial.println("Item 1 selected");
break;
}
case 2: { // Item 2
Serial.println("Item 2 selected");
break;
}
}
```
**Sketch:** [Menu](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Menu/Menu.ino)
### Time Input
Time input widget allows you to select start/stop time, day of week, timezone, sunrise/sunset formatted values
and send them to your hardware. Supported formats for time now are ```HH:MM``` and ```HH:MM AM/PM```.
Hardware will get selected on UI time as seconds of day (```3600 * hours + 60 * minutes```) for start/stop time.
Time that widget sends to hardware is user local time.
Selected days indexes:
```
Monday - 1
Tuesday - 2
...
Saturday - 6
Sundays - 7
```
You can also change state of widget on UI. See below sketches.
**Sketch:** [Simple Time Input for start time](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/SimpleTimeInput/SimpleTimeInput.ino)
**Sketch:** [Advanced Time Input](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/AdvancedTimeInput/AdvancedTimeInput.ino)
**Sketch:** [Update Time Input State on UI](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/TimeInput/UpdateTimeInputState/UpdateTimeInputState.ino)
### Map
Map widget allows you set points/pins on map from hardware side. This is very useful widget in case you have
multiple devices and you want track their values on map.
You can send a point to map with regular virtual wrtei command:
```cpp
Blynk.virtualWrite(V1, pointIndex, lat, lon, "value");
```
We also created wrapper for you to make suage of map simpler:
You can change button labels from hardware with:
```cpp
WidgetMap myMap(V1);
...
int index = 1;
float lat = 51.5074;
float lon = 0.1278;
myMap.location(index, lat, lon, "value");
```
Using save ```index``` allows you to override existing point value.
**Sketch:** [Basic Sketch](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Map/Map.ino)
### Table
Table widget comes handy when you need to structure similar data within 1 graphical element. It works as a usual table.
You can add a row to the table with:
```
Blynk.virtualWrite(V1, "add", id, "Name", "Value");
```
You can update a row in the table with:
```
Blynk.virtualWrite(V1, "update", id, "UpdatedName", "UpdatedValue");
```
To highlight any item in a table by using it's id in a table:
```
Blynk.virtualWrite(V1, "pick", 0);
```
To select/deselect (make icon green/grey) item in a table by using it's row id in a table:
```
Blynk.virtualWrite(V1, "select", 0);
Blynk.virtualWrite(V1, "deselect", 0);
```
To clear the table at any time with:
```
Blynk.virtualWrite(V1, "clr");
```
You can also handle other actions coming from table. For example, use row as a switch button.
```
BLYNK_WRITE(V1) {
String cmd = param[0].asStr();
if (cmd == "select") {
//row in table was selected.
int rowId = param[1].asInt();
}
if (cmd == "deselect") {
//row in table was deselected.
int rowId = param[1].asInt();
}
if (cmd == "order") {
//rows in table where reodered
int oldRowIndex = param[1].asInt();
int newRowIndex = param[2].asInt();
}
}
```
**Note:** Max number of rows in the table is 100. When you reach the limit, table will work as FIFO (First In First Out) list.
This limit can be changed by configuring ```table.rows.pool.size``` property for Local Server.
**Sketch:** [Simple Table usage](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Table/Table_Simple/Table_Simple.ino)
**Sketch:** [Advanced Table usage](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Table/Table_Advanced/Table_Advanced.ino)
### Device Selector
Device selector is a powerful widget which allows you to update widgets based on one active device. This widget is particlularly helpful when you have a fleet of devices with similar functionality.
Imagine you have 4 devices and every device has a Temperature & Humidity sensor connected to it. To display the data for all 4 devices you would need to add 8 widgets.
With Device Selector, you can use only 2 Widgets which will display Temperature and Humidity based on the active device chosen in Device Selector.
All you have to do is:
1. Add Device Selector Widget to the project
2. Add 2 widgets (for example Value Display Widget) to show Temperature and Humidity
3. In Widgets Settings you will be able assign them to Device Selector (Source or Target section)
4. Exit settings, Run the project.
Now you can change the active device in Device Selector and you will see that Temperature and Humidity values are reflecting the data updates for the device you just picked.
**NOTE:** Webhook Widget will not work with Device Selector (yet).
### Device Tiles
Device tiles is a powerful widget and very similar to the device selector widget, but with UI.
It allows you to display 1 pin per device per tile.
This widget is particularly helpful when you have a fleet of devices with similar functionality. So you can
group similar devices within one layout (template).
## Sensors
### Accelerometer
Accelerometer is kind of [motion sensors](https://developer.android.com/guide/topics/sensors/sensors_motion.html)
that allows you to detect motion of your smartphone.
Useful for monitoring device movement, such as tilt, shake, rotation, or swing.
Conceptually, an acceleration sensor determines the acceleration that is applied to a device by measuring the forces
that are applied to the sensor. Measured in ```m/s^2``` applied to ```x```, ```y```, ```z``` axis.
In order to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
//acceleration force applied to axis x
int x = param[0].asFloat();
//acceleration force applied to axis y
int y = param[1].asFloat();
//acceleration force applied to axis y
int z = param[2].asFloat();
}
```
Accelerometer doesn't work in background.
### Barometer/pressure
Barometer/pressure is kind of [environment sensors](https://developer.android.com/guide/topics/sensors/sensors_environment.html)
that allows you to measure the ambient air pressure.
Measured in in ```hPa``` or ```mbar```.
In oder to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
//pressure in mbar
int pressure = param[0].asInt();
}
```
Barometer doesn't work in background.
### Gravity
Gravity is kind of [motion sensors](https://developer.android.com/guide/topics/sensors/sensors_motion.html)
that allows you to detect motion of your smartphone.
Useful for monitoring device movement, such as tilt, shake, rotation, or swing.
The gravity sensor provides a three dimensional vector indicating the direction and magnitude of gravity.
Measured in ```m/s^2``` of gravity force applied to ```x```, ```y```, ```z``` axis.
In oder to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
//force of gravity applied to axis x
int x = param[0].asFloat();
//force of gravity applied to axis y
int y = param[1].asFloat();
//force of gravity applied to axis y
int z = param[2].asFloat();
}
```
Gravity doesn't work in background.
### Humidity
Humidity is kind of [environment sensors](https://developer.android.com/guide/topics/sensors/sensors_environment.html)
that allows you to measure ambient relative humidity.
Measured in ```%``` - actual relative humidity in percent.
In oder to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
// humidity in %
int humidity = param.asInt();
}
```
Humidity doesn't work in background.
### Light
Light is kind of [environment sensors](https://developer.android.com/guide/topics/sensors/sensors_environment.html)
that allows you to measure level of light (measures the ambient light level (illumination) in lx).
In phones it is used to control screen brightness.
In order to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
//light value
int lx = param.asInt();
}
```
Light doesn't work in background.
### Proximity
Proximity is kind of [position sensors](https://developer.android.com/guide/topics/sensors/sensors_position.html)
that allows you to determine how close the face of a smartphone is to an object.
Measured in ```cm``` - distance from phone face to object. However most of this sensors returns only FAR / NEAR information.
So return value will be ```0/1```. Where 0/LOW is ```FAR``` and 1/HIGH is ```NEAR```.
In order to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
// distance to object
int proximity = param.asInt();
if (proximity) {
//NEAR
} else {
//FAR
}
}
```
Proximity doesn't work in background.
### Temperature
Temperature is kind of [environment sensors](https://developer.android.com/guide/topics/sensors/sensors_environment.html)
that allows you to measure ambient air temperature.
Measured in ```°C``` - celcius.
In order to accept data from it you need to:
```cpp
BLYNK_WRITE(V1) {
// temperature in celcius
int celcius = param.asInt();
}
```
Temperature doesn't work in background.
### GPS Trigger
GPS trigger widget allows easily trigger events when you arrive to or leave from some destination. This widget
will work in background and periodically will check your coordinates. In case your location is within/out required
radius (selected on widget map) widget will send ```HIGH```/```LOW``` command to hardware. For example, let's assume you have
GPS Trigger widget assigned to pin ```V1``` and option ```Trigger When Enter```. In that case when you'll arrive to destination
point widget will trigger ```HIGH``` event.
```cpp
BLYNK_WRITE(V1) {
int state = param.asInt();
if (state) {
//You enter destination
} else {
//You leave destination
}
}
```
More details on how GPS widget works you can read [here](https://developer.android.com/guide/topics/location/strategies.html).
GPS trigger widget works in background.
### GPS Streaming
Useful for monitoring smartphone location data such as latitude, longitude, altitude and speed (speed could be often 0
in case smartphone doesn't support it).
In order to accept data from this widget you need to:
```cpp
BLYNK_WRITE(V1) {
float latitude = param[0].asFloat();
float longitude = param[1].asFloat();
float altitude = param[2].asFloat();
float speed = param[3].asFloat();
}
```
or you can use prepared wrapper ```GpsParam```:
```cpp
BLYNK_WRITE(V1) {
GpsParam gps(param);
// Print 6 decimal places for Lat
Serial.println(gps.getLat(), 7);
Serial.println(gps.getLon(), 7);
Serial.println(gps.getAltitude(), 2);
Serial.println(gps.getSpeed(), 2);
}
```
GPS Streaming works in background.
**Sketch:** [GPS Stream](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/GPS_Stream/GPS_Stream.ino)
## Other
### Bridge
Bridge can be used for Device-to-Device communication (no app. involved). You can send digital/analog/virtual write commands from one device to another, knowing it's auth token.
At the moment Bridge widget is not required on application side (it is mostly used for indication that we have such feature).
**You can use multiple bridges to control multiple devices.**
<img src="images/bridge.png" style="width: 77px; height:80px"/>
Bridge widget takes a virtual pin, and turns it into a channel to control another device. It means you can control any virtual, digital or analog pins of the target device.
Be careful not to use pins like ```A0, A1, A2 ...``` when communicating between different device types, as Arduino Core may refer to wrong pins in such cases.
Example code for device A which will send values to device B:
```cpp
WidgetBridge bridge1(V1); //Initiating Bridge Widget on V1 of Device A
...
void setup() {
Blynk.begin(...);
while (Blynk.connect() == false) {
// Wait until Blynk is connected
}
bridge1.digitalWrite(9, HIGH); // will trigger D9 HIGH on Device B. No code on Device B required
bridge1.analogWrite(10, 123);
bridge1.virtualWrite(V1, "hello"); // you need to write code on Device B in order to receive this value. See below
bridge1.virtualWrite(V2, "value1", "value2", "value3");
}
BLYNK_CONNECTED() {
bridge1.setAuthToken("OtherAuthToken"); // Token of the hardware B
}
```
**IMPORTANT:** when performing ```virtualWrite()``` with Bridge Widget, Device B would need to process the incoming data from Device A.
For example, if you are sending value from Device A to Device B using ```bridge.virtualWrite(V5)``` you would need to use this handler on Device B:
```cpp
BLYNK_WRITE(V5){
int pinData = param.asInt(); //pinData variable will store value that came via Bridge
}
```
Keep in mind that ```bridge.virtualWrite``` doesn't send any value to mobile app. You need to call ```Blynk.virtualWrite``` for that.
**Sketch:** [Bridge](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Bridge/Bridge.ino)
### Eventor
Eventor widget allows you to create simple behaviour rules or **events**.
Let's look at a typical use case: read temperature from DHT sensor and send push notification when the temperature is over a certain limit:
```cpp
float t = dht.readTemperature();
if (isnan(t)) {
return;
}
if (t > 40) {
Blynk.notify(String("Temperature is too high: ") + t);
}
```
With Eventor you don't need to write this code. All you need is to send the value from the sensor to the server:
```cpp
float t = dht.readTemperature();
Blynk.virtualWrite(V0, t);
```
Don't forget that ```virtualWrite``` commands should be wrapped in the timer and can't be used in the main loop.
Now configure new **Event** in Eventor widget:
<img src="images/eventor/eventor_for_temp_example.png" style="width: 200px; height:360px"/>
**NOTE** Don't forget to add notification widget.
Eventor comes handy when you need to change conditions on the fly without re-uploading new sketch on
the hardware. You can create as many **events** as you need.
Eventor also could be triggered from the application side.
You just need to assign the widget to the same pin as your Event within Eventor.
Eventor doesn't constantly sends events. Let's consider simple event as above ```if (temperature > 40) send notification ```.
When temperature goes beyond 40 threshold - notification action is triggered. If temperature continues to stay above the
40 threshold no actions will be triggered. But if ```temperature``` goes below threshold and then passes it again -
notification will be sent again (there is no 5 sec limit on Eventor notifications).
Eventor also supports Timer events. For example, you can set a pin ```V1``` ON/HIGH at 21:00:00 every Friday.
With Eventor Time Event you can assign multiple timers on same pin, send any string/number, select days and timezone.
In order to remove created **event** please use swipe. You can also swipe out last element in the Event itself.
**NOTE:** The timer widget rely on the server time and not your phone time. Sometimes the phone time may not match the server time.
**NOTE:** Events are triggered only once when the condition is met. That's mean
[chaining of events](https://community.blynk.cc/t/eventor-behavior-bug-feature/20962) is not possible (however, could be enabled for commercials).
<img src="images/eventor/eventor_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [Eventor](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Eventor/Eventor.ino)
**NOTE:**: Events are triggered only once when the condition is met.
Exception:
Let's consider simple event as above ```if (temperature > 40) send notification ```.
When temperature goes beyond 40 threshold - notification action is triggered. If temperature continues to stay above the 40 threshold no actions will be triggered. But if ```temperature``` goes below threshold and then passes it again -
notification will be sent again (there is no 5 sec limit on Eventor notifications).
### RTC
Real-time clock allows you to get time from server. You can preselect any timezone on UI to get time on hardware in required locale.
No pin required for RTC widget.
<img src="images/rtc_edit.png" style="width: 200px; height:360px"/>
**Sketch:** [RTC](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/RTC/RTC.ino)
### BLE
Widget to enable Bluetooth Low Energy support. At the moment BLE widget requires
internet connection in order to login and load your profile. However this will be fixed soon. Also some Blynk
widgets are not supported within the BLE connection.
Blynk currently supports a handful of different BLE modules. Please check sketches below.
**Sketches:** [BLE](https://github.com/blynkkk/blynk-library/tree/master/examples/Boards_Bluetooth)
### Bluetooth
Widget to enable Bluetooth support. At the moment Bluetooth widget is supported only on Android and requires
internet connection to login and to load your profile. This will be fixed soon. Alsom some Blynk
widgets do not work within the Bluetooth connection.
Blynk currently supports bunch of different modules. Please check sketches below.
**Sketches:** [Bluetooth](https://github.com/blynkkk/blynk-library/tree/master/examples/Boards_Bluetooth)
### Music Player
Simple UI element with 3 buttons with common music player controls. Every button sends it's own command to hardware:
```play```, ```stop```, ```prev```, ```next```.
You can change widget state within the app from hardware side with next commands:
```
Blynk.virtualWrite(Vx, “play”);
Blynk.virtualWrite(Vx, “stop”);
```
You can also change widget play/stop state with next code (equivalent to above commands):
```Blynk.setProperty(V1, "isOnPlay", "false");```
**Sketch:** [Music Player](https://github.com/blynkkk/blynk-library/blob/master/examples/Widgets/Player/Player.ino)
### Webhook
Webhook is a widget designed to communicate with 3rd party services. With Webhook widget you can send HTTP(S) requests to any 3rd party service or device that has HTTP(S) API (e.g. Philips Hue bulb). You can trigger 3-d party service with a single click of a button.
Any `write` operation from hardware side will trigger Webhook Widget. You can also trigger webhook from Blynk app when a app widget is assigned to the same pin as Webhook.
For example, when you need to send data from your hardware not only to Blynk, but also to Thingspeak, you would need to write a long http request code like this (this is just an example, not a full sketch):
```
WiFiClient client;
if (client.connect("api.thingspeak.com", 80)) {
client.print("POST /update HTTP/1.1\n");
client.print("Host: api.thingspeak.com\n");
client.print("Connection: close\n");
client.print("X-THINGSPEAKAPIKEY: " + apiKeyThingspeak1 + "\n");
client.print("Content-Type: application/x-www-form-urlencoded\n");
client.print("Content-Length: ");
client.print(postStr.length());
client.print("\n\n");
client.print(postStr);
}
```
Instead, with Webhook widget you would only need to fill in these fields:
<img src="images/webhook_settings.png" style="width: 200px; height:360px"/>
And add this code on hardware side:
```
Blynk.virtualWrite(V0, value);
```
where `V0` is pin assigned to the Webhook widget.
Use standard Blynk placeholders for Pin Value in the body or URL, for example:
```
https://api.thingspeak.com/update?api_key=xxxxxx&field1=/pin/
```
or for the body
```
["/pin/"]
```
When you need to send an array of values, you can refer to a specific index of the array value. Blynk Pin can hold an array of max 10 values:
```/pin[0]/```,```/pin[1]/```, ```/pin[2]/```
You can also make GET requests from Blynk Server and get responses directly to your hardware.
For example, to get current weather from a 3rd party Weather service that uses an URL similar to this:
```http://api.sunrise-sunset.org/json?lat=33.3823&lng=35.1856&date=2016-10-01```, you would need to put this URL in Webhook widget and assign it to ```V0``` pin.
To parse the response on the hardware side:
```
BLYNK_WRITE(V0){
String webhookdata = param.asStr();
Serial.println(webhookdata);
}
```
Now, every time there is a "write" command to ```V0``` pin (e.g. with ```Blynk.virtualWrite(V0, 1)``` from hardware or from app widget assigned to ```V0```), ```BLYNK_WRITE(V0)``` construction will be triggered and processed.
**NOTE:** Usually, 3rd party servers return long responses. You have to increase the maximum allowed message size your hardware can process. Modify this line in your firmware code:
```#define BLYNK_MAX_READBYTES 1024```. Where ```1024``` - is maximum allowed message size.
**NOTE:** Blynk Cloud has limitation for Webhook Widget - you can only send 1 request per second. This can be
changed on a Local Server by changing ```webhooks.frequency.user.quota.limit```. Be careful with Webhooks,
as many 3rd party services can't handle 1 req/sec, and you can be banned on some of them.
For example, Thingspeak allows only 1 request per 15 seconds.
**NOTE:** To avoid spamming, Blynk Webhook feature has another limitation - if your Webhook requests fail 10 times in a row, Webhook Widget will be stopped. To resume it, you would need to open Widget Settings and re-save it. Failed request is a request that doesn't return `200` or `302`.
**NOTE:** Webhook widget may affect ```Blynk.syncAll()``` function when a returned response is large.
### Reports Widget
Function of Reports is to configure and customize data reports in CSV format. You can choose between one-time or continuous scheduled reports.
Also, within the Reports you can clear all the data collected by your devices.
You need to configure initial inputs in Edit mode, and then, in Play mode you will be able to customize reports.
#### Edit mode. Data inputs configuration
In edit mode (when your project is stopped) you define the Datastreams you would like to later be included in reports.
Reports widget is designed to work with the Device Tiles widget. If you don't use Device Tiles you can still select a single device or a group of devices as a source of data for reports.
You have to choose either Device Tiles or single / group of the devices for the report. You can't combine these 2 options.
#### Play mode.
After you added source devices and their Datastreams click Play button and click on the Reports button.
### Customizing Reports.
Every Report option supposes it's own settings:
```Report name``` - give your report a meaningful name.
```Data source``` - select the Datastreams you would like to be included in reports.
```Report Frequency``` - Defines how often reports will be sent. They can be one-time and scheduled.
```one-time``` - will instantly generate report and send it to the email addresses specified. Click on the right icon to send it.
Scheduled reports can be sent ```daily```/```weekly```/```monthly```.
```At Time``` will set up a time of the day the report will be sent.
```Start```/```End``` specifies start and end date the reports will continue to be sent.
For Weekly Report you can select a day of the week when report should be sent.
For Monthly report you can choose whether to send report on the first or last day of the month.
```Recipients``` - specify up to 5 email addresses.
```Data resolution``` defines granularity of your reports. Supported granularities are: ```minute```, ```hourly``` and ```daily```.
For example, when you generate daily report with 1 minute granularity you'll get ```24 * 60 * 60```
points in your daily report for every selected Datastream.
```Group data in reports by``` - specify the output format of the CSV file(s).
```Datastream``` you will get 1 CSV file for each Datastream.
```Device``` you will get 1 CSV file per each device. Each file will contain all of the included Datastreams.
```Report``` you will get 1 CSV file for all your devices and all your Datastreams.
```Timezone correction``` - specify the time zone adjustment if you need to get report date and time adjusted to a specific time zone
```Date and time format``` - defines the format of the timestamp field of your data. You can select ```2018-06-21 20:16:48```,
```2018-06-21T20:16:48+03:00``` or other supported formats.
There is one specific ```Timestamp``` format - which reflects the difference between the current time and midnight, January 1, 1970 UTC measured in milliseconds.
After the report is set up - click on "OK" button at the right upper corner. Your report is ready.
Once you configured the report you will see when is the ```Next``` report scheduled and also a schedule for this report.
After the report was sent at least once, you can see when the ```Last``` report was sent.
```Last``` label also contains the status regarding the report:
- ```OK```: the report was generated and sent to the Recipients successfully;
- ```No Data```: the report doesn't contain any data for the configured period;
- ```Error```: something went wrong. Please contact the Blynk Team support;
Reports will be generated even if your project is not in active (Play) mode. However, inactive projects don't generate any data.
**NOTE:** all reports are encoded in UTF-16. Please, make sure you selected UTF-16 as required "Character set" for your csv reader.
================================================
FILE: amendments.md
================================================
# Blynk Amendments
## Tell every maker about Blynk
No pressure. Just do it. Now.
## Make your idea work without Blynk
Blynk can be easily integrated in almost any project. But before that - make it work **without** it. After you are sure that you can get all the sensor data or can control things from the code – integrate Blynk and make it even more awesome.
## Use search
We are always happy to chat and help, but remember - e
gitextract_308jsc33/ ├── Amendments.md ├── AppExport.md ├── BlynkFirmware.md ├── BlynkMainOperations.md ├── BlynkProtocol.md ├── BlynkServer.md ├── CNAME ├── FAQ.md ├── GettingStarted.md ├── HardwareSetUps.md ├── Implementing.md ├── IntroAndDownloads.md ├── License.md ├── Links.md ├── OTA.md ├── README.md ├── Roadmap.md ├── SUMMARY.md ├── Security.md ├── Sharing.md ├── SupportedHardware.md ├── Troubleshooting.md ├── Widgets-RU.md ├── Widgets.md ├── amendments.md ├── api/ │ ├── README.md │ ├── api_getlastweekdata.md │ ├── events-api.md │ └── external_api.md ├── appexport.md ├── blynkfirmware.md ├── blynkmainoperations.md ├── blynkprotocol.md ├── blynkserver.md ├── css/ │ └── style.css ├── en/ │ ├── README.md │ ├── api/ │ │ └── README.md │ ├── infra/ │ │ └── backup_policy_FAQ.md │ └── product/ │ ├── README.md │ └── product-template-settings/ │ ├── README.md │ ├── dashboard.md │ ├── datastreams/ │ │ ├── README.md │ │ ├── datastream_alias.md │ │ ├── datastream_automation.md │ │ ├── datastream_datatype.md │ │ ├── datastream_default_value.md │ │ ├── datastream_deicmals.md │ │ ├── datastream_feedback.md │ │ ├── datastream_invalidate.md │ │ ├── datastream_min_max.md │ │ ├── datastream_name.md │ │ ├── datastream_save_raw.md │ │ ├── datastream_sync.md │ │ └── datastream_virtual_pin.md │ ├── events/ │ │ ├── README.md │ │ ├── event_code.md │ │ ├── event_name.md │ │ ├── event_notification.md │ │ ├── event_notification_period.md │ │ └── event_online_offline.md │ ├── general-settings/ │ │ ├── README.md │ │ ├── product_manufacturer.md │ │ └── product_offline_ignore_period.md │ └── metadata.md ├── en-product/ │ ├── create-new-product.md │ ├── dashboard/ │ │ └── chart.md │ ├── datastreams/ │ │ ├── README.md │ │ ├── datastream-alias.md │ │ ├── datastream-data-type.md │ │ ├── datastream-invalidate-value.md │ │ ├── datastream-min-max-values.md │ │ ├── datastream-name.md │ │ ├── datastream-save-raw-data.md │ │ ├── datastream-virtual-pin.md │ │ ├── decimals-formatting.md │ │ ├── default-value.md │ │ ├── expose-to-automation.md │ │ ├── sync-with-the-latest-server-value.md │ │ └── wait-for-confirmation-from-the-device.md │ ├── events/ │ │ ├── README.md │ │ ├── events-code.md │ │ ├── events-name.md │ │ ├── events-notification-period.md │ │ ├── events-notification.md │ │ └── events-online-offline.md │ ├── general-settings/ │ │ ├── README.md │ │ ├── manufacturer.md │ │ └── offline-ignore-period.md │ ├── metadata.md │ ├── mobile-app-ui.md │ └── web-dashboard.md ├── faq.md ├── firmware-api/ │ ├── README.md │ └── disable-widgets-in-the-app.md ├── firmware-api-1/ │ └── disable-widgets-in-the-app.md ├── gettingstarted.md ├── google-code-prettify/ │ ├── CHANGES.html │ ├── COPYING │ ├── Makefile │ ├── README.html │ ├── examples/ │ │ └── quine.html │ ├── js-modules/ │ │ ├── combinePrefixPatterns.js │ │ ├── externs.js │ │ ├── extractSourceSpans.js │ │ ├── extractSourceSpans_test.html │ │ ├── js_include.pl │ │ ├── numberLines.js │ │ ├── numberLines_test.html │ │ ├── prettify.js │ │ ├── recombineTagsAndDecorations.js │ │ ├── recombineTagsAndDecorations_test.html │ │ ├── regexpPrecederPatterns.pl │ │ └── run_prettify.js │ ├── src/ │ │ ├── lang-apollo.js │ │ ├── lang-basic.js │ │ ├── lang-clj.js │ │ ├── lang-css.js │ │ ├── lang-dart.js │ │ ├── lang-erlang.js │ │ ├── lang-go.js │ │ ├── lang-hs.js │ │ ├── lang-lisp.js │ │ ├── lang-llvm.js │ │ ├── lang-lua.js │ │ ├── lang-matlab.js │ │ ├── lang-ml.js │ │ ├── lang-mumps.js │ │ ├── lang-n.js │ │ ├── lang-pascal.js │ │ ├── lang-proto.js │ │ ├── lang-r.js │ │ ├── lang-rd.js │ │ ├── lang-scala.js │ │ ├── lang-sql.js │ │ ├── lang-tcl.js │ │ ├── lang-tex.js │ │ ├── lang-vb.js │ │ ├── lang-vhdl.js │ │ ├── lang-wiki.js │ │ ├── lang-xq.js │ │ ├── lang-yaml.js │ │ ├── prettify.css │ │ ├── prettify.js │ │ └── run_prettify.js │ ├── styles/ │ │ ├── demo.html │ │ ├── desert.css │ │ ├── doxy.css │ │ ├── index.html │ │ ├── sons-of-obsidian.css │ │ └── sunburst.css │ ├── tests/ │ │ ├── debug-ie-compat-matrix.html │ │ ├── ie-newline-copy-paste.html │ │ ├── large_input_test.html │ │ ├── prettify_test.html │ │ ├── prettify_test_2.html │ │ ├── run_prettify_test.html │ │ ├── test_base.js │ │ └── test_styles.css │ └── tools/ │ ├── closure-compiler/ │ │ ├── COPYING │ │ ├── README │ │ ├── amd-externs.js │ │ ├── compiler.jar │ │ └── console-externs.js │ ├── cut-release.sh │ ├── googlecode_upload.py │ ├── lang-handler-aliases.sh │ └── yui-compressor/ │ ├── LICENSE.TXT │ ├── README │ └── yuicompressor-2.4.4.jar ├── hardwaresetups.md ├── http.md ├── https-api/ │ ├── api_getlastweekdata.md │ ├── events-api.md │ └── external_api.md ├── implementing.md ├── index.html ├── introanddownloads.md ├── license.md ├── links.md ├── mobile/ │ ├── README.md │ ├── accelerometer.md │ ├── barometer.md │ ├── ble.md │ ├── bluetooth.md │ ├── bridge.md │ ├── button.md │ ├── datastreams.md │ ├── device_selector.md │ ├── device_tiles.md │ ├── email.md │ ├── eventor.md │ ├── gauge.md │ ├── gps_streaming.md │ ├── gps_trigger.md │ ├── graph.md │ ├── gravity.md │ ├── humidity.md │ ├── image.md │ ├── joystick.md │ ├── labeled_value.md │ ├── labeled_value_display.md │ ├── lcd.md │ ├── led.md │ ├── level_display.md │ ├── light.md │ ├── map.md │ ├── menu.md │ ├── music_player.md │ ├── notification.md │ ├── numberInput.md │ ├── number_input.md │ ├── proximity.md │ ├── report.md │ ├── rgb.md │ ├── rtc.md │ ├── ru/ │ │ ├── accelerometer.md │ │ ├── barometer.md │ │ ├── ble.md │ │ ├── bluetooth.md │ │ ├── bridge.md │ │ ├── button.md │ │ ├── device_selector.md │ │ ├── device_tiles.md │ │ ├── email.md │ │ ├── eventor.md │ │ ├── gauge.md │ │ ├── gps_streaming.md │ │ ├── gps_trigger.md │ │ ├── graph.md │ │ ├── gravity.md │ │ ├── humidity.md │ │ ├── image.md │ │ ├── joystick.md │ │ ├── labeled_value.md │ │ ├── labeled_value_display.md │ │ ├── lcd.md │ │ ├── led.md │ │ ├── level_display.md │ │ ├── light.md │ │ ├── map.md │ │ ├── menu.md │ │ ├── music_player.md │ │ ├── notification.md │ │ ├── numberInput.md │ │ ├── number_input.md │ │ ├── proximity.md │ │ ├── report.md │ │ ├── rgb.md │ │ ├── rtc.md │ │ ├── segmentedSwitch.md │ │ ├── segmented_control.md │ │ ├── slider.md │ │ ├── step.md │ │ ├── styled_button.md │ │ ├── super_chart.md │ │ ├── table.md │ │ ├── tabs.md │ │ ├── temperature.md │ │ ├── terminal.md │ │ ├── textInput.md │ │ ├── text_input.md │ │ ├── time_input.md │ │ ├── timeinput.md │ │ ├── timer.md │ │ ├── twitter.md │ │ ├── value_display.md │ │ ├── video.md │ │ └── webhook.md │ ├── segmentedSwitch.md │ ├── segmented_control.md │ ├── slider.md │ ├── step.md │ ├── styled_button.md │ ├── super_chart.md │ ├── table.md │ ├── tabs.md │ ├── temperature.md │ ├── terminal.md │ ├── textInput.md │ ├── text_input.md │ ├── time_input/ │ │ ├── README.md │ │ └── untitled-1.md │ ├── time_input.md │ ├── timeinput.md │ ├── timer.md │ ├── twitter.md │ ├── value_display.md │ ├── video.md │ └── webhook.md ├── mobile-app/ │ └── untitled.md ├── new/ │ └── en/ │ ├── product_categories.md │ ├── product_hotspot_prefix.md │ └── product_template_ids.md ├── ota.md ├── roadmap.md ├── ru/ │ ├── Amendments.md │ ├── AppExport.md │ ├── BlynkFirmware.md │ ├── BlynkMainOperations.md │ ├── BlynkProtocol.md │ ├── BlynkServer.md │ ├── FAQ.md │ ├── GettingStarted.md │ ├── HardwareSetUps.md │ ├── Implementing.md │ ├── IntroAndDownloads.md │ ├── License.md │ ├── Links.md │ ├── OTA.md │ ├── README.md │ ├── Roadmap.md │ ├── Security.md │ ├── Sharing.md │ ├── SupportedHardware.md │ ├── Troubleshooting.md │ ├── Widgets.md │ ├── amendments.md │ ├── appexport.md │ ├── blynkfirmware.md │ ├── blynkmainoperations.md │ ├── blynkprotocol.md │ ├── blynkserver.md │ ├── faq.md │ ├── gettingstarted.md │ ├── hardwaresetups.md │ ├── http.md │ ├── implementing.md │ ├── introanddownloads.md │ ├── license.md │ ├── links.md │ ├── ota.md │ ├── readme.md │ ├── roadmap.md │ ├── ru.md │ ├── security.md │ ├── sharing.md │ ├── supportedhardware.md │ ├── troubleshooting.md │ └── widgets.md ├── scripts/ │ ├── flatdoc.js │ ├── legacy.js │ └── script.js ├── security.md ├── sharing.md ├── supportedhardware.md ├── table.css ├── themes/ │ ├── blynk.css │ └── prism.css ├── troubleshooting.md ├── untitled/ │ ├── README.md │ ├── accelerometer.md │ ├── archive/ │ │ ├── README.md │ │ ├── bad-request-github.md │ │ ├── joystick.md │ │ └── super_chart.md │ ├── barometer.md │ ├── ble.md │ ├── blob/ │ │ ├── README.md │ │ ├── master.md │ │ ├── menu/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-1.md │ │ ├── proximity.md │ │ ├── styled_button/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io.md │ │ ├── textinput.md │ │ └── timeinput/ │ │ ├── README.md │ │ └── blynkkk-blynkkk.github.io-2.md │ ├── bluetooth.md │ ├── blynkkk-blynkkk.github.io/ │ │ ├── README.md │ │ └── gps_trigger.md │ ├── blynkkk-blynkkk.github.io-1/ │ │ ├── README.md │ │ └── rtc.md │ ├── blynkkk-blynkkk.github.io-2/ │ │ ├── README.md │ │ └── eventor.md │ ├── blynkkk-blynkkk.github.io-3/ │ │ ├── README.md │ │ └── email.md │ ├── blynkkk-blynkkk.github.io-4/ │ │ ├── README.md │ │ └── tabs.md │ ├── blynkkk-blynkkk.github.io-5/ │ │ ├── README.md │ │ └── map.md │ ├── blynkkk-blynkkk.github.io-6/ │ │ ├── README.md │ │ └── ble.md │ ├── blynkkk-blynkkk.github.io-7/ │ │ ├── README.md │ │ └── device_tiles.md │ ├── blynkkk-blynkkk.github.io-8/ │ │ ├── README.md │ │ └── temperature.md │ ├── blynkkk-blynkkk.github.io-9/ │ │ ├── README.md │ │ └── value_display.md │ ├── bridge.md │ ├── build-software-better-together/ │ │ ├── README.md │ │ └── video.md │ ├── button.md │ ├── commit/ │ │ ├── README.md │ │ ├── change-float-to-double-41-b1f1a43.md │ │ ├── gauge.md │ │ └── music_player.md │ ├── commits/ │ │ ├── README.md │ │ ├── blynkkk-blynkkk.github.io.md │ │ ├── light.md │ │ └── time_input.md │ ├── device_selector.md │ ├── device_tiles.md │ ├── email.md │ ├── eventor.md │ ├── find/ │ │ ├── README.md │ │ ├── blynkkk-blynkkk.github.io.md │ │ ├── image.md │ │ └── terminal.md │ ├── gauge.md │ ├── gps_streaming.md │ ├── gps_trigger.md │ ├── graph.md │ ├── gravity.md │ ├── humidity.md │ ├── image.md │ ├── joystick.md │ ├── labeled_value.md │ ├── labeled_value_display.md │ ├── lcd.md │ ├── led.md │ ├── level_display.md │ ├── light.md │ ├── map.md │ ├── menu.md │ ├── music_player.md │ ├── network/ │ │ ├── README.md │ │ ├── blynkkk-blynkkk.github.io.md │ │ ├── numberinput.md │ │ └── slider.md │ ├── notification.md │ ├── number_input.md │ ├── numberinput.md │ ├── proximity.md │ ├── pull/ │ │ ├── README.md │ │ ├── change-float-to-double-by-earlold-pull-request-41.md │ │ ├── text_input.md │ │ └── webhook.md │ ├── report.md │ ├── rgb.md │ ├── rtc.md │ ├── ru.md │ ├── segmented_control.md │ ├── segmentedswitch.md │ ├── slider.md │ ├── step.md │ ├── styled_button.md │ ├── super_chart.md │ ├── table.md │ ├── tabs.md │ ├── temperature.md │ ├── terminal.md │ ├── textinput.md │ ├── timeinput.md │ ├── timer.md │ ├── tree/ │ │ ├── README.md │ │ ├── accelerometer/ │ │ │ ├── README.md │ │ │ └── new.md │ │ ├── barometer.md │ │ ├── bluetooth/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-4.md │ │ ├── blynkkk-blynkkk.github.io.md │ │ ├── bridge.md │ │ ├── button/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-3.md │ │ ├── device_selector.md │ │ ├── gps_streaming.md │ │ ├── graph/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-6.md │ │ ├── gravity/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-5.md │ │ ├── humidity/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-1.md │ │ ├── labeled_value.md │ │ ├── labeled_value_display.md │ │ ├── lcd.md │ │ ├── led.md │ │ ├── level_display.md │ │ ├── master.md │ │ ├── notification.md │ │ ├── number_input/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io.md │ │ ├── report.md │ │ ├── rgb.md │ │ ├── segmented_control/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io-2.md │ │ ├── segmentedswitch.md │ │ ├── step.md │ │ ├── table/ │ │ │ ├── README.md │ │ │ └── blynkkk-blynkkk.github.io.md │ │ ├── timer.md │ │ └── twitter.md │ ├── twitter.md │ ├── value_display.md │ ├── video.md │ └── webhook.md ├── widgets-ru.md └── widgets.md
SYMBOL INDEX (79 symbols across 14 files)
FILE: google-code-prettify/js-modules/combinePrefixPatterns.js
function combinePrefixPatterns (line 9) | function combinePrefixPatterns(regexs) {
FILE: google-code-prettify/js-modules/extractSourceSpans.js
function extractSourceSpans (line 46) | function extractSourceSpans(node, isPreformatted) {
FILE: google-code-prettify/js-modules/numberLines.js
function numberLines (line 12) | function numberLines(node, opt_startLineNum, isPreformatted) {
FILE: google-code-prettify/js-modules/prettify.js
function appendDecorations (line 225) | function appendDecorations(basePos, sourceCode, langHandler, out) {
function childContentWrapper (line 248) | function childContentWrapper(element) {
function createSimpleLexer (line 307) | function createSimpleLexer(shortcutStylePatterns, fallthroughStylePatter...
function sourceDecorator (line 450) | function sourceDecorator(options) {
function registerLangHandler (line 647) | function registerLangHandler(handler, fileExtensions) {
function langHandlerForExtension (line 657) | function langHandlerForExtension(extension, source) {
function applyDecorator (line 772) | function applyDecorator(job) {
function $prettyPrintOne (line 805) | function $prettyPrintOne(sourceCodeHtml, opt_langExtension, opt_numberLi...
function $prettyPrint (line 839) | function $prettyPrint(opt_whenDone, opt_root) {
FILE: google-code-prettify/js-modules/recombineTagsAndDecorations.js
function recombineTagsAndDecorations (line 15) | function recombineTagsAndDecorations(job) {
FILE: google-code-prettify/js-modules/run_prettify.js
function contentLoaded (line 72) | function contentLoaded(callback) {
function loadStylesheetsFallingBack (line 112) | function loadStylesheetsFallingBack(stylesheets) {
function checkPendingLanguages (line 207) | function checkPendingLanguages() {
function onLangsLoaded (line 229) | function onLangsLoaded() {
FILE: google-code-prettify/src/prettify.js
function combinePrefixPatterns (line 250) | function combinePrefixPatterns(regexs) {
function extractSourceSpans (line 528) | function extractSourceSpans(node, isPreformatted) {
function appendDecorations (line 580) | function appendDecorations(basePos, sourceCode, langHandler, out) {
function childContentWrapper (line 603) | function childContentWrapper(element) {
function createSimpleLexer (line 662) | function createSimpleLexer(shortcutStylePatterns, fallthroughStylePatter...
function sourceDecorator (line 805) | function sourceDecorator(options) {
function numberLines (line 991) | function numberLines(node, opt_startLineNum, isPreformatted) {
function recombineTagsAndDecorations (line 1127) | function recombineTagsAndDecorations(job) {
function registerLangHandler (line 1255) | function registerLangHandler(handler, fileExtensions) {
function langHandlerForExtension (line 1265) | function langHandlerForExtension(extension, source) {
function applyDecorator (line 1380) | function applyDecorator(job) {
function $prettyPrintOne (line 1413) | function $prettyPrintOne(sourceCodeHtml, opt_langExtension, opt_numberLi...
function $prettyPrint (line 1447) | function $prettyPrint(opt_whenDone, opt_root) {
FILE: google-code-prettify/src/run_prettify.js
function contentLoaded (line 76) | function contentLoaded(callback) {
function loadStylesheetsFallingBack (line 116) | function loadStylesheetsFallingBack(stylesheets) {
function checkPendingLanguages (line 211) | function checkPendingLanguages() {
function combinePrefixPatterns (line 472) | function combinePrefixPatterns(regexs) {
function extractSourceSpans (line 750) | function extractSourceSpans(node, isPreformatted) {
function appendDecorations (line 802) | function appendDecorations(basePos, sourceCode, langHandler, out) {
function childContentWrapper (line 825) | function childContentWrapper(element) {
function createSimpleLexer (line 884) | function createSimpleLexer(shortcutStylePatterns, fallthroughStylePatter...
function sourceDecorator (line 1027) | function sourceDecorator(options) {
function numberLines (line 1213) | function numberLines(node, opt_startLineNum, isPreformatted) {
function recombineTagsAndDecorations (line 1349) | function recombineTagsAndDecorations(job) {
function registerLangHandler (line 1477) | function registerLangHandler(handler, fileExtensions) {
function langHandlerForExtension (line 1487) | function langHandlerForExtension(extension, source) {
function applyDecorator (line 1602) | function applyDecorator(job) {
function $prettyPrintOne (line 1635) | function $prettyPrintOne(sourceCodeHtml, opt_langExtension, opt_numberLi...
function $prettyPrint (line 1669) | function $prettyPrint(opt_whenDone, opt_root) {
function onLangsLoaded (line 1884) | function onLangsLoaded() {
FILE: google-code-prettify/tests/test_base.js
function isRawContent (line 11) | function isRawContent(node) {
function isPreformatted (line 19) | function isPreformatted(node, content) {
function normalizedHtml (line 92) | function normalizedHtml(node, out, opt_sortAttrs) {
function go (line 136) | function go(goldens) {
function runTests (line 141) | function runTests(goldens) {
function startClock (line 243) | function startClock() {
function stopClock (line 247) | function stopClock() {
FILE: google-code-prettify/tools/closure-compiler/amd-externs.js
function define (line 6) | function define(id, dependencies, factory) {}
FILE: google-code-prettify/tools/googlecode_upload.py
function upload (line 59) | def upload(file, project_name, user_name, password, summary, labels=None):
function encode_upload_request (line 110) | def encode_upload_request(fields, file_path):
function upload_find_auth (line 155) | def upload_find_auth(file_path, project_name, summary, labels=None,
function main (line 209) | def main():
FILE: scripts/flatdoc.js
function loadData (line 52) | function loadData(locations, response, callback) {
function mkdir_p (line 255) | function mkdir_p(level) {
function process (line 369) | function process(node, $parent) {
function getTextNodesIn (line 503) | function getTextNodesIn(el) {
function quotify (line 511) | function quotify(a) {
function e (line 531) | function e(e){this.tokens=[];this.tokens.links={};this.options=e||a.defa...
function s (line 531) | function s(t,e){this.options=e||a.defaults;this.links=t;this.rules=n.nor...
function i (line 531) | function i(t){this.tokens=[];this.token=null;this.options=t||a.defaults}
function r (line 531) | function r(t,e){return t.replace(!e?/&(?!#?\w+;)/g:/&/g,"&").replace...
function l (line 531) | function l(t,e){t=t.source;e=e||"";return function n(s,i){if(!s)return n...
function o (line 531) | function o(){}
function h (line 531) | function h(t){var e=1,n,s;for(;e<arguments.length;e++){n=arguments[e];fo...
function a (line 531) | function a(t,n,s){if(s||typeof n==="function"){if(!s){s=n;n=null}if(n)n=...
FILE: scripts/legacy.js
function m (line 23) | function m(){var a=e.elements;return"string"==typeof a?a.split(" "):a}
function i (line 23) | function i(a){var b=n[a[o]];b||(b={},h++,a[o]=h,n[h]=b);return b}
function p (line 23) | function p(a,b,c){b||(b=f);if(g)return b.createElement(a);c||(c=i(b));b=...
function t (line 23) | function t(a,b){if(!b.cache)b.cache={},b.createElem=a.createElement,b.cr...
function q (line 24) | function q(a){a||(a=f);var b=i(a);if(e.shivCSS&&!j&&!b.hasCSS){var c,d=a...
function callMedia (line 360) | function callMedia(){
FILE: scripts/script.js
function onClick (line 200) | function onClick(e) {
Condensed preview — 497 files, each showing path, character count, and a content snippet. Download the .json file or copy for the full structured content (2,921K chars).
[
{
"path": "Amendments.md",
"chars": 741,
"preview": "#Blynk Amendments\n###Tell every maker about Blynk\nNo pressure. Just do it. Now.\n###Make your idea work without Blynk\nBly"
},
{
"path": "AppExport.md",
"chars": 1326,
"preview": "# App Export\n\n## Firmware for ESP8266, NodeMCU, BlynkBoard, etc.\n\n#### Prepare development environment\n1. Install [Ardui"
},
{
"path": "BlynkFirmware.md",
"chars": 11512,
"preview": "#Blynk Firmware\n## Configuration\n\n### Blynk.begin()\n\nThe easiest way to configure Blynk is to use ```Blynk.begin()```:\n\n"
},
{
"path": "BlynkMainOperations.md",
"chars": 15195,
"preview": "# Blynk main operations\n\n## Virtual Pins\nBlynk can control Digital and Analog I/O Pins on you hardware directly. You don"
},
{
"path": "BlynkProtocol.md",
"chars": 3599,
"preview": "# Blynk protocol\n\nBlynk transfers binary messages with the following structure:\n\n| Command | Message Id | Lengt"
},
{
"path": "BlynkServer.md",
"chars": 34,
"preview": "# Blynk server\nNo longer supported"
},
{
"path": "CNAME",
"chars": 13,
"preview": "docs.blynk.cc"
},
{
"path": "FAQ.md",
"chars": 3010,
"preview": "#FAQ\n\n- I backed Blynk on Kickstarter. Where are my widgets and why the app is free?\n> App is free because otherwise you"
},
{
"path": "GettingStarted.md",
"chars": 5975,
"preview": "#Getting Started \nLet's get you started in 5 minutes (reading doesn't count!). \nWe will switch on an LED connected to y"
},
{
"path": "HardwareSetUps.md",
"chars": 7601,
"preview": "# Hardware set-ups\n## Arduino over USB (no shield)\nIf you don't have any shield and your hardware doesn't have any conne"
},
{
"path": "Implementing.md",
"chars": 2547,
"preview": "# Implementing a Blynk HW client (library)\nCurrently we provide Arduino/C++ implementation of the library.\nIt is very ex"
},
{
"path": "IntroAndDownloads.md",
"chars": 4323,
"preview": "# Intro\n\n<h2 class=\"banner-header\">🚨🚨🚨 IMPORTANT:</h2> \n\n<p class=\"banner\">\n This documentation is for the LEGACY versi"
},
{
"path": "License.md",
"chars": 63,
"preview": "# License\nThis project is released under The MIT License (MIT)\n"
},
{
"path": "Links.md",
"chars": 513,
"preview": "#Links\n\n* [Blynk site](https://www.blynk.cc)\n* [Blynk community](https://community.blynk.cc)\n* [Facebook](https://www.fb"
},
{
"path": "OTA.md",
"chars": 3491,
"preview": "#OTA\n\nBlynk also supports over the air updates for - ESP8266, NodeMCU and SparkFun Blynk boards. OTA supported only \nfor"
},
{
"path": "README.md",
"chars": 962,
"preview": "# This documentation is no longer maintained and supported. Latest documentation is available here: https://docs.blynk.i"
},
{
"path": "Roadmap.md",
"chars": 1037,
"preview": "#Roadmap\n\nWe build Blynk based on Blynkers feedback but with limited resources we have to prioritize our features. At th"
},
{
"path": "SUMMARY.md",
"chars": 2214,
"preview": "# Table of contents\n\n* [What is Blynk](README.md)\n\n## overview\n\n* [Blynk Components](overview/blynk-components.md)\n\n## P"
},
{
"path": "Security.md",
"chars": 1674,
"preview": "#Security\n\nBlynk server has 5 ports open for different security levels.\n\n* **80** - plain TCP connection for the hardwar"
},
{
"path": "Sharing.md",
"chars": 2712,
"preview": "#Sharing\nBlynk offers two types of sharing your projects with other people:\n\n- **Share access to your hardware.** Think "
},
{
"path": "SupportedHardware.md",
"chars": 4902,
"preview": "# Supported Hardware\n\n**Attention!** This documentation is for the LEGACY version of Blynk platform which is no longer s"
},
{
"path": "Troubleshooting.md",
"chars": 4959,
"preview": "# Troubleshooting\n\n## Connection\n\nIf you experience connection problems, follow these steps:\n\n1. Check that your hardwar"
},
{
"path": "Widgets-RU.md",
"chars": 65024,
"preview": "<h2 class=\"banner-header\"> 🚨🚨🚨 ВАЖНО:</h2> \n\n<p class=\"banner\">\n Эта документация предназначена для УСТАРЕВШЕЙ версии п"
},
{
"path": "Widgets.md",
"chars": 53145,
"preview": "#Widgets\nWidgets are interface modules. Each of them performs a specific input/ output function when communicating with "
},
{
"path": "amendments.md",
"chars": 754,
"preview": "# Blynk Amendments\n\n## Tell every maker about Blynk\n\nNo pressure. Just do it. Now.\n\n## Make your idea work without Blynk"
},
{
"path": "api/README.md",
"chars": 13,
"preview": "# HTTPs API\n\n"
},
{
"path": "api/api_getlastweekdata.md",
"chars": 239,
"preview": "# Download Datastream Data\n\nTo get the device data for last week, use this API call:\n\n**API call:**\n\n```text\napi/externa"
},
{
"path": "api/events-api.md",
"chars": 690,
"preview": "# Events API\n\nTo trigger [Events](../product/events/) creation from hardware \\(or other sources\\) and render them on Tim"
},
{
"path": "api/external_api.md",
"chars": 592,
"preview": "# Datastreams API\n\n## Hardware\n\nGet datastream value \\(via HTTP GET\\):\n\n* `/external/api/get?token={token}&pin={pin}`\n* "
},
{
"path": "appexport.md",
"chars": 1423,
"preview": "# App Export\n\n## Firmware for ESP8266, NodeMCU, BlynkBoard, etc.\n\n### Prepare development environment\n\n1. Install [Ardui"
},
{
"path": "blynkfirmware.md",
"chars": 11445,
"preview": "# Blynk Firmware\n\n## Configuration\n\n### Blynk.begin\\(\\)\n\nThe easiest way to configure Blynk is to use `Blynk.begin()`:\n\n"
},
{
"path": "blynkmainoperations.md",
"chars": 14752,
"preview": "# Blynk main operations\n\n## Virtual Pins\n\nBlynk can control Digital and Analog I/O Pins on you hardware directly. You do"
},
{
"path": "blynkprotocol.md",
"chars": 3553,
"preview": "# Blynk protocol\n\nBlynk transfers binary messages with the following structure:\n\n| Command | Message Id | Length/Status "
},
{
"path": "blynkserver.md",
"chars": 38,
"preview": "# Blynk server\n\nNo longer supported.\n\n"
},
{
"path": "css/style.css",
"chars": 19647,
"preview": "/*\n\nPlease don't edit this file directly.\nInstead, edit the stylus (.styl) files and compile it to CSS on your machine.\n"
},
{
"path": "en/README.md",
"chars": 6,
"preview": "# EN\n\n"
},
{
"path": "en/api/README.md",
"chars": 7,
"preview": "# API\n\n"
},
{
"path": "en/infra/backup_policy_FAQ.md",
"chars": 1250,
"preview": "**- What is backed up?**\n \nEverything. Users, devices, their data, etc.\n\n**- Where are backups stored?**\n\nThey are sto"
},
{
"path": "en/product/README.md",
"chars": 82,
"preview": "---\ndescription: How Product templates work on Blynk IoT platform\n---\n\n# Product\n\n"
},
{
"path": "en/product/product-template-settings/README.md",
"chars": 29,
"preview": "# Product Template Settings\n\n"
},
{
"path": "en/product/product-template-settings/dashboard.md",
"chars": 13,
"preview": "# Dashboard\n\n"
},
{
"path": "en/product/product-template-settings/datastreams/README.md",
"chars": 15,
"preview": "# Datastreams\n\n"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_alias.md",
"chars": 332,
"preview": "# Datastream: Alias\n\nAlias is an alternative Datastream name which can be changed by the end-user. For example, it can b"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_automation.md",
"chars": 1535,
"preview": "# datastream\\_automation\n\n## Datastream: Expose to Automation\n\nThis setting makes current Datastream available for Autom"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_datatype.md",
"chars": 808,
"preview": "# Datastream: Data Type\n\nEvery Datastream has a Data Type setting. Data Type is used to specify the type and format of t"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_default_value.md",
"chars": 947,
"preview": "# Datastream: Default Value\n\nDefault Value is a setting that allows you to set the initial value for the Datastream. Thi"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_deicmals.md",
"chars": 585,
"preview": "# Datastream: Decimals\n\nThis setting defines the formatting of the incoming value.\n\nDecimals formatting is available for"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_feedback.md",
"chars": 1192,
"preview": "# Datastream: Wait for confirmation from the device\n\nIn some cases, it's crucial to get a confirmation that hardware has"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_invalidate.md",
"chars": 1102,
"preview": "# Datastream: Invalidate Value\n\nUse this setting to manage the _freshness_ of the data. When enabled, the server will au"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_min_max.md",
"chars": 834,
"preview": "# Datastream: Min/Max values\n\n**Min / Max** fields are used to specify the range of incoming values. This setting is app"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_name.md",
"chars": 171,
"preview": "# Datastream: Name\n\nAlways try to give a meaningful name to the Datastream as it's extensively used across the platform."
},
{
"path": "en/product/product-template-settings/datastreams/datastream_save_raw.md",
"chars": 294,
"preview": "# Datastream: Save Raw Data\n\nThis setting allows storing raw data \\(uncompressed, non-aggregated\\).\n\nBy default, data on"
},
{
"path": "en/product/product-template-settings/datastreams/datastream_sync.md",
"chars": 884,
"preview": "# Datastream: Sync with the latest server value\n\nThis setting enables the device to sync with the latest known value on "
},
{
"path": "en/product/product-template-settings/datastreams/datastream_virtual_pin.md",
"chars": 1589,
"preview": "# Datastream: Virtual Pin\n\nVirtual Pin is a way to exchange data between hardware, web, and mobile apps. Think about Vir"
},
{
"path": "en/product/product-template-settings/events/README.md",
"chars": 10,
"preview": "# Events\n\n"
},
{
"path": "en/product/product-template-settings/events/event_code.md",
"chars": 1053,
"preview": "# Events: Code\n\nEvent code is used in firmware API to trigger and render events from the device.\n\n**IMPORTANT:** Event c"
},
{
"path": "en/product/product-template-settings/events/event_name.md",
"chars": 154,
"preview": "# Events: Name\n\nGive your event a meaningful name because it will be shown to end-users.\n\n**IMPORTANT:** Event name shou"
},
{
"path": "en/product/product-template-settings/events/event_notification.md",
"chars": 1247,
"preview": "# Events: Notification\n\nEvery event can additionally trigger notifications.\n\nYou can:\n\n* Send Emails\n* Send Push Notific"
},
{
"path": "en/product/product-template-settings/events/event_notification_period.md",
"chars": 592,
"preview": "# Events: Notification Period\n\nNotification Period defines how often notifications are sent for this particular event.\n\n"
},
{
"path": "en/product/product-template-settings/events/event_online_offline.md",
"chars": 446,
"preview": "# Events: Online, Offline\n\nOnline and Offline events are system events handled by the server.\n\nThese events tell the cur"
},
{
"path": "en/product/product-template-settings/general-settings/README.md",
"chars": 20,
"preview": "# General Settings\n\n"
},
{
"path": "en/product/product-template-settings/general-settings/product_manufacturer.md",
"chars": 286,
"preview": "# Manufacturer\n\nIs the name of a Manufacturer that makes your product. This field used in multiple places on the UI and "
},
{
"path": "en/product/product-template-settings/general-settings/product_offline_ignore_period.md",
"chars": 579,
"preview": "# Offline Ignore Period\n\nOffline ignore period is an option that allows you to hide \"offline\" event on the device timeli"
},
{
"path": "en/product/product-template-settings/metadata.md",
"chars": 12,
"preview": "# Metadata\n\n"
},
{
"path": "en-product/create-new-product.md",
"chars": 91,
"preview": "---\ndescription: How to create new Product on Blynk IoT platform\n---\n\n# What is a Product\n\n"
},
{
"path": "en-product/dashboard/chart.md",
"chars": 1626,
"preview": " \n Chart is used to visualise live and historical data. You can use it for sensor data, for binary event logging "
},
{
"path": "en-product/datastreams/README.md",
"chars": 15,
"preview": "# Datastreams\n\n"
},
{
"path": "en-product/datastreams/datastream-alias.md",
"chars": 21,
"preview": "# Datastream: Alias\n\n"
},
{
"path": "en-product/datastreams/datastream-data-type.md",
"chars": 25,
"preview": "# Datastream: Data Type\n\n"
},
{
"path": "en-product/datastreams/datastream-invalidate-value.md",
"chars": 32,
"preview": "# Datastream: Invalidate Value\n\n"
},
{
"path": "en-product/datastreams/datastream-min-max-values.md",
"chars": 30,
"preview": "# Datastream: Min/Max values\n\n"
},
{
"path": "en-product/datastreams/datastream-name.md",
"chars": 19,
"preview": "# Datastream Name\n\n"
},
{
"path": "en-product/datastreams/datastream-save-raw-data.md",
"chars": 29,
"preview": "# Datastream: Save Raw Data\n\n"
},
{
"path": "en-product/datastreams/datastream-virtual-pin.md",
"chars": 27,
"preview": "# Datastream: Virtual Pin\n\n"
},
{
"path": "en-product/datastreams/decimals-formatting.md",
"chars": 23,
"preview": "# Decimals Formatting\n\n"
},
{
"path": "en-product/datastreams/default-value.md",
"chars": 17,
"preview": "# Default Value\n\n"
},
{
"path": "en-product/datastreams/expose-to-automation.md",
"chars": 24,
"preview": "# Expose to Automation\n\n"
},
{
"path": "en-product/datastreams/sync-with-the-latest-server-value.md",
"chars": 37,
"preview": "# Sync with the latest server value\n\n"
},
{
"path": "en-product/datastreams/wait-for-confirmation-from-the-device.md",
"chars": 41,
"preview": "# Wait for confirmation from the device\n\n"
},
{
"path": "en-product/events/README.md",
"chars": 10,
"preview": "# Events\n\n"
},
{
"path": "en-product/events/events-code.md",
"chars": 16,
"preview": "# Events: Code\n\n"
},
{
"path": "en-product/events/events-name.md",
"chars": 16,
"preview": "# Events: Name\n\n"
},
{
"path": "en-product/events/events-notification-period.md",
"chars": 483,
"preview": "# Events: Notifications Limit\n\nThis setting limits the number of notifications for a specified time period. \n\nExample: 1"
},
{
"path": "en-product/events/events-notification.md",
"chars": 24,
"preview": "# Events: Notification\n\n"
},
{
"path": "en-product/events/events-online-offline.md",
"chars": 17,
"preview": "# System Events\n\n"
},
{
"path": "en-product/general-settings/README.md",
"chars": 20,
"preview": "# General Settings\n\n"
},
{
"path": "en-product/general-settings/manufacturer.md",
"chars": 16,
"preview": "# Manufacturer\n\n"
},
{
"path": "en-product/general-settings/offline-ignore-period.md",
"chars": 25,
"preview": "# Offline Ignore Period\n\n"
},
{
"path": "en-product/metadata.md",
"chars": 12,
"preview": "# Metadata\n\n"
},
{
"path": "en-product/mobile-app-ui.md",
"chars": 17,
"preview": "# Mobile app UI\n\n"
},
{
"path": "en-product/web-dashboard.md",
"chars": 17,
"preview": "# Web Dashboard\n\n"
},
{
"path": "faq.md",
"chars": 3154,
"preview": "# FAQ\n\n* I backed Blynk on Kickstarter. Where are my widgets and why the app is free?\n\n > App is free because otherwise"
},
{
"path": "firmware-api/README.md",
"chars": 24,
"preview": "# Firmware API \\(C++\\)\n\n"
},
{
"path": "firmware-api/disable-widgets-in-the-app.md",
"chars": 139,
"preview": "# Disable Widgets in the App\n\nThis command disables and enables widget in the app\n\n```cpp\nBlynk.setProperty(V0,\"isDisabl"
},
{
"path": "firmware-api-1/disable-widgets-in-the-app.md",
"chars": 137,
"preview": "# Disable Widgets in the App\n\nThis command disables and enables widget in the app\n\n```cpp\nBlynk.setProperty(V0,\"isDisabl"
},
{
"path": "gettingstarted.md",
"chars": 5412,
"preview": "# Getting Started\n\nLet's get you started in 5 minutes \\(reading doesn't count!\\). We will switch on an LED connected to "
},
{
"path": "google-code-prettify/CHANGES.html",
"chars": 7896,
"preview": "<html>\n <head>\n <meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\">\n <title>Change Log</title>\n "
},
{
"path": "google-code-prettify/COPYING",
"chars": 10763,
"preview": "\n Apache License\n Version 2.0, January 2004\n "
},
{
"path": "google-code-prettify/Makefile",
"chars": 3896,
"preview": "SHELL := /bin/bash\n\nCLOSURE_COMPILER=java -jar tools/closure-compiler/compiler.jar \\\n\t --warning_level VERBOSE \\\n\t "
},
{
"path": "google-code-prettify/README.html",
"chars": 11564,
"preview": "<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
},
{
"path": "google-code-prettify/examples/quine.html",
"chars": 1892,
"preview": "<!DOCTYPE html>\n<html>\n<head>\n<meta charset=\"utf-8\" />\n<title>Making Quines Prettier</title>\n<!-- The defer is not neces"
},
{
"path": "google-code-prettify/js-modules/combinePrefixPatterns.js",
"chars": 7972,
"preview": "/**\n * Given a group of {@link RegExp}s, returns a {@code RegExp} that globally\n * matches the union of the sets of stri"
},
{
"path": "google-code-prettify/js-modules/externs.js",
"chars": 976,
"preview": "var PR = {};\n\n/**\n * @param {function (Object)} handler\n * @param {Array.<string>} fileExtensions\n */\nPR.registerLangHan"
},
{
"path": "google-code-prettify/js-modules/extractSourceSpans.js",
"chars": 2578,
"preview": "/**\n * Split markup into a string of source code and an array mapping ranges in\n * that string to the text nodes in whic"
},
{
"path": "google-code-prettify/js-modules/extractSourceSpans_test.html",
"chars": 4868,
"preview": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML//EN\">\n<html> <head>\n<title>Extract Source Spans Test</title>\n<script src=\"extra"
},
{
"path": "google-code-prettify/js-modules/js_include.pl",
"chars": 2296,
"preview": "#!/usr/bin/perl\n\n# Given a JS file looks for lines like\n# include(\"path/to/file/to/include\");\n# and replaces them wit"
},
{
"path": "google-code-prettify/js-modules/numberLines.js",
"chars": 4666,
"preview": "/**\n * Given a DOM subtree, wraps it in a list, and puts each line into its own\n * list item.\n *\n * @param {Node} node m"
},
{
"path": "google-code-prettify/js-modules/numberLines_test.html",
"chars": 4725,
"preview": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML//EN\">\n<html> <head>\n<title>Number Lines Test</title>\n<script src=\"numberLines.j"
},
{
"path": "google-code-prettify/js-modules/prettify.js",
"chars": 41412,
"preview": "// Copyright (C) 2006 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/js-modules/recombineTagsAndDecorations.js",
"chars": 4262,
"preview": "/**\n * Breaks {@code job.sourceCode} around style boundaries in\n * {@code job.decorations} and modifies {@code job.sourc"
},
{
"path": "google-code-prettify/js-modules/recombineTagsAndDecorations_test.html",
"chars": 4018,
"preview": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML//EN\">\n<html> <head>\n<title>Recombine Tags And Decorations</title>\n<script src=\""
},
{
"path": "google-code-prettify/js-modules/regexpPrecederPatterns.pl",
"chars": 2594,
"preview": "use strict;\n\nprint \"\n\n/**\n * A set of tokens that can precede a regular expression literal in\n * javascript\n * http://we"
},
{
"path": "google-code-prettify/js-modules/run_prettify.js",
"chars": 9752,
"preview": "// Copyright (C) 2013 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-apollo.js",
"chars": 2618,
"preview": "// Copyright (C) 2009 Onno Hommes.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not "
},
{
"path": "google-code-prettify/src/lang-basic.js",
"chars": 1388,
"preview": "// Contributed by peter dot kofler at code minus cop dot org\n\n/**\n * @fileoverview\n * Registers a language handler for B"
},
{
"path": "google-code-prettify/src/lang-clj.js",
"chars": 2808,
"preview": "/**\n * @license Copyright (C) 2011 Google Inc.\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");\n * "
},
{
"path": "google-code-prettify/src/lang-css.js",
"chars": 6183,
"preview": "// Copyright (C) 2009 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-dart.js",
"chars": 2969,
"preview": "// Copyright (C) 2013 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-erlang.js",
"chars": 3501,
"preview": "// Copyright (C) 2013 Andrew Allen\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not "
},
{
"path": "google-code-prettify/src/lang-go.js",
"chars": 2348,
"preview": "// Copyright (C) 2010 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-hs.js",
"chars": 4649,
"preview": "// Copyright (C) 2009 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-lisp.js",
"chars": 3630,
"preview": "// Copyright (C) 2008 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-llvm.js",
"chars": 2275,
"preview": "// Copyright (C) 2013 Nikhil Dabas\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not "
},
{
"path": "google-code-prettify/src/lang-lua.js",
"chars": 2443,
"preview": "// Copyright (C) 2008 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-matlab.js",
"chars": 25651,
"preview": "// Copyright (c) 2013 by Amro <amroamroamro@gmail.com>\n//\n// Permission is hereby granted, free of charge, to any person"
},
{
"path": "google-code-prettify/src/lang-ml.js",
"chars": 2976,
"preview": "// Copyright (C) 2008 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-mumps.js",
"chars": 5317,
"preview": "// Copyright (C) 2011 Kitware Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not "
},
{
"path": "google-code-prettify/src/lang-n.js",
"chars": 3109,
"preview": "// Copyright (C) 2011 Zimin A.V.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not us"
},
{
"path": "google-code-prettify/src/lang-pascal.js",
"chars": 1578,
"preview": "// Contributed by peter dot kofler at code minus cop dot org\n\n/**\n * @fileoverview\n * Registers a language handler for ("
},
{
"path": "google-code-prettify/src/lang-proto.js",
"chars": 1294,
"preview": "// Copyright (C) 2006 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-r.js",
"chars": 2391,
"preview": "// Copyright (C) 2012 Jeffrey B. Arnold\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may"
},
{
"path": "google-code-prettify/src/lang-rd.js",
"chars": 1758,
"preview": "// Copyright (C) 2012 Jeffrey Arnold\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may no"
},
{
"path": "google-code-prettify/src/lang-scala.js",
"chars": 2564,
"preview": "// Copyright (C) 2010 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-sql.js",
"chars": 3559,
"preview": "// Copyright (C) 2008 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-tcl.js",
"chars": 2610,
"preview": "// Copyright (C) 2012 Pyrios.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not use t"
},
{
"path": "google-code-prettify/src/lang-tex.js",
"chars": 1891,
"preview": "// Copyright (C) 2011 Martin S.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not use"
},
{
"path": "google-code-prettify/src/lang-vb.js",
"chars": 3922,
"preview": "// Copyright (C) 2009 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-vhdl.js",
"chars": 2230,
"preview": "/**\n * @fileoverview\n * Registers a language handler for VHDL '93.\n *\n * Based on the lexical grammar and keywords at\n *"
},
{
"path": "google-code-prettify/src/lang-wiki.js",
"chars": 1911,
"preview": "// Copyright (C) 2009 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/lang-xq.js",
"chars": 25439,
"preview": "// Copyright (C) 2011 Patrick Wied\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not "
},
{
"path": "google-code-prettify/src/lang-yaml.js",
"chars": 839,
"preview": "// Contributed by ribrdb @ code.google.com\n\n/**\n * @fileoverview\n * Registers a language handler for YAML.\n *\n * @author"
},
{
"path": "google-code-prettify/src/prettify.css",
"chars": 1570,
"preview": "/* Pretty printing styles. Used with prettify.js. */\n\n/* SPAN elements with the classes below are added by prettyprint. "
},
{
"path": "google-code-prettify/src/prettify.js",
"chars": 63320,
"preview": "// Copyright (C) 2006 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/src/run_prettify.js",
"chars": 79658,
"preview": "// Copyright (C) 2013 Google Inc.\n//\n// Licensed under the Apache License, Version 2.0 (the \"License\");\n// you may not u"
},
{
"path": "google-code-prettify/styles/demo.html",
"chars": 1734,
"preview": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML//EN\">\n<html><head>\n<script src=\"../src/prettify.js\"></script>\n<script src=\"../s"
},
{
"path": "google-code-prettify/styles/desert.css",
"chars": 1645,
"preview": "/* desert scheme ported from vim to google prettify */\r\npre.prettyprint { display: block; background-color: #333 }\r\npre "
},
{
"path": "google-code-prettify/styles/doxy.css",
"chars": 2726,
"preview": "/* Doxy pretty-printing styles. Used with prettify.js. */\n\npre .str, code .str { color: #fec243; } /* string - eggyolk"
},
{
"path": "google-code-prettify/styles/index.html",
"chars": 3150,
"preview": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML//EN\">\n<html><head>\n<title>Prettify Themes Gallery</title>\n<style type=\"text/css"
},
{
"path": "google-code-prettify/styles/sons-of-obsidian.css",
"chars": 1519,
"preview": "/*\r\n * Derived from einaros's Sons of Obsidian theme at\r\n * http://studiostyl.es/schemes/son-of-obsidian by\r\n * Alex For"
},
{
"path": "google-code-prettify/styles/sunburst.css",
"chars": 1945,
"preview": "/* Pretty printing styles. Used with prettify.js. */\n/* Vim sunburst theme by David Leibovic */\n\npre .str, code .str { c"
},
{
"path": "google-code-prettify/tests/debug-ie-compat-matrix.html",
"chars": 2976,
"preview": "<style>\ncode {\n white-space: pre; padding: 0; margin: 0; display: block\n}\n</style>\n\n<code id=\"one-line\"\n>one short line"
},
{
"path": "google-code-prettify/tests/ie-newline-copy-paste.html",
"chars": 4521,
"preview": "<title>IE Newline Copy/Paste Info Gathering</title>\n\n<body>\n<p>\nI'm trying to squash, <a href=\"http://code.google.com/p/"
},
{
"path": "google-code-prettify/tests/large_input_test.html",
"chars": 3568,
"preview": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">\n<html>\n<head>\n<title>Tests of Prettifier w/ large data f"
},
{
"path": "google-code-prettify/tests/prettify_test.html",
"chars": 116707,
"preview": "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\">\n<html>\n<head>\n<title>Code Prettifier</title>\n<script>(fu"
},
{
"path": "google-code-prettify/tests/prettify_test_2.html",
"chars": 89486,
"preview": "<!DOCTYPE HTML PUBLIC \"-//W5C//DTD HTML 4.01 Transitional//EN\">\n<html>\n<head>\n<title>Code Prettifier</title>\n<script>(fu"
},
{
"path": "google-code-prettify/tests/run_prettify_test.html",
"chars": 1492,
"preview": "<!DOCTYPE HTML>\n<html>\n <head>\n <title>Run_Prettify Test</title>\n <script>\n (function () {\n var known"
},
{
"path": "google-code-prettify/tests/test_base.js",
"chars": 8133,
"preview": "// get accurate timing.\n// This file must be loaded after prettify.js for this to work.\nPR_SHOULD_USE_CONTINUATION = fal"
},
{
"path": "google-code-prettify/tests/test_styles.css",
"chars": 247,
"preview": "/* Used by error reporting code in test_base.js */\n.mismatch { background: #fee; font-weight: bold }\nspan.annot { margin"
},
{
"path": "google-code-prettify/tools/closure-compiler/COPYING",
"chars": 11358,
"preview": "\n Apache License\n Version 2.0, January 2004\n "
},
{
"path": "google-code-prettify/tools/closure-compiler/README",
"chars": 6809,
"preview": "/*\n * Copyright 2009 The Closure Compiler Authors.\n *\n * Licensed under the Apache License, Version 2.0 (the \"License\");"
},
{
"path": "google-code-prettify/tools/closure-compiler/amd-externs.js",
"chars": 174,
"preview": "/**\n * @param {string} id\n * @param {Array.<string>} dependencies\n * @param {Function} factory\n */\nfunction define(id, d"
},
{
"path": "google-code-prettify/tools/closure-compiler/console-externs.js",
"chars": 101,
"preview": "var console = {};\n/**\n * @param {string} message\n */\nconsole.warn = function (message, var_args) {};\n"
},
{
"path": "google-code-prettify/tools/cut-release.sh",
"chars": 6507,
"preview": "#!/bin/bash\n\nfunction help_and_exit() {\n echo \"Usage: $0 [-go] [-verbose] [-force]\"\n echo\n echo \"Moves minified"
},
{
"path": "google-code-prettify/tools/googlecode_upload.py",
"chars": 9200,
"preview": "#!/usr/bin/env python\n#\n# Copyright 2006, 2007 Google Inc. All Rights Reserved.\n# Author: danderson@google.com (David An"
},
{
"path": "google-code-prettify/tools/lang-handler-aliases.sh",
"chars": 1956,
"preview": "#!/bin/bash\n\nLANG_DIR=\"$1\"\nshift\n\nHAS_LANG_FILES=1\nif echo \"$LANG_DIR\"/lang-*.js | egrep -q \"[*]\" >& /dev/null; then\n H"
},
{
"path": "google-code-prettify/tools/yui-compressor/LICENSE.TXT",
"chars": 2418,
"preview": "YUI Compressor Copyright License Agreement (BSD License)\n\nCopyright (c) 2009, Yahoo! Inc.\nAll rights reserved.\n\nRedistri"
},
{
"path": "google-code-prettify/tools/yui-compressor/README",
"chars": 5206,
"preview": "==============================================================================\nYUI Compressor\n=========================="
},
{
"path": "hardwaresetups.md",
"chars": 7598,
"preview": "# Hardware set-ups\n\n## Arduino over USB \\(no shield\\)\n\nIf you don't have any shield and your hardware doesn't have any c"
},
{
"path": "http.md",
"chars": 377,
"preview": "# HTTP RESTful API\n\nBlynk HTTP RESTful API allows to easily read and write values of Pins in Blynk apps and Hardware. \n"
},
{
"path": "https-api/api_getlastweekdata.md",
"chars": 239,
"preview": "# Download Datastream Data\n\nTo get the device data for last week, use this API call:\n\n**API call:**\n\n```text\napi/externa"
},
{
"path": "https-api/events-api.md",
"chars": 1033,
"preview": "# Events\n\nTo trigger [Events](https://github.com/blynkkk/blynkkk.github.io/tree/1b828d2e6ad5add190596bc1bfad64e2d6aa0832"
},
{
"path": "https-api/external_api.md",
"chars": 3265,
"preview": "# Devices\n\n## Datastreams API\n\n### Hardware\n\nGet datastream value \\(via HTTP GET\\):\n\n* `/external/api/get?token={token}&"
},
{
"path": "implementing.md",
"chars": 2567,
"preview": "# Implementing a Blynk HW client \\(library\\)\n\nCurrently we provide Arduino/C++ implementation of the library. It is very"
},
{
"path": "index.html",
"chars": 3890,
"preview": " <!-- Flatdoc -->\n <script src=\"scripts/jquery-1.9.1.min.js\"></script>\n <script src='scripts/legacy.js'></script>\n <"
},
{
"path": "introanddownloads.md",
"chars": 4206,
"preview": "\n## Intro\n\n## 🚨🚨🚨 **IMPORTANT:** \n\n> ## :warning: This documentation is for the LEGACY version of Blynk platform which i"
},
{
"path": "license.md",
"chars": 67,
"preview": "# License\n\nThis project is released under The MIT License \\(MIT\\)\n\n"
},
{
"path": "links.md",
"chars": 516,
"preview": "# Links\n\n* [Blynk site](https://www.blynk.cc)\n* [Blynk community](https://community.blynk.cc)\n* [Facebook](https://www.f"
},
{
"path": "mobile/README.md",
"chars": 10,
"preview": "# mobile\n\n"
},
{
"path": "mobile/accelerometer.md",
"chars": 824,
"preview": "\n### Accelerometer\n\nAccelerometer is kind of [motion sensors](https://developer.android.com/guide/topics/sensors/sensors"
},
{
"path": "mobile/barometer.md",
"chars": 424,
"preview": "\n### Barometer/pressure\n\nBarometer/pressure is kind of [environment sensors](https://developer.android.com/guide/topics/"
},
{
"path": "mobile/ble.md",
"chars": 419,
"preview": "\n### BLE\n\nWidget for enabling Bluetooth Low Energy support. At the moment BLE widget requires \ninternet connection in or"
},
{
"path": "mobile/bluetooth.md",
"chars": 557,
"preview": "\n### Bluetooth\n\nWidget for enabling Bluetooth support. At the moment Bluetooth widget supported only for Android and req"
},
{
"path": "mobile/bridge.md",
"chars": 2046,
"preview": "\n### Bridge\n\nBridge can be used for Device-to-Device communication (no app. involved). You can send digital/analog/virtu"
},
{
"path": "mobile/button.md",
"chars": 1905,
"preview": "\n### Button\n\nWorks in push or switch modes. Allows to send any number value on button click and button release events. B"
},
{
"path": "mobile/datastreams.md",
"chars": 15,
"preview": "# Datastreams\n\n"
},
{
"path": "mobile/device_selector.md",
"chars": 1073,
"preview": "\n### Device Selector\n\nDevice selector is a powerful widget which allows you to update widgets based on one active device"
},
{
"path": "mobile/device_tiles.md",
"chars": 325,
"preview": "### Device Tiles\n\nDevice tiles is a powerful widget and very similar to the device selector widget, but with UI. It allo"
},
{
"path": "mobile/email.md",
"chars": 2374,
"preview": "\n### Email\n\nEmail widget allows you to send email from your hardware to any address.\n\nExample code:\n```cpp\nBlynk.email(\""
},
{
"path": "mobile/eventor.md",
"chars": 2323,
"preview": "\n### Eventor\n\nEventor widget allows you to create simple behaviour rules or **events**. \nLet's look at a typical use cas"
},
{
"path": "mobile/gauge.md",
"chars": 1680,
"preview": "\n### Gauge\n\nA great visual way to display incoming numeric values.\n\nCan work in 2 modes : \n\n- PUSH mode (select if from "
},
{
"path": "mobile/gps_streaming.md",
"chars": 874,
"preview": "\n### GPS Streaming\n\nUseful for monitoring smartphone location data such as latitude, longitude, altitude and speed (spee"
},
{
"path": "mobile/gps_trigger.md",
"chars": 865,
"preview": "\n### GPS Trigger\n\nGPS trigger widget allows easily trigger events when you arrive to or leave from some destination. Thi"
},
{
"path": "mobile/graph.md",
"chars": 1035,
"preview": "\n### Graph\n\nEasily plot incoming data from your project in various designs. You can also scroll and zoom graph.\n\nCan wor"
},
{
"path": "mobile/gravity.md",
"chars": 774,
"preview": "\n### Gravity\n\nGravity is kind of [motion sensors](https://developer.android.com/guide/topics/sensors/sensors_motion.html"
},
{
"path": "mobile/humidity.md",
"chars": 417,
"preview": "\n### Humidity\n\nHumidity is kind of [environment sensors](https://developer.android.com/guide/topics/sensors/sensors_envi"
},
{
"path": "mobile/image.md",
"chars": 1249,
"preview": "\n### Image\n\nImage widget allows you to display any image within your project. You need to provide http/s url to it.\nUrl "
},
{
"path": "mobile/joystick.md",
"chars": 2153,
"preview": "\n### Joystick\n\nControl servo movements in 4 directions.\n\n#### Settings:\n\n- **SPLIT**:\nEach of the parameters is sent dir"
},
{
"path": "mobile/labeled_value.md",
"chars": 2193,
"preview": "\n### Labeled Value\n\nDisplays incoming data from your sensors or Virtual Pins. It is a better version of 'Value Display' "
},
{
"path": "mobile/labeled_value_display.md",
"chars": 2193,
"preview": "\n### Labeled Value\n\nDisplays incoming data from your sensors or Virtual Pins. It is a better version of 'Value Display' "
},
{
"path": "mobile/lcd.md",
"chars": 1928,
"preview": "\n### LCD\n\nThis is a regular 16x2 LCD display made in our secret facility in China. It can work in 2 modes : \n\n- Simple\n-"
}
]
// ... and 297 more files (download for full content)
About this extraction
This page contains the full source code of the blynkkk/blynkkk.github.io GitHub repository, extracted and formatted as plain text for AI agents and large language models (LLMs). The extraction includes 497 files (2.4 MB), approximately 649.1k tokens, and a symbol index with 79 extracted functions, classes, methods, constants, and types. Use this with OpenClaw, Claude, ChatGPT, Cursor, Windsurf, or any other AI tool that accepts text input. You can copy the full output to your clipboard or download it as a .txt file.
Extracted by GitExtract — free GitHub repo to text converter for AI. Built by Nikandr Surkov.