-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README and Project Management Improvements #109
Comments
Everyone flashing Tasmota to a unknow device is doing that at his own risk |
Hi @Jason2866 I'm not sure what you're getting at, would you please clarify? Sounds like you maybe misunderstood my post, as it does not concern awareness of the risk of flashing custom firmware. tuya-convert is not specific to Tasmota, it can flash any custom firmware on stock Tuya devices. Many issues opened here are reporting successful flashing (which is the goal of this project) but then going on to ask for support setting up Tasmota (which this project is not responsible for) and they would be better served by directing them to the existing support channels for the firmware they're trying to set up, whatever that may be. |
Maybe change from support to help, and have a few different people look at the description? For example, if someone wanted help setting up Tasmota (popular as it is) on a new device, does the Tasmota wiki have a page of advice for that? |
Hi @dshanske
I'm not sure what you're asking. Whatever the firmware that a user chooses to install, once installed, the job of tuya-convert is done. Any issues after that should be directed to the relevant project. If a user has an issue with Tasmota, there are no actionable items as tuya-convert does not own or maintain Tasmota.
Indeed, the Sonoff-Tasmota wiki has several pages dedicated to initial configuration of devices. |
I was brainstorming how such an entry in the readme might read. |
What i want to say. Just flashing Tasmota to devices means not the will work with. |
Ahah, thank you for your input.
There is no claim that it will
Neither can tuya-convert. If there is any place to ask for support for any given software, it is from that software's community.
That is your prerogative
Then this is where users should go for support, not tuya-convert
I'm not saying that devices bricked through the flashing process itself should be issues of Tasmota. If the issue is with flashing then indeed, tuya-convert is the place to ask for support. If the issue is with setup of Tasmota, tuya-convert is not the place to ask. |
And that is the point, we cant help in most cases too. We dont know which GPIO is used for what |
Sure, if you wish you limit the scope of your project (a good idea, and exactly what I'm doing here) then you may wish to indicate which devices you will support. I'm not arguing with you here. Again, that is entirely your prerogative and not relevant to this particular issue. The point made here is only that the scope of tuya-convert does not include setting up the firmware you choose to flash. Issues here should only pertain to the flashing process. |
I think where your confusion lies @Jason2866 is that I'm not suggesting the Sonoff-Tasmota community do anything. That is entirely up to you/them. I am simply declaring what the tuya-convert community will not do. |
I agree with you 100% All users should know that the get support here for Software Tuya not for Tasmota Software. And Tasmota cant provide support for unknown specific device questions. |
Great @Jason2866, I'm glad we have found common ground and agree with the approach. Thanks for your input! |
The Sonoff User Forum is a perfect place to discuss new devices that have had Tasmota flashed to them. |
Resolved |
Hi @ctandi and @merlinschumacher
I've been keeping up with issues on the repo here and I'm noticing a trend with users seeking Tasmota support here where they may be better helped by existing support channels. With that may I recommend some additions to the README.
For increased visibility these items could also be made part of the issue template.
I'd also ask you to consider the following, as a significant amount of energy and time has been dedicated by several others in the parallel research and development of these techniques, independently of your paper. After this project was published, much of the support for maintaining and supporting the project has come from the community.
For ongoing support of the project, you may wish to consider asking one or more community members to be a member of this repository so they may better assist with answering and closing issues, pull requests, and maintenance. I would be happy to take on a more active role to keep the project moving and address support issues faster.
Thanks for your consideration
// CK
The text was updated successfully, but these errors were encountered: