So I checked node 10 (a window) and status was reported to Homey. For me it looks like that a node 14 is availabe, but will not be shown in the DevTools and also not in Martijn’s map.
Is there a easy way to get some info of node 14, (the name of the node would be great).
@Sharkys, thanks for your feedback.
I have called up the code and it shows me the same result as in the map. Node 14 is not listed as a node in the list.
But I saw also that node 14 is “neighbour” of several nodes.
Would it be possible to create a script that queries node 14 for the name or its capabilites?
Neighbour are end devices and routers.
I tried yesterday a power cut for 30 minutes of Homey, but with the same result.
Can it be a ghost node if the status of the window (node 10) is reported to Homey?
It could be, yes. Ghost nodes are already several times discussed in the forum.
These ghost nodes are usually not displayed in Developer Tools → Devices, but maybe you could search for it there.
However, my suggestion is to contact the support.
Hi Dirk,
I searched also for this topic, and found several discussions, but not a solution.
No, my ghost node (14) is not visible in DevTools/Devices.
Yes, I’ll contact support. I thought that it’s easier to identify the ghost node by name. Then fixing the problem would be easy.
What can we do with / learn from the pictures that the script generates?
When visualizing, we can see that there may be some strange looking journeys that some of the information seems to pass, given the relative proximity of the devices, but as far as I know we can’t force / encourage homey to optimize the routes can we?
several blobs, unwieldly splayed apart like a firework.
