-
Notifications
You must be signed in to change notification settings - Fork 679
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
[Device Support Request] Blind motor "_TZE200_libht6ua" #2636
Comments
I have the same blind motor... How can this be added to HA? |
I would also like a quirk for this device. |
I have the same motor for Tuya's blind that appears to me as unsupported if someone could help us I would appreciate it |
I'm working on being able to add it to z2m, I would say it's ready but I need to learn how to upload it to the code... while I'm learning, if anyone wants to try it, I uploaded it here https://github.com/javilopezalarcon/Blind-motor-_TZE200_libht6ua-z2m It works well, with position and battery control, the motor failure remains to be tested if it is real. |
Does this also work without zigbee2mqtt? I only have ZHA plugin installed.
Op za 25 nov 2023 om 17:31 schreef javilopezalarcon <
***@***.***>:
… I'm working on being able to add it to z2m, I would say it's ready but I
need to learn how to upload it to the code... while I'm learning, if anyone
wants to try it, I uploaded it here
https://github.com/javilopezalarcon/Blind-motor-_TZE200_libht6ua-z2m It
works well, with position and battery control, the motor failure remains to
be tested if it is real.
—
Reply to this email directly, view it on GitHub
<#2636 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5CTKMN7SCNG4GLAVX24WEDYGIMMPAVCNFSM6AAAAAA5ZP6B6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGM3TCNRXGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thx for converter, now I found this motor have very limited range opening/closing 0-100, its not enough to open curtains, any ideas? Thank you! |
Thanks for the converter @javilopezalarcon. I managed to figure out that datapoint 101 is for motor direction and 102 sets the upper limit and have made the following changes to your converter. exposes: [
...,
e.enum('motor_direction', ea.STATE_SET, ['left', 'right']).withDescription('Motor side'),
e.enum('set_upper_limit', ea.STATE_SET, ['start', 'stop']).withDescription('Learning')
],
meta: {
tuyaDatapoints: [
...,
[101, 'motor_direction', tuya.valueConverterBasic.lookup({ 'left': tuya.enum(0), 'right': tuya.enum(1) })],
[102, 'set_upper_limit', tuya.valueConverterBasic.lookup({ 'start': tuya.enum(0), 'stop': tuya.enum(1) })],
],
}, @env-dxb I had a similar problem to you until I found out about setting an upper limit. You can try the following to see if it helps.
|
Tilt mode exactly what I need, but it’s about half of required limit, and manual doesn’t work for me as well(( |
Seems I need a hub and app for it, I don’t) |
Kind of weird the way this issue on the ZHA repository has turned into a Zigbee2MQTT thread, but hopefully that will lead to a quirk being available for ZHA I guess? |
Yeah, I have homebridge based on raspberry and zigbee. That’s why. I spent a lot of time to connect this motor to any system, but all I get is sleepless nights and state in mqtt. I returned it today. Enough) |
Thank you very much @env-dxb for the contribution of the new sensors, I will add them before sending it to z2m (sorry for the delay, I was very busy) 👍🏻👍🏻 |
It's my fault for converting this from zha to z2m, I'm sorry @kineticscreen ... I was the same, I couldn't find anything that worked for me and I found this thread, where I saw that there were more people like me, in zha yes, but like me, without integration. .. I started to work to be able to add it in z2m and I wanted you to be the first to know, since you were like me... I imagine, that having the data from each sensor, passing it to zha will be much easier than not having anything, If it helps, I already fulfilled what I wanted, which was to help 😅 |
But is it possible to make it work in ZHA? |
Also interested in this. |
I've had some success by using the following quirk: """Tuya based cover and blinds."""
from zigpy.profiles import zha
from zigpy.zcl.clusters.general import Basic, Groups, Identify, OnOff, Ota, Scenes, Time
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya import (
TuyaManufacturerWindowCover,
TuyaManufCluster,
TuyaWindowCover,
TuyaWindowCoverControl,
)
class TuyaMoesCover0601(TuyaWindowCover):
"""Tuya blind controller device."""
tuya_cover_inverted_by_default = True
signature = {
# "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4098,
# maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264,
# maximum_outgoing_transfer_size=82, descriptor_capability_field=0)",
# "endpoints": {
# "1": { "profile_id": 260, "device_type": "0x0051", "in_clusters": [ "0x0000", "0x0004","0x0005","0xef00"], "out_clusters": ["0x000a","0x0019"] }
# },
# "manufacturer": "_TZE200_zah67ekd",
# "model": "TS0601",
# "class": "zigpy.device.Device"
# }
MODELS_INFO: [
("_TZE200_libht6ua", "TS0601"),
],
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.WINDOW_COVERING_DEVICE,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaManufacturerWindowCover,
TuyaWindowCoverControl,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
}
} Opening and closing works, which is what i need. I set the open and close positions by using the buttons on the device itself. |
Does the quirk expose anything else, like Battery status etc? Or just basic up down. Does it support percentage adjustments? |
It supports percentage adjustments but no battery status yet. I planed to
do more research in this device tomorrow. Maybe i'm able to figure out how
the battery status reporting works.
Kinetic Screen ***@***.***> schrieb am Sa., 17. Feb. 2024,
06:01:
… Does the quirk expose anything else, like Battery status etc? Or just
basic up down. Does it support percentage adjustments?
—
Reply to this email directly, view it on GitHub
<#2636 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAZ6YERC6TWM4UTKDLEGKDYUA2UFAVCNFSM6AAAAAA5ZP6B6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZGY2DSOBTGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Taking the tuya 0610 cover quirk and adding the device to the modified MODELS_INFO, line 173
EDIT: I just realized that those two are virtually identical, so makes sense both would work. Also, I think it's in "tilt" mode. I tried the method described above to change, but this didn't work, I just lost the connection to ZHA (I think it went into pairing mode). @TeaMoe, how do you "set the open and close positions by using the buttons on the device itself."? |
Hey guys, converter by @javilopezalarcon with modifications by @fearless666 worked well, thanks a lot. However, I have a slight issue I imagine can be fixed in code but I am quite a newbie so struggling on how to do so. When pressing up or down in HA, it does the opposite of what the buttons do in the remote and the device. |
@helzarto I am really sorry to apparently ask a dumb question. How did you add the converter _TZE200_libht6ua.js to HA and zigbee2mqqt? (i am really new to HA). Help is really appreciated and sorry for "pushing" the thread to HA Z2M again. Edit: Got it running. I did everything "right" but there was a change because of the last update: Koenkk/zigbee2mqtt#22083 (comment) |
Hi there, did You solve this issue - And do You have the battery-state? |
Problem description
This appears to be similar to other blind motors - just another variation on the manufacturer name?
https://www.aliexpress.com/item/1005002954586484.html?spm=a2g0o.order_list.order_list_main.5.529e1802C56G4M
Solution description
Hopefully is just a simple port of the other quirks for similar devices
Screenshots/Video
Screenshots/Video
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: