Problem with +20dBm Sonoff Zigbee dongle plus router

[Smandurlo]

What happened?

Hello, yesterday I added another sonoff zigbee dongle plus as router. I will write down my results:

• I us the latest router firmware dev. I wasn't able to increase the dBm, I got timeout writing the setting. The first sonoff zigbee router worked already @+20dBm.
• Updated the coordinator firmware, rebooted zigbee2mqtt and now I am able to change the setting to the first router, not in the second.

What is the problem? The coordinator firmware? The router firmware? The z2m version (I have the lastest master)?
Any idea?

Thanks

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.30.1-1

Adapter firmware version

20221226

Adapter

Sonoff Zigbee stick

Debug log

changing the dBm first router
info 2023-01-03 12:56:46MQTT publish: topic 'zigbee2mqtt/0x00124b0024c0af49', payload '{"last_seen":"2023-01-03T12:56:47+01:00","linkquality":81,"transmit_power":20}'
info 2023-01-03 12:56:46MQTT publish: topic 'zigbee2mqtt/0x00124b0024c0af49', payload '{"last_seen":"2023-01-03T12:56:47+01:00","linkquality":43,"transmit_power":10}'
info 2023-01-03 12:57:06MQTT publish: topic 'zigbee2mqtt/0x00124b0024c0af49', payload '{"last_seen":"2023-01-03T12:57:07+01:00","linkquality":45,"transmit_power":10}'
info 2023-01-03 12:57:07MQTT publish: topic 'zigbee2mqtt/0x00124b0024c0af49', payload '{"last_seen":"2023-01-03T12:57:07+01:00","linkquality":80,"transmit_power":20}'

Changing the dBm to the 2nd router:

nothing on the log at info level, so I selected debug:

Debug 2023-01-03 13:23:56Received MQTT message on 'zigbee2mqtt/7490/set' with data '{"transmit_power":10}'
Debug 2023-01-03 13:23:57Received MQTT message on 'zigbee2mqtt/7490/get' with data '{"transmit_power":""}'
Debug 2023-01-03 13:24:39Received MQTT message on 'zigbee2mqtt/7490/set' with data '{"transmit_power":20}'
Debug 2023-01-03 13:24:40Received MQTT message on 'zigbee2mqtt/7490/get' with data '{"transmit_power":""}'
Debug 2023-01-03 13:24:41Received MQTT message on 'zigbee2mqtt/7490/get' with data '{"transmit_power":""}'

[radek-kafka]

I have Sonoff Dongle-P with router firmware : CC1352P2_CC2652P_launchpad_router_20221102.hex

