Sonoff S26R2ZB Smart Plug Zigbee Router devices by ITead disconnect from network after a day or two - Firmware bug or?

daufinsyd commented 2 years ago

Hello :)

What happened

After a day or two running perfectly fine, routers kind of disconnect from the network; trying to execute any command results in timeout. It happens for all routers I have (6 sonoff s26r2zb). End devices (sonoff snzb02 / 03) (directly connected to the coordinator) don't appear to be affected.

example of failed command:

Zigbee2MQTT:error 2021-12-18 16:30:30: Publish 'set' 'state' to 'PLUG-SF-SALON' failed: 'Error: Command 0x00124b0024c08124/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 22057 - 1 - 184 - 6 - 11 after 10000ms)'

After the router "disconnected", most of the time, simply plugging it off and back solve the issue for a day or two.

I tried increasing the TX power but it didn't help, all devices (with either good or bad LQI disconnect).

What did you expect to happen

Devices are working.

How to reproduce it (minimal and precise)

Join devices
Wait a day or two

Debug info

Zigbee2MQTT version: 1.22.1 Adapter hardware: CC2652RB (from slae.sh, as recommended in the official website) Adapter firmware version: transportrev 2, product 1, majorrel 2, minorrel 7, maintrel 1, revision: 20210708

Edit: typo

andrazek commented 2 years ago

Aliexpress offered me a full refund if I return the plug on my expenses (can be expensive to ship it back), or alternatively, a partial refund (half the price) if I keep the product. Nothing is perfect. Can it work for someone not using z2m?

nickwild-999 commented 2 years ago

I'm just going to eBay mine and NEVER buy anything from them again. Life's too short to try and repair some inept manufacturer's faults who have included NO means to update their products with new firmware. Shame on you!

dangnguyen0906 commented 2 years ago

Aliexpress offered me a full refund if I return the plug on my expenses (can be expensive to ship it back), or alternatively, a partial refund (half the price) if I keep the product. Nothing is perfect. Can it work for someone not using z2m?

I buy on Lazada so it's hard to return so i still keep it. Agree it's a shame. BTW you can try with Sonoff ZB hub. I see rarely complain of this device with Sonoff hub

Daniel-zhan-itead commented 2 years ago

Aliexpress offered me a full refund if I return the plug on my expenses (can be expensive to ship it back), or alternatively, a partial refund (half the price) if I keep the product. Nothing is perfect. Can it work for someone not using z2m?

Please disable the permit join in Z2M after you've peered your devices, the S26R2ZB will work as you expect. Please try it. As Koenkk suggested from the below link: https://www.zigbee2mqtt.io/guide/configuration/zigbee-network.html#permit-join

Hedda commented 2 years ago

Please disable the permit join in Z2M after you've peered your devices, the S26R2ZB will work as you expect. Please try it. As Koenkk suggested from the below link: https://www.zigbee2mqtt.io/guide/configuration/zigbee-network.html#permit-join

It should be noted that doing so is only a temporary workaround as a it a security risk to leave permit join enabled for longer time.

@Daniel-zhan-itead In fact, to be compliant with the Zigbee 3.0 specification and to get Zigbee 3.0 cerified products by the CSA / Zigbee Alliance you are not allowed to be able to set permit join for no more than 254 seconds as its maximum time.

That is, Zigbee 3.0 security specification imposes a limited window of time in which a network can permit joining; the maximum joining window allowed by the Zigbee specifications is 254 seconds (NJ=0xFE). Whenever the join window is opened, the NJ value of the device that opens the window will be used; this timeout value is not shared by the rest of the network.

https://csa-iot.org/csa-iot_products/

So you as a company might want to consider this permit join maximum of 254 seconds if plan to keep certifiying Sonoff products.

MattWestb commented 2 years ago

@Hedda :

Please disable the permit join in Z2M . . .

Disable = turning off = not possible joining device.

Z2M is broadcasting permit join with timer if setting it permanent in the config and THAT is one large security risk that most user don understand and is having open system that every one with little knowledge can doing what there like !

