Zigbee gateway integration

[Rune]

It would be nice if you add this to the Zigbee collection:

Aqara Mini Switch

Manufacturer: LUMI
Model: lumi.remote.b1acn01

Device type: End device
Power source: Battery
Receive when idle: No

Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- MultistateInput (18)
- Identify (3)
Output clusters
- Basic (0)

[admin]

@Rune, it can be added but only with raw value reporting. It sends a certain number for single/double press and hold/release events. A small event script will be needed to perform required actions based on the switch action number.

[Zen]

Hi guys! Is this gateway supported by LM5?

https://phoscon.de/en/conbee2

Thanks for answers

[admin]

We don't have plans to support third-party adapters. Some might work if they are based on the same hardware as ours but this is not guaranteed. conbee has a different protocol so it's not supported.

[gilles38]

Hello !
I have the 60cm/60cm led ikea that is badly supported: the white temperature is not supported . here after the profile:

anufacturer: IKEA of Sweden
Model: FLOALT panel WS 60x60

Device type: Router
Power source: Mains
Receive when idle: Yes

Endpoint 1
Profile: 49246
Input clusters
- Basic (0)
- Identify (3)
- Groups (4)
- Scenes (5)
- OnOff (6)
- LevelCtrl (8)
- LightingColorCtrl (768)
- HaDiagnostic (2821)
- LightLink (4096)
Output clusters
- Scenes (5)
- Ota (25)
- PollCtrl (32)
- LightLink (4096)

thanks for your help
Gilles

[admin]

FLOALT panel is supported in the version that will be published soon.

[gilles38]

perfect thanks a lot for your support

[Zen]

We have fully working prototypes at the moment. Production devices should be ready in two months or so.

Hi sir, is there any update for the newest Zigbee sticks?

[tigi]

I noticed that the Active Power measurement of my Aqara Zigbee plugs is not working anymore, however I don't know for how long that is. The On/Off command is working though.

Also the zigbee device information of the Aqara plug shows in it's profile Electrical Measurement and Activepower.

Code:

Manufacturer: LUMI
Model: lumi.plug.maeu01

Device type: Router
Power source: Mains
Receive when idle: Yes

Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- DeviceTempCfg (2)
- Identify (3)
- Groups (4)
- Scenes (5)
- OnOff (6)
- Alarms (9)
- SeMetering (1794)
- HaElectricalMeasurement (2820)
Output clusters
- Time (10)
- Ota (25)

Endpoint 242
Profile: 41440
Output clusters
- GreenPwr (33)

Reported attributes
- activepower: 0.1
- onoff: true
- powerdivisor: 1000
- powermultiplier: 1

However the logs show something strange "unsupported attribute", but maybe this is not related.

Code:

2022-06-29 12:59:06    ZB: packet from 54ef4410003a6b1e:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 66, GeneralCommandFrame = { CommandIdentifier = "ReadAttributesResponse", ReadAttributesResponse = { ReadAttributeStatusRecords = [ { AttributeIdentifier = 1024, Status = "UNSUPPORTED_ATTRIBUTE" }, { AttributeIdentifier = 769, Status = "SUCCESS", Attribute = { Type = "uint24", Value = 1 } }, { AttributeIdentifier = 770, Status = "SUCCESS", Attribute = { Type = "uint24", Value = 1000 } } ] } } }

I also tried by removing the device and re-adding is, but Active Power keeps at 0.0W
I'm running on Zigbee v20220322 and Logicmachine SW 20211215
Can you have a look? Thanks!

[admin]

We will take a look. The problem with measurements as there are two ways of doing this. Some devices claim to support both but only partially. Looks like this plug has the same issue.

[tigi]

We will take a look. The problem with measurements as there are two ways of doing this. Some devices claim to support both but only partially. Looks like this plug has the same issue.

Thanks already!
I've investigated it a little further and I have some more information.

Apparently it has something to do with adding an extra Aqara plug to the network.
Till Thusday-Wednesday the other plugs were working fine, then I added an extra plug on Wednesday.
In the Trend logs I see that the Active Power results are still received, however something has happend to the multiplier settings, see image.
The green color is the newly added plug.
   
Maybe helpfull for solving the problem.

[fleeceable]

Hi!

I'm working on project where we want to control sockets based on electricity price. 
I'm using Sonoff zigbee 3.0 USB Dongle Plus (changed ID so LM gonna recognize that dongle). 

Sometimes after some period of time (about 12-24h) Sonoff S26 sockets stop working. 
Devices are about 4-5m away from LM so I don't think bad signal can be the problem. 

With one socket I receive status when pressing on/off button physically. Other one is basically tottaly dead. When requesting status - I get error "timeout"

LM and Zigbee app is up to date.

I have tried to restart LM, took out dongle, physical restart to zigbee socket - no success. Also to change channels etc... When I change network parameters and connect these sockets again, then it will work some time again.

Anyone has faced up with that problem? 

Log:

Code:

2022-07-07 10:06:11    ZB: permit join: -1
2022-07-07 10:05:42    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 29, Endpoint = 1 }
2022-07-07 10:05:42    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 1D
2022-07-07 10:05:42    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:42    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:42    ZB: attribute report from 00124b0024c24e83:
{ onoff = false }
2022-07-07 10:05:42    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 1D 00 1E 05 18 1C 0B 0A 00 7D
2022-07-07 10:05:42    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 24, 28, 11, 10, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 29, SrcEndpoint = 1 }
2022-07-07 10:05:42    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 28, GeneralCommandFrame = { CommandIdentifier = "DefaultResponse", DefaultResponse = { Status = "SUCCESS", CommandIdentifier = 10 } } }
2022-07-07 10:05:42    ZB: packet from 00124b0024c24e83:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer" ], TransactionSequenceNumber = 28, GeneralCommandFrame = { CommandIdentifier = "ReportAttributes", ReportAttributes = { AttributeReports = [ { AttributeIdentifier = 0, Attribute = { Type = "uint8", Value = 0 } } ] } } }
2022-07-07 10:05:42    CC: incoming message from 6735, cluster 0006, dst EP 1
2022-07-07 10:05:42    CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 58, Data = [ 8, 28, 10, 0, 0, 32, 0 ], SrcAddr = 26421, SecurityUse = 0, Radius = 29, ClusterId = 6, SrcEndpoint = 1, MacSrcAddr = 26421, GroupId = 0, TransSeqNumber = 0, Timestamp = 9726149, DstEndpoint = 1, WasBroadcast = 0 }
2022-07-07 10:05:42    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x81, data:
[29] 44 81 00 00 06 00 35 67 01 01 00 3A 00 C5 68 94 00 00 07 08 1C 0A 00 00 20 00 35 67 1D
2022-07-07 10:05:42    CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [  ], DstAddr = 26421 }
2022-07-07 10:05:42    CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[5] 45 C4 35 67 00
2022-07-07 10:05:37    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 28, Endpoint = 1 }
2022-07-07 10:05:37    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 1C
2022-07-07 10:05:37    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:37    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:37    CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [  ], DstAddr = 26421 }
2022-07-07 10:05:37    CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[5] 45 C4 35 67 00
2022-07-07 10:05:37    ZB: attribute report from 00124b0024c24e83:
{ onoff = true }
2022-07-07 10:05:37    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 1C 00 1E 05 18 1B 0B 0A 00 7B
2022-07-07 10:05:37    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 24, 27, 11, 10, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 28, SrcEndpoint = 1 }
2022-07-07 10:05:37    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 27, GeneralCommandFrame = { CommandIdentifier = "DefaultResponse", DefaultResponse = { Status = "SUCCESS", CommandIdentifier = 10 } } }
2022-07-07 10:05:37    ZB: packet from 00124b0024c24e83:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer" ], TransactionSequenceNumber = 27, GeneralCommandFrame = { CommandIdentifier = "ReportAttributes", ReportAttributes = { AttributeReports = [ { AttributeIdentifier = 0, Attribute = { Type = "uint8", Value = 1 } } ] } } }
2022-07-07 10:05:37    CC: incoming message from 6735, cluster 0006, dst EP 1
2022-07-07 10:05:37    CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 43, Data = [ 8, 27, 10, 0, 0, 32, 1 ], SrcAddr = 26421, SecurityUse = 0, Radius = 29, ClusterId = 6, SrcEndpoint = 1, MacSrcAddr = 26421, GroupId = 0, TransSeqNumber = 0, Timestamp = 9389666, DstEndpoint = 1, WasBroadcast = 0 }
2022-07-07 10:05:37    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x81, data:
[29] 44 81 00 00 06 00 35 67 01 01 00 2B 00 62 46 8F 00 00 07 08 1B 0A 00 00 20 01 35 67 1D
2022-07-07 10:05:36    CC: MT command SRSP_ZDO_EXT_ROUTE_DISC, payload:
{ Status = 0 }
2022-07-07 10:05:36    CC: MT type SRSP (3), subsystem ZDO (0x05), command id 0x45, data:
[3] 65 45 00
2022-07-07 10:05:36    ZNP: sending request:
[9] FE 04 25 45 FC FF 03 03 67
2022-07-07 10:05:36    SREQ: sending ZDO_EXT_ROUTE_DISC, data:
{ Radius = 3, DestinationAddress = 65532, Options = 3 }
2022-07-07 10:05:36    ZB: send many to one route request
2022-07-07 10:05:32    CC: MT command AREQ_ZDO_SRC_RTG_IND, payload:
{ RelayList = [  ], DstAddr = 26421 }
2022-07-07 10:05:32    CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xC4, data:
[5] 45 C4 35 67 00
2022-07-07 10:05:30    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 27, Endpoint = 1 }
2022-07-07 10:05:30    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 1B
2022-07-07 10:05:30    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:30    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:30    ZB: attribute report from 00124b0024c24e83:
{ onoff = true }
2022-07-07 10:05:30    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 1B 00 1E 05 18 19 0B 0A 00 7E
2022-07-07 10:05:30    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 24, 25, 11, 10, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 27, SrcEndpoint = 1 }
2022-07-07 10:05:30    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 25, GeneralCommandFrame = { CommandIdentifier = "DefaultResponse", DefaultResponse = { Status = "SUCCESS", CommandIdentifier = 10 } } }
2022-07-07 10:05:30    ZB: packet from 00124b0024c24e83:
{ FrameControl = [ "FrameTypeGlobal", "DirectionFromServer" ], TransactionSequenceNumber = 25, GeneralCommandFrame = { CommandIdentifier = "ReportAttributes", ReportAttributes = { AttributeReports = [ { AttributeIdentifier = 0, Attribute = { Type = "uint8", Value = 1 } } ] } } }
2022-07-07 10:05:30    CC: incoming message from 6735, cluster 0006, dst EP 1
2022-07-07 10:05:30    CC: MT command AREQ_AF_INCOMING_MSG, payload:
{ LinkQuality = 43, Data = [ 8, 25, 10, 0, 0, 32, 1 ], SrcAddr = 26421, SecurityUse = 0, Radius = 29, ClusterId = 6, SrcEndpoint = 1, MacSrcAddr = 26421, GroupId = 0, TransSeqNumber = 0, Timestamp = 8955041, DstEndpoint = 1, WasBroadcast = 0 }
2022-07-07 10:05:30    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x81, data:
[29] 44 81 00 00 06 00 35 67 01 01 00 2B 00 A1 A4 88 00 00 07 08 19 0A 00 00 20 01 35 67 1D
2022-07-07 10:05:11    CC: MT command AREQ_ZDO_MGMT_PERMIT_JOIN_RSP, payload:
{ SrcAddr = 0, Status = 0 }
2022-07-07 10:05:11    CC: MT type AREQ (2), subsystem ZDO (0x05), command id 0xB6, data:
[5] 45 B6 00 00 00
2022-07-07 10:05:11    CC: MT command SRSP_ZDO_MGMT_PERMIT_JOIN_REQ, payload:
{ Status = 0 }
2022-07-07 10:05:11    CC: MT type SRSP (3), subsystem ZDO (0x05), command id 0x36, data:
[3] 65 36 00
2022-07-07 10:05:11    ZNP: sending request:
[9] FE 04 25 36 FF FF 00 00 17
2022-07-07 10:05:11    SREQ: sending ZDO_MGMT_PERMIT_JOIN_REQ, data:
{ AddrMode = 255, TCSignificance = 0, Duration = 0, DstAddr = 65535 }
2022-07-07 10:05:11    ZB: permit join: -1
2022-07-07 10:05:10    ZCL ERR 00124b0024c24e83: timeout
2022-07-07 10:05:10    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 26, Endpoint = 1 }
2022-07-07 10:05:10    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 1A
2022-07-07 10:05:10    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:10    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:10    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 1A 00 1E 05 00 18 00 00 00 67
2022-07-07 10:05:10    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 0, 24, 0, 0, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 26, SrcEndpoint = 1 }
2022-07-07 10:05:10    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionToServer" ], TransactionSequenceNumber = 24, GeneralCommandFrame = { CommandIdentifier = "ReadAttributes", ReadAttributes = { AttributeIdentifiers = [ 0 ] } } }
2022-07-07 10:05:10    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 25, Endpoint = 1 }
2022-07-07 10:05:10    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 19
2022-07-07 10:05:10    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:10    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:10    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 19 00 1E 05 00 17 00 00 00 6B
2022-07-07 10:05:10    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 0, 23, 0, 0, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 25, SrcEndpoint = 1 }
2022-07-07 10:05:10    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionToServer" ], TransactionSequenceNumber = 23, GeneralCommandFrame = { CommandIdentifier = "ReadAttributes", ReadAttributes = { AttributeIdentifiers = [ 0 ] } } }
2022-07-07 10:05:10    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 24, Endpoint = 1 }
2022-07-07 10:05:10    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 18
2022-07-07 10:05:10    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:10    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:10    ZNP: sending request:
[20] FE 0F 24 01 35 67 01 01 06 00 18 00 1E 05 00 16 00 00 00 6B
2022-07-07 10:05:10    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 0, 22, 0, 0, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 24, SrcEndpoint = 1 }
2022-07-07 10:05:10    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeGlobal", "DirectionToServer" ], TransactionSequenceNumber = 22, GeneralCommandFrame = { CommandIdentifier = "ReadAttributes", ReadAttributes = { AttributeIdentifiers = [ 0 ] } } }
2022-07-07 10:05:08    ZCL ERR 00124b0024c24e83: nil
2022-07-07 10:05:08    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 23, Endpoint = 1 }
2022-07-07 10:05:08    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 17
2022-07-07 10:05:08    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:08    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:08    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 17 00 1E 03 11 15 00 72
2022-07-07 10:05:08    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 21, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 23, SrcEndpoint = 1 }
2022-07-07 10:05:08    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 21, OnOffClusterFrame = { CommandIdentifier = "Off" }, ClusterName = "OnOff" }
2022-07-07 10:05:08    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 22, Endpoint = 1 }
2022-07-07 10:05:08    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 16
2022-07-07 10:05:08    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:08    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:08    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 16 00 1E 03 11 14 00 72
2022-07-07 10:05:08    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 20, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 22, SrcEndpoint = 1 }
2022-07-07 10:05:08    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 20, OnOffClusterFrame = { CommandIdentifier = "Off" }, ClusterName = "OnOff" }
2022-07-07 10:05:08    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 21, Endpoint = 1 }
2022-07-07 10:05:08    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 15
2022-07-07 10:05:08    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:08    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:08    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 15 00 1E 03 11 13 00 76
2022-07-07 10:05:08    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 19, 0 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 21, SrcEndpoint = 1 }
2022-07-07 10:05:08    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 19, OnOffClusterFrame = { CommandIdentifier = "Off" } }
2022-07-07 10:05:05    ZCL ERR 00124b0024c24e83: nil
2022-07-07 10:05:05    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 20, Endpoint = 1 }
2022-07-07 10:05:05    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 14
2022-07-07 10:05:05    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:05    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:05    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 14 00 1E 03 11 12 01 77
2022-07-07 10:05:05    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 18, 1 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 20, SrcEndpoint = 1 }
2022-07-07 10:05:05    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 18, OnOffClusterFrame = { CommandIdentifier = "On" }, ClusterName = "OnOff" }
2022-07-07 10:05:05    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 19, Endpoint = 1 }
2022-07-07 10:05:05    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 13
2022-07-07 10:05:05    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:05    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:05    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 13 00 1E 03 11 11 01 73
2022-07-07 10:05:05    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 17, 1 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 19, SrcEndpoint = 1 }
2022-07-07 10:05:05    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 17, OnOffClusterFrame = { CommandIdentifier = "On" }, ClusterName = "OnOff" }
2022-07-07 10:05:05    CC: MT command AREQ_AF_DATA_CONFIRM, payload:
{ Status = 233, TransId = 18, Endpoint = 1 }
2022-07-07 10:05:05    CC: MT type AREQ (2), subsystem AF (0x04), command id 0x80, data:
[5] 44 80 E9 01 12
2022-07-07 10:05:05    CC: MT command SRSP_AF_DATA_REQUEST, payload:
{ Status = 0 }
2022-07-07 10:05:05    CC: MT type SRSP (3), subsystem AF (0x04), command id 0x01, data:
[3] 64 01 00
2022-07-07 10:05:05    ZNP: sending request:
[18] FE 0D 24 01 35 67 01 01 06 00 12 00 1E 03 11 10 01 73
2022-07-07 10:05:05    SREQ: sending AF_DATA_REQUEST, data:
{ ClusterId = 6, DstEndpoint = 1, Data = [ 17, 16, 1 ], DstAddr = 26421, Radius = 30, Options = [  ], TransId = 18, SrcEndpoint = 1 }
2022-07-07 10:05:05    ZB: sending ZCL message to 00124b0024c24e83, cluster 0006:
{ FrameControl = [ "FrameTypeLocal", "DirectionToServer", "DisableDefaultResponse" ], TransactionSequenceNumber = 16, OnOffClusterFrame = { CommandIdentifier = "On" } }

