You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-18
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ These scripts were tested in
34
34
* a Raspberry Pi 3B / 3B+ Raspberry Pi OS Buster (previously called Raspbian) and its internal Wifi chip
35
35
* a Raspberry Pi 3B+ + USB-WIFI with an image from [here](https://www.offensive-security.com/kali-linux-arm-images/)
36
36
* Ubuntu 18.04.3 64Bit in VirtualBox on Win10 with a cheap RTL8188CU Wifi Adapter connected to the VM
37
+
* Ubuntu Mate 18.04.5 32bit in VirtualBox on Win 10 with cheap Ralink 802.11n WLAN (MediaTek RT5370) WiFi Adapter connected to VM
37
38
38
39
Any Linux with a Wifi adapter which can act as an Access Point should also work. Please note that we have tested the Raspberry Pi with clean installations only. If you use your Raspberry Pi for anything else, we recommend using another SD card with a clean installation.
* copy docker/docker-compose.sample.yml to a new folder you created, the file should be named docker-compose.yml
93
-
* you may adjust this docker-compose.yml, if necessary:
94
-
* environment-variables may be different, for example network-adapter may be different from wlan0
95
-
* adjust the volume folder, where you want your backups stored
96
-
97
-
Run the image:
98
-
* go into the folder you copied docker-compose.yml
99
-
* docker-compose up -d
100
-
* docker-compose exec tuya start
101
-
* tuya-convert now starts within docker
102
-
103
-
Stop the image:
104
-
* docker-compose exec tuya stop
105
-
* docker-compose down
90
+
* if you have already cloned this repo just cd into the directory and execute `git pull`
91
+
* cp .env-template .env
92
+
* adjust the created .env-file, it contains usage information as comments
93
+
94
+
Building and running your container:
95
+
*`docker-compose build && docker-compose run --rm tuya`
96
+
* This directly starts into tuya. If you press ctrl+break or exit tuya after flashing, your container is closed and deleted
97
+
98
+
Troubleshooting:
99
+
* Q: Where are my logs after flashing? A: The folder can be adjusted in .env with LOCALBACKUPDIR, the path here may be relative or absolute
100
+
* Q: I don't want that my container is deleted after running tuya, I need this for troubleshooting! How do I accomplish this? A: Just remove --rm from `docker-compose run --rm tuya`
101
+
* Q: I want to start the container, but instead of starting tuya immediately I want to get into bash. Is this possible? A: Yes just start the container with `docker-compose run --entrypoint bash tuya`.
102
+
* Q: I want to rebuild my docker-image, even if there are no changes. Is this possible? A: Just start `docker-compose build --no-cache` instead of `docker-compose build`! Don't do this all the time, this is a time consuming process ...
103
+
* Q: I can't connect to my USB, PCI, ... network card. How do I get this working? A: You may have an error in your .env-File. The WLAN-variable should reflect the name of your network interface on your host. Execute ifconfig and look through your interfaces.
104
+
* Q: I can't get an IP-address and or connection on my phone, what's the problem? A: You may look into smarthack-wifi.log (location is set in .env with LOCALBACKUPDIR) or possible stop your firewall (e.g. NixOS seems to have a problem here). It may be a problem with a wrongly set network interface (see previous question)
0 commit comments