search

jamesbarnett91 / tplink-energy-monitor

An energy monitoring dashboard for TP-Link smart plugs
GNU General Public License v3.0
467 stars 104 forks source link

Avoid initial scan #60

Open jmllamasg opened 4 years ago

jmllamasg commented 4 years ago

Hi everyone. The title is very meaningful. I'd like to jump the initial scan, and start using a plug with a specific IP. The problem: I'm accessing to my home LAN through a VPN client. The software runs into the client, but it doesn't detect the plug because the client VPN LAN is different from the remote LAN. I think the solution might be something like "npm start IP_plug". If I ping the plug from the client VPN LAN, it works perfectly. Therefore, there is communication between both sides of the VPN. Any idea?

DutchFlander commented 4 years ago

Hi,

Your issue is somewhat related to mine (https://github.com/jamesbarnett91/tplink-energy-monitor/issues/58) I have the same problem that it seems, the scan is running on the first interface only in the list. I assume, your VPN connection is also not the main one, therefor it is skipped.

Hopefully we will have a solution to this :)

Turbobussi commented 3 years ago

Also here need to add manually monitoring ip devices.