[admin]

The indicated signal level is not very good. Try moving the socket closer just to check if it's working this way or not. The indicated error code tells that the socket did not ACK coordinator's request.

[fleeceable]

Now I restarted sockets (disconnected from AC side). Both are working and signal strength shows 31% and 34%. For me this looks like there is problem with sockets...

[admin]

The signal level in ZigBee is a tricky thing. For each message only the receiving signal level for the last hop is known (since it's a mesh network a message can pass through several routers). Next ZigBee app version will have a network map feature where you can see signal levels in both directions and active routes.

[fleeceable]

Weirdest part is that I made script yesterday to turn on and off sockets every 5 seconds. After I made restart to sockets, every command goes thru and I receive feedback signal as well (tested it about 5-10 minutes). Turned that script on multiple times on daily - everything works.
Script was disabled overnight and when I turned it on today morning - no command goes thru. One socket was frozen also (physical button press didn't worked).
Sockets position is the same (4-5m from gateway) and one socket have line of sight with antenna as well...

After restart to sockets everything works again. It looks like sockets don't work well. Next week I receive Aqara SP-EUC01 sockets. Gonna test with these...

[tigi]

We will take a look. The problem with measurements as there are two ways of doing this. Some devices claim to support both but only partially. Looks like this plug has the same issue.

Problem is solved with the latest zigbee update, values are shown correctly now.
Thanks!

[tigi]

We have fully working prototypes at the moment. Production devices should be ready in two months or so.

Hi, was wondering what the status was on the new zigbee usb devices.

[fleeceable]

I have now tested system with Aqara devices as well. 
Sonoff sockets gonna freeze overnight. Aqara ones will work as they should. This is probably Sonoff socket problem so I don't suggest to use these in future...

Yesterday there was active routes as well to reach Sonoff sockets but today they are dead. They start to work after hard reset. 

Here is signal strenght data (all sockets are placed on the same place):
   
Socket 1 and 2 are Sonoff, TV is Aqara.

Is there any solution to get signal strenght to group address?

EDIT:
Here is example after overnight period:
   

[admin]

@tigi, new USB device is still in the works unfortunately. There will be an RS232 alternative as well and it might be ready sooner than USB.

@fleeceable, the network map might not show all active devices if they don't have a profile. Without a profile these devices do not periodically report their statuses so these devices are marked as offline. Signal/route information is not requested from such devices even though they can be actually online. You can try reading status manually via the UI then running network map again.
As I've mentioned before due to mesh network organization the signal strength is not really meaningful because it only provides info about the last hop.