Hedda commented 2 years ago

@Daniel-zhan-itead Another suggestion would be for ITead to release the very latest OTW (Over-The-Wire) firmware image for these products that do not support OTA updates so that at least advanced users have the option to manually flash newer firmware on these using an external "cJTAG debug probe adapter" such as the CC-DEVPACK-DEBUG from Texas Instruments:(c/JTAG debugger tool adapter for JTAG flashing over TMS and TCK pins, i.e. the cJTAG interface, a.k.a. IEEE 1149.7 interface):

https://electrolama.com/radio-docs/advanced/flash-jtag/

https://www.ti.com/tool/CC-DEVPACK-DEBUG

@Daniel-zhan-itead Maybe even consider convincing management at ITead to make and sell some CC2652 development kits?

https://www.ti.com/design-resources/embedded-development/hardware-kits-boards.html

https://www.ti.com/wireless-connectivity/overview.html

I bet there is a market within the DIY community that would be interested in buying relatively inexpensive development kits for:

Debug probe adapter with cJTAG support similar to CC-DEVPACK-DEBUG -> https://www.ti.com/tool/CC-DEVPACK-DEBUG
Battery-operated SensorTag Kit like the LPSTK-CC1352R evaluation board with on-board sensors (temperature, humidity, hall effect, light, motion) -> https://www.ti.com/tool/LPSTK-CC1352R
CC2652P developer board with multiprotocol support similar to LAUNCHXL-CC26X2R1 -> https://www.ti.com/tool/LAUNCHXL-CC26X2R1
CC1352P developer board with Sub-1 GHz multiband support similar to LAUNCHXL-CC1352P1 -> https://www.ti.com/tool/LAUNCHXL-CC1352P

Daniel-zhan-itead commented 2 years ago

Aliexpress offered me a full refund if I return the plug on my expenses (can be expensive to ship it back), or alternatively, a partial refund (half the price) if I keep the product. Nothing is perfect. Can it work for someone not using z2m?

Please submit us a ticket and our customer service representative will help.🤝 https://itead.freshdesk.com/support/tickets/new

daufinsyd commented 2 years ago

Aliexpress offered me a full refund if I return the plug on my expenses (can be expensive to ship it back), or alternatively, a partial refund (half the price) if I keep the product. Nothing is perfect. Can it work for someone not using z2m? Hi @andrazek, how did you managed to get a (partial) refund ? Did you bought them fron official sonoff tech store ?

andrazek commented 2 years ago

@daufinsyd No, it was an unbranded seller. The seller did not understand the case well. They suggested connecting to a 5G WIFI and similar nonsenses. Then Aliexpress joined the dispute and made a decision. @Daniel-zhan-itead Thank you for the link, I'll submit a ticket. In case I disable permit join, will I have to pair the plug every time I add a new Zigbee device (for that I have to enable permit join)?

Daniel-zhan-itead commented 2 years ago

Please disable the permit join in Z2M after you've peered your devices, the S26R2ZB will work as you expect. Please try it. As Koenkk suggested from the below link: https://www.zigbee2mqtt.io/guide/configuration/zigbee-network.html#permit-join

It should be noted that doing so is only a temporary workaround as a it a security risk to leave permit join enabled for longer time.

@Daniel-zhan-itead In fact, to be compliant with the Zigbee 3.0 specification and to get Zigbee 3.0 cerified products by the CSA / Zigbee Alliance you are not allowed to be able to set permit join for no more than 254 seconds as its maximum time.

That is, Zigbee 3.0 security specification imposes a limited window of time in which a network can permit joining; the maximum joining window allowed by the Zigbee specifications is 254 seconds (NJ=0xFE). Whenever the join window is opened, the NJ value of the device that opens the window will be used; this timeout value is not shared by the rest of the network.

https://csa-iot.org/csa-iot_products/

So you as a company might want to consider this permit join maximum of 254 seconds if plan to keep certifiying Sonoff products.

If users did not disable the permit join configuration in Z2M, the Z2M will broadcast the permit join request every 250s in the network, what I mean to disable the permit join is for the Z2M coordinator, but not for the router or ED.

Daniel-zhan-itead commented 2 years ago

@daufinsyd No, it was an unbranded seller. The seller did not understand the case well. They suggested connecting to a 5G WIFI and similar nonsenses. Then Aliexpress joined the dispute and made a decision. @Daniel-zhan-itead Thank you for the link, I'll submit a ticket. In case I disable permit join, will I have to pair the plug every time I add a new Zigbee device (for that I have to enable permit join)?

When you need to add the new devices to the network, then enable the "permit join" config, it is not necessary to keep it enabled all the time. I don't think users have the need to join the device every day.

aj-2 commented 2 years ago

Quick update, I have not had any issues for over 2 weeks now. @Daniel-zhan-itead do you know why they won't work as routers, is this caused by the same bug in the firmware?

Daniel-zhan-itead commented 2 years ago

Quick update, I have not had any issues for over 2 weeks now. @Daniel-zhan-itead do you know why they won't work as routers, is this caused by the same bug in the firmware?

The S26ZBR2 definitely plays the router role in the Zigbee network, However, when the device does not work as expected, each user has different descriptions for the issue, like not working as a router, device offline, the signal is so bad, etc. Such issues can be fixed by disabling the permit join configuration in Z2M as I suggested.

daufinsyd commented 2 years ago

@Daniel-zhan-itead Thank you for the link, I'll submit a ticket. In case I disable permit join, will I have to pair the plug every time I add a new Zigbee device (for that I have to enable permit join)?

When you need to add the new devices to the network, then enable the "permit join" config, it is not necessary to keep it enabled all the time. I don't think users have the need to join the device every day.

@Daniel-zhan-itead so each time we join a new device to the network, it reduces the time to live till manual power reset i need.

JavierJMzgz commented 2 years ago

Quick update, I have not had any issues for over 2 weeks now. @Daniel-zhan-itead do you know why they won't work as routers, is this caused by the same bug in the firmware?

The S26ZBR2 definitely plays the router role in the Zigbee network, However, when the device does not work as expected, each user has different descriptions for the issue, like not working as a router, device offline, the signal is so bad, etc. Such issues can be fixed by disabling the permit join configuration in Z2M as I suggested.

I'm affraid this is not really true (at least in my case), I never keep the "Permit join" enabled more than the necessary and I have signal and router issues from the very first time. I have two S26ZBR2 and none of them can joined to each other beyond 3 meters in the same room (I switched the position of them just to try). And It was also impossible to join a couple of SNZB-04 between them (1,5 m far from the S26ZBR2 "routers"). I bought both S26ZBR2 to expand the Zigbee range and it was completely useless.

I am very disappointed with SONOFF. Most of the devices I bought are abandoned in a drawer: one Sonoff Zigbee 3.0 USB Dongle Plus (router firmware), two ZBMINI and two S26ZBR2, all of them (5) bought just to work as routers (due to a lack of signal in a few meters in the same room), three SNZB-04, which stop working in few hours after I reset them (they do not transmit any change in the status). The only ones that keep working are the coordinator (another Sonoff Zigbee 3.0 USB Dongle Plus, but with many other relays to expand the network a few meters) and two SNZB-02.

Honestly, from my experience, SONOFF is the worst manufacturer I have ever met: many failures in many devices with no solution.

Daniel-zhan-itead commented 2 years ago

Quick update, I have not had any issues for over 2 weeks now. @Daniel-zhan-itead do you know why they won't work as routers, is this caused by the same bug in the firmware?

The S26ZBR2 definitely plays the router role in the Zigbee network, However, when the device does not work as expected, each user has different descriptions for the issue, like not working as a router, device offline, the signal is so bad, etc. Such issues can be fixed by disabling the permit join configuration in Z2M as I suggested.

