search

Apollon77 / ioBroker.tuya

ioBroker adapter to connect to several small and cheap Wifi devices that care connected to the Tuya Cloud and mostly use the Smartlife App/Alexa-Skill
MIT License
87 stars 21 forks source link

[Questiion?] How to interpret values for NX-6477 irrigation valves #541

Closed mcm1957 closed 1 year ago

mcm1957 commented 1 year ago

I installed NX-6477 irrigation valves and integrated them into ioBroker via Tuya Adapter. The coupling works. But there are a few states that I can't interpret with the best will in the world:

How to interpret those states for time plans?

image

And how should I interpret next_time !? image

I'll ask here if I just don't understand that or if something doesn't fit here.

Apollon77 commented 1 year ago

They all look like base64 encoded binary data, content unknown in a first place. So the only thing you can do is to decode them to binary data (Buffer.from("...", "base64") ) and then maybe do changes in the app and try to find out how to interpret them. Usually such dsta are multiple bytes with different meaning (Timer like maybe the day and time or such or length).

Maybe check also Google if someone did such an decoding already.

If you find out details open a issue or PR with infos and I can try to implement it, but for now I close the issue.

mcm1957 commented 1 year ago

OkI ll checkEspecially the next time value should be guessable. -------- Ursprüngliche Nachricht --------Von: Ingo Fischer @.> Datum: 18.06.23 23:50 (GMT+02:00) An: "Apollon77/ioBroker.tuya" @.> Cc: "Martin M." @.>, Author @.> Betreff: Re: [Apollon77/ioBroker.tuya] [Questiion?] How to interpret values for NX-6477 irrigation valves (Issue #541) They all look like base64 encoded binary data, content unknown in a first place. So the only thing you can do is to decode them to binary data (Buffer.from("...", "base64") ) and then maybe do changes in the app and try to find out how to interpret them. Usually such dsta are multiple bytes with different meaning (Timer like maybe the day and time or such or length). Maybe check also Google if someone did such an decoding already. If you find out details open a issue or PR with infos and I can try to implement it, but for now I close the issue.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>