Closed NdK73 closed 11 months ago
<Status.NWK_NO_ROUTE: 205>
and Extending timeout for 0x9d request
= the device is sleeping.
Try waking the device up then its paring by pressing the button every 2 seconds then its looks its failing in sleep and not receiving the configuration OK.
Also if its paired OK do one reconfigure this device from the device card and not forgetting waking it up then sending things to it.
I can see you is having more sleepers but do you also have some routers that can helping the network preforms better ? Also wot coordinator is you using ?
Seems the anwer via mail got lost. But I now have news.
Just before re-pairing, I retested the button that yesterday didn't work and now it's working. The only change was a system upgrade (including a HA update to 2022.9.4) and a reboot. None of those changes was about the bridge, and previously I didn't see button presses in bridge's console. I'm really confused. But maybe the hint could help others: update and reboot! And wait the next day before trying do pair again.
Tks and sorry for the noise.
I already tried pressing the button at regular intervals w/ no luck :( The (currently...) working one did not require any presses, and its log is the one I attached at the end of the report.
I also read that newer fw on the button only allows binding to another device, so I also tried binding it to the coordinator from the device page in HA before retrying pairing.
The coordinator is a ZigStar Lan Gateway (link at the beginning of the report).
Tks, Diego
Il mer 14 set 2022, 08:46 MattWestb @.***> ha scritto:
<Status.NWK_NO_ROUTE: 205> and Extending timeout for 0x9d request = the device is sleeping. Try waking the device up then its paring by pressing the button every 2 seconds then its looks its failing in sleep and not receiving the configuration OK.
Also if its paired OK do one reconfigure this device from the device card and not forgetting waking it up then sending things to it.
I can see you is having more sleepers but do you also have some routers that can helping the network preforms better ? Also wot coordinator is you using ?
— Reply to this email directly, view it on GitHub https://github.com/zigpy/zha-device-handlers/issues/1752#issuecomment-1246316754, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAODXYJLLAZIF52364AK7HTV6FYFXANCNFSM6AAAAAAQL22PTA . You are receiving this because you authored the thread.Message ID: @.***>
Is there still an issue here? IKEA devices often need to be woken up again after re-pairing to reconfigure them.
So, open the device page -> click reconfigure device and shortly after starting the reconfiguration, press a button on the remote to wake it up.
issue seems device-dependant. One of the buttons is working w/o issues. The other one gets paired and then disappears. Sometimes it works for some time but suddenly stops. Also tried pressing the action button, start reconfiguration, press the button again every few seconds to keep it awake: reconfiguration failed anyway. BUT if I single-press the pairing button just before starting reconfiguration, it fails very early and events start to come thru.
Its can being problems if paring direct with the coordinator or one router (depends of the coordinator type). And IT coordinator is not setting up them OK then having them as direct children. Try paring thru on router and its very likely working OK and also reconfigure after its being paired.
Actually I couldn't pair it with various routers, but only with coordinator. I now moved it where it does have to go thru 2 or 3 routers and seems it's still working. But pairing is a nightmare.
Had a similar issue. This did the trick for me:
The reconfigure went really fast, exited with an error, but it works nonetheless. I've tried removing/repairing/reconfiguring many times and removing the battery was the thing that finally did the trick for me.
@aykevl I have the same issue, even got IKEA to send another one but neither of them i can detect events. I have tried custom quirks but nothing is working :(
@donoghdb I've now switched over to zigbee2mqtt and they got recognized instantly, no issues whatsoever. At least it shows that the issue really is with ZHA and not with any hardware.
Thank you @aykevl. I now have two working buttons :). ZHA is the issue.
Hey there,
i have the same issue.
i've switched vom deconz to zha with my conbee 2 stick.
i use 3 tradfri shortcut buttons but only 1 is working after i tried hours of reconfiguration and so on but the 2 other buttons won't work.
does someone figured out a method to get them work ?
After getting the the device paired you shall doing one reconfigure from the device card and waking the device up by pressing one key so its not sleeping and can receiving the commands.
It can being tricky getting it working and with the new 24.5 firmware for IKEA controllers its the best way taking the battery out and waiting one half minute and putting it back then start the reconfigure at the same time (I know its not easy, im a Man ;-).
I had the same issue with pairing Shortcut Button with my ZHA and CC2652P. I made several attempts to pair the button. The successful attempt was when I pressed the button regularly (every 1-2 seconds) during pairing and ~2 minutes after pairing. Now I see button events in the Home Assistant logbook
@radian997 I think TI is having one bug that is making problem adding all Zigbee 3 controllers / sleeping end devices direct to the coordinator. If having some router devices try joining them thru them and is very likely working better.
Already tried both workarounds (also combined):
Other devices (including a Tuya 4-button scene switch) work w/o issues. One of the two buttons also worked for some months then decided to not fire events. My Z2M-managed dongle (also CC2652P) w/ no routers attached ( = buttons are bound to the coordinator) sees events from both buttons. That makes me think it's a ZHA/zigpy issue, maybe in a quirk.
Seems the only procedure that seems to work quite often is: 1) delete shortcut button 2) restart HA 3) re-bind the button
Without step 2, events do not appear.
HIH.
After new paring IKEA controller always do one reconfigure for getting the reporting working OK and also dot forgetting binding the group for older for firmware / devices for latest versions if searing lights with them.
Edit: Then deleting one device wait one minute for letting (Z)HA writing the changes in the DB before joining the device or restart HA is also working well or ZHA is reusing the old data and not doing one new paring.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug Similar to #1516 but different context.
I'm using supervised HA where I confugured ZHA to access a ZigStar LAN Gateway. I can succesfully bind a Sonoff SNZB-04 (door/window sensor) and a RSH-ZigBee-SC04 4-button scene switch. Both devices report events to HA. But both the Ikea E1812 I tested seems to have troubles both during discovery and after binding. I once saw events while testing a CC2531-based bridge, but only for a short time. (Actually, while collecting debug info, one of the buttons started generating events... hope it continues)
To Reproduce Steps to reproduce the behavior:
Note that the E1812 gets recognized twice, getting different addresses.
Expected behavior E1812 gets recognized once and generates events when clicked.
Device signature
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant Supervised", "version": "2022.9.2", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.5", "docker": true, "arch": "x86_64", "timezone": "Europe/Rome", "os_name": "Linux", "os_version": "5.10.0-17-amd64", "supervisor": "2022.08.6", "host_os": "Debian GNU/Linux 11 (bullseye)", "docker_version": "20.10.17", "chassis": "vm", "run_as_root": true }, "custom_components": { "tasmota_irhvac": { "version": "2021.12.0", "requirements": [] }, "scheduler": { "version": "v0.0.0", "requirements": [] }, "nodered": { "version": "1.0.9", "requirements": [] }, "remote_homeassistant": { "version": "3.6", "requirements": [] }, "sonoff": { "version": "3.2.0", "requirements": [ "pycryptodome>=3.6.6" ] }, "shelly": { "version": "1.0.2", "requirements": [ "pyShelly==1.0.2", "paho-mqtt==1.6.1", "websocket-client" ] }, "hacs": { "version": "1.27.2", "requirements": [ "aiogithubapi>=22.2.4" ] }, "hisense_tv": { "version": "22.05.09", "requirements": [ "wakeonlan==2.0.1" ] }, "localtuya": { "version": "4.1.0", "requirements": [] }, "dual_smart_thermostat": { "version": "0.5.5", "requirements": [] }, "zha_toolkit": { "version": "v0.8.16", "requirements": [] }, "aquaariston": { "version": "1.0.50", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.33.1", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.79", "zigpy-deconz==0.18.1", "zigpy==0.50.3", "zigpy-xbee==0.15.0", "zigpy-zigate==0.9.2", "zigpy-znp==0.8.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 54828, "manufacturer": "IKEA of Sweden", "model": "TRADFRI SHORTCUT Button", "name": "IKEA of Sweden TRADFRI SHORTCUT Button", "quirk_applied": true, "quirk_class": "zhaquirks.ikea.shortcutbtn.IkeaTradfriShortcutBtn", "manufacturer_code": 4476, "power_source": "Battery or Unknown", "lqi": 178, "rssi": null, "last_seen": "2022-09-13T23:35:18", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional logs: one of the buttons started working while collecting report info
Bind log: ``` [0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_rsp: [