Pre-release v1.6.0-beta.x (@0x5e/homebridge-tuya-platform)

[0x5e]

Hello everyone,

I'm the former employee of Tuya, who proposed to create this project.

Although didn't work for the Tuya anymore, but as a personal developer, I will still maintain this project from now on.

Here's my fork of next release (still work in progress): https://github.com/0x5e/homebridge-tuya-platform/releases

Welcome to have a try :)

I will use my spare time merging and solving issues.

When it becomes stable, I will contact my colleague merge into the official repo.

Changelog

v1.6.0-beta.x

Changed

• Rewritten in TypeScript, brings benefits of type checking, smart code hints, etc.
• Reimplement accessory logics. More friendly for accessory developers. (old accessory class still compatible to use yet)
• Update device info list polling logic. Less errors.
• Add config validation on plugin start.
• Add device manufactor, serial number (device id) and model displayed in HomeKit.
• Add GitHub action Build and Lint.
• Remove debug option. Silence logs for users. For debugging, please start homebridge in debug mode: homebridge -D
• Remove lang option.
• Update unit test.

Fixed

• 1106 permission error when polling device info list.
• Fix access_token undefined error. (Code 2406 - after running smoothly for ages #298 (comment) by @Azukovskij )

Accessory category specific

• Rewrite BaseAccessory, SwitchAccessory, OutletAccessory, LightAccessory, reduce about 50% code size. Now writing a BaseAccessory child class is much more simple.
• Add debounce and command send queue for LightAccessory, more stable during frequent operations on different characteristics.
• Legacy accessory codes moved to src/accessory/legacy/ folder.
• Fix wrong color temperature map. (homekit光色映射与tuya platform不一致/homekit color temperature map not match with tuya platform #136 by @XiaoTonyLuo and Fix inversed colour temperature. #135 by @levidhuyvetter)

Known issue

• LightAccessory may not work properly, espasially on work mode change. need more test and info.
• Sometimes mqtt not respond quickly, will influence the accessory status update. still addressing the issue.