-
Notifications
You must be signed in to change notification settings - Fork 483
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
Blinds Tuya AM43 #4806
Comments
It seem this device is already in the code
Wich one deconz version are you using ? Remember you need 2 inclusions without deleting anything. Or your device is a battery powered one and need too this "helper" to be detected ? |
Are you able to test it ? (need a linux machine with full OS) |
@Smanar is there a chance this device is different then the others? |
I am using the last beta V2.11.1 under windows so I can't test, sorry. |
@mimix, impossible to known, tuya magic, but I have already added 2/3 models of this device and only 1 with the battery tips, because an user have opened an issue just for that. It help a lot to reconize the device, deconz create a battery device, and the "light" part can use this data to reconize the "light" entry @Wimaware this device can work without this PR, but it s harder, try that
|
In that case I'd like the user to add all screenshots. @Smanar please wait with any integration until all screens are provided and you can confirm the functionality |
Nothing more, the PR is already validated #4807 (just today) Can try with the next version. |
Oké, thanks I will try with the next release. |
Yep, that you see in deconz is the reality, the code don't change the device characteristic. Try 2 inclusions, without deleting anything, the first one create a sensor entry, a ZHABattery, and the second one will create the "light" ressource. |
Yesss, that's it. Works great !! Just to know how to do it. |
Np ^^ |
Hey @Smanar , i own the AM43 with battery and i cant add it completely in my system. I use Phoscon 2.11.05 and Fhem. I add the shutter as a sensor two times. FHEM displayed one as battery and the other one as daylight. But it didnt add a "light" . In fhem it displayed in line manufacture: _TZE200_rddyvrci |
I have perhaps found an issue, you don't have the GUI to check for manufacture number ? Have you tried a second inclusion without deleting the battery entry ? |
All seem fine ... Can you share logs during the inclusion ? with "info" and "info_l2" ? |
i deleted the node and added it new. now i have the light. over fhem now i can open and close over bri.
|
Don't worry
It s just because the device is making request on Time cluster (0x000A), but I don't use it, haven't found an utility to that yet. Only 2 devices use it in fingerprint ATM
And BTW, what was the magic trick for the inclusion works finaly ? |
okay. |
BTW, there is a special procedure for calibration on this device ? |
Ha nice, the complete procedure, thx ^^ |
Hello, no one else have direction issue with the device ? Or no issue ? |
Hi everybody. AM43 blinds motor has two physical operating buttons: Up and Down. Up button (located higher, with the arrow heading up) is meant to open the blind, obviously. Please mind you should configure motor rotation to fit your mounting location and rotation requirements, so that this Up button actually moves up / opens your blind. After you press button Up and wait for your blind to fully open, deCONZ API reports states:
I find those data points to report the opposite values, either not true to real world or not compliant with general API docs. I'm NOT using Tuya app or Home Assistant; I control AM43 motors directly from ioBroker via deCONZ API. Could anyone confirm my observations? |
hey, |
Hello, so you have inclusion issue ? Can you try to make a DDF for this device ? https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/DDF-cheat-sheet I can't say if it will work because there is a hack in the code for this device You just need to create the DDf and drag and drop a window covering type, no configuration, no bind, no report. |
yes. i used it on my old system. now i have a new deconz and it dont work. i will test it with ddf next days. thank you |
What was the trick exactly? I added the device in the deconz app through phoscon, pressed "read" two times and then press find new light in phoscon.. nothing happens. How does this work? |
You general need to make 2 inclusions without deleting the device between.
(Phoscon need to be in permit join to add device in the API) Else if you can start a DDF I can finish it (I need at least a skeleton) |
@Smanar Thanks for your fast reply. That is really helpful. I did as you proposed, using the 'read' button (see below). However, it still only finds this one device/entity/node. I was suspecting to get a new node. I am right in this? Anyways, my main goal is to somehow implement this device in Home Assistant, and looking around on the forum, I don't know, even if I would be able to add the entity in the Deconz App, if it would work in Home Assistant.. |
@Smanar I just saw the link for the DDF instructions,
I can see the preview but somehow cannot get the copy to paste in here.. |
No, on deconz there is only 1 node by device (when the name is something like 0xXXXX it mean the device is not in the API, else you have something in it) Deconz have problem with tuya stuff, because they don't respect zigbee rules, the firsts informations deconz obtain are useless and deconz have problem to reconise the device.
Honnestly the inclusion on the legacy code is realy random, I haven't a better procedure than another for tuya stuff. And another bad news for you, you can forget the DDF, this device use too the tuya cluster and this one is not ready yet to be used with DDF for covering. |
Hi, I'm trying to pair some Moes AM43 to Deconz, one motor worked, the other ones don't. Did we have bug fixed recently with this device ? The process that worked for one motor was to add it as a switch then restart the pairing process to add as a light, it showed up as a smart plug and is exposed to HA. I can't reproduce the method to my other motors. Any idea the step I would have missed ? Thanks ! |
No, they are using the old system, and IDK what can happen if we make a DDF to include it. The DDF can help for inclusion but not possible to use the DDF during the working mode. Generaly, you need to include the device at least one time for deconz have the manufacture name, then include it a second time and deconz will use the manufacture name already in database to reconize it. Are you sure all device are the same model ? Tuya use lot of clones. |
I've tried to include them 2 times in a row, multiple times. Thanks ! |
Here is some logs when trying to redo the pairing a second time : |
This is the sensor part.
If you have the GUI and if you have the ZHAbattery
|
This one ?
Johan Arens
***@***.***
… On Jan 11, 2023, at 1:04 PM, Smanar ***@***.***> wrote:
This is the sensor part.
On the light part you need to have in log (visible with info_l2 and "info)
DBG_Printf(DBG_INFO_L2, "Tuya debug 7 : Missing manufacture name for 0x%016llx\n", node->address().ext());
DBG_Printf(DBG_INFO, "DeviceAnnce of LightNode: %s Permit Join: %i\n", qPrintable(i->address().toStringExt()), gwPermitJoinDuration);
If you have the GUI and if you have the ZHAbattery
set phoscon in permit join (add new light)
read the descriptors (on the menu, on the first circle on the node title)
—
Reply to this email directly, view it on GitHub <#4806 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJZAUAX4JHK5BDKHEOTAZO3WR3Y33ANCNFSM43QJTPFQ>.
You are receiving this because you commented.
|
I don't have ZHA-Battery, is it part of the zha integration in HA ? |
Ok I figured out with the node descriptor thing. Here is what I've tried, deleting the node, re-adding the node, click on read description, re-starting the pairing process as light. No luck, the motor is stays as battery. |
OK found the way to do this. When adding a new motor, once it is detected and seen as a battery, right-click and point to read simple descriptor, that turns the node into a Smart Plug. |
I think it's the good place. |
Hey guys, I have a strange issue with 2 motors, I'd like to pickup your brain. With the motors paired to deConz and exposed to HA, I was able to use the motors. Another motor is seen as disconnected in HA, but it is well there in deConz, I see it as active, I can read descriptors etc. Any idea what could be going on ? Thanks ! Johan |
Hi, Please open a forum topic for device specific help. Locking this up. Kind regards, |
I noticed the new beta release V2.11.1 beta.
There is an addition of the Moes AM43.
Initial support for Moes ZigBee Smart DIY Motorized Roller AM43-0.45/40-ES-EZ(TY) #4674
Is there a way to add the _TZE200_zah67ekd to it, it's exactly the same device.
See #4310
Thanks
Screenshots
Basic
Identify
Alarms
Device Temperature
Groups
Scenes
On/Off
Level Control
Color Control
Simple Metering
Diagnostics
Other clusters that are not mentioned above
The text was updated successfully, but these errors were encountered: