Open RoboChopp opened 3 months ago
This protocol is identified by 0x00006699
instead of 0x000055aa
.
https://github.com/jasonacox/tinytuya/discussions/260 https://github.com/jasonacox/tinytuya/issues/247
Thankyou for this @NickDarvey , is there anything I can do to implement a fix for 3.5 protocol devices?
I have the same problem: recently updated my tuya lamp's, now with protocol version 3.5.
So i tried a demo homeassistant install using custom integration of localtuya which supports version 3.5 and voilá the lamp's are controllable via homeassistant - so protocol 3.5 handling is already manageable 😉
Ha nice, thanks @alexwala - I'd never tried Home Assistant before but just switched everything over to that using the local tuya setup you mentioned and rebuilt some of my custom automations using the blueprint setup. Bit of a learning curve but nothing crazy - all protocols currently available work! Thankyou
Same here. Got 2 new bulbs from local warehouse and they are 3.5 protocol. Had to connect through homeassistant plugin mentioned here. It works but I'm missing adaptive temperature in HomeKit.
I'm running the latest 3.1.2-beta.2 version of Homebridge-tuya and it looks like (maybe) 3.5 protocol Tuya devices aren't supported yet? I think that's what the issue is. I bought some new bulbs that connect via smart life and found the secret local key and configured the same as I have with my 3.3/3.4 version devices but it just won't discover these new ones unfortunately. Devices work find in Smart Life which is what makes me think this might be the issue.
Does this sound right? And if this is the potential reason are there plans to work on 3.5?
thankyou