Full reset zigate, what to know

[ronaldbro]

Hi,

I'm having trouble adding new devices to zigate. I tried to add two xiaomi power plugs and a Gelopto LED dimmer but they all fail. See log below.
I had the same problem last week with some tradfri bulbs, but solved it after removing some devices. Went from 46 devices back to 31.

The trouble started after switching from stable to beta and back multiple times which resulted in some lost devices. (Pipiche already explained me that it was better not to do that.) I think the zigate hardware has some paired devices not known by zigate, so I want to do a full reset. Erase all the paired devices from the hardware and start over.

If I do that, do I need to remove the devices from Domoticz first or will it be mapped to the same device after pairing the clean zigate again?

Code: Select all

 2019-11-14 20:36:27.269 Status: (Zigate) Device Announced ShortAddr: d7dc, IEEE: 00124b001d43d2b3
2019-11-14 20:36:40.888 Status: (Zigate) [0] NEW OBJECT: d7dc TimeOut in 0045 restarting at 0x004d
2019-11-14 20:36:55.883 Status: (Zigate) [1] NEW OBJECT: d7dc TimeOut in 0045 restarting at 0x004d
2019-11-14 20:37:10.878 Status: (Zigate) [2] NEW OBJECT: d7dc TimeOut in 0045 restarting at 0x004d
2019-11-14 20:37:29.551 Status: (Zigate) [3] NEW OBJECT: d7dc TimeOut in 0045 restarting at 0x004d
2019-11-14 20:37:47.537 Status: (Zigate) [4] NEW OBJECT: d7dc TimeOut in 0045 restarting at 0x004d
2019-11-14 20:37:52.539 Error: (Zigate) [5] NEW OBJECT: d7dc Not able to get all needed attributes on time
2019-11-14 20:37:52.539 Error: (Zigate) processNotinDB - not able to find response from d7dc stop process at 0045
2019-11-14 20:37:52.540 Error: (Zigate) processNotinDB - RIA: 5 waitForDomoDeviceCreation: False, capturePairingInfos: 0 Model: {}
2019-11-14 20:37:52.540 Error: (Zigate) processNotinDB - Collected Infos are : {'SQN': '', 'Heartbeat': '1', 'Ep': {}, 'ConsistencyCheck': 'Bad Pairing', 'Status': 'UNKNOW', 'PowerSource': '', 'ZDeviceName': '', 'Model': {}, 'Capability': ['Full-Function Device', 'Main Powered', 'Receiver during Idle', 'Standard security', 'NwkAddr should be allocated'], 'Stack Version': '', 'Attributes List': {}, 'App Version': '', 'Announced': 1573760187.2695537, 'Stamp': {'LastSeen': 1573760187, 'Time': '2019-11-14 20:37:47', 'MsgType': '8702'}, 'NbEp': '', 'ReceiveOnIdle': '', 'RIA': '5', 'HW Version': '', 'Last Cmds': [(1573760267.5396159, '0100', None), (1573760267.65652, '0100', None), (1573760267.759993, '0100', None), (1573760267.8633986, '0100', None), (1573760267.966667, '0100', None)], 'Type': {}, 'ZCL Version': '', 'Health': 'Live', 'IEEE': '00124b001d43d2b3', 'MacCapa': '8e', 'LogicalType': '', 'ZDeviceID': {}, 'Version': '3', 'Manufacturer Name': '', 'ReadAttributes': {'TimeStamps': {'06-0000': 1573760267, '09-0000': 1573760267, '03-0000': 1573760267, '02-0000': 1573760267, '01-0000': 1573760267}, 'Ep': {'09': {'0000': {}}, '06': {'0000': {}}, '03': {'0000': {}}, '01': {'0000': {}}, '02': {'0000': {}}}}, 'DeviceType': '', 'Battery': {}, 'RSSI': {}, 'Manufacturer': '', 'ProfileID': {}}

[pipiche]

The message you have paste, could indeed be related to a full zigate . It is unfortunate that the Zigate is not able to provide a clear status on the Max level

The way I would do it in order to limit lost of information is to only do an ErasePDM of the Zigate. In such you'll reset it.

Then I'll put the Zigate in Pairing mode, and will pair device by device

the plugin will then reconnect the new paired device with the existing information in plugin DB and Domoticz DB

[ronaldbro]

Thanks Pipiche, I will try that.
If I understand correctly then I need to check the eraseZigatePDM checkbox at the advance settings and then an erase on the admin page. Correct?

[pipiche]

For now, you can simply go into teh Hardware page, and put ErasePDM to True (this will short-cut the Web Admin Stuff ).
Please put it back to False after the restart

[ronaldbro]

Thanks for the advice Pipiche, it worked perfectly.

I could bind all devices again and they were mapped to the old domoticz devices.

I notices the setting 'allowRemoveZigateDevice', it was off. I guess that's the reason Zigate stayed full although I removed a lot of devices. It would be an improvement in the log when a device is deleted to add text if it is also deleted from Zigate or not. This would make it more clear. I think I also removed some devices in the past which I don't own anymore which were still in the Zigate memory.
It would also be an improvement to keep all devices in a data file and add an option in the web GUI to remove them from Zigate. At this moment I don't think it's possible to delete a device from zigate when it's already deleted from domoticz and when it's not possible to rebind. For example when I device is broken, return to shop or given away.

[pipiche]

Thanks for the advice Pipiche, it worked perfectly.

I could bind all devices again and they were mapped to the old domoticz devices.

Great !

I notices the setting 'allowRemoveZigateDevice', it was off. I guess that's the reason Zigate stayed full although I removed a lot of devices.

Yes and not. For instance for battery based device, there is no real way to do the removal, except if the device has a way to send a Leave message.

It would be an improvement in the log when a device is deleted to add text if it is also deleted from Zigate or not. This would make it more clear. I think I also removed some devices in the past which I don't own anymore which were still in the Zigate memory.

At that point of time, it is hard to know the completness of the removal, as the pugin cannot query the Zigate on those matters.

It would also be an improvement to keep all devices in a data file and add an option in the web GUI to remove them from Zigate. At this moment I don't think it's possible to delete a device from zigate when it's already deleted from domoticz and when it's not possible to rebind. For example when I device is broken, return to shop or given away.

As of today in beta branch, any devices which are not present on Domoticz, can be removed. So if at start time, the plugin detect an inconsitency between its database and the domoticz one, the device is tagged and you have a trash icon.
There is the same thing happening if a pairing is not successful, then the entry created in plugin Db can be removed.
Last as said before, the plugin cannot know the list of devices known by the Zigate. This is a current limitation - as of plugin don't know if the Zigate is at max number of devices -, so no way to cross-check

[ronaldbro]

Thanks for the explanation Pipiche, I hope you get a way to query the zigate devicelist in the next firmware. This would make zigate more predictable.

In the meantime an extra hint in the log based on the AllowRemoveZigateDevice setting would be helpfull.

[bertbigb]

Hi,

I hope someone can help me because I did something stupid.
It started that I couldn't pair a few of my devices with Zigate.
And then I removed the Zigate plugin from the hardware and when I looked at the domoticz devices I saw some leftovers and deleted them from the Domoticz devices.
Then I reinstalled the plugin - restarted Domoticz - Add the Zigate hardware - did a Erase of Persistent data - rebooted Domoticz again.
And now I'm not able to pair the previous devices to Zigate and get them back in the Domoticz devices.

So never connected hardware I can get into Domoticz, but previous connected hardware I can't

Can someone advise me what to do?

[pipiche]

Hi,

I hope someone can help me because I did something stupid.
It started that I couldn't pair a few of my devices with Zigate.
And then I removed the Zigate plugin from the hardware and when I looked at the domoticz devices I saw some leftovers and deleted them from the Domoticz devices.
Then I reinstalled the plugin - restarted Domoticz - Add the Zigate hardware - did a Erase of Persistent data - rebooted Domoticz again.
And now I'm not able to pair the previous devices to Zigate and get them back in the Domoticz devices.

So never connected hardware I can get into Domoticz, but previous connected hardware I can't

Can someone advise me what to do?

It would have great to see what the Logs said when trying to pair the already paired devices ?
I suspect that the plugin complains about inconsistency ( as the devices are known by Domoticz but not by the plugin ). --> If that is the case, you must remove the Widgets from Domoticz first and then you'll be able to pair the device again

If that is still (or it is not that case), please provide:

- the log (from Domoticz)
- the file Data/DeviceList-xx.txt ( you might have now several of them as xx stands for the HardwarId (of the plugin in Domoticz), so check what is the hardwareId in the Hardware list .

[bertbigb]

Hi Pipiche,

First all thanks for offering help.
This is the Domoticz log, I have deleted the parts from dzVents

2019-12-02 20:22:12.764 Error: (ZiGate) Decode8102 - Receiving a message from unknown device : a292 with Data : 2ba29201040600000018000101
2019-12-02 20:22:20.076 Error: (ZiGate) Decode8102 - Receiving a message from unknown device : a292 with Data : 2ca2920104000000002100020000
2019-12-02 20:22:20.077 Error: (ZiGate) Decode8102 - Receiving a message from unknown device : a292 with Data : 2da29201040600000018000101
2019-12-02 20:22:35.424 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0045/071b (0)
2019-12-02 20:22:37.189 (ZiGate) Request a Bind for 071b/01 on Cluster 0406
2019-12-02 20:22:37.189 (ZiGate) Request a Bind for 071b/01 on Cluster 0400
2019-12-02 20:22:37.189 (ZiGate) Request a Bind for 071b/01 on Cluster 0000
2019-12-02 20:22:41.429 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Lux-00158d00035fea9f-01) 0:0
2019-12-02 20:22:41.431 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0043/071b01 (0)
2019-12-02 20:22:41.483 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:22:47.052 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0043/071b01 (1)
2019-12-02 20:22:47.054 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:22:47.059 (ZiGate) Decode8043 - Overwrite ProfileID {} with 0104 from Ep: 01
2019-12-02 20:22:47.060 (ZiGate) Decode8043 - Overwrite ZDeviceID {} with 0104 from Ep: 01
2019-12-02 20:22:47.060 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 5: 0500 (IAS Zone)
2019-12-02 20:22:47.060 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 6: 0001 (Power Configuration)
2019-12-02 20:22:47.060 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 7: 0003 (Identify)
2019-12-02 20:22:47.061 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster OUT Count: 02
2019-12-02 20:22:47.061 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster Out 1: 0000 (Basic)
2019-12-02 20:22:47.061 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster Out 2: 0019 (Over-the-Air Upgrade)
2019-12-02 20:22:53.233 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b Simple Descriptor EP 01
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b ProfileID 0104
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b ZDeviceID 0107
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster IN Count: 07
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 1: 0000 (Basic)
2019-12-02 20:22:53.238 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 2: ffff
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 3: 0406 (Occupancy Sensing)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 4: 0400 (Illuminance Measurement)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 5: 0500 (IAS Zone)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 6: 0001 (Power Configuration)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster In 7: 0003 (Identify)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster OUT Count: 02
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster Out 1: 0000 (Basic)
2019-12-02 20:22:53.239 Status: (ZiGate) [-] NEW OBJECT: 071b Cluster Out 2: 0019 (Over-the-Air Upgrade)

dzVentz

2019-12-02 20:23:07.129 Status: (ZiGate) Device Annoucement ShortAddr: 136c, IEEE: 00158d00014dbafb
2019-12-02 20:23:14.371 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:23:17.179 Status: (ZiGate) [0] NEW OBJECT: 136c TimeOut in 0045 restarting at 0x004d
2019-12-02 20:23:17.179 Status: (ZiGate) [0] NEW OBJECT: 136c Request Model Name
2019-12-02 20:23:32.436 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:23:32.223 Status: (ZiGate) [1] NEW OBJECT: 136c TimeOut in 0045 restarting at 0x004d
2019-12-02 20:23:32.223 Status: (ZiGate) [1] NEW OBJECT: 136c Request Model Name
2019-12-02 20:23:38.010 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:23:47.183 Status: (ZiGate) [2] NEW OBJECT: 136c TimeOut in 0045 restarting at 0x004d
2019-12-02 20:23:47.183 Status: (ZiGate) [2] NEW OBJECT: 136c Request Model Name
2019-12-02 20:23:55.024 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Lux-00158d00035fea9f-01) 8:8
2019-12-02 20:23:55.029 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:24:00.295 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Lux-00158d00035fea9f-01) 0:0
2019-12-02 20:24:00.300 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On

dzVents part

adding an Xiaomi motion sensor

2019-12-02 20:24:02.208 Status: (ZiGate) [3] NEW OBJECT: 136c TimeOut in 0045 restarting at 0x004d
2019-12-02 20:24:02.208 Status: (ZiGate) [3] NEW OBJECT: 136c Request Model Name
2019-12-02 20:24:17.219 Status: (ZiGate) [4] NEW OBJECT: 136c TimeOut in 0045 restarting at 0x004d
2019-12-02 20:24:17.220 Status: (ZiGate) [4] NEW OBJECT: 136c Request Model Name
2019-12-02 20:24:18.544 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:24:22.205 (ZiGate) processNotinDB - not able to find response from 136c stop process at 0045
2019-12-02 20:24:22.205 (ZiGate) processNotinDB - RIA: 5 waitForDomoDeviceCreation: False, capturePairingInfos: 0 Model: {}
2019-12-02 20:24:22.205 (ZiGate) processNotinDB - Collected Infos are : {'Version': '3', 'ZDeviceName': '', 'Status': 'UNKNOW', 'SQN': '', 'Ep': {}, 'Heartbeat': '1', 'RIA': '5', 'RSSI': {}, 'Battery': {}, 'Model': {}, 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': {}, 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [(1575314657.2214158, '0100', None), (1575314657.326824, '0100', None), (1575314657.4298234, '0100', None), (1575314657.5327117, '0100', None), (1575314657.6357899, '0100', None)], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {'Ep': {'01': {'0000': {}}, '02': {'0000': {}}, '03': {'0000': {}}, '06': {'0000': {}}, '09': {'0000': {}}}, 'TimeStamps': {'01-0000': 1575314657, '02-0000': 1575314657, '03-0000': 1575314657, '06-0000': 1575314657, '09-0000': 1575314657}}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:17', 'MsgType': '8702'}, 'ZCL Version': '', 'Health': '', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'APS Failure': [(1575314642.4194036, 'd4'), (1575314642.521013, 'd4'), (1575314657.3279798, 'd4'), (1575314657.4309042, 'd4'), (1575314657.533908, 'd4')]}
2019-12-02 20:24:22.204 Status: (ZiGate) [5] NEW OBJECT: 136c Not able to get all needed attributes on time
2019-12-02 20:24:23.968 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:24:30.038 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:24:50.251 (ZiGate) Decode004d - self.IEEE2NWK[MsgIEEE] = 136c
2019-12-02 20:24:50.251 Status: (ZiGate) Device Annoucement ShortAddr: db96, IEEE: 00158d00014dbafb
2019-12-02 20:24:51.020 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On

Adding an object what I deleted from Domoticz Database before (the stupid mistake)

2019-12-02 20:24:52.227 Status: (ZiGate) [0] NEW OBJECT: db96 Model Name: lumi.sensor_magnet
2019-12-02 20:24:52.228 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '1', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:50', 'MsgType': '8102', 'LastSeen': 1575314690}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': '01', 'Type': 'Door', '0000': {}}}}
2019-12-02 20:24:52.228 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.
2019-12-02 20:24:57.092 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0045/db96 (0)

2019-12-02 20:24:57.193 Status: (ZiGate) [0] NEW OBJECT: db96 Model Name: lumi.sensor_magnet
2019-12-02 20:24:57.194 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '2', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:50', 'MsgType': '8102', 'LastSeen': 1575314690}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': '01', 'Type': 'Door', '0000': {}}}}
2019-12-02 20:24:57.194 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.

dzVents

2019-12-02 20:25:01.109 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0045/db96 (1)
2019-12-02 20:25:02.212 Status: (ZiGate) [0] NEW OBJECT: db96 Model Name: lumi.sensor_magnet
2019-12-02 20:25:02.517 Status: (ZiGate) (136c/00158d00014dbafb) send a Leave indication and will be outside of the network
2019-12-02 20:25:02.213 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '3', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:58', 'MsgType': '8702', 'LastSeen': 1575314690}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': '01', 'Type': 'Door', '0000': {}}}, 'APS Failure': [(1575314698.249762, 'f0')]}
2019-12-02 20:25:02.213 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.

2019-12-02 20:25:04.674 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:25:05.178 (ZiGate) Decode004d - self.IEEE2NWK[MsgIEEE] = db96
2019-12-02 20:25:05.178 Status: (ZiGate) Device Annoucement ShortAddr: 58ad, IEEE: 00158d00014dbafb

2019-12-02 20:25:07.192 Status: (ZiGate) [0] NEW OBJECT: db96 Model Name: lumi.sensor_magnet
2019-12-02 20:25:07.193 Status: (ZiGate) [0] NEW OBJECT: 58ad Model Name: lumi.sensor_magnet
2019-12-02 20:25:07.193 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '4', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:58', 'MsgType': '8702', 'LastSeen': 1575314690}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': '01', 'Type': 'Door', '0000': {}}}, 'APS Failure': [(1575314698.249762, 'f0')]}
2019-12-02 20:25:07.193 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.

2019-12-02 20:25:07.194 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '1', 'RIA': '0', 'RSSI': 120, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:25:05', 'MsgType': '8102', 'LastSeen': 1575314705}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': {}, 'Type': 'Door', '0000': {}}}}
2019-12-02 20:25:07.194 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.


And this repeats and repeats

2019-12-02 20:25:10.710 (ZiGate) checkTOwaitForStatus - Request a reTransmit of Command : 0045/58ad (0)
2019-12-02 20:25:11.665 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Lux-00158d00035fea9f-01) 4:4
2019-12-02 20:25:11.667 (ZiGate) UpdateDevice - (ZiGate - lumi.sensor_motion.aq2_Motion-00158d00035fea9f-01) 1:On
2019-12-02 20:25:12.221 Status: (ZiGate) [0] NEW OBJECT: db96 Model Name: lumi.sensor_magnet
2019-12-02 20:25:12.221 Status: (ZiGate) [0] NEW OBJECT: 58ad Model Name: lumi.sensor_magnet
2019-12-02 20:25:12.221 Error: (ZiGate) processNotinDBDevices - Devices already exist. Deur-Tuin with {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '5', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': '', 'ProfileID': {}, 'ZDeviceID': {}, 'App Version': '10', 'Attributes List': {}, 'DeviceType': '', 'HW Version': '', 'Last Cmds': [], 'LogicalType': '', 'Manufacturer': '', 'Maufacturer Name': '', 'NbEp': '', 'PowerSource': '', 'ReadAttributes': {}, 'ReceiveOnIdle': '', 'Stack Version': '', 'Stamp': {'Time': '2019-12-02 20:24:58', 'MsgType': '8702', 'LastSeen': 1575314690}, 'ZCL Version': '', 'Health': 'Live', 'Capability': ['Reduced-Function Device', 'Standard security', 'NwkAddr should be allocated'], 'ConfigSource': 'DeviceConf', 'Ep': {'01': {'0006': '01', 'Type': 'Door', '0000': {}}}, 'APS Failure': [(1575314698.249762, 'f0')]}
2019-12-02 20:25:12.221 Error: (ZiGate) processNotinDBDevices - Please cross check the consistency of the Domoticz and Plugin database.

You also asked also for the DeviceList, this is the content:

0000 : {'version': '3', 'IEEE': '00158d0001eda585', 'Ep': {'01': {'0004': {}, '0006': {}, '0008': {}}}, 'PowerSource': 'Main'}
071b : {'Version': '3', 'ZDeviceName': '', 'Status': 'inDB', 'SQN': '', 'Heartbeat': '52', 'RIA': '0', 'RSSI': 120, 'Battery': {}, 'Model': 'lumi.sensor_motion.aq2', 'MacCapa': '80', 'IEEE': '00158d00035fea9f', $
136c : {'Version': '3', 'ZDeviceName': '', 'Status': 'UNKNOW', 'SQN': '', 'Ep': {}, 'Heartbeat': '31', 'RIA': '5', 'RSSI': {}, 'Battery': {}, 'Model': {}, 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Type': {},$
db96 : {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '25', 'RIA': '0', 'RSSI': 123, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Typ$
58ad : {'Version': '3', 'ZDeviceName': '', 'Status': '0045', 'SQN': '', 'Heartbeat': '22', 'RIA': '0', 'RSSI': 120, 'Battery': {}, 'Model': 'lumi.sensor_magnet', 'MacCapa': '80', 'IEEE': '00158d00014dbafb', 'Typ$

You told me to remove the widgets from Domoticz first, but I do not understand what that is and how to do that.
I hope you can give me some guidance in this process.
And to not forget, thanks for your help

[bertbigb]

To be complete here is also the devicelist

DeviceList-9.txt

(4.44 KiB) Downloaded 80 times

[pipiche]

I think that you are on a very bad situation here is what I suggest :

-1 Remove the Hardware Zigate from Domoticz. It will remove all associated devices
-2 Stop Domoticz
-3 remove the files which are under Domoticz-Zigate/Data/*
-4 Start Domoticz
-5 Add Hardware Zigate. This will create a full new environment

Then you'll have to pair all the devices again

[bertbigb]

Hello Pipiche,

With your good help I have come out of my very bad situation.
After doing the steps you suggested I was able to pair new and previously connected devices again.
Many. many thanks.

[pipiche]

Great ....