I have before downgrading one wireless dimmer (the old round with gyro) and it was working but its dont with the new firmware installed and i have flashing back one E1743 with SWD for testing but its not possible for normal user to do. Line 85203: 2020-12-09 14:35:13 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 Line 84890: 2020-12-09 14:33:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL deserialize: to your account, Running Ikea on/off switches and remote controls with ZHA and Sonoff ZB Bridge on HA running on Proxmox. Were you able to somehow figure this problem out? And using the zigpy/zha-device-handlers#693 for editing the file. I doing like that then having firmware files that need being looked at.
Couldn't fix it and wound up taking it back to Ikea and they gave me an exchange for a new one. Also I opened a ticket with POPP to check on this, waiting still. Some IKEA controllers is not reporting voltage other do but all is reporting %. I solved it by adding the remote via add devices by a lamp not over the coordinator. Dispose of used batteries according to the, The remote control is for indoor use only and can be used. This is what I get when re-pairing one Ikea remote control. But any press on the remote, zha receives data and marks it online again. We have to reset it and pair it again in order for the device to become available again in the network. Better is doing one copy of you configure.yam before editing it and then easy to redo it :-))). Line 30290: 2020-12-09 01:00:01 DEBUG (MainThread) [bellows.zigbee.application] Extending timeout for 00:0d:6f:ff:fe:11:b4:06/0x3f43 I thought maybe some chance its the pairing outside of the Tradfri gateway but reviews on IKEA website seem to indicate its common issue. TRADFRI remote control (E1524) (5 Btm Remotes new and old) Line 84957: 2020-12-09 14:33:35 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 Line 85229: 2020-12-09 14:35:15 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: []
3b T9DD+5%)1"R(%$Q k%f#^k/bZ(A@[8qO3m61~j9--Q `bI66S} cbdJatV3`J (bf+x"(QmLKj) >VW:>8d41PGp\ RKE$5R}! The draining is a lot less then what it was before but on some devices i am still only getting 2-3 weeks out of them before they go offline and need a new battery. But now with ZHA and Sonoff ZB Bridge the batteries get emptied very fast without me pushing any buttons. Open the back of the remote. Line 68376: 2020-12-09 12:10:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 Line 55888: 2020-12-09 08:59:26 DEBUG (MainThread) [zigpy.neighbor] [0x0000] request status: Status.SUCCESS. Thanks for the ikea firmware insight, i won't upgrade. Try again. Good and bad things: For the moment I only seeing one premium product on the market and its @tube0013 (https://www.tubeszb.com/) network attached coordinator with TI and EZSP chips onboard :-)). fyrtur kadrilj opac opaco estore cinz pilhas fios estores verdunklungsrollo kabellos baterii rullo tenda ajustar includo comando I having one RaspBee I (x-production system) its not bad but not good for 50 and the deCONZ is having support that is not working as expected for one "premium product". I got two set of Fyrtur blinds for two windows on the same wall a few months ago. vwf6EH+ Press J to jump to the feed. When the remote control is used regularly and as, intended, the batteries will last for approximately 2, When it's time to replace the battery, a red LED indicator, will flash when you press any button on the remote, Open the battery lid and replace the battery with a new, Risk of explosion if battery is replaced by an incorrect, type. Nothing. by IKEA of Sweden Successfully merging a pull request may close this issue. After I replaced the first battery from Ikea with a descent battery, the battery lasts. Have seen user is having problem with the same coordinators in ZHA, tasmota and deCONZ :-((. c%b71$p";ipLx "Y8zzjK Network attached with ZHYA TBGW (Ethernet) and ESPHome (WiFi) that working good if having satiable WiFi / Ethernet. Can you please let me know how to enable debug logging and monitoring, please? Yeah, that was the first thing I did to see if the battery was dead. Your zigbee network dont like the remote (or more correct the router its using is making bad things). I just set up a switch and the sound controller and both are dying VERY quickly (24 hours or so). Create an account to follow your favorite communities and start taking part in conversations. Are you sure they are charged up ok?
Line 47046: 2020-12-09 05:56:28 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0020] ZCL deserialize: e.g a device with NWK address. Line 67017: 2020-12-09 11:57:20 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (, 0x3f43, EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1, destinationEndpoint=1, options=, groupId=0, sequence=66), 67, b'\x00B\x00\x04\x00')
I created a blueprint to catch the events from the remotes. Line 68374: 2020-12-09 12:10:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL deserialize:
I use a 2 button-IKEA switch with Zigbee2MQTT. After switching from, Light flashes 4 times. If IKEA is not relenting one working version you is sucked with one not working version :-(( I agree with you that E1743s battery is lasting lasting longer on the IKEA GW. I have tried re configuring once paired. Line 1529: 2020-12-08 20:55:21 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] [0x3f43](IKEA of Sweden TRADFRI remote control) restored as 'available', last seen: 1:56:07 ago
Could this be caused by incorrect configuration in HA? Hopefully that can help with the issues. You signed in with another tab or window. Also if can doing little hacking the tuya Ethernet ZBGW (https://github.com/banksy-git/lidl-gateway-freedom) is working great after patching it and updating the firmware on the module and working great in all platforms also docker then its using network attached com ports and not local comports / USB that is making it flexible. Once the TubeZB Coordinators come back in stock i might order one from all the issues this sonoff bridge has given me.
Line 30298: 2020-12-09 01:00:04 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0000] ZCL deserialize: Line 1676: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0000]: 'async_initialize' stage succeeded Line 68373: 2020-12-09 12:10:32 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=255, options=, groupId=0, sequence=250), 192, -52, 0x3f43, 255, 255, b'\x01C\x02'] Line 5772: 2020-12-08 21:15:24 DEBUG (MainThread) [zigpy.neighbor] [0x0000] request status: Status.SUCCESS. Any way to downgrade to previous version? Have quite a few that are reporting full to 60% a couple that have been on 30+ for a rather long period. It is located close to a router. I think so for some users but not all and its still looks like one Sonoff problem with the hardware in ZBB and the stick. ! I could not solve this problem and IKEA replaced my switch with a new one. I think the most is related to Sonoff ZBB but some user was reporting having the same problem with CorrnBee II. For more information, please, Manual will be automatically added to "My Manuals", Remote Control IKEA TRDFRI Instructions Manual, Accessories IKEA TRADFRI Instructions Manual, Accessories IKEA TRADFRI Assembly Instructions Manual, Lighting Equipment IKEA TRDFRI Quick Manual. The thing is an Ikea switch that sits next to it and is used the same still has plenty of battery. Hypothesis, maybe if home assistant didnt poll the remotes all the time to ask for battery life, just maybe, the battery might last longer. And this is why the battery depletes that fast. Line 83011: 2020-12-09 14:18:14 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] Nwk is 0x3f43 for this case, ` Line 670: 2020-12-08 20:55:06 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0000] Attribute id: 5 value: TRADFRI remote control Hold down both buttons on the blinds. More than 2 days ago, I noticed that the Ikea remote control I am monitoring finished the battery again. After one week, it works great. Welcome to the IKEA Home Smart sub (Formally TRDFRI Sub). I like these switches but they arent work new batteries every single day. Y{wON!y'u)I7i^wJ2.M=Xh^Q_qz^PGub CzYbtBRIb'W^rBB[! I have 6 and they are all dead. By the way the IKEA batteries is not very god but also not very bad but pretty OK for the price (Its no VERTA ones also by price) and if its not very old more than 3V. Line 84889: 2020-12-09 14:33:32 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=255, options=, groupId=0, sequence=253), 172, -57, 0x3f43, 255, 255, b'\x01G\x02'] Line 1684: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x3f43](TRADFRI remote control): completed initialization New one works great. Very bad news for battery saver is that IKEA have updates in the pipe (released in the OTA test feed) so need more CR-2032 :-(((. TRDFRI on/off switch (E1743) (2 Btm Remote and i think Open/Close for blinds is using the same firmware but not the KNYCKLAN Open/Close remote (E1841) that have one other firmware images). I reporting back if doing some new findings. Zigbee Dongle : Telegesis ETRX357USB. New batteries discharge only after a few days and the remote controls stop working. https://github.com/banksy-git/lidl-gateway-freedom, Implement Ignore list for poll control configuration on Ikea devices, Home Assistant Core release with the issue: 0.118.4, Last working Home Assistant Core release (if known): Not known, Operating environment (OS/Container/Supervised/Core): Proxmox, Integration causing this issue: ZHA with Sonoff ZB Bridge. Powered by Discourse, best viewed with JavaScript enabled, IKEA TRADFRI on/off switch with ZHA using a lot of battery, Migrating from IKEA TRADFRI to Zigbee Home Assistant, [solved, sort of] ZHA IKEA remotes not pairing properly or not working after pairing, Ikea Tradfri Remote (5 button version) was working, now doesn't, very confused, IKEA Tradfri - Batteries in the remote controls are quickly discharged.
Also then changing batteries always putting 2 new ones from the same batch / type or it can being that one is falling faster and the other is lasting longer but cant being used then the summary of the voltage its failing to low. Until today. Line 85230: 2020-12-09 14:35:15 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 If it reports more often, then this must be the problem. Line 1679: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0019]: 'async_initialize' stage succeeded The remote did not connect to the network as it should (I tested it with zha_event). and you'll get all the messages related to the device, Finally I managed to do it. Zigbee Coordinator Press the button. ZHA is fixing that with dubbling the battery % on IKEA devices in the quirk. Return it for a new one. Hold it up to the blind. --- Cool. I suggesting first look on the network map witch router is the bad remotes parent (Integration > ZHA > Configure > visualization = network map). Sign in response: Neighbors(entries=10, start_index=9, neighbor_table_list=[Neighbor(extended_pan_id=cc:cc:cc:cc:d7:12:cf:a4, ieee=00:0d:6f:ff:fe:11:b4:06, nwk=0x3f43, packed=18, permit_joining=, depth=1, lqi=0)]) Interesting is the network map to see if the remotes is connected in the system. Nothing. If you is looking in ZHA visualization (the network map) is the remotes that is draining the batteries direct connected to the coordinator or also to routers ?? Its more issues that can helping that: 675253 and 703231. Wait for it to open all the way. Line 85227: 2020-12-09 14:35:15 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=255, options=, groupId=0, sequence=1), 160, -60, 0x3f43, 255, 255, b'\x01K\x02'] g}[EFI`B!5I4DpU;1n c DpD/T Line 1115: 2020-12-08 20:55:08 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0001] Attribute id: 33 value: 174
I have been using the Sonoff zigbee bridge with firmware version 6.7.9 for over a month and am still experiencing battery draining. Line 70021: 2020-12-09 12:25:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] I have to say that I used the respective switches and remotes with the Ikea Tradfri Gateway and I did not have this problem. The one exemplified above is e1810, but I also have E1743 but create the same problems. This looks very similar.to your situation, but i don't know when the bug was introduced.
And I can see in Zigbee2MQTT logs that this module barely ever speak with the zigbee controler, sometimes it does not communicate for 12 hours.
I had the same problem. First E1743 little more then 10 month and the second around 15 month running on the original batteries. I had the same problem with ZHA. So Sonoff ZBB with ZHA is killing the remotes and CornBee II with Z2M is not.
LCd-C\$V X@ T/. It remains unavailable.
I will let it add some more data. I don't have to pair again. This is the largest community of users for the IKEA product range, and has a wealth of knowledge and experience in all things Smart Home. @ygreq I and no one can recommending that something that is working 100% with all devices and combination of them. Some very cheap cels can having under 3.0 V then taking them out of the package and that is nearly zero in lifetime of the battery. Once paired, they are recognized by the system with their old names I set. I dont have the gateway. Is you using on Sonoff ZBB as coordinator or somthing else ? Restart HA between the changes and dont forgetting reversing the changes in step one then have doing all or you is getting problem later. when zigpy receives a message from a device on the network, it would normally log that message with NWK address of the device. I will maybe try to see if it has the same behavior. Line 1138: 2020-12-08 20:55:08 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0000] Attribute id: 4 value: IKEA of Sweden The lost devices on reboot can being fixes in the new firmware but i have not seen that problem so i cant testing it. blinds Line 85200: 2020-12-09 14:35:13 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=1, destinationEndpoint=255, options=, groupId=0, sequence=0), 164, -59, 0x3f43, 255, 255, b'\x01J\x02'] LE: Found it: secondary_info: last-changed, As you can see in the report, and about what @macfly92 is reporting as well, we have 2 problems, the second one being that once battery is depleted and we change it, the device does not come back online even if we leave it for hours or we press on it many times. Looks like the battery percent is calculated based on the difference between current reading and the minimum value, so in this case 1V (1000mV) drop is actually 35% of the useable capacity and reaching 2.82V (2820mV) is equivalent of 0% capacity, even though device might still be working fine with this voltage. I don't know it it is repeating itself so I copied 2 examples: 2020-12-06 18:16:45 DEBUG (MainThread) [bellows.zigbee.application] EZSP Counters: COUNTER_MAC_RX_BROADCAST: 65535,COUNTER_MAC_TX_BROADCAST: 65535,COUNTER_MAC_RX_UNICAST: 65535,COUNTER_MAC_TX_UNICAST_SUCCESS: 12971,COUNTER_MAC_TX_UNICAST_RETRY: 29902,COUNTER_MAC_TX_UNICAST_FAILED: 10168,COUNTER_APS_DATA_RX_BROADCAST: 484,COUNTER_APS_DATA_TX_BROADCAST: 484,COUNTER_APS_DATA_RX_UNICAST: 7797,COUNTER_APS_DATA_TX_UNICAST_SUCCESS: 6796,COUNTER_APS_DATA_TX_UNICAST_RETRY: 2522,COUNTER_APS_DATA_TX_UNICAST_FAILED: 1165,COUNTER_ROUTE_DISCOVERY_INITIATED: 1135,COUNTER_NEIGHBOR_ADDED: 20,COUNTER_NEIGHBOR_REMOVED: 10,COUNTER_NEIGHBOR_STALE: 440,COUNTER_JOIN_INDICATION: 15,COUNTER_CHILD_REMOVED: 9,COUNTER_ASH_OVERFLOW_ERROR: 0,COUNTER_ASH_FRAMING_ERROR: 0,COUNTER_ASH_OVERRUN_ERROR: 0,COUNTER_NWK_FRAME_COUNTER_FAILURE: 0,COUNTER_APS_FRAME_COUNTER_FAILURE: 0,COUNTER_UTILITY: 0,COUNTER_APS_LINK_KEY_NOT_AUTHORIZED: 0,COUNTER_NWK_DECRYPTION_FAILURE: 0,COUNTER_APS_DECRYPTION_FAILURE: 0,COUNTER_ALLOCATE_PACKET_BUFFER_FAILURE: 0,COUNTER_RELAYED_UNICAST: 0,COUNTER_PHY_TO_MAC_QUEUE_LIMIT_REACHED: 0,COUNTER_PACKET_VALIDATE_LIBRARY_DROPPED_COUNT: 0,COUNTER_TYPE_NWK_RETRY_OVERFLOW: 0,COUNTER_PHY_CCA_FAIL_COUNT: 2411,COUNTER_BROADCAST_TABLE_FULL: 158,COUNTER_PTA_LO_PRI_REQUESTED: 0,COUNTER_PTA_HI_PRI_REQUESTED: 0,COUNTER_PTA_LO_PRI_DENIED: 0,COUNTER_PTA_HI_PRI_DENIED: 0,COUNTER_PTA_LO_PRI_TX_ABORTED: 0,COUNTER_PTA_HI_PRI_TX_ABORTED: 0,COUNTER_ADDRESS_CONFLICT_SENT: 0, 2020-12-06 18:17:06 DEBUG (MainThread) [bellows.zigbee.application] EZSP Counters: COUNTER_MAC_RX_BROADCAST: 65535,COUNTER_MAC_TX_BROADCAST: 65535,COUNTER_MAC_RX_UNICAST: 65535,COUNTER_MAC_TX_UNICAST_SUCCESS: 12971,COUNTER_MAC_TX_UNICAST_RETRY: 29902,COUNTER_MAC_TX_UNICAST_FAILED: 10168,COUNTER_APS_DATA_RX_BROADCAST: 484,COUNTER_APS_DATA_TX_BROADCAST: 484,COUNTER_APS_DATA_RX_UNICAST: 7797,COUNTER_APS_DATA_TX_UNICAST_SUCCESS: 6796,COUNTER_APS_DATA_TX_UNICAST_RETRY: 2522,COUNTER_APS_DATA_TX_UNICAST_FAILED: 1165,COUNTER_ROUTE_DISCOVERY_INITIATED: 1135,COUNTER_NEIGHBOR_ADDED: 20,COUNTER_NEIGHBOR_REMOVED: 10,COUNTER_NEIGHBOR_STALE: 440,COUNTER_JOIN_INDICATION: 15,COUNTER_CHILD_REMOVED: 9,COUNTER_ASH_OVERFLOW_ERROR: 0,COUNTER_ASH_FRAMING_ERROR: 0,COUNTER_ASH_OVERRUN_ERROR: 0,COUNTER_NWK_FRAME_COUNTER_FAILURE: 0,COUNTER_APS_FRAME_COUNTER_FAILURE: 0,COUNTER_UTILITY: 0,COUNTER_APS_LINK_KEY_NOT_AUTHORIZED: 0,COUNTER_NWK_DECRYPTION_FAILURE: 0,COUNTER_APS_DECRYPTION_FAILURE: 0,COUNTER_ALLOCATE_PACKET_BUFFER_FAILURE: 0,COUNTER_RELAYED_UNICAST: 0,COUNTER_PHY_TO_MAC_QUEUE_LIMIT_REACHED: 0,COUNTER_PACKET_VALIDATE_LIBRARY_DROPPED_COUNT: 0,COUNTER_TYPE_NWK_RETRY_OVERFLOW: 0,COUNTER_PHY_CCA_FAIL_COUNT: 2411,COUNTER_BROADCAST_TABLE_FULL: 158,COUNTER_PTA_LO_PRI_REQUESTED: 0,COUNTER_PTA_HI_PRI_REQUESTED: 0,COUNTER_PTA_LO_PRI_DENIED: 0,COUNTER_PTA_HI_PRI_DENIED: 0,COUNTER_PTA_LO_PRI_TX_ABORTED: 0,COUNTER_PTA_HI_PRI_TX_ABORTED: 0,COUNTER_ADDRESS_CONFLICT_SENT: 0, you can filter the log with grep, like grep -i 0x2d1c /config/home-assistant.log That button's battery has depleted down to 16% within hours, while the other buttons that are paired with ZHA but have no automation active are currently fine. Not sure what to do about that. One more "personality" with IKEA controllers is sending the same battery status all the time to the coordinator and is only updating the real reading then its being activated (button being pressed) then the new attribute is made and being reported until . I would keep this thread posted for progress. Are you using zha or deconz? Thanks you to report it. My recommendation if its very power hungry returning it and getting one new one. In this issue I started with Ikea switches not working with Sonoff ZB Bridge running via ZHA, what part should I change in order to make it work? --- Line 1678: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0006]: 'async_initialize' stage succeeded
Couldn't fix it and wound up taking it back to Ikea and they gave me an exchange for a new one. Also I opened a ticket with POPP to check on this, waiting still. Some IKEA controllers is not reporting voltage other do but all is reporting %. I solved it by adding the remote via add devices by a lamp not over the coordinator. Dispose of used batteries according to the, The remote control is for indoor use only and can be used. This is what I get when re-pairing one Ikea remote control. But any press on the remote, zha receives data and marks it online again. We have to reset it and pair it again in order for the device to become available again in the network. Better is doing one copy of you configure.yam before editing it and then easy to redo it :-))). Line 30290: 2020-12-09 01:00:01 DEBUG (MainThread) [bellows.zigbee.application] Extending timeout for 00:0d:6f:ff:fe:11:b4:06/0x3f43 I thought maybe some chance its the pairing outside of the Tradfri gateway but reviews on IKEA website seem to indicate its common issue. TRADFRI remote control (E1524) (5 Btm Remotes new and old) Line 84957: 2020-12-09 14:33:35 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 Line 85229: 2020-12-09 14:35:15 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: []
3b T9DD+5%)1"R(%$Q k%f#^k/bZ(A@[8qO3m61~j9--Q `bI66S} cbdJatV3`J (bf+x"(QmLKj) >VW:>8d41PGp\ RKE$5R}! The draining is a lot less then what it was before but on some devices i am still only getting 2-3 weeks out of them before they go offline and need a new battery. But now with ZHA and Sonoff ZB Bridge the batteries get emptied very fast without me pushing any buttons. Open the back of the remote. Line 68376: 2020-12-09 12:10:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 Line 55888: 2020-12-09 08:59:26 DEBUG (MainThread) [zigpy.neighbor] [0x0000] request status: Status.SUCCESS. Thanks for the ikea firmware insight, i won't upgrade. Try again. Good and bad things: For the moment I only seeing one premium product on the market and its @tube0013 (https://www.tubeszb.com/) network attached coordinator with TI and EZSP chips onboard :-)). fyrtur kadrilj opac opaco estore cinz pilhas fios estores verdunklungsrollo kabellos baterii rullo tenda ajustar includo comando I having one RaspBee I (x-production system) its not bad but not good for 50 and the deCONZ is having support that is not working as expected for one "premium product". I got two set of Fyrtur blinds for two windows on the same wall a few months ago. vwf6EH+ Press J to jump to the feed. When the remote control is used regularly and as, intended, the batteries will last for approximately 2, When it's time to replace the battery, a red LED indicator, will flash when you press any button on the remote, Open the battery lid and replace the battery with a new, Risk of explosion if battery is replaced by an incorrect, type. Nothing. by IKEA of Sweden Successfully merging a pull request may close this issue. After I replaced the first battery from Ikea with a descent battery, the battery lasts. Have seen user is having problem with the same coordinators in ZHA, tasmota and deCONZ :-((. c%b71$p";ipLx "Y8zzjK Network attached with ZHYA TBGW (Ethernet) and ESPHome (WiFi) that working good if having satiable WiFi / Ethernet. Can you please let me know how to enable debug logging and monitoring, please? Yeah, that was the first thing I did to see if the battery was dead. Your zigbee network dont like the remote (or more correct the router its using is making bad things). I just set up a switch and the sound controller and both are dying VERY quickly (24 hours or so). Create an account to follow your favorite communities and start taking part in conversations. Are you sure they are charged up ok?
Line 47046: 2020-12-09 05:56:28 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0020] ZCL deserialize:
I created a blueprint to catch the events from the remotes. Line 68374: 2020-12-09 12:10:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL deserialize:
I use a 2 button-IKEA switch with Zigbee2MQTT. After switching from, Light flashes 4 times. If IKEA is not relenting one working version you is sucked with one not working version :-(( I agree with you that E1743s battery is lasting lasting longer on the IKEA GW. I have tried re configuring once paired. Line 1529: 2020-12-08 20:55:21 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] [0x3f43](IKEA of Sweden TRADFRI remote control) restored as 'available', last seen: 1:56:07 ago
Could this be caused by incorrect configuration in HA? Hopefully that can help with the issues. You signed in with another tab or window. Also if can doing little hacking the tuya Ethernet ZBGW (https://github.com/banksy-git/lidl-gateway-freedom) is working great after patching it and updating the firmware on the module and working great in all platforms also docker then its using network attached com ports and not local comports / USB that is making it flexible. Once the TubeZB Coordinators come back in stock i might order one from all the issues this sonoff bridge has given me.
Line 30298: 2020-12-09 01:00:04 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0000] ZCL deserialize:
Also then changing batteries always putting 2 new ones from the same batch / type or it can being that one is falling faster and the other is lasting longer but cant being used then the summary of the voltage its failing to low. Until today. Line 85230: 2020-12-09 14:35:15 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 If it reports more often, then this must be the problem. Line 1679: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0019]: 'async_initialize' stage succeeded The remote did not connect to the network as it should (I tested it with zha_event). and you'll get all the messages related to the device, Finally I managed to do it. Zigbee Coordinator Press the button. ZHA is fixing that with dubbling the battery % on IKEA devices in the quirk. Return it for a new one. Hold it up to the blind. --- Cool. I suggesting first look on the network map witch router is the bad remotes parent (Integration > ZHA > Configure > visualization = network map). Sign in response: Neighbors(entries=10, start_index=9, neighbor_table_list=[Neighbor(extended_pan_id=cc:cc:cc:cc:d7:12:cf:a4, ieee=00:0d:6f:ff:fe:11:b4:06, nwk=0x3f43, packed=18, permit_joining=I have been using the Sonoff zigbee bridge with firmware version 6.7.9 for over a month and am still experiencing battery draining. Line 70021: 2020-12-09 12:25:32 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] I have to say that I used the respective switches and remotes with the Ikea Tradfri Gateway and I did not have this problem. The one exemplified above is e1810, but I also have E1743 but create the same problems. This looks very similar.to your situation, but i don't know when the bug was introduced.
And I can see in Zigbee2MQTT logs that this module barely ever speak with the zigbee controler, sometimes it does not communicate for 12 hours.
I had the same problem. First E1743 little more then 10 month and the second around 15 month running on the original batteries. I had the same problem with ZHA. So Sonoff ZBB with ZHA is killing the remotes and CornBee II with Z2M is not.
LCd-C\$V X@ T/. It remains unavailable.
I will let it add some more data. I don't have to pair again. This is the largest community of users for the IKEA product range, and has a wealth of knowledge and experience in all things Smart Home. @ygreq I and no one can recommending that something that is working 100% with all devices and combination of them. Some very cheap cels can having under 3.0 V then taking them out of the package and that is nearly zero in lifetime of the battery. Once paired, they are recognized by the system with their old names I set. I dont have the gateway. Is you using on Sonoff ZBB as coordinator or somthing else ? Restart HA between the changes and dont forgetting reversing the changes in step one then have doing all or you is getting problem later. when zigpy receives a message from a device on the network, it would normally log that message with NWK address of the device. I will maybe try to see if it has the same behavior. Line 1138: 2020-12-08 20:55:08 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0000] Attribute id: 4 value: IKEA of Sweden The lost devices on reboot can being fixes in the new firmware but i have not seen that problem so i cant testing it. blinds Line 85200: 2020-12-09 14:35:13 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [