Skip to content
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

unreadable 'data' output from node #147

Open
andy0983 opened this issue Jun 13, 2024 · 3 comments
Open

unreadable 'data' output from node #147

andy0983 opened this issue Jun 13, 2024 · 3 comments

Comments

@andy0983
Copy link

{data: "3.3� �[��?�,�r��U��e�?�)���x�P�t�(���_o������.�O#����Irj�tu�}����e�d�"
deviceId: "bf72b73d01c0d0cdfbyh6j"
deviceName: "Smart Meter "}

I changed "Tuya Protocol Version, Default : 3.1 (don't change if you are not sure)" to version 3.3 but it didn't help
please advise

@petersturrock
Copy link

Did you make any progress with this ? I had the same issue with two different energy meters today but when I changed the version to 3.3 on the node I started to get readable data. I'm struggling to see read much data beyond the total kwh used though

@grabula
Copy link

grabula commented Oct 24, 2024

similar problem

Moes Temperature and Humidity Smart Switch Module
https://moeshouse.com/products/wifi-temperature-humidity-sensor-relay?variant=39560614150225
I can control both relays and id responds correctly, but trying to get any data including schema I get "$���m�j�ѻLݰ�=n~@��np�^��A�j\��"

also what is interesting while controlling another device (dimmer) Temperature and Humidity Smart Switch also responds with 3.3�
��P|���i,��N�
����
�t[����w� ��֪v,�0��g����t���:

or
3.3���Ԛ:>l
dD���dֵ
����t-�G�\bM�y�
or
3.3� �Ԛ:>~l
dD���dֵ4a����q���J�L\ߛ

does't matter which protocol version is set

Works with phone app with no problem

@Solarspatz
Copy link

Hi all,
I got the exact same problem. Changing the protocol version from 3.1 to 3.3 doesn´t fix it. I also tried another Node ([node-red-contrib-tuya-devices]
(https://github.com/simeonovp/node-red-contrib-tuya-devices)

which exactly produced the same output. I also raised an issue over there. The device (Magnum floor heating thermostate) is fully accessible from the IOT Portal. Another guy in an German Community postest the exact same issue (but with a different tuya device). He mentioned that he solved the issue by "updating" the node. Unfortunately, no further explanations what he did exactly.

So it seems a general problem (maybe a change in protocol?) and not related to this node.

image

Best regards,
Solarspatz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants