Tuya Switches w/ Power Usage Data (No TuyaConvert Needed)

perr · January 30, 2020, 11:26am

Have you got this solved???

perr · January 30, 2020, 11:54am

Hi Phillip,

I have been working days on days to try to solve this, it is an en/decoding problem.

I tried this: https://github.com/TradeFace/python-tuya, which is an addition to PYTUYA, it works with the decoding in the sens that it correctly decode and encode the first part of the messages, the message sent, but my challenge is the Python programming, I am a skilled programmer, but Python is so different from all other lanquages I have programmed in, so I have not yet succeded to integrate his solution into your program.

He also explaines why some en/decoding do not work.

Hope this can help you, as I expect that TUYA is changing their en/decoding in new devices.

dferrandizmont · January 30, 2020, 4:46pm

Not yet … haven’t looked further. If someone has any news let us know!

Phill_Healey · January 30, 2020, 6:42pm

Please can we keep this to one place, as it’s impossible to keep track of your comments when they are bouncing between here and the Github issue tracker. Thanks.

Phill_Healey · January 30, 2020, 7:28pm

I just pushed version 1.1.2 to PyPi. This fixes an issue with some device using different dps keys.

This may solve some of the recent issue discussed in this thread.

Let me know how you get on with it.

Big thanks to @WeldFire for his input / pr!

kklicker · February 1, 2020, 8:18pm

Just wanted to say big thanks for this latest version. I’ve been following along and I’ve been having the same issues as WeldFire. I upgraded just now, and I’m seeing the power stuff. Big thanks to both of you. Good stuff!

Phill_Healey · February 1, 2020, 9:14pm

You’re welcome. I created the early versions based on my experience with my own device. @WeldFire came along and worked out that a lot of devices used the same dps keys as the devices on the old API. Until more people jump in and start adding fixes or making suggestions there is not much I can do to improve things. There are so many Tuya devices that it’s impossible for 1 person to make a script that covers them all.

I’m glad the new version was what you needed to get your devices up & running!

@dferrandizmont @perr have you tried the latest version yet (see above) ?

dferrandizmont · February 1, 2020, 9:39pm

Hey Phill! Thanks for the new version. Already tried but seems that doesn’t works at all …

{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.158].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T21:35:25Z"}

from the logs:

INFO:pytuya:pytuya version 7.0.5
INFO:pytuya:Python 2.7.16 (default, Oct 10 2019, 22:02:15)
[GCC 8.3.0] on linux2
INFO:pytuya:Using PyCrypto (3, 9, '4')
INFO:pytuya:Using PyCrypto from '/home/pi/.local/lib/python2.7/site-packages/Crypto/__init__.pyc'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'
DEBUG:pytuya:status() entry
DEBUG:pytuya:json_payload='{"devId":"bfb50067e2c0b15c28udin","gwId":"bfb50067e2c0b15c28udin"}'
DEBUG:pytuya:status received data="\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>a'\x01\x1d\x00\x00\xaaU"
DEBUG:pytuya:result='d\x8f\xf6\xc4\xbf\xf1\xb3\xe3\xa0\xaa\xc3Y\xcb\xaeC\x84\xbe\xec\xf6\x9d\x13\x17\xf0P{\x19\xd5\xc7\xa6\xdbO>'
DEBUG:pytuya:decrypted result=u'json obj data unvalid'

Thank you so much for your effort

kklicker · February 1, 2020, 10:02pm

Just FYI, I was getting that same response before I realized I had the wrong IP for the device.

dferrandizmont · February 1, 2020, 10:31pm

Thanks for pointing this, tried with all the IP and had the same response:

{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.157].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:24:59Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.158].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:25:15Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.166].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:25:33Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.167].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:25:55Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.168].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:26:13Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.173].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:26:29Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.174].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:26:45Z"}
{"result": "Incomplete response from plugbfb50067e2c0b15c28udin [192.168.1.192].", "deviceid": "bfb50067e2c0b15c28udin", "datetime": "2020-02-01T22:27:13Z"}

kklicker · February 1, 2020, 10:41pm

Are you obfuscating the id? The last 4 characters look odd to me. Also, both my device id’s contain 20 characters instead of 22.

dferrandizmont · February 1, 2020, 11:04pm

Mmm … this is what I get from the Smart Life app:

Phill_Healey · February 1, 2020, 11:24pm

Why does this show a different IP for each row? Incorrect &/or failed attempts to connect to a device will result in it just blocking connections then send out seemingly random data.

perr · February 2, 2020, 8:49am

Phill,

I did a try, but I am afraid my testenvironment needed to be reset.

I did however get the new message about the devise info not found.

I will go deeper into this next week, and let you know.

dferrandizmont · February 2, 2020, 9:05am

Each row has a different IP because I tried the getstats.py with all those IPs just in case i’m pointing the wrong IP.

Tested with:

python getstats.py "bfb50067e2c0b15c28udin" "192.168.1.157" "417ad98dbcbb4fa6" "3.3"

and

python getstats.py "bfb50067e2c0b15c28udin" "192.168.1.157" "417ad98dbcbb4fa6" "3.1"

for each of those IPs.

Anyway, as @kklicker said, my device ID is 22 characters long, it’s wrong?

Thank you so much.

Phill_Healey · February 2, 2020, 11:34am

Ok, Please post an issue over on Github and I’ll see if we can somehow work it out.

dferrandizmont · February 2, 2020, 11:42am

Done it , thanks Phill!

nmsr · February 2, 2020, 7:25pm

Hi Phill,

I’m trying to check the connection under firmware 1.0.2 and It only returns this:

{“deviceid”: “03268688807d3a7c9aab”, “datetime”: “2020-02-02T19:04:38Z”}

I don’t know how to get the local key but following your info it would not be needed anyway. What’s could be wrong?

Thank you.

perr · February 3, 2020, 9:46am

Hi Phill

Did a complete clean of my environment, and reinstalled your packet (1.1.3)?

and both with protecol 3.1 and 3.3, i get this message from mosquitto:

pi@raspberrypi:~ $ mosquitto_sub -t “devices/tuya/plug/TestPlug” -u “per” -P “per”
{“datetime”: “2020-02-03T09:41:45Z”, “deviceid”: “TestPlug”, “result”: “Incomplete response from plugTestPlug [192.168.1.139].”}

I have added it to the Github

Phill_Healey · February 3, 2020, 3:52pm

It’s always best to try with keys & the firmware version varies from device to device. You can get the device key using the instructions linked to in my first post. Once you have those you can try against both api versions.