and while setting the power I'm receiving:
Zigbee2MQTT:error 2023-01-03 15:18:02: Publish 'set' 'transmit_power' to 'SonoffRouter' failed: 'Error: Write 0x00124b00257b2eb5/242 genBasic({"4919":{"value":20,"type":40}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 34526 - 242 - 72 - 0 - 4 after 10000ms)'
Jan 03 15:18:02 homeassistant addon_45df7312_zigbee2mqtt[638]: Zigbee2MQTT:debug 2023-01-03 15:18:02: Error: Write 0x00124b00257b2eb5/242 genBasic({"4919":{"value":20,"type":40}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 34526 - 242 - 72 - 0 - 4 after 10000ms)
Jan 03 15:18:02 homeassistant addon_45df7312_zigbee2mqtt[638]: at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
Jan 03 15:18:02 homeassistant addon_45df7312_zigbee2mqtt[638]: at listOnTimeout (node:internal/timers:559:17)
Jan 03 15:18:02 homeassistant addon_45df7312_zigbee2mqtt[638]: at processTimers (node:internal/timers:502:7)
Jan 03 15:18:02 homeassistant addon_45df7312_zigbee2mqtt[638]: Zigbee2MQTT:info 2023-01-03 15:18:02: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'transmit_power' to 'SonoffRouter' failed: 'Error: Write 0x00124b00257b2eb5/242 genBasic({"4919":{"value":20,"type":40}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 34526 - 242 - 72 - 0 - 4 after 10000ms)'","meta":{"friendly_name":"SonoffRouter"},"type":"zigbee_publish_error"}'

[Smandurlo]

Try the 6.10.01.01 firmware version, it should solve the timeout problem (there is the coordinator and router firmware)

[radek-kafka]

Hmm... I have tried and nothing has changed. I downloaded the firmware from : https://github.com/Koenkk/Z-Stack-firmware/raw/6.10.01.01/router/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_router_20221102.zip
edit:
After update of firmware on coordinator to same 6.10.01.01 version is seems to be better .. Thx ..

[xekil]

I have the same problem, I tried version 6.10.01.01 on the Router (Sonoff) and also on the Coordinator (ZZH), without success, I get this error :(

Error 2023-01-06 23:00:05Publish 'get' 'transmit_power' to '0x00124b00257b3eb7' failed: 'Error: Read 0x00124b00257b3eb7/242 genBasic([4919], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 27116 - 242 - 24 - 0 - 1 after 10000ms)'

[manumora]

I have the same error:

Error 2023-01-16 13:34:21Publish 'set' 'transmit_power' to 'device.sonoff.router' failed: 'Error: Write 0x00124b0029dbfc9d/8 genBasic({"4919":{"value":6,"type":40}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')'

Firmware version: 20220125

[Smandurlo]

that firmware doesn't support the +20dBm feature

[Smandurlo]

I think I've narrowed down the problem: it seems related to the latest router you add.

My second router didn't want to update the transmit power: timeout error. Yesterday I added a 3rd router: now the second router updates the transmit power and the 3rd doesn't with the transmit power timeout error. I have no other router available, but I am pretty sure that if I add a 4th router, the 3rd will start to work properly and the 4th won't.

Lastest master firmware for the coordinator and dev for the routers.

[underqualifieditguy]

Am I experiencing the same issue? I am on the latest firmware and I am getting this error which led me to this page. This happens to me when I deploy a new flow in nodered that contains a connection to Z2M.

Zigbee2MQTT:error 2023-02-07 19:40:28: Publish 'get' 'transmit_power' to '0×00124b0026b806f8' failed: 'Err or: Read 0x00124b0026b806f8/8 genBasic([4919], {"sendWhen":"immediate","timeout": 10000, "disableResponse":f alse, "disableRecovery": false,"disableDefaultResponse":true, "direction":, "srcEndpoint":null, "reservedBits" :,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORT ED ATTRIBUTE')'
Zigbee2MQTT: info 2023-02-07 19:40:28: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":" Publish 'get' 'transmit_power' to '0×001240026b806f8' failed: 'Error: Read 0×00124b0026b806f8/8 genBasicl
(4919], {\"sendWhen\": \"immediate\", \"timeout\": 10000, \"disableResponse\": false, l"disableRecovery\": false,
"disableDefaultResponseve-truebertrection.tesreEndpoints"null,lereservedBiteNsurroranufacturercode
'": null, "transactionSequenceNumber)":null, ("writeUndivi": false)) failed (Status 'UNSUPPORTED _ATTRIBUTE') ,"meta": {"friendly_name": "Ox00124b0026b806f8"}, "type":"zigbee_publish_error"}'
Zigbee2MQTT: info
2023-02-07 19:40:34: MQTT publish: topic 'zigbee2mqtt/Kitchen Window 6',

[s0ftice]

Same here.
What's worse, in my setup, the affected "lastly added" router also drops connected devices. Not sure if that's the case for you guys as well.

This started happening early Dec 2022:

• around the Z2M 1.28.4 upgrade (I am now on 1.30.1-1, the issue persists).
• when the four routers ran firmware 20220125, but the issue persists after upgrading all of them to 20221102 (develop).
• when the coordinator ran firmware 20220219, but the issue persists after upgrading it to 20221226 (master).
  (my coordinator and 4x routers are all SONOFF Dongle-P).

I'm aware that the transmit_power was not yet implemented on the 20220125 router firmware. But when one router started dropping connections, I upgraded to 20221102 and realised that the one dropping connections is always the one that times out on changing transmit_power. In my setup, there is a clear correlation between the two issues.

[radek-kafka]

As I wrote: "After update of firmware on coordinator to same 6.10.01.01 version is seems to be better .. Thx .." .. So I have updated version on Coordinator and Router to 6.10.01.01 brach and is working weel now.. The network is stable ..

[Smandurlo]

Coordinator and Router to 6.10.01.01 brach

they are not available anymore, there are new master and dev branches. I had the same problem with 6.10.01.01 too.

[underqualifieditguy]

Coordinator and Router to 6.10.01.01 brach

they are not available anymore, there are new master and dev branches. I had the same problem with 6.10.01.01 too.

@Koenkk can you comment as to why the branch was pulled?

[Koenkk]

6.10.01.01 has been integrated into the master branch.

[underqualifieditguy]

6.10.01.01 has been integrated into the master branch.

not for the launchpad_router firmware though? That is still on 20220125 version

[Koenkk]

@underqualifieditguy it was still in the develop branch, but I just added it to master.

[underqualifieditguy]

@underqualifieditguy it was still in the develop branch, but I just added it to master.

@Koenkk 20221102 contains the SimpleLink SDK version 6.10.01.01?

[Koenkk]

6.30.00.84

[underqualifieditguy]

6.30.00.84

OK do you know if this is supposed to fix the TX power issue that this thread was started about?

[Smandurlo]

May I be honest? I find a little bit confusing the way you name the versions. They looks like yyyymmdd and you don't get easily if they are old (2022) or new or a repack of an old build with the same name or whatever.

So, do we have a new router version? Does it solve this problem with the last added router?

[Enzokot]

Does it solve this problem with the last added router?

The last added router firmware 20221102 doesn't solve this problem.

[Smandurlo]

ok... thank. So we will wait for it :-)

