jamesbarnett91 / tplink-energy-monitor

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

No device found on debian server #58

Open DutchFlander opened 4 years ago

DutchFlander commented 4 years ago

Hi,

I have a debian server, which acts as my internet router, my internal network center, my cloud server, my openvpn server, tor client and many other thing. When I run the application on my win10 on the same network, I can see the data on the web-page on port 3000, but when I start it on my server, it cannot find the same device on the same network. I'm suspecting, it is looking on the first interface (eth0), which is my interface toward the internet and not on eth1, which is my whole internal LAN interface (192.168.2.X), where the win10 PC and the HS110 is located as well. Is there a way to determine which interface the tplink-monitor-linux application should look for my HS110? I would like to run this tool on my server 24/7, after all this is what servers are for :)

Thanks for your help and reply in advance! Dutch Flander

bobmorane06 commented 2 years ago

Did you find a fix? I'm in the exact same situation with an Ubuntu server that is my router.

I got it working using the npm install route and modifying services/device-manager.js as per probins suggestion in issue #68

https://github.com/jamesbarnett91/tplink-energy-monitor/issues/68#issuecomment-704153434