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.

Sign up for GitHub

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

Jump to bottom

SONOFF Zigbee 3.0 USB Dongle Plus fails to OTA update IKEA Buttons without a repeater #11473

Closed
nvx opened this issue Feb 18, 2022 · 40 comments
Closed

SONOFF Zigbee 3.0 USB Dongle Plus fails to OTA update IKEA Buttons without a repeater #11473

nvx opened this issue Feb 18, 2022 · 40 comments
Labels
problem Something isn't working

Comments

@nvx
Copy link

nvx commented Feb 18, 2022

What happened?

I have two SONOFF Zigbee 3.0 USB Dongle Plus sticks, both updated using CC1352P2_CC2652P_launchpad_coordinator_20211217.zip with Zigbee2MQTT at different locations. Both locations have a number of IKEA buttons (mostly E1812, but also the odd E1743). One location has a couple of IKEA E1746 repeaters, while the other location just has the coordinator.

The site with the repeaters can OTA update the buttons fine (the buttons are connected to a repeater according to the map), while the site without any repeaters manages to (after a few attempts) check for firmware updates and determine there's an update available, any attempts to actually update the firmware says failed.

What did you expect to happen?

Successfully OTA update the buttons

How to reproduce it (minimal and precise)

Pair a IKEA E1812 button to a SONOFF Zigbee 3.0 USB Dongle Plus coordiantor without any routers in the network
Attempt to firmware update the button

Zigbee2MQTT version

1.23.0

Adapter firmware version

20211217

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus

Debug log

No response
@nvx nvx added the problem Something isn't working label Feb 18, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Mar 21, 2022
@nvx
Copy link
Author

nvx commented Mar 21, 2022

Still relevant

@nvx
Copy link
Author

nvx commented Mar 21, 2022

@Koenkk I notice the stale label is still on this, is the bot broken?

@github-actions github-actions bot removed the stale Stale issues label Mar 22, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Apr 21, 2022
@nvx
Copy link
Author

nvx commented Apr 21, 2022

Still relevant

@github-actions github-actions bot removed the stale Stale issues label Apr 22, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label May 23, 2022
@nvx
Copy link
Author

nvx commented May 23, 2022

Still relevant

@github-actions github-actions bot removed the stale Stale issues label May 24, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jun 23, 2022
@nvx
Copy link
Author

nvx commented Jun 23, 2022

Still legit. Can the bot be disabled for this issue @Koenkk?

@github-actions github-actions bot removed the stale Stale issues label Jun 24, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jul 24, 2022
@nvx
Copy link
Author

nvx commented Jul 24, 2022

Still an issue on the latest version

@github-actions github-actions bot removed the stale Stale issues label Jul 25, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Aug 24, 2022
@nvx
Copy link
Author

nvx commented Aug 24, 2022

Still an issue

@github-actions github-actions bot removed the stale Stale issues label Aug 25, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Sep 24, 2022
@nvx
Copy link
Author

nvx commented Sep 24, 2022

Still relevant

@github-actions github-actions bot removed the stale Stale issues label Sep 25, 2022
@nvx
Copy link
Author

nvx commented Jan 30, 2023

Ping

@github-actions github-actions bot removed the stale Stale issues label Jan 31, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Mar 3, 2023
@nvx
Copy link
Author

nvx commented Mar 3, 2023

Pong

@github-actions github-actions bot removed the stale Stale issues label Mar 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Apr 3, 2023
@ttonyh
Copy link

ttonyh commented Apr 3, 2023

Ping

@github-actions github-actions bot removed the stale Stale issues label Apr 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label May 5, 2023
@ttonyh
Copy link

ttonyh commented May 5, 2023

Pong

@github-actions github-actions bot removed the stale Stale issues label May 6, 2023
@kevin-david
Copy link

kevin-david commented Jun 5, 2023 •
edited

Since stale will hit this, commenting to say that I also reproduced this with the new firmware update that just came out

This issue allowed me to figure out a (very annoying) workaround 😊

kevin-david added a commit to kevin-david/zigbee2mqtt.io that referenced this issue Jun 5, 2023
@kevin-david
Doc E1743 update issues with Sonoff dongle
962a10c 
Since Koenkk/zigbee2mqtt#11473 has been open for a while and has no current path to a fix, at least unblock people.
@kevin-david kevin-david mentioned this issue Jun 5, 2023
Merged
@kevin-david
Copy link

Created a PR for people who take a while to remember to search GitHub issues: Koenkk/zigbee2mqtt.io#2069

Koenkk pushed a commit to Koenkk/zigbee2mqtt.io that referenced this issue Jun 5, 2023
@kevin-david
Doc E1743 update issues with Sonoff dongle (#2069)
332b500 
Since Koenkk/zigbee2mqtt#11473 has been open for a while and has no current path to a fix, at least unblock people.
@github-actions
Copy link
Contributor

github-actions bot commented Jul 6, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jul 6, 2023
@nvx
Copy link
Author

nvx commented Jul 11, 2023

ping

@github-actions github-actions bot removed the stale Stale issues label Jul 12, 2023
@MattWestb
Copy link

For TI coordinators you need updating the firmware then the old is having Zigbee 3 functionality disables so real Zigbee 3 end devices cant have it as parent but is OK with other good routers in the network if you is having some.

@nvx
Copy link
Author

nvx commented Jul 13, 2023

For TI coordinators you need updating the firmware then the old is having Zigbee 3 functionality disables so real Zigbee 3 end devices cant have it as parent but is OK with other good routers in the network if you is having some.

I'm not quire sure I follow. Are you saying newer firmware versions cause issues and using an older firmware fixes it? Or the other way around? (Or something else again?)

@MattWestb
Copy link

Pre 2023 was having end device functionality disables => Zigbee 3 direct children was having problems. But they have still some not standard settings that is doing problems but direct children looks working OK. (Direct children = end device is using the coordinator as parent and not one other router)
Koenkk/Z-Stack-firmware#439

@nvx
Copy link
Author

nvx commented Jul 16, 2023

Pre 2023 was having end device functionality disables => Zigbee 3 direct children was having problems. But they have still some not standard settings that is doing problems but direct children looks working OK. (Direct children = end device is using the coordinator as parent and not one other router) Koenkk/Z-Stack-firmware#439

Oh hey, so updating to the latest z stack coordinator firmware seems to have fixed the problem! Cheers for the tip!

@nvx nvx closed this as completed Jul 16, 2023
@cooperaj
Copy link

cooperaj commented Jan 8, 2024

What coordinator version did you find worked? I've just upgraded to 20230507 to fix this and still have the issue.

@nvx
Copy link
Author

nvx commented Jan 9, 2024

What coordinator version did you find worked? I've just upgraded to 20230507 to fix this and still have the issue.

That's the version I'm on that fixed it for me

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

No branches or pull requests
5 participants
@cooperaj @nvx @ttonyh @kevin-david @MattWestb