Hybrid E-Wand CP180335E getting error "Failed to interview" when paired #9604
Comments
|
Could you provide the herdsman debug logging when trying to pair this device? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. |
|
Thank you for looking at this. I am attaching file to this message. Just in case it does not come through here is the main part: 2021-11-17T20:28:34.006Z zigbee-herdsman:adapter:zStack:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":1,"srcaddr":27654,"srcendpoint":196,"dstendpoint":1,"wasbroadcast":1,"linkquality":18,"securityuse":0,"timestamp":4667442,"transseqnumber":0,"len":64,"data":{"type":"Buffer","data":[0,77,10,7,0,66,9,99,112,99,58,101,119,97,110,100,4,0,66,8,48,48,46,48,48,46,49,56,5,0,32,255,6,0,33,22,0,0,0,32,4,1,0,33,44,1,2,0,33,176,4,3,0,32,3,11,0,33,10,0,12,0,32,11]}} |
|
Do you by any chance have the original gateway? If yes, could you make a sniff when pairing this device to it? https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531 |
|
I don't - I have the Circuit Setup's CC2652P2 USB Coordinator. I also have a ZZH! coming in someday... If you can point me to the product you are talking about I can buy one if they are still available? Thanks. |
|
|
I did try 5x with each change. First I did try pairing right up next to coordinator in my basement. Then I tried the USB extension cable, tried pairing again. Finally tried to pair next to close by repeater plugged into wall. The E-wand makes the ode to joy tune to indicate successful pair each time too. Also replaced batteries with same result. Keep getting the interview failed message. Thank you. |
|
No, I didn't follow any special procedure except what was in the manual. That said I'm pretty sure all mine are Gen 2 (they show as CP180335E-01, not sure if that is different than CP180335E or what they've changed between Gen 1 and Gen 2). @gregjwinter are these new? I had to replace one that kept dropping off the network, and had a very positive experience with Current Products Corp's support. Soon as I explained my issue and gave my order number a fedex package was on the way. They may be able to help you if there's something wrong with your E-Wand. |
|
Yes I purchased one unit from Amazon. There is a tape seal that I had to cut through to open the box. It has "A ZigBee Certified Product on the box. First thing I did when I had this issue is call support at Current Products Corp to verify that I did indeed have a Gen 2 unit. He asked me to unscrew the battery cover and see if the grommet is blue vs black. I have blue grommet which is Gen 2 unit. My part number printed in small print on unit is: CP180355E-01 serial 2408210007. |
|
I think I bought mine off Amazon as well, they gave me no trouble. If you
haven't already I would try the factory reset procedure from the manual,
otherwise you may have a faulty unit.
…On Thu, Nov 18, 2021, 12:34 PM Greg J. Winter ***@***.***> wrote:
Yes I purchased one unit from Amazon. There is a tape seal that I had to
cut through to open the box. It has "A ZigBee Certified Product on the box.
First thing I did when I had this issue is call support at Current Products
Corp to verify that I did indeed have a Gen 2 unit. He asked me to unscrew
the battery cover and see if the grommet is blue vs black. I have blue
grommet which is Gen 2 unit. My part number printed in small print on unit
is: CP180355E-01 serial 2408210007.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMTZ2FVRE6XSMGSTZXJVQTUMU2KXANCNFSM5H3DL7CA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
I just tried 2x factory reset and tried to pair. I will contact manufacturer now. Thank you. -Greg. |
|
Good news. I have an advanced replacement on the way and arriving on Tueaday! Will report back. |
|
@Koenkk 2021-11-26T01:58:21.942Z zigbee-herdsman:controller:error Interview failed for '0x588e81fffe9711ab with error 'Error: AREQ - ZDO - simpleDescRsp after 10000ms' Is there anything else I can do? 2021-11-26T01:58:11.880Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 7 - 2 - 5 - 133 - [156,173,0,156,173,1,1] - 199 |
|
Could you make sniff when trying to pair this device?https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531 |
|
@Koenkk - do I need to buy a CC2531 adapter for this purpose (sniffing)? I do have 2 different CC2652R1 units: zzh! and CircuitSetup's CC2652P2 USB Coordinator. If these do not work it would be easier to get a HUSBZB-1 stick on Amazon. Let me know and I'll order one. Thanks! |
|
@gregjwinter sniffing using a C2652 seems to be possible with packet sniffer 2 (haven't tried this myself yet). fws are bundled with packet sniffer 2: https://software-dl.ti.com/simplelink/esd/simplelink_cc13x2_26x2_sdk/3.20.00.68/exports/docs/zigbee/html/zigbee/packet_sniffer.html#hardware-setup |
|
Sorry, I'm still relatively new to all this ZigBee and custom home automation stuff so I'm not sure how much help I can be, other than to say, I had no trouble going through the initial setup with these, no trouble at all aside from the one they replaced for me through warranty, and my setup is this:
Mosquitto Broker and Zigbee2MQTT are both running on the HAOS VM I think these are the only flags in my Zigbee2MQTT config which aren't default: |
|
@scottpk @Koenkk - some news that is positive this time! |
|
@Koenkk - how do I capture the pairing of the E-wand and send the data to you? I have this in my config: There is a "log" tab in Home Assistant: Supervisor --> MQTT2Zigbee but it only captures 100 events and it missed the pairing event. I also used Wireshark to capture a pcapng type file with all the events. How do I send this to you? Thanks. -Greg. |
|
I think these would be the instructions to follow for capturing the logging: |
|
@scottpk I can see zigbee-herdman events that show up in the log tab of the zigbee2mqqt addon but it seems to miss the pairing event. I don't know how to grab the past events. I am running Home Assistant OS/Supervised addon and when I go into Terminal I try to enter "docker ps" under the [core-ssh ~]$ it replies "bash: docker: command not found" Any ideas of what I can do? I am stuck. Feel like we are getting close, at least it recognizes the manufacture/device. I just fails the interview process. Thanks guys. -Greg. |
|
I think I captured the herdman log of the device pairing finally. This is the most interesting part: Attaching the whole thing: |
|
@gregjwinter could you share me that pcapng file that wireshark creates on save? To keep the sniff as clean as possible:
|
|
@Koenkk the file is here: https://www.dropbox.com/s/xvpsdkpaesc43ud/E-Wand_20121205.pcapng?dl=0 |
|
@gregjwinter thanks for the sniff, I don't see the e-wand initiating any pairing, it should send a "Beacon" request (under the info column) after you factory reset it, can you manage to produce this? |
|
@Koenkk OK I have re-created the sniff with the pairing taking place. So I started sniffing, permit joining, factory reset e-wand, wait 30 sec., initiated e-wand paring, waited 2 minutes, then saved the pcapng file. I now see the "Beacon Request" under Info column. If I missed any steps let me know and I'll try it again. |
|
@gregjwinter could you do the same and also provide the herdsman debug log of this pairing attempt? With this sniff it shouldn't fail with a See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. |
|
@Koenkk Did you see this? https://www.dropbox.com/s/mrc1z4e7taedn84/E-Wand_Herdsman.txt?dl=0 If this is not enough and need the log: I already have herdsman debug logging turned on. I am running Home Assistant OS/Supervised addon and when I go into Terminal addon to HA I try to enter "docker ps" under the [core-ssh ~]$ it replies "bash: docker: command not found" Sorry for my lack of Linux knowledge. I also tried using putty to log into the Raspberry Pi that my HA is installed and it will not allow me to connect. Thanks. -Greg. |
|
Did an attempt to fix it, can you check? Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
|
Just a pointer since you mentioned you too are using HomeAssistant OS - scroll to the bottom of that page. Below is a screenshot of what it's talking about, you would uninstall the one called "Zigbee2mqtt" and install "Zigbee2mqtt Edge"
|
|
@gregjwinter no repairing needed, just uninstall normal and install edge. |
|
@Koenkk Progress! I can pair the device using Edge version just fine. Things appear normal, however I cannot control the tilt at all. Previously I could pair the device (and have that ! indicator) but failing the interview. But I could tilt/control the blind motor. Now the ! indicator is gone and I don't have any control. Here is my most current log here: https://www.dropbox.com/s/0sfgro509a65a6i/E-Wand_Herdsman_20211207.txt?dl=0 |
|
@Koenkk Got back to this after work. I realized I did not have Herdsman debug turned on. For some odd reason my control from Home Assistant is working now! But don't close this yet as I have more testing to do :-) I did see this in the log: Zigbee2MQTT:debug 2021-12-07 17:33:30: No converter available for 'CP180335E-01' with cluster '64528' and type 'raw' and data '{"data":[13,99,18,111,128,168,0,0,0,0,2,0,0,0,64,96,62,0,0,156,65,1,0,0,0,180,0],"type":"Buffer"}' What does this mean? It does send this when I closed the shades: |
|
Could you provide the data/database.db entry of this device for the following 2 cases:
|
|
Koen - I can control the device in Home Assistant now. Just started to work later in the day. However as of now I do not have any feedback of position (shows up as unknown) and does not sync up to Google Assistant like my IKEA shades do, also controlled by Zigbee2MQQT. Here is a copy of my edge database.db file: https://www.dropbox.com/s/hlkns1s0h8qpzdd/DatabaseDb_20211208.txt?dl=0 Here is a link to a ZIP file containing some screen shots showing the unknown, comparison of data from IDEA "vs" Entity returned for my test E-Wand: https://www.dropbox.com/s/k2b3h7ynov011g8/E-Wand_20211208.zip?dl=0 Again, thank you for your help with this. Really appreciate it. -Greg. |
|
I'm surprised, I did not have so many problems... The Google Assistant issue I may have an idea for, because they didn't show up automatically in Alexa either. I had to go into the Home Assistant Cloud settings, and click the button that says "Sync Entities to Amazon" - then after telling the Alexa app to search again they were there. So it might be the same thing for Google Assistant. |
|
@gregjwinter the position/state (open/close) should be reported once you set the position once via HA. If not, please provide the debug log when setting it. |
|
I just tried it today, works but no position feed back in HA. Here is my Herdsman log: https://www.dropbox.com/s/fn9qfbbmjnsd10q/E-Wand_Herdsman_20211209.txt?dl=0 Note the line at bottom: Zigbee2MQTT:debug 2021-12-09 12:42:56: No converter available for 'CP180335E-01' with cluster '64528' and type 'raw' and data '{"data":[13,99...... What does this mean? @scottpk Yes I do push the button "Sync Entities to Google" after making changes in HA. Does your E-Wand give you data like this picture? |
|
I'm on the stable version not the dev version, but mine looks like this: |
|
|
The only way I can control the E-Wand is within the Home Assistant itself. For some reason the entity comes into Google Assistant and shows up as something to control, but cannot be controlled by saying OK Google, close the shades like I can do with my Ikea shades. I suspect the reason is that Google expects the entity parameter to be "current_position" and not "current_tilt_position." @Koenkk is there a way to change this parameter to "current_position"? |
|
@gregjwinter |
|
@gregjwinter I haven't fully tested this but you could try manually configuring the device in homeassistant (configuration.yaml) to imitate the position attribute. You'll obviously have to adjust for whatever your device name is but here's what I was able to get working (asking google to open,close, open to a specific percent, etc.) : If I had to guess Alexa can handle tilt devices where as Google can't from the looks of it. Originally when I added this I wanted to imitate the position at the converter level as that also fixed the state coloring in the HA dashboard. In any case if this works for you then you can prevent zigbee2mqtt from publishing discovery information (https://www.zigbee2mqtt.io/guide/usage/integrations/home_assistant.html#home-assistant-device-registry) and just manually configure them. With regards to the manufacturer specific cluster someone did provide more information about that (#7648 (comment)) but honestly I'm not sure exactly how to implement or address that. Hopefully that helps! |
|
@Koenkk I purchased 2 more E-Wands directly from manufacturer. They passed interview and show up in my Zigbee2Mqtt Edge controls. When I try to control them I get this error message in the log: Error Publish 'set' 'tilt' to 'Hallway Shade Right' failed: 'Error: Command 0x84fd27fffe80d5ce/196 closuresWindowCovering.goToTiltPercentage({"percentagetiltvalue":0}, {"sendWhenActive":true,"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 1789 - 196 - 48 - 258 - 11 after 10000ms)' I think we saw this message before you fixed things before. Anything I can do? I thought I was good but I was hoping to control 3 shades in my Hallway windows. Thank you. -Greg. I also get the same message with the other shade: |
|
This means the device cannot be reached, do they work when moving them closer to the coordinator? |
|
@Koenkk Thanks for the response. I just tried to re-paired one of them close to the coordinator (within a foot). Same thing, it shows up in m2q just fine but no response when I try to control it. I did see this error in the log after I paired it: Failed to configure '0x84fd27fffe80d5ce', attempt 1 (Error: Bind 0x84fd27fffe80d5ce/1 genPowerCfg from '0x00124b00237e084c/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7)) Also here is the debug when I try to move the new E-Wand: Debug Received Zigbee message from 'Hallway Shade Center', type 'raw', cluster '64528', data '{"data":[13,99,18,19,128,154,0,0,0,0,2,0,0,176,202,250,67,0,0,161,65,1,0,135,0,80,0],"type":"Buffer"}' from endpoint 1 with groupID 0 Finally here is a screen shot of device seen by m2q: |
|
Interesting, could you make a sniff of:
|
|
@Koenkk Here is a sniff with a pair of new left shade and then I try to open and then close it: Here is a sniff with the working center shade with a open and then close command. This one works: Finally a sniff of just the non-working left shade open and close command. Does not work. The command to open and close comes directly from Zigbee2MQQT Edge controls in Home Assistant and I am using the controls on the tab "Dashboard". Thank you. -Greg. |
|
@gregjwinter thanks, I've checked your sniff and it seems that the coordinator doesn't send the command. What should happen is that the coordinator send the command to the parent of the e-wand, then the e-wand should do a data request (which it does) and send the command. Could you make a sniff again and also provide the herdsman debug log when sending the command? A sniff + log with just the failing command is enough (like Also before making the sniff, also try with the latest firmware from: https://github.com/Koenkk/Z-Stack-firmware/tree/develop/coordinator/Z-Stack_3.x.0/bin |
|
@Koenkk So first thing I did was change the firmware on my Electrolama zig-a-zig-ah! (zzh!) moving it to CC2652R_coordinator_20211217. Not sure if that is the version is the one you wanted me to flash. Once I did this it took a restart of the service and unplugging the zzh! and plugging it back in to get stuff working again. I went to start testing and the left and right shades work now! I am not sure if the removal of the zzh to my laptop and then putting it back in made it restart the service or if it is the firmware upgrade. The only thing that does not work is Google Assistant but I can control them in Home Assistant. I just got a work around working using Node Red to trigger the open_cover_tilt command and it seems to work. |
|
Good to hear, assuming this issue can be closed now. If the issue re-appear feel free to reopen this issue with the sniff + logging as mentioned in #9604 (comment)
This seems to be related to Home Assistant, I suggest creating a post on the HA forum |
|
Thank you for all the help with this. -Greg. |
|
Hi team. Sorry (not sorry) to reopen this - but is there any way to get the State field in HA to reflect the state of this product? Seem Z2M can see the state (open stop close is shown) - but it's not translating that into the state field of HA. Looks like some missing data converting from MQTT to HA : https://www.home-assistant.io/integrations/cover.mqtt/ Otherwise how do we set a template to use Tilt 100 as Open, and Tilt 0 as Closed and feed that to the HA state? Thanks, |
Bug Report
Hybrid E-Wand CP180335E getting error "Failed to interview" when paired
What happened
E-Wand joined OK but does not complete interview process.
Failed to interview '0x588e81fffe9710d6', device has not successfully been paired
What did you expect to happen
All my other Zigbee devices paired OK from HUE and Leviton but not E-wand from Current Products Corp.
How to reproduce it (minimal and precise)
Happens when I try to pair the E-Wand device. Tried 5X Throws the following error:
Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
Received Zigbee message from '0x588e81fffe9710d6', type 'raw', cluster '64528', data '{"data":[13,99,18,62,128,192,0,0,0,0,2,0,0,0,136,225,64,0,0,183,65,0,255,0,0,0,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Received Zigbee message from '0x588e81fffe9710d6', type 'attributeReport', cluster 'genPowerCfg', data '{"11":10,"12":11,"2":1200,"3":3,"4":"00.00.18","5":255,"6":22,"7":"cpc:ewand","mainsFrequency":300,"mainsVoltage":4}' from endpoint 196 with groupID 0
Debug Info
Zigbee2MQTT version: 1.22.0-2
Adapter hardware: CircuitSetup's CC2652P2 USB Coordinator
Adapter firmware version: 20210708
The text was updated successfully, but these errors were encountered: