-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code data? #27
Comments
I fond a similar behavior: this is the device (sirene) response to a change (type) done by smartLive:
Very strange is the presence of many 0x00 bytes in a JSON value (not visible in the string !)
Any idea? Best regards, m.s. |
I suspect it is due to a newer firmware in the device. Did you update the firmware using the parent app ? |
I don't remember exactly if tuya updates the firmware of the siren device, I think yes, but that was some time ago, pairing many devices.
Any command send by smartLife (I'm in the phase of sending commands to explore existing dps) give some like this:
on debug pad, filtered by mine nodes:
And so for ANY command: it is executed (smartlife works very well) but that is the result using tuya-smart-device 2.0.0.
This issue has for me low priority: I have a workaround to exchange data with any devices not caught by tuyapi and tuya-smart-device node (but limited to BOOL and ENUM. don't sends/receives INT like sensor values). Thanks and best regards |
I found a solution that is not pretty but it works. I collect some samples of each state of the device and identify the position of the character in the string that matches what was expected.
|
A clever solution, to be taken into consideration. |
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. |
Auto closing the issue |
I getting strange data from tuya device. Anyone has the same issue?
data:
p�@x�J�K�=n���!�A2�}����2���hzmW
The text was updated successfully, but these errors were encountered: