Tuya LOCAL with energy monitoring and without tuya-convert

mkjustuk · November 17, 2020, 8:35am

Head into this link to see how to do it;

codetheweb/tuyapi/blob/5a08481689c5062e17ff9a280d0e51815e2cafb7/docs/SETUP.md

All methods below require you to install the CLI tool before proceeding.

Install it by running `npm i @tuyapi/cli -g`. If it returns an error, you may need to prefix the command with `sudo`. (Tip: using `sudo` to install global packages is not considered best practice. See [this NPM article](https://docs.npmjs.com/getting-started/fixing-npm-permissions) for some help.)

## Listing Tuya devices from the **Tuya Smart** or **Smart Life** apps (highly recommended)

This method is fast and easy. If you're having trouble manually linking your device with the below method, we recommend you try this. All devices that you want to use **must** be registered in either the Tuya Smart app or the Smart Life app.

1. Follow steps 1 through 4 from the "Linking a Tuya device with Smart Link" method below.
2. Click on "Cloud Development" in the top nav bar and click the project you created earlier. Under "Device Management" click "Linked Device" on the left side. Click the "Linked Devices by App Account" tab.
3. Click "Add App Account" and scan the QR code from your smart phone/tablet app by going to the 'Me' tab in the app, and tapping a QR code / Scan button in the upper right. Your account will now be linked.
4. On the command line, run `tuya-cli wizard`. It will prompt you for required information, and will then list out all your device names, IDs, and keys for use with TuyAPI. Copy and save this information to a safe place for later reference.

## Linking a Tuya device with Smart Link

This method requires you to create a developer account on [iot.tuya.com](https://iot.tuya.com). It doesn't matter if the device(s) are currently registered in the Tuya Smart app or Smart Life app or not.

1. Create a new account on [iot.tuya.com](https://iot.tuya.com) and make sure you are logged in. Click "Cloud Development" in the top nav bar and click "Create". After you've created a new project, click into it. The access ID and access key are equivalent to the API key and API secret values need in step 6.
2. Click "App Service" in the top nav bar and click "App SDK" from the left side. Click on "Obtain SDK" and enter whatever you want for the package names and channel ID (for the Android package name, you must enter a string beginning with `com.`). Take note of the **Channel ID** you entered. This is equivalent to the `schema` value needed in step 6. Ignore any app key and app secret values you see in this section as they are not used.
3. Click "Cloud Development" in the top nav bar and click the project you created earlier. Under "Device Management" click "Link Device" on the left side. Click the "Link devices by Apps" tab, and click "Add Apps". Check the app you just created and click "Ok".

This file has been truncated. show original

ThePirat · November 17, 2020, 8:36am

@rospogrigio Thanks but I already tried the fake setting with no luck.
I don’t know why but my switches don’t follow the fake positioning time.
For example, if I set 10sec and ask the switch to open, the relay doesn’t stop before the default time is past (30sec)…

Thanks

ThePirat · November 17, 2020, 4:36pm

UPDATE

I am playing with the fake positioning time and just found that my switches don’t respect this time when using the arrows on Lovelace, but they do when using the position slider.

The biggest problem I have right now is not having feedback on the actual state of the switch (and therefore of the shutter) because if I use both the arrows and the slider, the entity does not maintain the state and every time I reopen it on Lovelace I always find the slider set to 50%.

rospogrigio · November 18, 2020, 10:57am

This was the initial behavior I developed for the fake positioning, now it is improved, try to re-download master branch and test it.

TUISTERa · November 18, 2020, 10:58am

Hello, long thread , i’ve read it but i may be missed this part - with tuyalocal is there a connection to the tuya api and tuya iot website or it is local connection ? What happens if i lose internet connection, or if tuya decides to close or change their api? I have latest tuya smart switches with energy monitoring, and no way to use tuya-convert, i cant open them without braking their shell and i want to keep up with tuyalocal…

aleksey_z · November 19, 2020, 7:35am

Hi @rospogrigio, hi @postlund.

In my Hassio I have 15 Tuya devices connected: switches, relays, dimmers; plugs and rgbplugs with Energy Meter. All devices are working fine. Now installed last master branch.

I also have an Energy Meter Switch.

Energy Meter Switch

On AliExpress

It connected fine to Hassio, BUT I see it periodically becomes inactive in Hassio’s interface. At the same time, in the Tuya Smart app, it works fine.

Energy Meter Switch inactive

There are no error entries in Hassio’s logs from this Energy Meter Switch.

Why can he become inactive?

Thanks.

P.S. Also with the last master branch, a lot of entries appeared in the logs.

Entries in the logs

Logger: custom_components.localtuya.light
Source: custom_components/localtuya/pytuya/__init__.py:132
Integration: LocalTuya integration (documentation, issues)
First occurred: 10:25:53 (518 occurrences)
Last logged: 10:33:25

[121...281] Entity light.in_wall_dimmer_2 is requesting unknown DPS index None
[830...dcb] Entity light.on_wall_dimmer is requesting unset index for option color_mode
[830...dcb] Entity light.on_wall_dimmer is requesting unknown DPS index None
[046...60d] Entity light.rgb_power_plug_led is requesting unset index for option color_mode
[046...60d] Entity light.rgb_power_plug_led is requesting unknown DPS index None

But there is no color_temp or color_mode DP in dimmers. Brightness DP only.

OnWall dimmer has:

OnWall Dimmer

onwall dimmer

InWall dimmer has:

InWall Dimmer

inwall dimmer

In InWall Dimmers - DP 101 is a separate setting for the minimum brightness level.

I’ve returned to version 3.0.3 so far.

Senbei · November 19, 2020, 7:18pm

Why do you think it is called tuyaLOCAL

TUISTERa · November 20, 2020, 5:40am

Really… My mistake… but anyway, everyone can call his integration the way he likes. So, tuyalocal doesn’t have to be local

Makis · November 20, 2020, 7:59am

I have the same behavior. I did download the latest version but my covers are working as you describe. To be honest I am very happy that now are in the local network so not the position is nice to have.

*** Many thanks to all for the work and support!

pergola.fabio · November 20, 2020, 10:06am

isnt it possible to make a new release instead of master? cause everytime something is changed, like everyday in master, HACS gives a message, that there is an update available

and we need to reinstall master again

rospogrigio · November 20, 2020, 10:14am

We would love to, but we are waiting for the HA guys to approve our PR in order to have localtuya as a default integration, and publishing a new release would restart the checks and process probably… will try to ask when this will happen. Please hold on, hopefully it won’t be much longer.

kvvoff · November 20, 2020, 3:42pm

~~This is great news! Where can we track this?~~

Makis · November 20, 2020, 6:18pm

Hi all
I have localtuya and everything is working fine. However I have a tuya dehumidifier that is not integrated yet so is is not available in HA.
However with the original tuya integration I could use it through HA with the scenes of the smartlife app.
Now I am wondering, what if I make a new account for the smartlife app only for the dehumidifier and add it to HA with original tuya integrationn and have both original tuya and localtuya integrations with 2 different accounts. Would that be a problem-conflict or it could work?

postlund · November 20, 2020, 6:26pm

I don’t see any problem with that. Should work fine

Makis · November 20, 2020, 7:00pm

I confirm that it is working fine. Thanks again.

pergola.fabio · November 22, 2020, 7:19am

Seems merged with hacs now
So now we need to wait for 3.0.4 to install to go away from master?

rospogrigio · November 22, 2020, 2:42pm

… and here it comes!!
v3.1.0: first release after HACS integration!
First release after having been introduced as an official HACS repository!
What’s new:

improved connection handling, with several bugfixes
introduced devices autodetection, with dynamic IP addresses
introduced passive devices
improved light platform, introducing scenes and HSV handling
improved fake positioning for covers, and introduced reversed mode
improved fan platform
improved logging
other that I can’t remember now
Enjoy!

For all of you who have added localtuya as a custom repository, you should remove the custom repository and re-add it from the official one.
So happy for this achievement, thank you to all contributors!

pergola.fabio · November 22, 2020, 2:45pm

installed and working

pergola.fabio · November 22, 2020, 2:47pm

strange that i dont see it as a custom repository anymore , cause i wanted to remove from there
maybe HACS does that automaticly ?

RoyD2 · November 22, 2020, 3:07pm

I keep getting the following error.

Invalid config for [localtuya]: [switches] is an invalid option for [localtuya]. Check: localtuya->localtuya->0->switches. (See /config/configuration.yaml, line 19).

following in my configuration.yaml file:

``

#Local Tuya
localtuya:

host: 192.168.178.xx
device_id: 12345
local_key: 12345
friendly_name: wifi plug
protocol_version: “3.3”
switches:
sw01:
name: wifi_plug
friendly_name: wifi plug switch
id: 1
current: 4
current_consumption: 5
voltage: 6
sensor:
platform: template
sensors:
wifi_plug_voltage:
friendly_name: “G4 voltage”
unit_of_measurement: ‘V’
value_template: “{{ states.switch.wifi_plug.attributes.voltage }}”

wifi_plug_current:
friendly_name: “G4 current”
unit_of_measurement: ‘mA’
value_template: “{{ states.switch.wifi_plug.attributes.current }}”

wifi_plug_current_consumption:
friendly_name: “G4 current consumption”
unit_of_measurement: ‘W’
value_template: “{{ states.switch.wifi_plug.attributes.current_consumption }}”``