-
Notifications
You must be signed in to change notification settings - Fork 506
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
MoesHouse/Tuya AM43 Blinds Drive not working #4942
Comments
Hello, have take a fast look on code. And I have checked the API https://dresden-elektronik.github.io/deconz-rest-doc/endpoints/lights/ there is no "ontime" field at all. I think the first command don't work because of this field, and the second one because the covering is already in place. |
Sorry, on the second command, the blind was in DOWN/CLOSED position, so not in place. Unless somehow the internal state of deCONZ thinks it is in place? |
Ha yes, and for this openhab is right on = false is to open the covering. But it can be from the mounting side. Can you try the reverse request ?
|
This is what I got running PUT/PATCH. No movement on the device.
|
This command don't make mouvement, but it reverse the side (for some devices) |
Ok so there is an issue, if even with both command and the good param nothing is moving. I need to go for today, will check tommorow. And can you share some logs with "info" and "info_l2" when making a request with "on":true or false pls ? |
Logs when sending
Logs when sending
Logs when sending
|
Have take a look again on logs, I realy don't see something special for this device.
It s realy like your device was not connected, or in deep sleeping. |
I can't see any timeout errors. |
You haven't manualy command on the device ? To check from return in log from it ? |
When I press the buttons on the device it works. Where I can see logs? INFO_L2? |
yep, "info" and "info_l2". |
So blinds was in
|
Down
UP
STOP
??? 0x02 mean value, but don't remember 0x69
position reached
Fault
And when you make command for UP
So the command is good. And someone have succed somes days ago with the same device #4806 (comment) Can not be a "mode" problem ? You are locked in calibration mode, so commands can be disabled. |
I don't know what "mode" problem is supposed to be. Should I try pair it again? Should I use pwa/add lights or permit join in gui? |
You haven't already tried to include it again ? Better to use phoscon/add new light (and no need to delete the older entry, will be easier) And have checked on other project, there is no "calibration" command for device that use the tuya cluster. |
test to delete the note in gui. then connect it in phoscon as sensor 2 times. then it works at me. |
And he have put the procedure for his one #4806 (comment) |
If by calibration you mean the upper and lower limit I've set it before pairing it. I'm trying to re-pair it as we speak to see if it works. |
@Smanar I re-paired it as you suggested, now after I send a command through the API I can see device moving. |
It s a long story, will be corrected in a new api version, but to make short, deconz is not able to reconize tuya device. But don't sure you are concerned by that, this issue prevent the device creation and as you can see it in phoscon was another problem |
Thanks for the clarification and for your help. Since it is working feel free to close the issue. |
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Describe the question or issue you are having
I'm looking for advice on a device that seems to be supported, because it is shown in web ui, although I can't find in docs.
Device is: MoesHouse/Tuya AM43 Blinds Drive
So here is my scenario: I use openhab 3.1.0M4 which is the client of your deCONZ rest API, currently version 2.12-0-beta, Openhab has the following "actions" it sends to the api:
UP
,DOWN
,STOP
. When I clickDOWN
, I can see the following in the logs:And nothing happens.
If I click
UP
, I can see the following:And besides the successful message, and the blinds being closed/down, nothing happens.
Trying to manage the blinds through the web ui also does nothing.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: