smarthomej / addons

SmartHome/J addons for openHAB
Eclipse Public License 2.0
62 stars 26 forks source link

Device with 3.5 protocole #579

Closed xyz-09 closed 1 month ago

xyz-09 commented 6 months ago

My device is switching offline/offline on each protocole version. From json I know it uses protocole 3.5

On trace Level

19:09:49.567 [TRACE] [a.internal.local.handlers.TuyaDecoder] - Did not receive enough bytes from 'udpListener', exiting early

19:09:50.319 [DEBUG] [nal.local.handlers.TuyaMessageHandler] - bfbb1b76df3362a9e5pkns/local.controler.IP:6668: Connection terminated.

19:09:50.319 [DEBUG] [ya.internal.handler.TuyaDeviceHandler] - [tuya:ir-controller] stop ir learning
J-N-K commented 6 months ago

Currently protocol 3.5 is not supported.

J-N-K commented 6 months ago

https://github.com/jasonacox/tinytuya/discussions/260

This needs to be implemented. However, it's hard to do without a device. Do you know how to use Wireshark and do you use the SmartLife app?

xyz-09 commented 6 months ago

https://github.com/jasonacox/tinytuya/discussions/260

I ran this script to confirm that I have a proper connection with the device.

Yes, I use the SmartLife app, but I have never used Wireshark.

I installed Wireshark few minutes ago, but I don't see the IP address to which the device is connected in the monitoring list.

When I scanned my connection by running the script above again, I still don't see any communication with the device, even though the Python script prints a response - so connection exist.

I do not know how may i help better :thinking:

xyz-09 commented 6 months ago

This Python repository has partial support for protocol 3.5 implemented.

https://github.com/jasonacox/tinytuya

But it doesn't support my device.

xyz-09 commented 6 months ago

But it doesn't support my device.

I am correcting my entry - the device actually works on protocol 3.5.

So there is a starting point to implement protocol 3.5 :smile:

stale[bot] commented 4 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

J-N-K commented 4 months ago

Keep open

stale[bot] commented 2 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.