ikea fyrtur battery life

Others have demonstrated that the Idea buttons use a non-standard link protocol and if you Zigbee mesh changes, in any way, the IKEA battery devices will repetitively look for the original mesh and until their batteries are dead. ### PROBLEM DESCRIPTION I originally thought that this battery status was for the remote control battery, however I believe that is incorrect and instead represents the battery level of the blinds. Remote button battery also seems to be working fairly well. Rules output here: STATUS 0 output here: this looks promising, please can you indicate where this was from? I added 2 of the open-close remotes. Ok followed this but cant unbind from the coordinator at all before or after the bind to group. Tried a 3rd. - [x] Searched the problem in the [docs](https://tasmota.github.io/docs/FAQ) --> This is based on me observing the battery level on the remote going up after charging the blind battery. Ive had the back off mine this whole time and the problem remains. I do not think if having multiple setups, the repeaters ever talk to each other, unless grouping is used and then only one repeater is used as coordinator for that group. When I paired the remotes, I actually paired them in ZHA via the repeater devices. Just moved my personal 2.4ghz router to CH11 and moved the ZigBee to CH11. Disclaimer: I am running a Sonoff ZigBee stick with the original firmware, which doesnt support all the features the TRADFRI devices can support, such as the motion sensors presence reporting. Dustin my last pairing I noticed that the button actually worked when the back lid is off. You can use the zigbee2mqtt web UI to setup groups of blinds and bind the remote to them. The small amount of time you spend completing the template will also help the volunteers providing the assistance to you to reduce the time required to help you. Can I do something to prevent lots of communication? I agree completely with what youre saying, however it also becomes a ST problems as IKEA products are supposedly meant to work natively with ST (rather than via custom/community groovy handlers), and also presumably if IKEA fix this via device firmware update were still relying on ST to deploy it to hubs. I have them working 95% of the time by removing the battery on one of them and just keeping it disconnected. So I just have an automation that lowers/raises 4 blinds on a button press trigger. tradfri.zip, Where I have to move these files? It is again a base firmware issue for the devices, but it is coming from the manufacturer of the chipset. That makes them useless in HA since they can ONLY control the blinds, I have all blinds as ikea and thats my only complaint about them, no battery status of the actual blind. - If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team @hwikene thanks for your help! All the other IKEA tradfri devices I have (bulbs, drivers, motion sensor, outlets, repeaters) are working fine with ST. And yet, the biggest issue I see is the lack of official public information from IKEA and Smartthings (at least I couldnt find any). _Steps to reproduce the behavior:_ I do live in an apartment so Im pretty much bathed in every WIFI channel out there. to your account, Home Assistant release with the issue: - [x] Searched the problem in the [chat](https://discord.gg/Ks2Kzd4) @Ramblurr : Yes, Im running about 20 other ZHA devices. Fortunately they are perfectly happy to disable it. This little rascal produces a boat load of talking for each level change and if you do too much too quick, it can confuse the lights. {"NAME":"Generic","GPIO":[1,1,1,1,1,1,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18} ``` ```lua Also experiencing this issue, thought one of my buttons died but then both my 5 buttons started failing changed the battery but both died again. Also sometimes it refuses to either turn them on or off. So far they have been working well. That way Its still intact and can be returned for those that want to do that. We havent been able to fix this but there is a workaround that @hwikene is using. However, I've further observed that the Tradfri Remote control devices have a battery status on them. Did you try to remove battery and insert them back? We are talking about products that brings millions as profit to those companies, not an open source solution that relies on the community for support and testing. Successfully merging a pull request may close this issue. Also upgraded to 0.109.6 and battery status still does not appear on the blind devices themselves. Id say of all the things Ive added to my setup, these were some of the easiest to get running. Hmm, I have the same experience as @dmx21. If you have figured away to get the buttons to work with the repeaters and not have dead batteries after a few days then you have succeeded where dozens have failed. [](https://i.imgur.com/uqojeWd.png) Hi! Now TRADFRI is part of core integration of HA, so I dont have TRADFRI folder in CUSTOM_COMPONENTS folder. 24h passed and they are still working. No changes. GitHub. Normally this takes about 48hrs after the mesh changes. This issue template is meant to REPORT Tasmota software PROBLEMS ONLY Can I do something to prevent lots of communication? Add these files to custom_components/tradfri folder. - [x] Searched the problem in [issues](https://github.com/arendst/Tasmota/issues) Any update on if/when we get battery levels for the blinds? - [x] Searched the problem in [discussions](https://github.com/arendst/Tasmota/discussions) I only have an Ikea lamp next to the shades. I do not want to argue about this, but following your thinking in the previous occasion it was Fibaros fault, and all the others who has implemented the device firmwares. Thank you for your contributions. If so, it would be great to PR the core code, and let ggravelingen have a look. Ive tried both ways on a clean setup with a couple blinds and by far using the tradfri hub seems to be the best way to go for me. I use Tradfri as a custom component. The latest precompiled binaries of Tasmota can be downloaded from http://ota.tasmota.com/tasmota/ Right now I have 3 shades running in Hubitat and I have them close at sunset and open to 44% at sunrise. Is it possbile to restore the connection other then disconnect/connect power? **(Please, remember to close the issue when the problem has been addressed)**. EDIT: Hm, removing the integration, restarting Home Assistant and re-adding it had no effect. It still doesn't make sense even if it is showing via the remote, it was displayed on the blind before 0.101. But yea, my experience is 100% worth it and functional. Powered by Discourse, best viewed with JavaScript enabled, ssue template is meant to REPORT Tasmota software PROBLEMS ONLY I could absolutely be wrong about this so I will test it. My shades have only gone through ~13% battery in a month, and Ive never noticed a false or missed open/close event. _(Not always this light)_ The button and the Fyrtur itself do not appear. Console output here: They have been doing that for over 6 weeks now with my batteries showing 87% in HA. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. https://www.home-assistant.io/integrations/tradfri/, Show battery as a state attribute in FYRTUR blinds, https://community.home-assistant.io/t/add-air-quality-sensor-to-tradfri-starkvind/372490/2?u=mariusthvdb. Has anybody had the time to try it? Reading through this thread it seems to give mixed results just pairing directly with ZHA. Some comments suggests that it is an NCP firmware issue of the coordinator. The repeater information is good to have. This issue is related to if you are using the native Tradfri gateway, where we have added support for battery levels. You signed in with another tab or window. ### TO REPRODUCE By clicking Sign up for GitHub, you agree to our terms of service and Yes that is the case The IKEA Hub does NOT expose the Fyrtur button events to HA or at least so far I cant see the Button events on ZHA. I charged one of my blinds for an hour and it did not change the battery level on the remote (remained at 87%) so it looks like I'm wrong. privacy statement. These instructions worked great for me. They will never expose button events via any of the platforms, I dont think Deconz does this either (but might be doable via sniffing or such and still not out of the box). Console output here: You are very lucky Or you dont have a lot of Zigbee devices in your house. One known issue seems to be that if the IKEA hub goes down for any reason, power, network, ect, the HA integration must be restarted to establish a connection. My one uses some annoying software that automatically optimises your Wi-Fi configuration, which in my case meant moving my carefully chosen and manually configured Wi-Fi channel right on top of my carefully chosen and manually selected Zigbee channels. Removed the magnet and voila. Please DO NOT OPEN AN ISSUE: :), Hi @microadam! - If you have an issue when flashing was done via Tuya Convert, please address it to Tuya Convert Team This wakes up the device for configuration. Basically the remote will be working independently to open, close, and pause the blinds through the IKEA hub but will not be of any use in HA. Not sure about that My Fyrtur Blinds continue to work with ST But the battery life on these are impacted too. Can this be done without the Tradfri hub or do I need the hub? Just wondering is anyone monitoring IKEA or is there some other website that reports what the current firmware is for the buttons and the blinds? ```lua Although Im using ZHA and not Ziigbee2mqtt. I use ZHA with a CC2531 plugged into the pi4. I've applied your patch, and I now have the battery reading! ### SCREENSHOTS Let us know if that works for you by adding a comment I am moving over to HA and would like to have the same functionality. Is it possbile to restore the connection other then disconnect/connect power? I havent checked if they indeed sometimes connect via another powered device. 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. Without any hub, this constitutes a standalone ZigBee mesh. So we still need a fix for this. Every remote (2-button) that has the battery off still works. ``` - [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`: Does anyone have binding working with the latest remote firmware (0x23079631 / V-2.3.079)? Add these files to custom_components/tradfri folder. Running Home Assistant 0.107.7 - battery status still not present through Tradfri integration, Running Home Assistant 0.108.6 - add me to the list of people who would like to see this fixed. ### REQUESTED INFORMATION ```lua If someone else can try and verify we can be sure. :), 0.109.6 - blinds battery status still not presented. It decreases some percents per day while the switch is used sparingly This seems to not be all solved. I am using zigbee2mqtt and the IKEA TEST OTA option enabled, then restart and try to OTA again. ```lua - If your issue is a flashing issue, please address it to the [Tasmota Support Chat](https://discord.gg/Ks2Kzd4) Sot sure but I might have found something. Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant): Additional information: Ive been running 6 FYRTURs for a month now with basically no issues (Installed July 1 2021). - [x] Tasmota binary firmware version number used: 9.2.0.1 On/off buttons can now be used and no longer exhibit immediate battery drain to death. You could be right, however something magically made one of my remotes go from 35% to 100%, and another go from 60% to 100% (two different blinds) around the same time I charged both blind batteries. - [x] Read the [Contributing Guide and Policy](https://github.com/arendst/Tasmota/blob/development/CONTRIBUTING.md) and [the Code of Conduct](https://github.com/arendst/Tasmota/blob/development/CODE_OF_CONDUCT.md) - If your issue is a Wi-Fi problem or MQTT problem, please try the steps provided in the [FAQ](https://tasmota.github.io/docs/FAQ) and [Troubleshooting](https://tasmota.github.io/docs/Troubleshooting) Thank you!_ A week later both combos are working with lightning fast response, no issues of any kind. - [x] Read the [Contributing Guide and Policy](https://github.com/arendst/Tasmota/blob/development/CONTRIBUTING.md) and [the Code of Conduct](https://github.com/arendst/Tasmota/blob/development/CODE_OF_CONDUCT.md) I'm using the latest HA install and I have two blinds; one consistently show 0%, and the other shows 68% regardless of the actual state of charge. Maybe thats the issue? Cant remember how right now, maybe @hwikene can shed some light? If any the bind/unbind steps return red notifications, one of the devices (or both) was not ready to receive your commands. EDIT: interestingly one of the remotes reports offline vey often (as you can see in the screenshot), but when I press it, it actually reports instantly in HA. It's in the dev branch on Github so it'll be available in the beta release on February 23, or in the release of 2022.3 on March 3. Just to clarify and I forgot to mention is that the buttons I tried on are the 2-button ones. - If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue {"GPIO0":{"320":"Led_i1"},"GPIO1":{"3552":"Zigbee Tx"},"GPIO2":{"0":"None"},"GPIO3":{"3584":"Zigbee Rx"},"GPIO4":{"5312":"Zigbee Rst"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"640":"I2C SDA"},"GPIO13":{"576":"LedLink_i"},"GPIO14":{"608":"I2C SCL"},"GPIO15":{"0":"None"},"GPIO16":{"32":"Button1"},"GPIO17":{"0":"None"}} 2. The only remaining issue that I have is that only one of the shades is actively reporting its battery level to me, for the other 5 I need to go in and do the cluster fix that has been reported earlier in this thread (although Im not sure if there is something that Im doing something wrong with that as its never updating automatically, if I want a new battery reading I need to go back to the cluster settings and manually click get setting). These are all IKEA buttons. The Car Port button has been going through a bit more battery than I want. - [ ] Provide the output of command: `Backlog Template; Module; GPIO 255`: DO NOT DELETE ANY TEXT from this template! This is a different platform but the issue has happened with Philips Hue remotes as well. Any clue why? Oh! Otherwise the issue will be auto-closed. ``` - [ ] Flashing tools used: _____ i'll send beer money if it helps. 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 take a few minutes to complete the requested information below. These are the batteries we will have to swap most often :-). - If your Tasmota version is not the latest from the development branch, please update your device before submitting your issue. Im not expecting ST to fix, however I would expect ST to put pressure on IKEA to fix, and deliver to us when it becomes available. thank you, I will try this out :). could be very useful find also battery level of roller! This does not seem to appear for me and it broke some stuff of the official integration.. Hopefully the official integration will be fixed asap to include the battery again! - If your issue has been addressed before (i.e., duplicated issue), please ask in the original issue For what its worth, after using the blinds with ZHA for about 8 months and having reliability issues with all of the blinds in each room (3 in one room, 4 in another) opening 100% of the time, I ended up just buying the Tradfri hub and using the official Ikea integration. I tried to put the files in the zip posted by @microadam into the config/custom_components folder, but I can't see any change could somebody help me getting the custom component work while the official integration is being refactored? Im even using 2 of the IKEA repeaters outside of the Tradfri ecosystem to act as generic ZHA repeaters. So this might just be luck or something else at play but maybe someone else can try. What I noticed was that my buttons, like the rest of you, just lost connection. The details requested potentially affect which options to pursue. tradfri.zip, Ahh awesome! And actually they do have the same battery issues as well. - [ ] Provide the output of this command: `Status 0`: - [x] Device used (e.g., Sonoff Basic): Sonoff ZbBridge Cool stuff: this should work the same between any ZigBee devices. These used to last 6 months on a charge, now they drain in about 2 weeks. The USB-gateways you mention are unrelated. No solution though from what I read. When connected directly through ZHA commands seem to take longer to reach the device and stopping the blinds midway results in the inability to keep moving in the same direction. The blinds are able to be controlled fully though through HA with the IKEA integration. Please make sure to update to the latest Home Assistant version and check if that solves the issue. There hasn't been any activity on this issue recently. What could be the cause of this? I even think its causing the batteries on the blinds themselves to last longer. Otherwise the issue will be auto-closed. Get the battery indicator working correctly. I think its important anyone experiencing the issue open a ST support ticket. _(Not always this light)_ Powered by Discourse, best viewed with JavaScript enabled, IKEA FYRTUR block-out roller blind support.