uzlonewolf
uzlonewolf
An option for scanning within docker (or from any other routed network for that matter) is the force scan option. `python3 -m tinytuya scan -force 192.168.0.0/24`
Try this modified version of the above script (don't forget to replace DEVICEKEY with your key): ```python key = 'DEVICEKEY' ######### Don't change anything below here ########## import tinytuya import...
You can give it a shot, but I find it highly unlikely to help; a non-zero sequence number would have been picked up in the modified monitor script I posted...
> What about just remembering the last received sequence and then use this +1 for the next expected package? My 3.5 devices send 2 responses: an async STATUS (command 8)...
https://github.com/blakadder/tuya-uncover will spit out a TinyTuya-compatible JSON file with `-w devices.json`.
If it helps, my notes about the protocol itself are at https://github.com/jasonacox/tinytuya/discussions/260
It has been my experience that these types of devices do not respond to polls. If you have a monitor script running (i.e. https://github.com/jasonacox/tinytuya/blob/master/examples/monitor.py) you will see async updates as...
Hi @RedFlh . I have multiple devices with single quotes in the local key and they all work fine, so it's not an issue with the library. I'd run the...
I've seen all those symbols before (see #341 ) and none of them have ever caused problems. I'm going to blame this one on the device itself. It's kinda late...
> using AES GCM Wait, AES-GCM is a v3.5 thing, v3.4 devices still use AES-CBC but with a negotiated session key.