TuyaAPI / cloud / 51 / 1

73%

master: 73%

push

travis-ci

Feature: support new API sign mechanism (HMAC-SHA265) (#3)

Adding new API signage mechanism compatible with current (3.9.0) TuyaSmart App. This enables You to use API with `clientId/token` used in official apps - which means it's possible to continue using official app and read/control device from the cloud simultaneously.

For details regarding reverse-engineering process see: [tuya-sign-hacking repo](https://github.com/nalajcie/tuya-sign-hacking). You can also find there the credentials retrieved from the official app (I didn't include them here on purpose in case there will ever be any takedown action from Tuya).

Things to consider:
- there is no clear difference between old/new API in terms of submitted data (I've decided to use `apiEtVersion` which hopefully will change if the API will change in the future; moreover, the API is versioned on per-action basis (each `action` has it's own version field) which adds another level of confusion)
- I don't know if the distinction between using old and new API is clear enough (providing different options to constructor). Maybe there should be whole new class (`Cloud2`? but we don't even know if that's version 2). Maybe it should be made more explicit by adding e.g. `useHMACSign` option to the constructor?

What do You think?

45 of 68 branches covered (66.18%)

Branch coverage included in aggregate %.

103 of 136 relevant lines covered (75.74%)

8.89 hits per line