I'm affraid this is not really true (at least in my case), I never keep the "Permit join" enabled more than the necessary and I have signal and router issues from the very first time. I have two S26ZBR2 and none of them can joined to each other beyond 3 meters in the same room (I switched the position of them just to try). And It was also impossible to join a couple of SNZB-04 between them (1,5 m far from the S26ZBR2 "routers"). I bought both S26ZBR2 to expand the Zigbee range and it was completely useless.

I am very disappointed with SONOFF. Most of the devices I bought are abandoned in a drawer: one Sonoff Zigbee 3.0 USB Dongle Plus (router firmware), two ZBMINI and two S26ZBR2, all of them (5) bought just to work as routers (due to a lack of signal in a few meters in the same room), three SNZB-04, which stop working in few hours after I reset them (they do not transmit any change in the status). The only ones that keep working are the coordinator (another Sonoff Zigbee 3.0 USB Dongle Plus, but with many other relays to expand the network a few meters) and two SNZB-02.

Honestly, from my experience, SONOFF is the worst manufacturer I have ever met: many failures in many devices with no solution.

To be honest, I don't want to dispute your statement about SONOFF, this thread is aim to fix the issue that all guys you've met but not to discuss non-sense complaints. The after-sale support is always open for you to raise your request. https://itead.freshdesk.com/support/tickets/new When the device is running at your local network but not connected to our server, it is more complicated to address the root cause of the issue as we can not 100% reproduce it, all we can do is understand the case and try to catch any clue if you are willing to working with us. It is unfair to blame all on SONOFF as many other factors may also cause the issue and affect your application.

ChrisLane commented 2 years ago

I think this issue should be closed since there's now a workaround for zigbee2mqtt for the original issue and steps for getting a replacement device with fixed firmware have been outlined above.

Setting "permit join" to disabled worked for me as a workaround.

aj-2 commented 2 years ago

I agree one final update I did some proper testing last night and I did finally see some devices using the sonoff plugs as routers. So I was indeed wrong that this functionality didn't work. Best guess is my network was just laid out in such a way that the sockets were never the best route for any of my devices to use. However after some testing I did manage to get devices routing via the sockets so they do seem fully functional with the workaround in place. Thanks to everyone for working through this to what looks like an acceptable fix.

nickwild-999 commented 2 years ago

Is there a way to disable "permit Join" on a device-by-device basis? - I can only see a global toggle?

andrazek commented 2 years ago

@daufinsyd No, it was an unbranded seller. The seller did not understand the case well. They suggested connecting to a 5G WIFI and similar nonsenses. Then Aliexpress joined the dispute and made a decision. @Daniel-zhan-itead Thank you for the link, I'll submit a ticket. In case I disable permit join, will I have to pair the plug every time I add a new Zigbee device (for that I have to enable permit join)?

When you need to add the new devices to the network, then enable the "permit join" config, it is not necessary to keep it enabled all the time. I don't think users have the need to join the device every day.

I've put the permit_join: false to configs yml. The device stays connected, but after some time the LQI drops to unreliably low values (<20) which causes instability (lots of commands are simply lost). The device is located in the same room as the dongle (no walls in between), about 6-8 m apart. This should also be addressed with the new firmware if you're really working on it. No other Zigbee device I have (branded and unbranded) acts like that. I've opted for S26R2ZB mainly because it was clearly stated that it can work as a router. But do I really want to have an unreliable router? Haven't tested the router functionality though.

ITEAD support told me that the issue of dropping from the Zigbee network has been solved and that I have to use "permit_join: false". No answer to the question regarding bad reception yet.

SzymonZy commented 2 years ago

Permit join disabled permanently - s26 on 2.0.1. Today again unresponsive (even hardware button does not react). So sorry setting permit join false is not even a workaround in my case. Only one left to maintain water circulation - I have to replace.

wt., 7 cze 2022 o 13:23 andrazek @.***> napisał(a):

@daufinsyd https://github.com/daufinsyd No, it was an unbranded seller. The seller did not understand the case well. They suggested connecting to a 5G WIFI and similar nonsenses. Then Aliexpress joined the dispute and made a decision. @Daniel-zhan-itead https://github.com/Daniel-zhan-itead Thank you for the link, I'll submit a ticket. In case I disable permit join, will I have to pair the plug every time I add a new Zigbee device (for that I have to enable permit join)?

When you need to add the new devices to the network, then enable the "permit join" config, it is not necessary to keep it enabled all the time. I don't think users have the need to join the device every day.

I've put the permit_join: false to configs yml. The device stays connected, but after some time the LQI drops to unreliably low values (<20) which causes instability (lots of commands are simply lost). The device is located in the same room as the dongle (no walls in between), about 6-8 m apart. This should also be addressed with the new firmware if you're really working on it. No other Zigbee device I have (branded and unbranded) acts like that. I've opted for S26R2ZB mainly because it was clearly stated that it can work as a router. But do I really want to have an unreliable router? Haven't tested the router functionality though.

ITEAD support told me that the issue of dropping from the Zigbee network has been solved and that I have to use "permit_join: false". No answer to the question regarding bad reception yet.

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/10282#issuecomment-1148535720, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY2JJRFANLNJR2L6Y3M5V3VN4WLRANCNFSM5KOWETCA . You are receiving this because you commented.Message ID: @.***>

github-actions[bot] commented 2 years ago

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

SzymonZy commented 2 years ago

This week I had to replug last two S26r2zb devices. In my case I don't have permit join: true. And these are stable up to one week.

śr., 18 maj 2022 o 18:01 aj-2 @.***> napisał(a):

Thanks @Koenkk https://github.com/Koenkk

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/10282#issuecomment-1130204990, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY2JJQR5WNAZEZAJV4R6U3VKUH6VANCNFSM5KOWETCA . You are receiving this because you commented.Message ID: @.***>

SzymonZy commented 2 years ago

I jest realized that two sonoff on 2.0.1 failed until repliged info socket. Already replaced two with https://www.zigbee2mqtt.io/devices/TS011F_plug_3.html#tuya-ts011f_plug_3 These two work flawessly and cost 50% of sonoff price. Need to order two more and put sonoff info trash or wait until we will be able to update firmware on our own.

pon., 9 maj 2022, 20:44 użytkownik wormvortex @.***> napisał:

I’ve had one of these for a few weeks and as far as I could tell it was working fine. However since buying a 2nd both of them seem to be disconnecting constantly or maybe I’m just paying more attention?

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/10282#issuecomment-1121449904, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY2JJUEKK3Y6T7DGWSKXO3VJFMIPANCNFSM5KOWETCA . You are receiving this because you commented.Message ID: @.***>

eokgnah commented 1 year ago

I have eight newly ordered S26R2ZB and they don't behave nice too.

Zigbee2mqtt tells me that they have the firmware "20210511", "2.0.0".

Looks like i got them with a old firmware.

Is there a newer image i can flash, like i can flash the WIFI Sonoffs?

Now i ordered some sockets from IKEA for exchanging the Sonoffs. But it would nice to get them working.

SzymonZy commented 1 year ago

Sorry, You can put them info trash. Even if You disable permit and do not add any new devices to network, every one or two weeks You will have to unplug, plugin again. Sonoff have only one good device. Cordinator - old one.

sob., 12 lis 2022, 13:13 użytkownik eokgnah @.***> napisał:

I have eight newly ordered S26R2ZB and they don't behave nice too.

Zigbee2mqtt tells me that they have the firmware "20210511", "2.0.0".

Looks like i got them with a old firmware.

Is there a newer image i can flash, like i can flash the WIFI Sonoffs?

Now i ordered some sockets from IKEA for exchanging the Sonoffs. But it would nice to get them working.

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/10282#issuecomment-1312465995, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY2JJQRI2VMDBV3JS6QH3LWH6CWBANCNFSM5KOWETCA . You are receiving this because you commented.Message ID: @.***>

Daniel-zhan-itead commented 1 year ago

