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

An unusual response #117

Closed
msillano opened this issue May 7, 2023 · 3 comments
Closed

An unusual response #117

msillano opened this issue May 7, 2023 · 3 comments
Labels
wontfix This will not be worked on

Comments

@msillano
Copy link

msillano commented May 7, 2023

Not an issue, only a report.
Trying a gateway (IR + Bluetooth + ZigBee), I met a PUSHed message never seen before in Tuya devices, Perfectly decoded, but NOT in the standard format.

4 May 09:18:02 - [info] [tuya-smart-device:Multimode Gateway] Data from device [event:data]: {"online":["a4c138******","a4c1383********","a4c138f******","804b50*******"],"offline":[], "nearby":["a4c138******"]}

Standard format, as I know:

msg.payload:{     
        "deviceId":    gatewayID|deviceid,   // from subdevices => "deviceId": gatewayId
        "deviceName":  name,                     // from tuya-smart-device node,
        "data": {
            "t": Math.floor( Date.now() / 1000 );       // timestamp (sec), by tuya-smart node
            "cid": deviceid;                                        // only from subdevices, mandatory
            "dps":{
                [dp]: value                               //  atomic or string or encoded, 
               ...                                              //  more than one dp in some cases
            }}}}

Nothing serious, I intercept and process it adequately (I replace it with 4 connected subdevice messages), but if custom formats were to proliferate, it would lead to confusion!
Best regards.
m.s.

@stale
Copy link

stale bot commented Jul 15, 2023

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.

@stale stale bot added wontfix This will not be worked on and removed wontfix This will not be worked on labels Jul 15, 2023
@stale
Copy link

stale bot commented Oct 15, 2023

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.

@stale stale bot added the wontfix This will not be worked on label Oct 15, 2023
Copy link

stale bot commented Jan 21, 2025

Auto closing the issue

@stale stale bot closed this as completed Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant