C7 "created unknown zigbee device" actually did not create anything Bug?

🛎️ Get Help Devices
1

2/7/23 this keeps happening. My orginal post got zero exposure. I'd like to know if anyone else has seen this? Why does the log indicate inaccurate information?
C7 on 2.3.4.110 with tons of zigbee repeaters and sitting 2 feet from hub.
This has happened with several devices, including officially supported devices, Eria Dimmer, Sylvania Dimmer Switch, Iris Keypad V3, etc.

@gopher.ny
@mike.maxwell
Paired my sonoff zigbee dongle, finally. It immediately fell off and each time I try to rejoin it I see these unknown zigbee devices and the hub is saying "created unknown zigbee device" but nothing is visible in my devices page. I don't see any of these 64 bit addresses in my C7, nor in any of my hubs, and neither of the addresses match the 64 bit of the dongle.

Summary

sys:12022-04-04 01:11:52.229 pm Zigbee Discovery Running

sys:12022-04-04 01:10:58.542 pm Created Unknown Zigbee Device

sys:12022-04-04 01:10:52.225 pm Zigbee Discovery Stopped

dev:1942022-04-04 01:10:44.225 pm infoManufacturer Name Received

dev:1732022-04-04 01:10:33.934 pm infoApplication ID Received

dev:1362022-04-04 01:10:20.632 pm infoLED Porch Flex colorTemperature is 2801°K

dev:2022022-04-04 01:10:09.230 pm infoApplication ID Received

sys:12022-04-04 01:09:55.509 pm Initializing Zigbee Device 000D6F0001071B9A, 5F30

sys:12022-04-04 01:09:52.219 pm Zigbee Discovery Running

dev:312022-04-04 01:09:29.391 pm infoQubino 2 Patio Spots/Sconces power is 1.3W

dev:362022-04-04 01:09:24.116 pm infoManufacturer Name Received

dev:8302022-04-04 01:09:15.821 pm infoDoor Slider🚪 is inactive

dev:2262022-04-04 01:09:12.614 pm infoDoor Driveway :door: temperature is 51.80°F

dev:8302022-04-04 01:09:05.840 pm infoDoor Slider🚪 is [x:74,y:1029,z:-15]

sys:12022-04-04 01:08:52.703 pm Created Unknown Zigbee Device

sys:12022-04-04 01:08:52.224 pm Zigbee Discovery Stopped

sys:12022-04-04 01:08:36.306 pm Created Unknown Zigbee Device

dev:7962022-04-04 01:08:18.255 pm infoMotion 2nd Floor Hue illuminance is 13 Lux

dev:10362022-04-04 01:08:07.957 pm infoAlarm Keypad XHK tamper is clear

dev:10362022-04-04 01:08:06.220 pm debugdescMap: [raw:catchall: 0104 0501 01 01 0040 00 B859 01 00 0000 07 00 , profileId:0104, clusterId:0501, clusterInt:1281, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:B859, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]

dev:10362022-04-04 01:08:06.005 pm infoskipped: [raw:catchall: 0000 0013 00 00 0040 00 B859 00 00 0000 00 00 A559B870C98513006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B859, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A5, 59, B8, 70, C9, 85, 13, 00, 6F, 0D, 00, 80]], description:catchall: 0000 0013 00 00 0040 00 B859 00 00 0000 00 00 A559B870C98513006F0D0080

dev:10362022-04-04 01:08:06.002 pm debugdescMap: [raw:catchall: 0000 0013 00 00 0040 00 B859 00 00 0000 00 00 A559B870C98513006F0D0080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B859, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A5, 59, B8, 70, C9, 85, 13, 00, 6F, 0D, 00, 80]]

dev:1012022-04-04 01:08:05.545 pm warnDID NOT PARSE MESSAGE for description : catchall: 0000 8038 00 00 0040 00 9C9D 00 00 0000 00 00 000000F8FF071E00080010CBD8B5C8C4A7BEABA7B1ABACC1BDC3D2

dev:3152022-04-04 01:07:59.897 pm infoLight By Furnace was turned off

dev:10362022-04-04 01:07:54.166 pm infoAlarm Keypad XHK battery is 100%

dev:10362022-04-04 01:07:54.165 pm debuggetBatteryResult: 61

dev:10362022-04-04 01:07:54.162 pm debugdescMap: [raw:B859010001082000203D, dni:B859, endpoint:01, cluster:0001, size:08, attrId:0020, encoding:20, command:0A, value:3D, clusterInt:1, attrInt:32]

sys:12022-04-04 01:07:52.219 pm Zigbee Discovery Running

sys:12022-04-04 01:07:52.204 pm Zigbee Discovery Stopped

sys:12022-04-04 01:07:49.671 pm Initializing Zigbee Device 000D6F0001071B9A, 6785

dev:6352022-04-04 01:07:48.193 pm debugFan Light Addition: MeterReport(scale: 0, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: [0, 0, 0, 0], meterType: 1, precision: 3, size: 4, meterValue: [0, 0, 27, 146])

dev:6352022-04-04 01:07:47.677 pm debugFan Light Addition: MeterReport(scale: 2, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: [], meterType: 1, precision: 1, size: 4, meterValue: [0, 0, 0, 8])

dev:1732022-04-04 01:07:45.329 pm infoApplication ID Received

sys:12022-04-04 01:07:33.274 pm Initializing Zigbee Device 000D6F000106C40C, A24D

2

This happened to me once a long time ago. And was fixed by a powerdown and reboot.

2 Likes
3

Thanks Aaiyar. So any idea where the "unknown device" goes? I want to be sure I'm not creating issues down the road with the zigbee table

1 Like
4

No idea. Other than that zigbee is way more resilient to z-wave in this particular matter.

2 Likes
5

Never got a real answer, 1+ years later.
I wonder if @support_team has any idea or is even aware?

6

The join isnt completing, there isnt a way to say why without running a sniffer during the failed join.

1 Like
7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.