Announcement

Collapse
No announcement yet.

Subnet Monitoring

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Subnet Monitoring

    I'm trying to monitor a workstation on a different subnet. From my hs server, I can ping the subnet okay, but I'm having trouble getting UltraMon to see it. I noticed that in the area where I enter my IP range, it says ... "Monitored subnets must be directly connected to your HomeSeer3 system." What would be an example of this?

    #2
    What would be an example of this?

    Say your Homeseer IP was 192.168.100.5 and your subnet is 255.255.255.0

    You can monitor IPs from 192.168.100.1 to 192.168.100.254

    If you VPN to your home network you can utilize a local browser and log in to your router to see IPs on line.

    How are you connecting this workstation on a different subnet?

    You can also send a syslog from your router to Homeseer 3 to see activity of your router.

    or

    You can purchase a gizmo called Fingbox which sells for around $129 on Amazon which will monitor your home devices. (designed in Italy, offices in Italy and UK and MFG in Taiwan).
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.12.X
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.12.X
    HS4 Pro - V4.1.7.0 - Ubuntu 18.04/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono 6.12.x
    HS4 Lite -

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

    Comment

    Working...
    X