uzlonewolf
uzlonewolf
Wait, that device doesn't happen to be a device22 does it? Those use CONTROL_NEW instead of DP_QUERY which would explain it not responding to DP_QUERY. Also, slight change of plans....
:facepalm: I was reopening the connection but not re-sending the payload, so of course none of the retries ever succeeded. It also seems your device requires some payload data or...
Great! I just need to get v3.1 working now... That "OSError: [Errno 107] Transport endpoint is not connected" just means the device accepted the connection but then immediately closed it....
I was able to reproduce this with a correct key and secret, but wrong region and/or device id. Double-check to make sure both the Region and Device ID are correct....
That "ablilty" is directly from the device itself, there is nothing we can do about it. Are you sure those devices are linked to your developer account? The Region must...
Unfortunately I'm not really feeling this one. In my experience the DP mapping is only half right with a significant number of device DPs not being in the list, the...
I say there's no such thing as too much data and would also include `model` and `sub`. `sub` is important for device scanning/polling as sub-devices are not directly connected to...
While working on my test scripts for #188 I realized `d = tinytuya.OutletDevice( '0123456789abcdef0123' )` works but `d = tinytuya.OutletDevice( '0123456789abcdef0123', '1.2.3.4' )` does not since the version (3.3 for...
In the PR I already had open I added the storing of that additional data to devices.json. `version` and `last_ip` still need to be added somehow, probably via the scanner...
@fhempy I agree with the theory and would love to see that, however where will the DP mappings come from? The "official" mappings are just straight up wrong, and trying...