-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
LXX60-CS27LX1.0 and LXN59-CS27LX1.0 smart curtain switch #2489
Comments
Additional: also it seems that while on the "60" model currentPositionLiftPercentage does nothing. on the "59" it seems to "work" saying when I go aall the way up by switch then down and I stop it after a few seks currentPositionLiftPercentage will be for example "90" instead of 100 edit: also tried the debug options in https://www.zigbee2mqtt.io/how_tos/how_to_support_new_tuya_devices.html but I get no debug tuya information |
Another update: got it working with the following configuration
seems to work "fine" art first glance but getting some horrible timeout issues when switching between open/ close for example.
|
Try changing meta to |
I'll try thanks, got the control "working" right now but having issues with the position since the modules seem to "remember" where they are. couldn't find a way to for example calibrate 0/100 yet and will keep trying. |
"disableDefaultResponse" seems to have fixed the timeout responses thank you :) could you elaborate why it did that? Still working on some other issues will create a pull request when I get it done |
This means the device doesn't confirm any received commands (happens with some quirky devices) |
Makes sense thanks :) |
Does this configuration also work for the LXX60 cover switch that you have? |
Right now I'm using these 2 configurations. Luckily 99% of my devices are 59 because I managed to get open/close/ stop working.
|
Thanks @a-bailey , this was the exact reason I asked because I wanted a configuration that supports stop on the LXX60. I guess I will have to wait or do some tweaking myself if I ever find the time for that. How about pushing your configurations to upstream? |
I will push it/ open a PR but I wanted to try to get it a bit better, I got a zigbee sniffer running on my old usb stick and will try to progress from there! :) quite happy that stop is working on the 59 at least. |
That will be great! if you get to a point where stop is working on the 60, I will be more than happy to verify this on my setup. |
Thanks @a-bailey, based on your work i got my LXN59 working . I changed a bit to get rid of a warning and to get better feedback into fhem` { added to "fromZigbee" :
|
sounds promising! Does calibration work on your code? I'll try it out later but that would be awesome! |
I use it to open a tilt window , so i do not use any calibration ( at least i'm not aware if i do ). |
I'm using them for my shutters and they work quite well, still it would be great to calibrate the 0 - 100 position since they seem to support setting a position by value there has to be some way to tell the device where 0 and 100 is I suppose? |
The code from @josi0815 works with my LXN59-CS27LX1.0. I did not try to calibrate it though. Just using open, close, stop. |
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 trying to use this on my LXN59-CS27LX1.0, but since it's my first time setting up a non-supported zigbee device, I can't make it work. I'm using zigbee2mqtt on Home Assistant, and I created a new external converter file
And I added the external converter declaration at the zigbee2mqtt configuration yml:
However, even after rebooting, my LXN59-CS27LX1.0 device still show up as "not compatible". Are there any steps I'm missing here? |
I justiced there was a typo on @a-bailey code:
is supposed to be:
|
My Open/Close commands to the switch are inverted but I couldn't find out how to change them. The state are read correctly, it's just the commands that are reversed. I tried modifying this line to Any tips on how to do that? |
You can mark the cover as being inverted by changing |
Well, this didn't work. I believe I will fix it by inverting the wires at the the switch. |
By the way, I declared the needed fromZigbee functions in the external converter itself. Is there a problem to do that or it should work? (I didn't want to change the node_modules folder to avoid being overwritten later)
|
Nope, doesn't matter |
@rrlevy , you can try my modification I posted here. And please remove |
Hello, const exposes = require('/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/exposes'); lfz = {
]; With a small script I can also open, stop and close the device. sendTo("zigbee.0", "SendToDevice", { However, I have not yet found a solution on how to calibrate the device. |
I wonder why |
@josi0815 could you share with us what do you use for shutters? I'm trying to figure out a solution for 5 shutters I have at home that are too heavy to use the motors with integrated zigbee/wifi and I was trying this device for this use case. |
@rrlevy I use 7 Rademacher RolloTube S-line shutters , connected via a DuoFern 9495 USB-Stick to my fhem backend running on a raspi 3 |
@rrlevy I have tried Lupus, Blaupunkt, LXN59-CS27LX1.0 shutter controllers and they are all crap in my opinion. |
That's great, @cody82 !! This is just what I was looking for! I'll get one to test with my shutters. That makes me think, since it's also a Tuya device, if we can adapt its converter to the LXN59-CS27LX1.0 |
I just bought the Lonsonho QS-Zigbee-C01 and it works perfectly well! I don’t recommend this LXN59/LXX60 device. Just don’t buy it. |
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 |
Hello, I hope someone might be able to help me. Yagusmart started selling really good prices curtain switch zigbee actuators on amazon.de https://www.amazon.de/gp/product/B08BFL1HDN/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1.
I bought one a few weeks ago to do aa test implementation and managed to get up/ down running relatively easily (just treating the device like a switch) using the following code in the devices.js
now comes the tricky part.
Since I got that to work I ordered 13 more to fit all of my switches.
I connected the first of the modules and to my suprise they look identical but are a different model number.
The first "test" one is LXX60-CS27LX1.0 the new ones are LXN59-CS27LX1.0.
Those new ones don't respond to anything I do. They seem to send the same messages to the network for example:
Debug Received Zigbee message from 'buero_rollladen_rechts', type 'attributeReport', cluster 'closuresWindowCovering', data '{"currentPositionLiftPercentage":0,"tuyaMovingState":2}' from endpoint 1 with groupID 0 Debug No converter available for 'LXN59-CS27LX1.0' with cluster 'closuresWindowCovering' and type 'attributeReport' and data '{"currentPositionLiftPercentage":0,"tuyaMovingState":2}' Debug Received Zigbee message from 'buero_rollladen_rechts', type 'attributeReport', cluster 'closuresWindowCovering', data '{"currentPositionLiftPercentage":0,"tuyaMovingState":2}' from endpoint 1 with groupID 0 Debug No converter available for 'LXX60-CS27LX1.0' with cluster 'closuresWindowCovering' and type 'attributeReport' and data '{"currentPositionLiftPercentage":0,"tuyaMovingState":2}'
But I can't control the 59er models only the 60s.
Can anyone give me a hint how to approach this problem? I can provide any data needed please feel free to ask.
The text was updated successfully, but these errors were encountered: