-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[New device support]: Aubess Universal Smart IR Remote Control - Tuya TS1201 #11633
Comments
I would be interested by this device, will follow this issue. |
I've got the device profiles: ZigBee Device Profile, Simple Descriptor Response, Nwk Addr: ------, Status: Success Sequence Number: 24 Status: Success (0) Nwk Addr of Interest: ------ Simple Descriptor Length: 26 Simple Descriptor Endpoint: 1 Profile: Home Automation (0x0104) Application Device: Unknown (0xf000) Application Version: 0x0001 Input Cluster Count: 7 Input Cluster List Input Cluster: Basic (0x0000) Input Cluster: Groups (0x0004) Input Cluster: Scenes (0x0005) Input Cluster: Identify (0x0003) Input Cluster: Unknown (0xed00) Input Cluster: Unknown (0xe004) Input Cluster: On/Off (0x0006) Output Cluster Count: 2 Output Cluster List Output Cluster: OTA Upgrade (0x0019) Output Cluster: Time (0x000a) The clusters '0xed00' and '0xe004' looks interesting. Does anyone have information about them? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I'm waiting for a tuya hub to sniff the protocol and add the device. |
I have a similar device that i bought for the same reason (was hoping it was a clone of the Heimann). This one is from Tuya (rebranded by Moes) and looks like it might be the same as your Aubess device. Let me know if i can help with anything would like to get mine working as well. I dont have a Tuya smart hub and this device just came in today so I haven't played with it much yet. |
I've received tuya hub and tried to sniff communication between the hub and the device. I think I know how to made the device receive a command from a remote control and transmit it. It seems the full protocol is quite complicated. I'll try to puzzle my brain over it a little bit more. Look at the packets which hub sending to the device. Maybe you can see something.
"key_code" contains the sequence (in base64) the device sent when it recorded pushing button on a remote control. |
I dug out the documentation of Dune HD player. It says:
I captured POWER button of an Dune HD player two times and sends it to the device:
It does not look like I expected. All the ideas how to transform NEC protocol code to the "key_code" value are welcome. Anyway. I'm going to make a custom script to support this device. It'll allow to learn keys returning the "key_code" value and send keys. |
Thanks you so much for looking into it. |
One does not simply write the script. It looks the developers of the device invented a custom protocol incapsulated into ZigBee packets. It requires to sends and received a sequence of ZigBee packets (usually command packets of six types) to transmit one IR command. I still don't understand how to make it right way. It seems it'll take more time when I expected. |
I've managed to send one of previously written ir code to my fan using my awfully written script. It switched the fan on. I hope I'll finish the first version of the script at the weekend. |
I've finished the first version of the script. It looks nasty, but should work. Adding the device:
The device should be recognized and ready to use. The device exposed three properties:
|
Hi! The original Aubess IR device removed from the Aliexpress shop. Now you can by this new one directly from Aubess, I hope this also work with your scripts, but I don't know, what will be the difference: |
I may be wrong but I think previous version of the device is always avaliable, see here: There is another one, but physically different: |
Ok as I see the difference is only the power supply: the new one works with 2xAAA betteries against USB charging. I order one, and I'll try it, how it works with your script. |
sipossz, I think the script should be modified for new device, because it should report battery status at least. Please send a database entry when you receive the device and I'll try to modify the script for you, |
External converter TS1201.js tested successfully on 2 IR devices: Well done, Sir!! Question: |
@kds69, thank you for testing. |
thank you so much Model:UFO-R11 i change "" manufacturerName: '_TZ3290_j37rooaxrcdcqo5n'}"" and works fine but it didn't show battery percentage at first time i try to configure it with ZHA, ZHA show battery percentage. can anyone please share how to add device button to dashboard after reading IR code , (for example power button in tv ) |
This is HA related question, I do recommend to check on the HA community forum or discord. |
share link please to any recommended page |
did you add this device to dashboard as button ? |
can you please share MQTT command . |
send topic zigbee2mqtt/your_aubess_device/set with payload { "IRCodeToSend": your_code_to_be_sent } |
You can do it like this as well: |
@naifzack, could you please publish a database entry for your MOES device. I need the information about clusters to add this device (with battery info) to zigbee2mqtt. |
* Add AUBESS ZXZIR-02 (_TZ3290_acv1iuslxi3shaaj) universal smart IR remote control. Koenkk/zigbee2mqtt#11633 * Eslint errors has been fixed. * Eslint errors has been fixed. * 1."fromZigbee,js" and "toZigbee.js" have been reverted to previous state. 2. All the logic has been moved to "lib/zsong.js". 3. All exposes converted to snake case. * "zigbee-herdsman" version has been updated to supporting ZSONG cluster. * Update aubess.js * Update zosung.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* Add TuYa ZS06 (_TZ3290_7v1k4vufotpowp9z) universal smart IR remote control. Koenkk/zigbee2mqtt#11633 * Update tuya.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* Add MOES UFO-R11 (_TZ3290_j37rooaxrcdcqo5n) universal smart IR remote control. Koenkk/zigbee2mqtt#11633 * Update moes.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Hi! I just set up my UFO R11 as well, but after sending commands nothing happened. Could you please describe how did you learn codes and send them? |
@Saharok14 I flowed the documentation and used commands, for example similar to this:
To get the code, click on the web interface to send the command ( |
And I did the same but never worked for me, looks like the device (Moes IR blaster) is rebooting after sending the command (from the Zigbee2mqtt logs, announce of the device after sending the IR command). I already ordered one more, will see what will |
Same problem as @Saharok14. I have 3 of them. @Saharok14 : are your test with the 2nd one better ? Thanks ! |
I just returned it and got a Wi-Fi one. So, this device didn’t work for me… |
:-( |
Try “Tuya IR remote Wi-Fi” I just got a first from the list in the local store… in my case - https://allegro.pl/oferta/smart-remote-uniwersalny-pilot-ir-wifi-tuya-11425213322 |
Is it possible to simulate up a sequential multi key sequence such as "123" to enter a three digit number. I can't "learn" a multi-key sequence or set up a script to emulate one. The remote only seems to want to do one single discrete command at a time. |
I figured out (enough of) how the devices custom encoding works to send any NEC command. I wrote a node js function to convert nec codes into this device's encoding. The script and a description of the encoding are here: https://gist.github.com/andrewcchen/f16eb20d19ea64d9f997c470e2addeaa |
can you make it work under deconz, thanks |
Hi, I guess TS1201 is still not supported. I have no clue how to add external converter. Could sb help me out with this? |
Hi everyone! I managed to crack the custom encoding of IR codes used by Tuya IR blasters. |
Hi @mildsunrise, thank you for your excellent documentation! Please take a look over here: zigpy/zha-device-handlers#1687. We have the same device and are working to understand the codes, too. I found your Gist, and would like to dig deeper on the protocol used by Tuya IR. Perhaps we can work on a conversion tool? I see your FIXME comment... 😆 Many thanks! |
it should use the same format, just try it and tell me if
oh, no worries, besides, I've just implemented the compression so it should now give reasonably small strings :) |
@mak-42 Do you still have the sniffing logs for this format ? |
I'll try if you tell me the command in the original application you want to sniff. |
It doesn't matter, for example Fan -> Westinghouse -> Power. |
Something have changed since the previous sniffing. I have not much suitable remote controls (Smart Life makes me press buttons to add new one). The codes for lamp remote control (ERA):
The codes for Dune player (I added 2 years ago):
it does not look like the code sniffed before:
|
Thanks for trying, I finally bought a sniffer and a Tuya GW (actually 2 because I didn't know that the wireless version doesn't support the IR blaster...) to do tests more easily. |
Link
https://www.aliexpress.com/item/1005003772831987.html?gatewayAdapt=glo2fra&gatewayAdapt=glo2fra&gatewayAdapt=glo2fra&spm=a2g0o.order_list.0.0.21ef5e5bnDdlPP
Database entry
{"id":63,"type":"Router","ieeeAddr":"0x2c1165fffe63aea3","nwkAddr":27932,"manufId":4098,"manufName":"_TZ3290_acv1iuslxi3shaaj","powerSource":"Mains (single phase)","modelId":"TS1201","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":61440,"inClusterList":[0,4,5,3,60672,57348,6],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS1201","manufacturerName":"_TZ3290_acv1iuslxi3shaaj","powerSource":1,"zclVersion":3,"appVersion":65,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b0022a54f44","endpointID":1},{"cluster":64642,"type":"endpoint","deviceIeeeAddress":"0x00124b0022a54f44","endpointID":1}],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":65,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1645952529076,"defaultSendRequestWhen":"immediate"}
Comments
I have purchased this item to give it a try in the hope that this device is a clone of HEIMAN HS2IRC (https://www.zigbee2mqtt.io/devices/HS2IRC.html).
External converter (see in "external converter" part) which was replicating HEIMAN HS2IRC's device didn't help to get any response from AUBESS device (send "create" device command, "get_list"). Sniffing didn't show reply from device, but I am not very competent in that area.
One thing I didn't try is to revert latest fix of heimen.js converter which force manufacturer to null on message toZigbee for HS2IRC.
This could be a track to explore.
Note that with or without external converter battery level exposure is causing non fatal errors as the Aubess device has no battery at all and obviously can't expose any...
External converter
Supported color modes
No response
Color temperature range
No response
The text was updated successfully, but these errors were encountered: