Unable to pair new zigbee eco-dim devices after the first

[dude]

Hi,

Using Zigbee for domoticz plugin, with an Sonoff USB Dongle plus V2.
Installed the first Eco-dim.07 zigbee basic dimmer this works flawless, recognized as Ecodim Zigbee 3.0
When trying to add a second or third, communcication is recognized, but added as non optimized in the device management list.
Cleaning the database and resettting the coordinator and try again to pair with another sequence of devices doesn't solve the problem, again the second one is not optimized.
The plugin log show the following information:

Code: Select all

2023-11-06 22:29:39,367 INFO    :b'Request Accepting new Hardware for 240 seconds '
2023-11-06 22:29:39,428 INFO    :b"PERMIT-TO-JOIN: {'cmd': 'PERMIT-TO-JOIN', 'datas': {'Duration': 240, 'targetRouter': 'FFFC'}, 'NwkId': None, 'TimeStamp': 1699306179.3657014, 'ACKIsDisable': False, 'Sqn': None}"
2023-11-06 22:29:39,429 INFO    :b'PERMIT-TO-JOIN: duration: 240 for Radio: ezsp for node: None'
2023-11-06 22:29:39,429 INFO    :b'Calling self.app.permit(time_s=240, node=None )'
2023-11-06 22:29:39,458 INFO    :b'returning from the self.app.permit(time_s=240, node=None )'
2023-11-06 22:29:51,147 INFO    :b'Request Accepting new Hardware for 240 seconds '
2023-11-06 22:29:51,218 INFO    :b"PERMIT-TO-JOIN: {'cmd': 'PERMIT-TO-JOIN', 'datas': {'Duration': 240, 'targetRouter': 'FFFC'}, 'NwkId': None, 'TimeStamp': 1699306191.145856, 'ACKIsDisable': False, 'Sqn': None}"
2023-11-06 22:29:51,218 INFO    :b'PERMIT-TO-JOIN: duration: 240 for Radio: ezsp for node: None'
2023-11-06 22:29:51,218 INFO    :b'Calling self.app.permit(time_s=240, node=None )'
2023-11-06 22:29:51,249 INFO    :b'returning from the self.app.permit(time_s=240, node=None )'
2023-11-06 22:31:00,983 INFO    :b'--> Adding device 46e4 in self.DevicesInPairingMode'
2023-11-06 22:31:00,983 INFO    :b"--> ['46e4']"
2023-11-06 22:31:00,984 INFO    :b'[None] NEW OBJECT: 46e4 None'
2023-11-06 22:31:01,985 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:01,993 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:05,995 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:06,008 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:07,999 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:08,009 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:10,005 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:10,011 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:13,016 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:13,025 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:15,022 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:15,029 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:16,024 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:16,033 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:20,048 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:20,055 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:21,053 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:21,061 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:25,065 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:25,078 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:27,074 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:27,084 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:29,076 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:29,082 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:30,079 INFO    :b'Device Annoucement: NwkId: d6a9 Ieee: 84b4dbfffe0bca7a MacCap: 8e'
2023-11-06 22:31:30,097 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device d6a9'
2023-11-06 22:31:31,066 ERROR   : [       MainThread] [6] NEW OBJECT: 46e4 Not able to get all needed attributes on time
2023-11-06 22:31:31,070 ERROR   : [       MainThread] processNotinDB - not able to find response from 46e4 stop process at 0045
2023-11-06 22:31:31,076 ERROR   : [       MainThread] processNotinDB - Collected Infos are : {'Version': '3', 'ZDeviceName': '', 'Status': 'UNKNOW', 'SQN': '', 'Ep': {}, 'Heartbeat': '1', 'RIA': '6', 'LQI': {}, 'Battery': {}, 'Model': '', 'ForceAckCommands': [], 'MacCapa': '8e', 'IEEE': '84b4dbfffe0bc8f9', 'Type': {}, 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '', 'Attributes List': {}, 'DeviceType': 'FFD', 'HW Version': '', 'Last Cmds': [], 'LogicalType': 'Router', 'Manufacturer': '', 'Manufacturer Name': '', 'NbEp': '', 'PowerSource': 'Main', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'time': 1699306289.0809712, 'Time': '2023-11-06 22:31:29', 'MsgType': '  4d', 'LastSeen': 1699306289}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Full-Function Device', 'Main Powered', 'Receiver during Idle', 'Standard security', 'NwkAddr should be allocated'], 'ZDPSQN': '07', 'PairingInProgress': True, 'ConsistencyCheck': 'Bad Pairing'}
2023-11-06 22:31:34,092 INFO    :b'Device Annoucement: NwkId: 46e4 Ieee: 84b4dbfffe0bc8f9 MacCap: 8e'
2023-11-06 22:31:34,096 INFO    :b'Forcing a check of configure reporting after Device Annoucement on Main Powered device 46e4'
2023-11-06 22:31:35,0

Any help is appriciated

Thx !

[dude]

Update;
Not manged to get this done in Domoticz.
Installed home assistant. Worked there without a problem. Pity i couldn't get this working no I have a split of devices in Domticz and HA

F.

[waltervl]

I think @pipiche missed this issue as it should not be an issue.

From your original log it does not seems to be a plugin issue.
Do you now have 2 sticks or are both programs, Domoticz and HA listen to the same zigbee USB stick?

[pipiche]

@dude I could have missed that one, but the information you are providing are not enough to get analysed.
It looks like the device is not providing enough information and so the discovery doesn't go through.

Do you have a way to send me that particular device, so I can make it working.

For your information the Zigbee4Domoticz plugin use the same zigpy radio libarry foundation as ZHA , so I don't see why it is not working

[dude]

Thanks for your reaction

@waltervl No I have one stick, i'm orginaly a domoticz user for a long time so tried to make it working. As I get stuck on this I installed HA on a seperate Rasp, with the zigbee plugin there. I moved my stick to the HA installation and was able to add the 6 eco-dimmers without problem.
@pipiche, off cours i can send a device, but I wonder if this is the issue. I can switch back with the stick to domoticz, and delivery you additional error logs if you wish.

G

[pipiche]

The error log won't be enough, as we would need to sniff the Zigbee radio to understand what is happening.

Let me clarify something

what ever device is, the 1st one paired work very well, and then you are not able to pair any other ?
If you invert the device and restart , you'll still be able to pair the first one and not the others ?

If that is the case, this is even worst, and only sniffing would help.
And last it would mean that I need two of those devices and not only one !

[dude]

@pipiche,

thx for the clarifacion.

"If you invert the device and restart , you'll still be able to pair the first one and not the others ? "

this is exactly the case.

Let me think if i can send you two devices, because the are physically installed now. I come back to you
G.

[pipiche]

Do you have a sonoff P or E


Envoyé de mon iPhone en utilisant Tapatalk

[keros]

Lets say you tried the thing with this order : n°1, n°2, n°3. n°1 is working and not n°2 and n°3.

Can you erase all the device from DomoticZ and the plugin and try pairing with another order : n°2, n°3, n°1 (make a plugin reboot between each pairing).

If it doesn't work, redo the erase and make the first pairing order n°1, n°2, n°3.

[dude]

@pipiche

I got a sonoff dongle plus E stick

G

[pipiche]

can you check the following

from the WebUI > Settings > Advanced --> "Disable direct pairing on Coordinator", so enable this parameter

Restart the plugin, and then try to pair a 2nd "Eco-dim.07".

Make sure that the 2nd Zigbee network is powered off, so we don't have any inter-action