@SzymonZy @eokgnah Due to the SDK bug of the flash leakage, if the device does not work properly, please contact SONOFF aftersale for the replacement with the latest firmware device. As I stated before, the S26ZBR2 is not able to update the firmware via OTA because of the limitation of the flash room. https://itead.freshdesk.com/support/tickets/new

To those Who also have a similar issue.

domneedham commented 1 year ago

I am seeing a similar issue running firmware 2.0.1. I have contact Sonoff support to help resolve this.

daufinsyd commented 1 year ago

@Koenkk could you reconsider advertising the plug as officially supported ? It hurt the trust on mqtt and pomotes a manafactuer who cleary do not have the skill the develop such product or at least the will to test them.

I wanted to buy a motion sensor, instead of searching on the supported devices list, I looked on github for user feedbacks to see it they were encountering issues.

After almost an entire year sonoff is still unable to fix their product, I understand it's a big plus advertising 2572 supported devices (as of writing) but if they are buggy, at the end it's more work for the contributors and dishonest (or tricky) for the buyers.

Koenkk commented 1 year ago

@daufinsyd I don't know whether this issue already has been fixed in the latest version of this plug, @Daniel-zhan-itead can you confirm this?

jodab commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

renatoyamane commented 1 year ago

Gateway: Sonoff NSPanel PRO (firmware 1.4.1)
Zigbee devices: Sonoff SNZB-01/02/03/04 (firmware is unknown)
Zigbee routers: S26R2ZBTPG (firmware is unknown)

All devices have been purchased recently on their official sales channel (ITEAD & Amazon UK).

Same problem. They usually stop working within a couple of days. As they are also routing, any devices routed through the plugs goes offline too. And looks like the range of these routers is too short. Looks like 3 meters, with a thin wall is enough to reduce the signal making them unusable.

Daniel-zhan-itead commented 1 year ago

@daufinsyd I don't know whether this issue already has been fixed in the latest version of this plug, @Daniel-zhan-itead can you confirm this?

Firmware 2.1.0 has fixed the bug of the flash leakage issue.

Daniel-zhan-itead commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

The firmware 2.0.1 still not fix the bug of the flash leakage, please contact our technical support for a replacement.

daufinsyd commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

The firmware 2.0.1 still not fix the bug of the flash leakage, please contact our technical support for a replacement.

Technical support asked me to smash the plugs and send them proof they were destroyed so that they accept to send new plugs (at the time certainly with the faulty firmware 2.0.x) ... sonoff is definitely not living in the same world.

aj-2 commented 1 year ago

My plugs are 2.0.1 and the permit join=false did resolve the issue for me. They have worked fine ever since. One plug is used multiple times a day so would have noticed any instability. Wonder what the difference between mine and your setup is.

They are terrible relays though as someone pointed out the range is poor.

renatoyamane commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

The firmware 2.0.1 still not fix the bug of the flash leakage, please contact our technical support for a replacement.

@Daniel-zhan-itead opening a ticked on the link you posted didn't help, because nobody answer. Sending an email to the support also is not working because people there is not able to understand absolutly nothing. Is there a contact channel that works?

Daniel-zhan-itead commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

The firmware 2.0.1 still not fix the bug of the flash leakage, please contact our technical support for a replacement.

@Daniel-zhan-itead opening a ticked on the link you posted didn't help, because nobody answer. Sending an email to the support also is not working because people there is not able to understand absolutly nothing. Is there a contact channel that works?

We are investigating why there is no firmware version in your case, I think the issue is caused by the S26R2ZB as it is not the latest firmware. We will reply to you via the ticket.

renatoyamane commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

Hi, did you receive any news from Itead/Sonoff? I have the same problem. Sent the serial number to them but I'm still waiting...

Thanks

jollytoad commented 1 year ago

I'll leave this note, in case any other Amazon customers stumble across this:

I purchased 8 of these (S26R2ZBTPG) from Amazon (UK) in Aug & Oct 2022, unaware of these issues. I've since started to encounter problems, and have only just come across this issue yesterday. The plugs have firmware 2.0.0. I've contacted Amazon customer support via their chat, explained they have a known firmware fault and cannot be updated, and they are refunding them.

