Jason Rumney

Note that 0.19.0 and 0.19.1 had some issues that might make it difficult to judge whether this is working correctly. And I found a further problem after 0.19.2 which probably...

Can you check the actual values for 102 (status)? The iot.tuya.com list says possible values are standby, cooking, done but the current value is "stop", so the documentation at iot.tuya.com...

Thanks, but the value returned locally in the log was clearly "stop". I assume this maps to either standby or done in the cloud API, but not sure which one,...

Thanks, let me know when you can capture the local value for "done" as well, and we'll be ready to start creating the config.

The C and F setting was swapped, and the device support is now released in 0.19.0. Please let me know if there is still an issue.

You won't know until you (or someone) tries it. Local protocol level detail is not publicly available, so we don't know if the ESP modules for these two models have...

For the temperature issue, the scale factor of 10 is already set in the config. Unfortunately 0.19.0 and 0.19.1 had general issues with the underlying tuya library, but you should...

Currently the integration only supports devices that conform to a simple model where all available status are returned by an empty get request, and commands are optionally available as set...

Since you have tuya-cli installed, I think you can use `tuya-cli get --id DEVICE_ID --key LOCAL_KEY -a` replacing DEVICE_ID and LOCAL_KEY with the appropriate values for your device. Based on...

Further information on discovery of DPs: the most complete info seems to be available by using the iot.tuya.com device debugging feature, along with the browser development tools to capture the...