Documentation optimization

[fuchs-fabian]

Since the official Local Tuya integration is now causing more and more problems and is no longer compatible with the new version HA 2025.1.0, many will or have already switched to this fork.

This fork is being developed much more actively and therefore causes fewer problems.

As there are even more features and documentation with MkDocs, it is probably the perfect long-term replacement for https://github.com/rospogrigio/localtuya (in my opinion).

To make it easier for many people to switch, I have set up a PR to help with this: #451

The project here seems to be really well developed and there is also a lot of emphasis on code quality, which I particularly like as a programmer.

Now that I've made the switch myself, I've taken a closer look at everything.

I was particularly impressed by the documentation, but even here I noticed a few things:

• Under https://xzetsubou.github.io/hass-localtuya/usage/configure_add_device/ (optional) Device Sleep Time the FAQ link leads to a 404 error. As a result, I am not yet able to understand from the documentation what exactly this does and what I can set there or in which example scenario.
• More information about the values that can be entered there and a concrete example to explain it.
• A step by step guide, similar to the README.md from localtuya, would be helpful, as not everyone knows how to deal with a terminal, scripts...

Apart from that, I would of course like to thank you for your excellent work. 💙

The idea with the discussion is to do a bit of brain storming about what is important in the documentation. From this, you could then deduce what should or should not be included. :)

[fuchs-fabian]

A list of which Tuya devices are now supported with the integration and which are currently not would also be very advisable. I have now created a discussion for this purpose, as fans, for example, no longer work on some of them after the change:

#456

[PauloGoncalves86]

Hi,

I switched to this fork and managed to get most of my devices working, configure additional sensors for my CT clamp device, etc. Congratulations! One exception is a thermometer, perhaps to do with chinese characterset being used in the name, which do not know if I can change.

Regarding docs, a lot of the documentation on the https://github.com/rospogrigio/localtuya/ rep, like how to enable Tuya cloud api, etc is essential to include here if this is meant to be a standalone fork.

Still, given that the official Local Tuya integration is also being maintained, with plenty of pull requests, is there any reason to not join efforts?

[phrak]

Still, given that the official Local Tuya integration is also being maintained, with plenty of pull requests, is there any reason to not join efforts?

Because it's not being maintained. 7 days of PRs over over the last year is not what I would consider active.
https://github.com/rospogrigio/localtuya/activity

And because this fork is now 513 commits ahead of the main branch.
rospogrigio/localtuya@master...xZetsubou:hass-localtuya:master

And because @xZetsubou and others have historically submitted a number of PRs back to the main branch which have generally been ignored by rospogrigio.

The reality is that /this/ repo should be the default HACS LocalTuya integration, but it's very difficult to effect that change.

[CloCkWeRX]

Rename + submit to HACS will do it, but this will mean a HUGE amount of people with problems and different skill levels.

I am happy to do a lot of triage or issue management (was doing it there to little effect).

Having the discussion area open is a great spot as well for overflow.

[CloCkWeRX]

Also, re the fork as the maintainer in September 2024 did finally say they were open to other help... I just fixed all the merge conflicts.and sent in a PR
I doubt it will get integrated.