This product is no available on Amazon or directly from Itead, so I'm guessing you would be better off claiming a refund than trying to get a replacement.

daufinsyd commented 1 year ago

@Koenkk don't know why you insist keeping the plug listed as supported given all the reports stating it's not working :-(

moorsey commented 1 year ago

I've contacted Itead/Sonoff support to see if they will replace my eight S26R2ZBTPF-DE I got recently, but I'm guessing not. These are all version 2.0.1 and usually stops working within a week. As they are also routing, any devices routed through the plugs goes offline too.. and if that device happened to be aqara then it's lost until repairing. These plugs really made my whole zigbee network unstable!

Hi, did you receive any news from Itead/Sonoff? I have the same problem. Sent the serial number to them but I'm still waiting...

Thanks

I had a quick reply to say they would replace, but no stock. Still waiting, 2 months ish now I think

Might do what @jollytoad said and try to refund via Amazon. What alternative did you end up with @jollytoad ?

jollytoad commented 1 year ago

I'm trying these out atm... https://www.amazon.co.uk/dp/B0B9NF7D22 Although they show as SA-029 in Z2M, they are very basic (no power on behaviour) ... not sure how well they work as routers yet. The packaging has no manufacturer name, no 'Woolley' on there. Zigbee manuf and model is: SONOFF/Z111PL0H-1JX according to Z2M. Appears to have no OTA update ability. You get what you pay for I guess! I still need a couple more plug, so still on the look out for something potentially more reliable/future proof. I was considering Innr plug.

tungmeister commented 1 year ago

I opened a ticket about 2 1/2 weeks ago and I'm yet to hear anything

eokgnah commented 1 year ago

sonoff Got replacements today... Only had to pay for shipping. They are: Firmware build date 20220420 Firmware version 2.1.1 Manufacturer SONOFF Model S26R2ZB

tungmeister commented 1 year ago

I never got a response to my ticket. Rather disappointing!

zomar76 commented 1 year ago

Hello, I have 3 S26R2ZB with Firmware version 2.0.1 all disconnect from the network as described in this thread.

I'm testing that solution: 1) from OpenHab at midnight I'm sending mqttActions.publishMQTT('zigbee2mqtt/bridge/request/device/remove', '{"id": "0x00124b0024caa5d3"}') 2) device is reconnecting instantly 3) all 3 devices are working more then 72h

tungmeister commented 1 year ago

@zomar76 I've just tried this however the test device didn't automatically rejoin unless I enabled joining and as I expected it forgot it's name. If this can all be done with MQTT though this could be set up as part of a script. I'll have a look.

EDIT: I've just set up this script which I'll run as an automation at 4am going forward and see what happens. hopefully, it'll do the trick, as they're not critical devices it doesn't matter at all if they're unavailable for a few seconds at that time. I went for the 35-second delay after a bit of testing the rejoining/interviewing time was consistently completed before that had elapsed.

  script:
    sonoff_zigbee_reset:
      alias: "Sonoff Zigbee Reset"
      sequence:
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/permit_join
            payload: >
              {"value": true}
        - delay: 00:00:01
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/device/remove
            payload: >
              { "id": "0x00124b00258a4187" }
        - delay: 00:00:01
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/device/remove
            payload: >
              { "id": "0x00124b0024c24c48" }
        - delay: 00:00:35
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/device/rename
            payload: >
              {"from": "0x00124b00258a4187", "to": "retropie","homeassistant_rename":true}
        - delay: 00:00:01
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/device/rename
            payload: >
              {"from": "0x00124b0024c24c48", "to": "Garden lights","homeassistant_rename":true}
        - service: mqtt.publish
          data:
            topic: zigbee2mqtt/bridge/request/permit_join
            payload: >
              {"value": false}

jaanek commented 1 year ago

@tungmeister How is that script working for you? I have the same plugs, just wondering if there is some workaround to fix the disconnect.

Koenkk / zigbee2mqtt