To clean the remote control, wipe with a soft cloth. j (l{MCz(CjXmz}Fs
O Im happy to see other people are having this issue. I will be grateful for your help. Sorry, Matt, but I don't quite understand everything you say. Need waiting for the firmware cooker have making working firmware that is stable before can start testing. Both open. Normally not but for my 3 new and one was killing the battery very fast (I have 8 of them). 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 The only problem, if nobody uses the remote, then we t doesn't report battery often enough and zha marks the device as offline. Changing the battery and updating the network map (refresh topography) after some minutes / hours and looking for its parent. (to control tradfri-light directly) I set the battery status update once a day but it didnt help. Also, most likely each device might define minimum voltage or/and report capacity differently. Just for testing im waiting on a Xiaomi remote to compare. Waiting waiting nothing. Seems to be related to the place in the Home, because for those 2 it doesn't matter if I use the older or the newer model motion sensor. New better and binding to bulb and little testing and 2 weeks batter was out. Also I opened a ticket with POPP to check on this, waiting still. upgraded E1524 (5-button remote) to 2.3.075 and now, i'm unable to use group-command. I noticed something interesting in the debug logs: 2021-06-21 21:44:29 DEBUG (MainThread) [zigpy.zcl] [0x7eb2:1:0x0001] Voltage mV: [Min]:2820 < [RAW]:3015 < [Max]:3100, Battery Percent: 69.5. If you have some good routers (no OSRAM plugs and so on) i can recommending testing the "force not using routers" patch #43969 (comment). I got two set of Fyrtur blinds for two windows on the same wall a few months ago. Line 1657: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0001]: initializing channel: from_cache: True Any idea what it means? ! Line 85666: 2020-12-09 14:37:53 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] Im using them with a conbee 2 and deconz add-on. ZHA is fixing that with dubbling the battery % on IKEA devices in the quirk. The E1743 is sending all commands to 0x0000 = coordinator so it shall being OK if not using it for controlling light groups. The IKEA ones both new and old modelle is little tricky of the state of the batteries, if one is week it can start triggering motion at level between 70 and 60 % battery level. 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. I was giving it back then the shutdown was over and getting one new family pack and the new E1743 is more normal. Line 85154: 2020-12-09 14:35:00 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] . Holding the remote to the blinds should see the white light on the side of the blind light upif it doesn't then surely the blind is dead? Line 1675: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x1000]: 'async_initialize' stage succeeded Thank you for all your help, MattWestb. maybe @ggravlingen would know if this is a HA matter polling the sensors, or simply an Ikea affair? If sleeping end device have god connection to one router in the near its using very low power and also dont need stretching for better one all the time that easting current. Dispose of used batteries according to the, The remote control is for indoor use only and can be used. I have my kitchen with 2 E1743 and one new 5 button remote still on IKEA GW (ZHA have not the scene working for the WS spots). Log looks fine, but it's too short, anyway. It lasted less than 2 weeks (~11 days). what firmware version does the device report, save the logs then run the following to filter egrep -i -e 'trustCenter|idConflict|70:8d:45|0xba48' home-assistant.log just replace 70:8d:45 with last digits of the remote IEEE address and replace 0xba48 with your remote NWK address, Device info I have a few Ikea remotes, and while one is showing blow battery, it still works and it defy lasted more that two weeks. I'm not saying that's ok. If it reports more often, then this must be the problem. The battery was "bad / old" from the store (can happen also with IKEA). Hi all, Is you using on Sonoff ZBB as coordinator or somthing else ? Okay. My recommendation if its very power hungry returning it and getting one new one. Line 84956: 2020-12-09 14:33:35 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL request 0x0002: [] Use another soft, Never use abrasive cleaners or chemical solvents as this, The crossed-out wheeled bin symbol indicates that, the item should be disposed of separately from, household waste. can affect the wireless connectivity range. 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. Line 85664: 2020-12-09 14:37:53 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [
I have two E1743 in production for at least two months and haven't changed the battery yet. Line 67022: 2020-12-09 11:57:23 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0000] ZCL deserialize:
Interesting is the network map to see if the remotes is connected in the system. I will try updating to the official one if that recommend? First E1743 little more then 10 month and the second around 15 month running on the original batteries. New firmware images ver 2.3.075 is for: By separating a marked, item from household waste, you will help reduce the, volume of waste sent to incinerators or land-fill and, minimize any potential negative impact on human health, and the environment.
Line 85201: 2020-12-09 14:35:13 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] ZCL deserialize:
Any way to downgrade to previous version? I reporting back if doing some new findings. Grab the other remote. moistened with a little mild detergent. 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. Have seen user is having problem with the same coordinators in ZHA, tasmota and deCONZ :-((. Well, the blinds themselves work if I press the up or down button on the blinds, so I assume that means theyre not dead but perhaps I should charge them anyway. Maybe it lost pairing? Line 47024: 2020-12-09 05:56:25 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0020]: Received 64 tsn command 'checkin': [] Do not leave the remote control in direct sunlight or near, Do not subject the remote control to wet, moist or, excessively dusty environments as this may cause, The range between the remote control and the receiver, Different building materials and placement of the units. 
The text was updated successfully, but these errors were encountered: Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as its been labeled with an integration (zha) you are listed as a codeowner for? Also some Conbee II users was having the same battery dining problems but i dont knowing if its present in ZHA after some fixes is made. Good and bad things: The solution I found is to pair them again. --- Line 1114: 2020-12-08 20:55:08 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0001] Attribute id: 32 value: 30 ---
I need to reset and pair it again too. Hypothesis, maybe if home assistant didnt poll the remotes all the time to ask for battery life, just maybe, the battery might last longer. Hold it up to the blind.
As with the sonoff bridge, the 6.7.9 version i am running is the one you posted in this thread somewhere, not the official one. Nothing. Line 67012: 2020-12-09 11:57:20 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x3f43](TRADFRI remote control): Attempting to checkin with device - missed checkins: 1 The second one the remote paired fine but it never "Found the device" on the app. Go buy all new batteries. For more advanced user like @MattXcz I think one Ethernet attached coordinator is one better but more expensive solution. Check the blinds. Here are the logs related to the remote I recently changed the battery to. Not a battery problem. By the way one E1743 with 21% battery was queering OTA image but canceling the update after the first package revived and was working OK with one new battery with 100% (and doing one fast battery changing and the network was still working with the new one). 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 Philips HUE I have not changing batteries after 2.5 year and one have 80% (perhaps falce reported) and the other 18% but I think they is not liking Zigbee 3 routers (Silabs ones) and sometimes they have periods and changing it parent like crazy and shushing on of the lowers LQI then having 8 better much nearer. If you dont have hacking the ZBB then you is using the firmware from the factory and no need updating it one more time then its only one that is signed version of the 6.7.9.0. Line 85203: 2020-12-09 14:35:13 DEBUG (MainThread) [zigpy.zcl] [0x3f43:1:0x0006] No handler for cluster command 2 https://www.home-assistant.io/integrations/zha/, https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates#downgrading-your-device-firmware. I found some errors here related to zigbee. New batteries discharge only after a few days and the remote controls stop working. Hold it back up to one of the blinds. brand of battery doesnt really matter, though the ikea ones are quickest. Let me know if based on this info, you manage to figure out what the problem is. Line 1648: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:ZDO](TRADFRI remote control): 'async_initialize' stage succeeded Line 1677: 2020-12-08 20:55:22 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x3f43:1:0x0008]: 'async_initialize' stage succeeded I have same issues with both IKEA controllers (TRADFRI on/off switch; SYMFONISK Sound Controller) with ZHA integration.
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). when zigpy receives a message from a device on the network, it would normally log that message with NWK address of the device. vwf6EH+ Someone knows a way to disable this? Should I put the next paste somewhere else like bitbucket or here considering the size? Line 74159: 2020-12-09 13:01:52 DEBUG (MainThread) [zigpy.neighbor] [0x0000] request status: Status.SUCCESS.
The last point i think its the personality of the firmware. Hold the button down. Anyone know how to work around this or prevent them from dying so quickly? HA Version : 0.118.3 Core on Docker HomeMade Line 1138: 2020-12-08 20:55:08 DEBUG (MainThread) [zigpy.appdb] [0x3f43:1:0x0000] Attribute id: 4 value: IKEA of Sweden Line 30293: 2020-12-09 01:00:01 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (
