Download PDF
        SAMOVAR 
×
Menu

Mobile apps and website

Remote control uses the samovar-tool.ru server, the Samovar apps for Android and iOS and the control page on the website. You do not need to install the Blynk app. Fields labelled “Blynk” refer to the account and token on the Samovar server. These instructions apply to this server, not the Blynk cloud or another private server.
Choose your case: new account, existing account, website connection, account migration or device list in the app. Samovar establishes the connection itself; no router ports need opening. See Remote control.
New account and first Samovar
1. Connect Samovar to Wi-Fi with internet access using Connecting to Wi-Fi. Install the Samovar app: Android or iOS through TestFlight.
2. Open “Settings” in the app and press “Create account”. Enter your email, password and password confirmation. Use at least 8 characters, including a lowercase and uppercase Latin letter and a digit. Confirm creation. The app creates an account and a project for the physical Samovar, saves the login details and displays “Device token”. Website registration is optional when controlling one Samovar through the app.
3. Copy the token: a secret key of 32 Latin letters, digits, “-” or “_”. On your local network open the Samovar web interface → Settings («Настройки») → Other («Прочие»). Paste the key into “Blynk token” («Токен Blynk») and press “Save” («Сохранить»). Stop the process, then switch Samovar off and on: it connects at startup. During initial Wi-Fi setup you can also enter the key in “blynk token”.
4. Check the saved token in the app and press “Test connection”. “Server reachable, device online” confirms the connection. Open the main screen and check the readings. Keep the token secret: it grants access to readings and control.
Connecting to the website
1. To connect Samovar directly through the website, register and sign in. Open “User → Devices”. Use your existing website account if you have one. To import a previously created Samovar, its account email and password must match the website; otherwise complete migration first.
2. At registration the website automatically creates “Device”, linked to the cheese, beer and distillation journals. It has a regular token: you can use it to connect an ESP32 and remotely control Samovar. Press “Show token” on its card, enter your current website password and copy the key. Enter it in the local Samovar interface → Settings → Other → Blynk token («Настройки → Прочие → Токен Blynk»), save and restart Samovar as in step 3 above. You do not need to create a separate account in the app for this. Readings, control and logs work with this token; push notifications from it may not arrive, because signing into its account from the app is not possible.
3. You can connect the first Samovar with “Devices used: 1 of 1” by using the automatically created device token. Importing another token or creating an additional device requires a free slot. If the limit is reached, ask the website administrator (info@samovar-tool.ru) to raise it. Add buttons are hidden when the limit is reached; migration also checks the available slots.
4. If Samovar already uses a token from the app or an existing account, you can add it separately with a free slot: press “Import device”, enter “Name”, “Blynk token” and “Current site password”, then press “Import”. The server checks token ownership against the account with the website email and password. The automatically created “Device” token needs no import. Press “Select” on the device card whose token is entered in the ESP32 (the card then shows “Selected for control”; the “Rename” button changes the name and requires the website password), open “Control” and check the readings. This selection also applies to logs.
5. You can view the token of any listed device again, including the automatically created one: press “Show token” on its card and enter the website password. For an additional Samovar, with a free slot, press “Create device” (the button is visible when the list already has a device) → enter the name and website password → “Create project”. This requires an existing remote control account with the website email and password; website registration alone does not create it. Save the new token in the corresponding ESP32 as in step 3 above.
Existing account without migration
If you already used Samovar through samovar-tool.ru, enter your previous email and password in the app “Settings” and press “Sign in and get token”. With several projects, the first matching token is returned: compare it with “Blynk token” («Токен Blynk») in the local interface of the Samovar you want (Settings → Other («Настройки → Прочие»)). You can paste a known token manually and press “Save”. A token is enough for viewing and control; push notifications require account sign-in and notification permission on the phone.
If the existing account email and password already match the website, add the Samovar using “Import device” as above. Use migration to add all matching projects or align passwords. You do not need to create a new account in place of the existing one.
Migrating an existing account to the website
Check emails and projects before migration. If the old email matches the website email, the account and projects are not deleted: matching Samovars are added to the website and the server password becomes the website password. If emails differ, matching Samovars are moved to the account with the website email (the website list and the limit also include Samovars that were already in that account), then the old account is deleted with all remaining projects — even when no matching Samovars are found. There is no preview or undo.
A matching project is named Samovar, case insensitive, has exactly one device and tabs Main («Основное»), Control («Управление»), Charts («Графики»). Projects with other names or contents are not migrated. If you do not know the contents of your old projects, check with the administrator before migration. If you need them, do not migrate to a different email until you have resolved this with the administrator. When migrating between different emails, if an account with the website email already exists on the server, its password must match the current website password.
1. Sign in to the website and open “User → Devices”. Make sure the limit has room for all added Samovars, allowing for occupied slots including the journal device. Ask for a higher limit first if necessary.
2. Press “Migrate Blynk account”. Fill “Old Blynk email” and “Old Blynk password” with the previous samovar-tool.ru account details, and “Current site password” with the current website password. Review the consequences for your case above and press “Migrate projects”.
3. After success, refresh the device page, select the physical Samovar and check the control page. Use the website email and password in the app. Migrated Samovar tokens are preserved: no ESP32 changes are needed. With several projects, verify the returned token or manually enter the known token of the Samovar you want.
If migration reports an error, do not immediately repeat it: the server operation may have succeeded while the website list failed to update. Refresh “Devices” and check app sign-in with the website email and password; contact the administrator if the result is unclear. To change the password on both website and server later, use “Change shared password” on the device page, then sign in again on the website and in the apps. A website password changed another way (for example, by password recovery) is also passed to the server.
One token or a device list in the app
Current Android and iOS limitation. “Connect devices from the site” works only when every listed device belongs to the same remote control account with the website email and password. The automatic journal device belongs to another account, so including it can cause a synchronization or project lookup error. Migrating the old account does not remove this limitation.
In this case use the app with one token: press “Return to single device” if needed, paste the same key as in the ESP32 into “Device token”, then press “Save”. The automatically created website “Device” token is also suitable. Viewing and control with a token do not require account sign-in. Push requires signing into the account that owns this Samovar. On the website control it through its selected card.
If all website devices belong to one regular account, enter the shared email and password in app settings and press “Connect devices from the site”. One device is selected automatically; several are selected by name. After website changes press “Refresh device list”. Android, iOS and the website store their selections independently. Push notifications arrive from devices in the connected list; tapping a notification switches the app to its sender.
If the server is available but Samovar is offline, check ESP32 internet access, matching firmware and app tokens, and a restart after saving. For sign-in errors check the email and password of the correct account; creating another account or repeating migration does not replace this check. The website page refreshes every 3 seconds while it is open and visible on screen (less often on connection errors, up to 30 seconds); phone push notifications arrive through the app.
Screens
"Main". Connection state, mode and status line, a process diagram with current temperatures (the same as in the web interface: by mode, beer brewing order and the second pump above the cooling water), sensor cards with mini-charts, the buttons "Turn heat on/Turn heat off", "Start"/"Next", "Pause"/"Resume" (Cheese mode has no pause), "Lock body T" (rectification and Lua) and "Reset process", the current program line, parameters and mode.
The "Main" screen on the website; in the apps it is the same
"Program". The program lines of the current mode with a decoding of the fields, the running line highlighted. The program is view-only here: it can be changed in the Samovar web interface.
The "Program" screen
"Control". Regulator voltage, take-off rate, locking the hearts temperature, the I2CStepper stirrer and pump (start and stop, relays R1-R4), running a Lua line and system information: the Samovar IP, firmware version, mode, time.
The "Control" screen
"Charts". The history of the current session from the server: the groups "Temperatures", "Pressure", "Takeoff and water", "Alcohol", "Power", an interval from 1 minute to the whole session, and individual lines are switched on and off with the buttons under the chart.
The "Charts" screen
"Messages" on the website, "More" in the app. On the website the fifth tab shows "Last device message" and "Session messages" — the whole current session from the server. An alarm stays on screen until it is closed; other pop-up messages disappear after 4 seconds. In the app, session messages are shown on the "Control" screen and arrive as push notifications. The fifth app tab, "More", opens a menu: Cheesemaker, Brewer, Distiller (journals, recipes, stock, calculators) and "Settings" — the account, a single token or device selection, and notifications.
The "Messages" tab on the website
How it works
Samovar sends the readings to the server by itself: during a process, temperatures, pressure and take-off rate every 4 seconds (every 5 seconds when idle), voltage and the status line every 5 seconds, the rest (program line number, the program, mode, heating and pause state) on change. Commands from the app and the website are applied immediately, without a confirmation prompt. Leave a pause of 1-2 seconds between commands.
Samovar messages are shown on the "Messages" tab and arrive as push notifications in the app; alarms come with the prefix "Alarm!" («Тревога!»), warnings with "Warning!" («Предупреждение!»). Through the same server the firmware transmits the process log and the session start; they are stored on the server and available on the website, see Logs and charts in the cloud.
Attention. Before a remote start, make sure the equipment is assembled safely and a person is nearby who can immediately cut the power and the product supply. The remote interface does not replace hardware protections and supervision of the installation.