search

Xeroxxx / tplink-energy-monitor

An energy monitoring dashboard for TP-Link smart plugs - Forked from https://github.com/jamesbarnett91/tplink-energy-monitor
GNU General Public License v3.0
21 stars 7 forks source link

TP-Link HS110 not being detected #24

Open andrewmooreio opened 3 years ago

andrewmooreio commented 3 years ago

I have 3 HS110 plugs, 2 are detected by the application and 1 is not. All plugs are on the same network. I'm running the packaged executable on CentOS 7.

Plugs that are detected: Plug 1 Hardware Version: 2.1 Firmware Version: 1.5.10

Plug 2 Hardware Version: 4.1 Firmware Version: 1.0.4

Plug that isn't detected: Plug 3 Hardware Version: 4.1 Firmware Version: 1.1.0

I've performed a factory reset on plug 3 with no change in behaviour.

Any assistance would be appreciated.

Xeroxxx commented 3 years ago

Hello @andrewmooreio, which branch are you using? ARM or x86/x64?

Maybe firmware related. I will check dependencies.

diegopereiran commented 3 years ago

I am having the same issue as @andrewmooreio. My HS110 versions are as follow:

Hardware Version: 4.0 Firmware Version: 1.0.5

I am using tag 1.0.0 on Docker and this is the execution log:

today at 08:03
today at 08:03 > tplink-monitor@1.0.0 start today at 08:03 > node ./src/app.js today at 08:03
today at 08:03 Logger config file: "logger-config.json" today at 08:03 Log directory path: "/opt/tplink-monitor/data" today at 08:03 Starting discovery on interface: 10.0.0.135 today at 08:03 Starting discovery on interface: 172.17.0.1 today at 08:04 GET / 200 69.389 ms - 4608 today at 08:04 GET /stylesheets/style.css 200 12.085 ms - 1997 today at 08:04 GET /favicon.ico 302 7.037 ms - 23 today at 08:04 GET / 304 8.429 ms - - today at 08:04 GET / 304 73.240 ms - - today at 08:04 GET /stylesheets/style.css 304 26.166 ms - - today at 08:04 GET /favicon.ico 302 3.961 ms - 23 today at 08:04 GET / 304 15.956 ms - - today at 08:04 GET /settings 200 32.512 ms - 5448 today at 08:04 GET /stylesheets/style.css 304 1.141 ms - - today at 08:04 GET /favicon.ico 302 0.840 ms - 23 today at 08:04 GET / 304 6.341 ms - - today at 08:05 GET / 304 51.320 ms - - today at 08:05 GET /stylesheets/style.css 304 1.235 ms - - today at 08:05 GET /favicon.ico 302 0.829 ms - 23 today at 08:05 GET / 304 5.949 ms - - today at 08:05 GET / 304 3.697 ms - - today at 08:05 GET /stylesheets/style.css 304 0.521 ms - - today at 08:05 GET /favicon.ico 302 0.816 ms - 23 today at 08:05 GET / 304 6.550 ms - - today at 08:05 GET / 304 6.550 ms - -

The HS110 is running on IP 10.0.0.7.

Xeroxxx commented 3 years ago

Hello @diegopereiran, we're on it. Currently developing next version.

Checkout dev-2.0 branch or latest dev-branch.

Does this happen there aswell?

frostinel commented 3 years ago

I have the new KP115 model and none are appearing in the list. I have 4 of them. Hardware 1.0 Firmware 1.0.7 It also does not detect a HS110 but does detect another one with the same config: Hardware 2.1 Firmware 1.5.7

It detects HS110 Hardware 4.1 Software 1.0.4 It also detects HS110 with: Hardware 2.1 Software 1.5.10

frostinel commented 3 years ago

I have the new KP115 model and none are appearing in the list. I have 4 of them. Hardware 1.0 Firmware 1.0.7 It also does not detect a HS110 but does detect another one with the same config: Hardware 2.1 Firmware 1.5.7

It detects HS110 Hardware 4.1 Software 1.0.4 It also detects HS110 with: Hardware 2.1 Software 1.5.10

OK, so I updated every single one of them and they now all appear. Everyone, make sure you have applied the latest updates and then restart the docker :D

frostinel commented 3 years ago

I have 3 HS110 plugs, 2 are detected by the application and 1 is not. All plugs are on the same network. I'm running the packaged executable on CentOS 7.

Plugs that are detected: Plug 1 Hardware Version: 2.1 Firmware Version: 1.5.10

Plug 2 Hardware Version: 4.1 Firmware Version: 1.0.4

Plug that isn't detected: Plug 3 Hardware Version: 4.1 Firmware Version: 1.1.0

I've performed a factory reset on plug 3 with no change in behaviour.

Any assistance would be appreciated.

Are you sure the hardware 4.1 is 1.1.0? Both of mine fully updated firmware go up to 1.0.4

frostinel commented 3 years ago

I now see the container crashed in Synology docker and only 4 out of 8 devices are displayed

frostinel commented 3 years ago

It also looks that the logs are one hour behind. It could be a reason to the connections not being there

Xeroxxx commented 3 years ago

Do have this issue with dev-2.0 branch or latest? We know that 'latest' is crashing from time to time on Synology.

frostinel commented 3 years ago

Do have this issue with dev-2.0 branch or latest? We know that 'latest' is crashing from time to time on Synology.

It is dev 2.0

Now it is showing 6 out of 8 devices