Read the statement by Michael Teeuw here.
MMM-NetworkScanner
-
@ianperrin
Yup good work on getting the updates…MAC is working again, but the entries are all duplicated. ;)
-
@pugsly same here -.-
-
@Speedy-one said in MMM-NetworkScanner:
@pugsly same here -.-
I freshly install rather than update the module, and working flawlessly.
-
@slametps Deleted the module and did a fresh install, still showing duplicate entries.
-
@pugsly said in MMM-NetworkScanner:
@slametps Deleted the module and did a fresh install, still showing duplicate entries.
Lucky me. Btw, had you installed v0.0.1?
-
@slametps Yes i did, and that one worked fine using MAC. I have actually reverted back to that one, so I don’t get the ‘last seen’ message anymore.
-
Any chance of an enhancement to scan outside the local network mask? i’m not sure if that is a config option in arp-scan that isn’t surfaced?
I have my MM on ethernet in one subnet, but want to scan for MAC addresses in another subnet (my Wifi). or at least a broader CIDR range
-
Does anyone have issues with the “occupied” and “vacant” part working? I tried to set it up and test it but i have had no luck. I want the mirror to turn off when i leave and turn back on when i return. I love this idea but need a little help configuring it to work.
My config is below:
{ module: 'MMM-NetworkScanner', position: 'top_right', header: "Network Scanner", config: { devices: [ { macAddress: "lower case", name: "B Phone", icon: "mobile"}, { macAddress: "lower case", name: "B Work Phone", icon: "mobile"}, { macAddress: "lower case", name: "B Work Laptop", icon: "laptop"}, ], showUnknown: false, showOffline: true, keepAlive: 300, updateInterval: 10, showLastSeen: true, residents: "B Phone", occupiedCMD: {notification: 'REMOTE_ACTION', payload: {action: 'MONITORON'}}, vacantCMD : {notification: 'REMOTE_ACTION', payload: {action: 'MONITOROFF'}}, } },
-
I am also getting duplicates as well. Any help on this?
-
@bluedoors modify the js file to scan your subnets? If your subnets were 192.168.1.0/24 and 192.168.2.0/24 you could scan 192.168.1.0/23 to scan both subnets, right? Same gateway for both subnets?