ct-Open-Source / ct-Open-Source/tuya-convert

Docker Tuya Convert unable to see esphome firmware.bin in the files folder

Open
#1,161 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
5.1k
Forks
523
PR merge metrics
No merged PRs in 30d

Description

Hi Everyone,

I am having two issues which I believe are related to each other likely both caused by my poor understanding of how Tuya convert in docker functions.

I built an esphome firmware.bin for my smart device and put it in the Tuya convert files directory with the default firmware .bin options. However, when connecting to my smart plug and then using the numbers to select the firmware, my custom esphome firmware.bin in the files folder is not a selectable option.

Similar to this problem, I cannot locate where docker Tuya convert is placing my factory firmware backup file.

My guess is that because docker containers run seperate that there is a localised file structure docker Tuya convert is using that is not the same as if I was using Tuya convert without docker and I am placing/looking in the wrong location.

Any help would be greatly appreciated please because I am very inexperienced with Linux and this is my first docker container use case as I couldn't fix the python missing library issues.

For what it is worth, I have successfully flashed 2x devices but I actually want to save the backup factory firmware for the next device as I may want to put it back on if developing my esphome yaml takes me too long as no one has done the gpio for this device before that I am aware of.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking how the Docker container maps its files directory to the host, then inspect the container location used for firmware files and factory backups. Confirm whether the custom firmware becomes selectable and where the backup is written; the issue provides no source files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
devops, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.