[underqualifieditguy]

Does it solve this problem with the last added router?

The last added router firmware 20221102 doesn't solve this problem.

@Koenkk is there a release planned to address it? Many thanks for your hard work.

[Enzokot]

And ping router timeout with availability setting

[Koenkk]

Does it solve this problem with the last added router?

Can you give me a summary of this problem? The OP is about something different it seems.

[Smandurlo]

@Koenkk it started differently, but now I norrowed down the problem: I still get the timeout error while changing the TX power to the sonoff dongle plus router, but it seems it is related to the last added router. Meanwhile, I switched some coordinator/router firmwares and things changed, but the timeout problem still happens.

I wrote it 2 days ago:
"My second router didn't want to update the transmit power: timeout error. Yesterday I added a 3rd router: now the second router updates the transmit power and the 3rd doesn't with the transmit power timeout error. I have no other router available, but I am pretty sure that if I add a 4th router, the 3rd will start to work properly and the 4th won't.

Lastest master firmware for the coordinator and dev for the routers."

[Enzokot]

@Smandurlo could you try to restart z2m after add the last router? It's seems this work for me. I can change TX power and the route is online
My config:
z2m v.1.30.1
Firmware from master branch:
Coordinator v.20221226 link
Router v.20221102 link

[Enzokot]

Maybe my example is bad, because I have only one TI router

[Smandurlo]

I tried to unplug a random router (so 2 left plugged in) and then reboot z2m: I always have 1 router that doesn't accept the TX change. That is odd.

[Koenkk]

@Smandurlo can you try moving them in direct range of the coordinator? Looks that the are unreachable.

[s0ftice]

I tried that, LQI around 200, same issue

[Smandurlo]

They are in the same room for the tests, but they are normally near enough to see each other.

[gerard33]

I experience the same issue with not being able to set transmit power to the latest router that is added, but it is indeed solved after a restart of Z2M as suggested by @Enzokot.

Information of the routers:

1. Router 1 is a SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P, is on correct firmware and setting transmit power to 20 works (after having added router 2 and 3)
2. Router 2 is a SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P as well, is on correct firmware and setting transmit power to 20 works (after having added router 3)
3. Router 3 is a SMLIGHT CC2652P Zigbee USB Adapter SLZB-02 and is added as the last of the 3 routers, is on correct firmware and setting transmit power to 20 does not work but gives this error:

Publish 'set' 'transmit_power' to 'Smartlight SLZB-02 router' failed: 'Error: Write 0x00124b002579310d/242 genBasic({"4919":{"value":20,"type":40}}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 21789 - 242 - 155 - 0 - 4 after 10000ms)'

After a restart of Z2M (running Z2M as a LXC on Proxmox so I stopped and restarted the LXC) changing the transmit power works and also immediately shows an increase of linkquality.

[Smandurlo]

@gerard33 try to change the TX power to all your routers. Pay attention to the other routers cause it probably won't give you any error, but the TX power will not actually change. Try this: change the TX power, move to another page and then return back to the "Exposes" page. I bet you will not see the new value, but it is locked to the previous one. The linkquality doesn't change anymore. I am pretty sure it will happen to one of your routers only.

[billyjoebob999]

I have 3 Sonoff dongles, one is the coordinator, and two are acting as routers. All have been updated with the latest firmware. I have no issues changing the TX on the routers. I can update the TX in Z2M and its reflected in HA. I can then change the TX in HA and confirmed Z2M shows the new value.

One thing I noticed after updating both routers, Z2M still showed them running the previous firmware. I had to removed both of then and add then back for things to work correctly.

[Smandurlo]

@billyjoebob999 could you please tell me how your coordinator/routers are arranged? I mean, is your coordinator in the middle of the two routers? Do your routers see each other?

[billyjoebob999]

@Smandurlo with the layout of my home I'm able to centrally locate the coordinator. Each router is then located at each end of the house. I don't know how to tell if the two routers are talking to each other. I assume they are.

[Smandurlo]

Just look at your map if your routers are connected :-) my coordinator is not in the middle of the routers, but on a side, so a router is connected to the coordinator through another router. Maybe this is the problem.

[billyjoebob999]

Per the map they connect to the coordinator. This also true for any mains powered devices that act as routers. They connect to the coordinator regardless of where they are placed (several placed through out the house).

[gmaslowski]

@gerard33 @Smandurlo @Koenkk

I'm experiencing similar issues, but I managed to configure the transmit power in the following manner.

Setup

• 1x Sonoff Zigbee 3.0 USB Dongle Plus as Coordinator on 20221226
• 2x Sonoff Zigbee 3.0 USB Dongle Plus as Routers on 20221102

Procedure

1. Add 1st Router to the network
2. Restart zigbee2mqtt
3. Set TX Power on Router
4. Add 2nd Router to the network
5. Restart zigbee2mqtt
6. Set TX Power on Router

Tried other options, with no luck. Looks like somehow, after the Routers pairing I needed to restart zigbee2mqtt. Not sure if that will really hold for long though :P. Looks like the value is set for now.

[Smandurlo]

nothing changed for me. I was able to change the TX power in my 2nd router when I added a 3rd one, but now the 2nd is "stuck". It shows +20dB, but it doesn't change anymore and I am not actually sure it is really +20dB. The first one works as expected.

[gmaslowski]

@Smandurlo I was not trying to change those values again though.

The json State states 20 as power for both the routers. The mesh network and LQI on all the devices in my network "looks better".

[Smandurlo]

yes, the json is +20dBm and if I move the slide I can see the topic /set/transmit_power changing, but it doesn't actually change. I cannot be sure the LQI "looks better" cause I had to move the coordinator in a different position and I have not a reference to compare.

[Smandurlo]

I made some tests and I can say that the +20dBm on my second router (the one I cannot change the TX power anymore) is not real. The LQI of the sensors next to it are way too low compared with the coordinator and first router with +20dBm at the same distance.

The problem is, I didn't understand if @Koenkk is aware of the problem and he is investigating on it.

[klu16]

Workaround from @gmaslowski worked for me.
I restarted the Z2M addon and after that the transmit power setting to 20 was saved. Thanks!

[github-actions]

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

[Smandurlo]

Sadly the problem is still there

[github-actions]

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

[Smandurlo]

I wish it was solved 😢

[github-actions]

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

[baerni]

Which router firmware version should I upload to have +20 transmit power? Why for cC2652 max transmit power is 5 and not 20?