Open harvindhillon opened 1 year ago
I agree but i dont knowing the coding things.
The unknown relay shall also being good to getting the IEEE so can see which device is it that ghosting around. Normally is it one sleeper that have being deleted in the system but was not getting the leave and not rejoining command so its have the network key and can communicating with the network or have migrating / importing the network its one device the system never have committing with. If have suspected device re power it so its doing one device accouterments and you is getting the IEEE and if the system is liking it its initiating it OK but can needing the network open for joining.
I suspect it was due to me moving my channel, might be some of the relays didnt migrate properly. I dont know which it is, I have around 65 routers and 150 devices overall, so its a pain to pin point which ones are the culprit. Everything seems to be working though, so it makes me more curious.
I think best is installing the https://github.com/mdeweerd/zha-network-card then you can see the lat seen and sorting and you can see if some devices is offline and can looking at them.
Actually prefer ZHA Toolkit, we can actually dump it in a csv file from service command :)
service: zha_toolkit.zha_devices data: csvlabel: ieee csvout: /config/csv/devices.csv
I is getting it now.
Logger: zigpy.application
Source: runner.py:188
First occurred: 15:58:53 (1 occurrences)
Last logged: 15:58:53
Unknown device AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x6FB6)
And i have debug activated and is getting :
2023-11-26 22:12:02.652 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received trustCenterJoinHandler: [0x6fb6, 00:17:88:01:04:a6:13:37, <EmberDeviceUpdate.STANDARD_SECURITY_UNSECURED_JOIN: 1>, <EmberJoinDecision.USE_PRECONFIGURED_KEY: 0>, 0xa983]
2023-11-26 22:12:02.653 DEBUG (MainThread) [bellows.zigbee.application] Received trustCenterJoinHandler frame with [0x6fb6, 00:17:88:01:04:a6:13:37, <EmberDeviceUpdate.STANDARD_SECURITY_UNSECURED_JOIN: 1>, <EmberJoinDecision.USE_PRECONFIGURED_KEY: 0>, 0xa983]
2023-11-26 22:12:02.653 INFO (MainThread) [zigpy.application] New device 0x6fb6 (00:17:88:01:04:a6:13:37) joined the network
And the IEEE is one old fried (Philip HUE light from one of my neighbors) that is trying joining late in the night after it was joining the network one time and i have trying deleting it so its loosing the network key. I was getting it working for nearly one year but was changing batteries in some remotes for 3 days ago and then it was joining the network agen so now i must sitting up after 22:00 for sending one leave without rejoining to it for getting it mot being in my production network
Possibility to increase detail in ERRORs to include NWK and IEEE of device. Example below for Device Didnt Respond ERROR
I do not have any information which device this is?
There are other examples where just NWK is present
Without IEEE since this is an unknown relay, the NWK is unregistered, I havent a clue which device is causing this error to be thrown