search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
21.8k stars 4.73k forks source link

Philips Hue Dimmer switch battery running down rapidly (ZbBridge) #10413

Closed pingel20 closed 3 years ago

pingel20 commented 3 years ago

PROBLEM DESCRIPTION

The battery percentage of my Philips Hue dimmer switch is running down quite rapidly since I paired it with the (Tasmota) ZbBridge. It decreases some percents per day while the switch is used sparingly

Is the ZbBridge requesting this device very often? Can I do something to prevent lots of communication?

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

- [ ] If using rules, provide the output of this command: `Backlog Rule1; Rule2; Rule3`:
```lua
  Rules output here:

- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

MattWestb commented 3 years ago

Then working with light in deCONZ you should using the old web app "Wireless Light Control" that is doing real bindings for lights to your remotes. Phoscon is only doing "HA" commands without binding = not working then your system is down.

And adding the group 65289 in one light (in deCOMZ GUI) then deCONZ is its hocking it up then you is re powering the light and you can adding more lights and scenes to that group that is working with your remote (only for IKEA lights).

IKEA_CT18

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

MattWestb commented 3 years ago

Still stable @s-hadinger ??

I have catching the "Sonoff bug" on one sniff from one tuya Zigbee gateway running EZSP 6.5.1. (on one of my more the 24 hours sniffing)

Its looks only happening then the device is direct connected with the coordinator and not with routers.

The reason is the coordinator is very lazy acking End Device Timeout Request and the remote is leaving multiple times and being locked in fast pull mode.

With routers and 6..7.8.0 NCP its looks being no problems but the remote can still rejoining after "looking little around".

s-hadinger commented 3 years ago

v6.7.8 is super stable. My IKEA battery is still well after months. And I had no errors from EZSP for more than 10 days.

MattWestb commented 3 years ago

You can configuring attribute reporting for battery and skipping the pull control and the IKEA devices is doing there "default" check in every 5 minutes and not getting any "heavy" battery draining then they is always pulling in the same pace and cant being locked in fast / short pull that was the large problem with the "6.7.8.0 fix".

Thanks for the information I trying getting ZHA changing the pull control for different device types then its crazy that sleeping end devices is pulling its parent every 6 seconds and there parents is having one time out of over 4 hours for the children.

xsp1989 commented 3 years ago

I checked the configuration of EZSP, a value about the frequency offset is set incorrectly, I will update a firmware, please test it.

Link: https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/SM-011/ncp-uart-nsw_6.7.9_115200.ota

MattWestb commented 3 years ago

@xsp1989 Thanks for information and the updated firmware !

I triggering some brave user to trying it out.

Regards

Mattias

tbemindt commented 3 years ago

I've been half following a couple of threads about the Ikea batteries draining, so I apologize if I ask a stupid question. I'm using ZHA with a Sonoff ZBBridge. Can I upgrade this as an alternative to the version found on Tasmota (6.7.8)? I tried but get an "Invalid file signature" message.

MattWestb commented 3 years ago

Its shall being one updated version of the "normal" 6.7.8.0 with the (false) name 6.7.9 but it shall being signed from the factory but i cant testing it then i dont have any sonoff ZBB with factory bootloader.

Must waiting to @s-hadinger or some other devs is coming on line and testing it if its working. It shall not being any problems flashing back the "old" 6.7.8.0 if all is OK made

PS: I think Stephan is normally running the "free version" (flashed with SWD and new bootloader with "Garys EZSP" 6.7.8.0) but hi is having some with original for factory signed files.

xsp1989 commented 3 years ago

@MattWestb You can test this firmware, it has the same parameters as the signed firmware. https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/Zigbee3.0_Dongle/ncp-uart-nsw_679_115200.gbl

tbemindt commented 3 years ago

I've been half following a couple of threads about the Ikea batteries draining, so I apologize if I ask a stupid question. I'm using ZHA with a Sonoff ZBBridge. Can I upgrade this as an alternative to the version found on Tasmota (6.7.8)? I tried but get an "Invalid file signature" message.

OK, that'll teach me for being adventurous. Figured it's because I forgot to do the Module 75 command. But when I tried after, it just bricked and can't get it back up. Hope I can restore it with the the TTL, unfortunately I don't have much time now.

s-hadinger commented 3 years ago

What is bricked? Tasmota or efr32?

tbemindt commented 3 years ago

What is bricked? Tasmota or efr32?

After I pressed the Start Upgrade, the webpage just switched to a This site can't be reached. It's no longer present on my router. I just checked, it's also not showing up as a host device. On the box itself the wifi light is solid blue. The ZigBee steadily short green pulses.

jesse-schein commented 3 years ago

I'm using the version 6.7.8 on a 9.1.0 tasmots version zbbridge. I have two two button remotes from ikea and both are burning through batteries. Is the issue fixed or not? Confused by s hadingers post earlier.

Update: Oh I didn't realize their was a PR with this issue and the fix was included in the 9.3.0 and subsequent release to not report battery percentage. I updated to 9.3.1.1 and I'll run another test to see how battery life goes.

patrickfong commented 3 years ago

https://github.com/xsp1989/zigbeeFirmware/blob/master/firmware/SM-011

Many thanks! I have successfully flashed this onto my Sonoff Zbbridge. Needs a few days (and new batteries) to verify if the drain issue is resolved. I'm using tasmota 9.2.0 since 9.3.0 and 9.3.1 will boot loop when I configure it with the "Module 75" command.

Coincidentally, what are 6.8.0.1 and 6.8.2.0 versions?

patrickfong commented 3 years ago

I'm using the version 6.7.8 on a 9.1.0 tasmots version zbbridge. I have two two button remotes from ikea and both are burning through batteries. Is the issue fixed or not? Confused by s hadingers post earlier.

Update: Oh I didn't realize their was a PR with this issue and the fix was included in the 9.3.0 and subsequent release to not report battery percentage. I updated to 9.3.1.1 and I'll run another test to see how battery life goes.

Did you have any luck with version 9.3.1.1? Previously I was using Tasmota 9.2 with 6.7.9 and two of my Ikea 2 button remotes were still drained overnight.

This morning I have just upgraded to 9.3.1.1, will see how it goes with the new Tasmota version.

jesse-schein commented 3 years ago

I'm using the version 6.7.8 on a 9.1.0 tasmots version zbbridge. I have two two button remotes from ikea and both are burning through batteries. Is the issue fixed or not? Confused by s hadingers post earlier. Update: Oh I didn't realize their was a PR with this issue and the fix was included in the 9.3.0 and subsequent release to not report battery percentage. I updated to 9.3.1.1 and I'll run another test to see how battery life goes.

Did you have any luck with version 9.3.1.1? Previously I was using Tasmota 9.2 with 6.7.9 and two of my Ikea 2 button remotes were still drained overnight.

This morning I have just upgraded to 9.3.1.1, will see how it goes with the new Tasmota version.

I have one dimmer that seems to be drain free in my living room but its battery is at 11% now since I installed the update while it was alreayd depleted.

The other dimmer was in my bedroom attached magnetically to an ikea lamp, I think this caused significant drain issues from weak signal and eventually that one died and I am reluctant to put another battery in that one. Im going to switch that one I think to an aqara button or perhaps give up and switch to zwave since I have some shades that are zwave I needed to buy a new zwave Usb.

patrickfong commented 3 years ago

I have been running for a couple days with Tasmota 9.3.1.1 with 6.7.9, and here is what I find. Ikea Tradfri 5 button remote

Ikea Tradfri 2 button remote

Is there anything I can do to help troubleshoot these devices? They work well but it's disappointing that they drain so quickly.

I'm using the version 6.7.8 on a 9.1.0 tasmots version zbbridge. I have two two button remotes from ikea and both are burning through batteries. Is the issue fixed or not? Confused by s hadingers post earlier. Update: Oh I didn't realize their was a PR with this issue and the fix was included in the 9.3.0 and subsequent release to not report battery percentage. I updated to 9.3.1.1 and I'll run another test to see how battery life goes.

Did you have any luck with version 9.3.1.1? Previously I was using Tasmota 9.2 with 6.7.9 and two of my Ikea 2 button remotes were still drained overnight. This morning I have just upgraded to 9.3.1.1, will see how it goes with the new Tasmota version.

I have one dimmer that seems to be drain free in my living room but its battery is at 11% now since I installed the update while it was alreayd depleted.

The other dimmer was in my bedroom attached magnetically to an ikea lamp, I think this caused significant drain issues from weak signal and eventually that one died and I am reluctant to put another battery in that one. Im going to switch that one I think to an aqara button or perhaps give up and switch to zwave since I have some shades that are zwave I needed to buy a new zwave Usb.

echauvet commented 3 years ago

I reopened the PR as it seems to be the right solution for now :(.

s-hadinger commented 3 years ago

I'm still using 6.7.8 for a while, and my IKEA 5 buttons has been running fine for months. So I'm optimistic that we can find a solution.

MattWestb commented 3 years ago

Have some of the tasmota devs trying the signed and the unsigned EZSP 6.7.9.0 firmware that the (factory) firmware cooker is recommended with the fixed miss tuned radio that is very likely doing the extreme battery draining if being connected direct to the coordinator ?

Then having SWD flashed the device use the firmware for the USB-Zigbee 3 stick and if factors state use the ZBB firmware.

kevinwells22 commented 3 years ago

I am trying to upgrade to the new firmware using 'ncp-uart-nsw_6.7.9_115200.ota', in Tasmota 9.3.1, I am using 'Upgrade by file upload', click to select the firmware file, click upload, but soon get the error back 'Invalid file signature'. What am I doing wrong?

patrickfong commented 3 years ago

I am trying to upgrade to the new firmware using 'ncp-uart-nsw_6.7.9_115200.ota', in Tasmota 9.3.1, I am using 'Upgrade by file upload', click to select the firmware file, click upload, but soon get the error back 'Invalid file signature'. What am I doing wrong?

In my experience, version 9.2 of Tasmota is the last version known to work for flashing the firmeware. Both 9.3 and 9.3.1 will refuse to flash the firmware and also bootloop when Module 75 command is issued.

Once you flashed the firmware, you can upgrade to 9.3.1 and have it work properly.

When switching Tasmota versions, you need to first flash the minimal build, then go to the Tasmota build you want.

kevinwells22 commented 3 years ago

hanks

I am trying to upgrade to the new firmware using 'ncp-uart-nsw_6.7.9_115200.ota', in Tasmota 9.3.1, I am using 'Upgrade by file upload', click to select the firmware file, click upload, but soon get the error back 'Invalid file signature'. What am I doing wrong?

In my experience, version 9.2 of Tasmota is the last version known to work for flashing the firmeware. Both 9.3 and 9.3.1 will refuse to flash the firmware and also bootloop when Module 75 command is issued.

Once you flashed the firmware, you can upgrade to 9.3.1 and have it work properly.

When switching Tasmota versions, you need to first flash the minimal build, then go to the Tasmota build you want.

Thanks, just have a couple of questions.

  1. If I have previously used the Module 75 command, how can I remove that please?
  2. Can I donwconvert the device to Tasmota 9.2?

Kind regards.

markokristof commented 3 years ago

when is the next release expected? current stabile version of firmware drains batteries for all connected devices, particularly for sensors and ikea fyrtur blinds.

MattWestb commented 3 years ago

Im curious what version is on your Zigbee module ? And what is behind "all connected devices" ? How is your setup looking ? Do you have some router devices ((IKEA blinds is no routers) in the network and perhaps one screenshot on the network map pleas.

Thanks in advance.

markokristof commented 3 years ago

I am using 6.7.8 and battery powered devices drain real quickly - remote controllers and sensors go out first (particularly those that are not close to routers - in less than a day) while fyrtur blinds used to go out after two days (situation improved after I placed a dedicated repeater nearby). Here is my network map, disconnect devices are fyrtur remotes and sonoff motion sensors Screenshot_20210507_080704

s-hadinger commented 3 years ago

Are you using ZHA ? If so it's not under control of Tasmota and you are on the wrong site to report issues.

MattWestb commented 3 years ago

The ZHA issue https://github.com/home-assistant/core/issues/43969

And upgrading the Zigbee module to EZSP 6.7.9.0.

markokristof commented 3 years ago

I use ZHA, tnx for the link. my initial question was regarding the 6.7.9 - when do you plan to release it?

MattWestb commented 3 years ago

Its released https://github.com/arendst/Tasmota/tree/development/tools/fw_TubeZigbee_efr32 And the factory cooker was positing it for some mouths in this thread.

MattWestb commented 3 years ago

@s-hadinger or some other tasmota devs that have one hacked sonoff ZBB or USB-stick and like testing forcing end device to routers for not getting fast battery draining i have cooked one unsigned EZSP 6.7.9.0 with the patch that the factory is recommending plus direct children stetted to 0.

That is making the coordinator not accepting any children and they must using routers (so you is needing at least on router in the network).

I have not testing it then i dont have and ZBB but i have running one similar firmware on one LIDL / tuya LED stripe drive with the same chip for 3 weeks and its working OK

ncp-679CH.zip

Its only working on "hacked" Sonoff ZBB or the new USB-Stick then its not signed from the factory !!

s-hadinger commented 3 years ago

The solution works only on erased zbbridges so not easy to use for regular users

MattWestb commented 3 years ago

Yes but if its working its possible requesting one signed firmware with the same patching. But i think its making no sin requesting firmware if its not being verified to working as intended.

xsp1989 commented 3 years ago

@MattWestb @s-hadinger Please confirm which parameter configuration is incorrect and there is a problem. I can reissue the signed factory firmware for you, and you can also provide the ISC file for me to rebuild the firmware.

MattWestb commented 3 years ago

Thanks for your attention @xsp1989 !!

Its one try forcing end end device using routers instead off the coordinator by setting: Plugins, Stack Library, Zigbee PRO Stack Library:Children Table Size = 0. I have not putting in the button and LED so i think its better that you is cooking one firmware with all the "extras" that is being used in ZBB and the Stick.

I have trying setting the same parameter with command line parameter in ZHA/Zigpy/bellows but its looks that the stack is not changing it and using the parameters in the firmware.

Give the firmware one ending with "NC" or somthing so users easy can reconciling it easy.

As i was saying its one test and its not verified to working for users with the fast battery draining (48 Hours) that some user is still having but all that is possible is worth trying that can helping / solving the problems for our unhappy users.

Thanks in advance.

Mattias

s-hadinger commented 3 years ago

Isn't this parameter MAX_END_DEVICE_CHILDREN ?

If so it is set at startup by Tasmota and wouldn't require a specific firmware

MattWestb commented 3 years ago

I have trying setting it to 0 in ZHA / Zigpy / bellows with CLI commands and the NSP is saying OK and then i reading it back its still 32 (its the default in my NCP firmware) and i can joining end devices to the coordinator. Also setting it in config file and restating ZHA its still possible (re)joining end devices to the coordinator.

Some of the setting in the NCP can being changed with host commands other is more hard coded but its not documented by Silabs.

Can you setting it to 0 (or 1 if you like trying more devices) and trying (re)adding one or 2 end device to the coordinator and see if its working (refusing end devices on the coordinator but OK on routers) ??

Mvh Mattias

s-hadinger commented 3 years ago

I will not be able to test before next week. If someone wants, it is set here https://github.com/arendst/Tasmota/blob/dd624c3ce6529a3c38b012eff35f2f1e526d38c4/tasmota/xdrv_23_zigbee_7_0_statemachine.ino#L634

MattWestb commented 3 years ago

@xsp1989 Do you have possibility testing if the parameter is working without being set in the firmware ?

In ZHA is made with the config:

zha:
  zigpy_config:
    ezsp_config:
      CONFIG_MAX_END_DEVICE_CHILDREN: 0

I have trying one time but i was still able paring end devices to the coordinator and also the NCP was reporting the valiue from the firmware after it have being sett with commands from the host.

And also if you can trying doing the same with one firmware with Children Table Size = 0.

Thanks in advance

Mattias

xsp1989 commented 3 years ago

I can set CONFIG_MAX_END_DEVICE_CHILDREN to 0 in the firmware, but I think this is not a good idea. If the user does not have a routing device, he cannot add any End device

MattWestb commented 3 years ago

Im very ware of that but then the user can using the normal 6.7.9.0 firmware and using only end devices and perhaps having the problems.

For user with some or meany routers i think i can helping then end devices dont have one complete zigbee stack, only one striped one (in Silans is leafe stack) that cant handle all problems so well as on full zigbee stack.

chvvkumar commented 3 years ago

Wanted to leave a comment that upgrading my Sonoff bridge to the following versions seems to have fixed the battery drain issue on my Ikea remotes.

Earlier, they were draining within a day but with the new firmware, they are holding up after 3 days:

ncp-uart-nsw_6.7.9_115200.ota Tasmota 9.4.0 Leslie

s-hadinger commented 3 years ago

Thanks for reporting

ascillato2 commented 3 years ago

upgrading my Sonoff bridge to the following versions seems to have fixed the battery drain issue

Thanks.

If the issue reappears, please open a new one. Thanks

s-hadinger commented 3 years ago

@MattWestb @xsp1989 CONFIG_MAX_END_DEVICE_CHILDREN can be set to zero at runtime by Tasmota. I will add this as an compile option, because I believe it's a dangerous feature for people who don't understand the implications.

No need for a specific firmware.

MattWestb commented 3 years ago

Great if its working. I was trying setting it in ZHA/bellows but it was not override the configured in the NCP firmware. And i agree with you is better doing it as one setting if the user like starting with only SED and later adding routers.

Have you testing if its working in real if having one or more routers and SED is not connecting to the coordinator ?

s-hadinger commented 3 years ago

Yes I tried, with no router, the end-device does not pair. It does pair with one router. PR is coming.

MattWestb commented 3 years ago

Great then its possible for user trying forcing SED using router then its possible and hopefully not getting problems with very fast battery draining.

MattWestb commented 3 years ago

I was doing little more testing in ZHA and its working setting the child to zero in the config (if doing it in the right place ;-) ) so no need for one separate firmware !!!

Its only one thing that is the same if setting in firmware or in config is that its not possible adding devices if not having one router already pared with the coordinator (must being one bug in EZSP).

I have putting it on my test network with many IKEA controllers and all was mowing to routers after restarting ZHA and waking the controller so it reconnecting to the mesh so its looks working OK only is if its helping the very fast (48 hours) battery draining problem or not.