We have moved at community.getvera.com

Author Topic: New Plugin : NETMON - a network device monitor  (Read 3898 times)

Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #30 on: January 13, 2019, 07:31:19 pm »
For example, what does "temperature_goes_above" have to do with the online status of Network devices?

Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #31 on: January 13, 2019, 07:44:00 pm »
I can definitely use 'offline count goes beyond' as the trigger, if it will fire on anything above 0.
Thx

Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #32 on: January 13, 2019, 08:19:29 pm »
Here's a snapshot of what I'm referring to.

Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #33 on: January 16, 2019, 05:00:23 am »
Hi amg,
I made the changes to both the lua file and the service file and all works well for my requested notification variable.  I did not touch the notification tab.  Should I push these changes up to git-hub, or is there a better way to incorporate the code. Thx

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +209/-8
Re: New Plugin : NETMON - a network device monitor
« Reply #34 on: January 17, 2019, 08:09:14 am »
Hi amg,
I made the changes to both the lua file and the service file and all works well for my requested notification variable.  I did not touch the notification tab.  Should I push these changes up to git-hub, or is there a better way to incorporate the code. Thx
I ll check, thx

Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #35 on: January 20, 2019, 04:22:44 pm »
Thx for the commit amg.   8)

Offline Vera Plus user

  • Newbie
  • *
  • Posts: 19
  • Karma: +0/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #36 on: January 21, 2019, 02:03:25 pm »
After updating today to 0.5 I think it?s some problem. It doesn?t see any of my devices anymore.

Do I have to do any adjustment?

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +209/-8
Re: New Plugin : NETMON - a network device monitor
« Reply #37 on: January 21, 2019, 02:15:42 pm »
After updating today to 0.5 I think it?s some problem. It doesn?t see any of my devices anymore.

Do I have to do any adjustment?
No. Must be another issue. Enable debug mode and share the log please

Offline Vera Plus user

  • Newbie
  • *
  • Posts: 19
  • Karma: +0/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #38 on: January 22, 2019, 01:34:46 am »
You are right.

I have another problem with my Vera and when this was solved it was alwright again.

Thank you

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: New Plugin : NETMON - a network device monitor
« Reply #39 on: January 26, 2019, 09:07:03 am »
amg0,

It is possible to have a toggle somewhere to "INVERT" the detector.   I will prefer like AK to have the inverse that a detectesd device is tripped...
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline amg0

  • Beta Testers
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +209/-8
Re: New Plugin : NETMON - a network device monitor
« Reply #40 on: January 26, 2019, 11:23:19 am »
amg0,

It is possible to have a toggle somewhere to "INVERT" the detector.   I will prefer like AK to have the inverse that a detectesd device is tripped...

I added the inverted option in v0.7 in github. if you change status inverted property, you need to wait until the device is tested, or to force a refresh on the device ( test button ) before you get a coherent status

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: New Plugin : NETMON - a network device monitor
« Reply #41 on: January 26, 2019, 12:23:51 pm »
Just update the plugin and change the settings for Invert and when I "test" a device it give me the right answer BUT all my devices are still Untripped...
amg0,

It is possible to have a toggle somewhere to "INVERT" the detector.   I will prefer like AK to have the inverse that a detectesd device is tripped...

I added the inverted option in v0.7 in github. if you change status inverted property, you need to wait until the device is tested, or to force a refresh on the device ( test button ) before you get a coherent status
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline DesT

  • Sr. Member
  • ****
  • Posts: 364
  • Karma: +5/-1
Re: New Plugin : NETMON - a network device monitor
« Reply #42 on: January 26, 2019, 12:32:26 pm »
Ohhh I think I understand my problem.

I need to invert the "motion" status... not the "online/offline" status....
Vera Edge-UI7/Plus-UI7 (2), DSC Partition (5 ) + Zones Sensors(31), Nest thermostat (1) & Protect Fire/CO (3), GE Sw (8 ), GE Dimr (14), FGMS-001 (2), ZW100 (2), RZCS4 (1), AL-DSC11 (1), Aeon HEM 2nd Edition (1), Aeon SSE (5), YRD220-ZW (1), SONOS (6), MyQ Chamberlain (1)
PINE64/openLuup/ALTUI/Rules

Offline jvanhambelgium

  • Jr. Member
  • **
  • Posts: 56
  • Karma: +2/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #43 on: February 01, 2019, 04:24:05 pm »
Hi,
I don't have the impression that this plugin is working on my Veraplus / UI7 / latest FW
So I defined just 2 IP's to check, 1 if certainly online, the other not.
Still they are bot reported online and nothing really seems to happen ?
I'm just seeing the main Netmon-app/device, no "child" devices/sensors are visible in my GUI even after browser-reload (latest Chrome , Version 72.0.3626.81 (Official Build) (64-bit) on Ubuntu)
I've put on the debug-mode and captured some output, followed by 2 ping tests myself from the console.


50   02/01/19 21:54:47.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesStatus,[ { "name": "TV", "ipaddr": "172.29.45.17" }, { "name": "FAKE", "ipaddr": "172.29.45.18" } ],6432) <0x748d8520>
50   02/01/19 21:54:47.105   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesOfflineCount,0,6432) <0x748d8520>
50   02/01/19 21:54:47.105   luup_log:6432: NETMON: debug: programming next refreshDevices(6432) in 10 sec <0x748d8520>
50   02/01/19 21:54:57.100   luup_log:6432: NETMON: debug: refreshDevices(6432) <0x748d8520>
50   02/01/19 21:54:57.102   luup_log:6432: NETMON: debug: refreshOneDevice(6432,null) <0x748d8520>
50   02/01/19 21:54:57.102   luup_log:6432: NETMON: debug: getDevicesStatus(6432) <0x748d8520>
50   02/01/19 21:54:57.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesNotification,,6432) <0x748d8520>
50   02/01/19 21:54:57.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesStatus,[ { "name": "TV", "ipaddr": "172.29.45.17" }, { "name": "FAKE", "ipaddr": "172.29.45.18" } ],6432) <0x748d8520>
50   02/01/19 21:54:57.105   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesOfflineCount,0,6432) <0x748d8520>
50   02/01/19 21:54:57.105   luup_log:6432: NETMON: debug: programming next refreshDevices(6432) in 10 sec <0x748d8520>
50   02/01/19 21:55:07.100   luup_log:6432: NETMON: debug: refreshDevices(6432) <0x748d8520>
50   02/01/19 21:55:07.102   luup_log:6432: NETMON: debug: refreshOneDevice(6432,null) <0x748d8520>
50   02/01/19 21:55:07.102   luup_log:6432: NETMON: debug: getDevicesStatus(6432) <0x748d8520>
50   02/01/19 21:55:07.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesNotification,,6432) <0x748d8520>
50   02/01/19 21:55:07.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesStatus,[ { "name": "TV", "ipaddr": "172.29.45.17" }, { "name": "FAKE", "ipaddr": "172.29.45.18" } ],6432) <0x748d8520>
50   02/01/19 21:55:07.105   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesOfflineCount,0,6432) <0x748d8520>
50   02/01/19 21:55:07.105   luup_log:6432: NETMON: debug: programming next refreshDevices(6432) in 10 sec <0x748d8520>
50   02/01/19 21:55:17.100   luup_log:6432: NETMON: debug: refreshDevices(6432) <0x748d8520>
50   02/01/19 21:55:17.102   luup_log:6432: NETMON: debug: refreshOneDevice(6432,null) <0x748d8520>
50   02/01/19 21:55:17.102   luup_log:6432: NETMON: debug: getDevicesStatus(6432) <0x748d8520>
50   02/01/19 21:55:17.104   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesNotification,,6432) <0x748d8520>
50   02/01/19 21:55:17.105   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesStatus,[ { "name": "TV", "ipaddr": "172.29.45.17" }, { "name": "FAKE", "ipaddr": "172.29.45.18" } ],6432) <0x748d8520>
50   02/01/19 21:55:17.105   luup_log:6432: NETMON: debug: setVariableIfChanged(urn:upnp-org:serviceId:netmon1,DevicesOfflineCount,0,6432) <0x748d8520>
50   02/01/19 21:55:17.105   luup_log:6432: NETMON: debug: programming next refreshDevices(6432) in 10 sec <0x748d8520>
^C
root@MiOS_50160552:/tmp/log/cmh# ping 172.29.45.17
PING 172.29.45.17 (172.29.45.17) 56(84) bytes of data.
64 bytes from 172.29.45.17: icmp_req=1 ttl=64 time=0.410 ms
64 bytes from 172.29.45.17: icmp_req=2 ttl=64 time=0.300 ms
64 bytes from 172.29.45.17: icmp_req=3 ttl=64 time=0.295 ms
^C
--- 172.29.45.17 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.295/0.335/0.410/0.053 ms
root@MiOS_50160552:/tmp/log/cmh# ping 172.29.45.18
PING 172.29.45.18 (172.29.45.18) 56(84) bytes of data.
From 172.29.45.250 icmp_seq=1 Destination Host Unreachable
From 172.29.45.250 icmp_seq=2 Destination Host Unreachable
From 172.29.45.250 icmp_seq=3 Destination Host Unreachable
^C
--- 172.29.45.18 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3999ms
pipe 4
root@MiOS_50160552:/tmp/log/cmh#



Offline Buxton

  • Full Member
  • ***
  • Posts: 209
  • Karma: +12/-0
Re: New Plugin : NETMON - a network device monitor
« Reply #44 on: February 01, 2019, 04:42:05 pm »
Try going to Settings:Z-Wave Settings:Advanced and click the reload engine button.  This will reload the luup engine, which should create the child devices.  Then reload the browser to clear anything in the cache.  Offline devices take about a minute to show up as the plugin will poll (ping) on a set schedule.