Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IKEA E1603/E1702/E1708 outlet is constantly unregistering and registering to zigbee network #25016

Open
groenmarsmannetje opened this issue Dec 2, 2024 · 3 comments
Labels
problem Something isn't working

Comments

@groenmarsmannetje
Copy link

groenmarsmannetje commented Dec 2, 2024

What happened?

Since a couple of weeks this device is frequently during the day unregistering and registering to the zigbee network. It has contant power. I have multiple of these devices and only this one is behaving like this. It worked without issues for more then 2 years.

Maybe the device is just slowly "dying". But I would like to check if there might be an other explanation for this.

What did you expect to happen?

The device should stay connected

How to reproduce it (minimal and precise)

It starts doing this when you unplug the device from power and plug it again.
I also updated to latest adapter firmware, but it happens on that too.

Zigbee2MQTT version

1.42.0

Adapter firmware version

20240710

Adapter

zzh!

Setup

Add-on on Home Assistant Os

Debug log

No response

@groenmarsmannetje groenmarsmannetje added the problem Something isn't working label Dec 2, 2024
@Nerivec
Copy link
Collaborator

Nerivec commented Dec 2, 2024

Did you change any other nearby device? Could it now be farther away from a good link to the network?

@groenmarsmannetje
Copy link
Author

It is in same room as 10 powered zigbee devices. But good hint. Will see if it correlates if one of these devices is switched off

@Nerivec
Copy link
Collaborator

Nerivec commented Dec 3, 2024

By switched off, do you mean entirely without power (equivalent to unplugged)?
If you do that with routers, that effectively breaks the network around them every time, since devices that were connected to it have to find a new router to connect through. That is a very disruptive operation for the network for sure and can lead exactly to that issue you are seeing.

Just an idea, but could be it was connected through a router that wasn't getting powered off before (or far less often), hence you didn't have a "problem", but some combination of environmental factors may have induced a move to a new router, and that one could be getting powered off often enough, that you began to notice side-effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants