Announcement

Collapse
No announcement yet.

Odd network possession....

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

    Odd network possession....

    My Homeseer computer has two network cards and two networks. Network "A" was meant to control Homeseer and Network "B" was meant to carry video (only) and respond to Sighthound.

    As of today, Homeseer has decided to only listen to network "B" and any attempt to bind the network "A" IP address only results in not being able to access Homeseer, at all.

    Any ideas, anyone?
    HomeSeer Version: HS3 Pro Edition 3.0.0.548
    Operating System: Microsoft Windows 10 Pro - Work Station

    Enabled Plug-Ins
    3.0.0.6: AK Smart Device 3.0.1.9: AmbientWeather 2.0.63.0: BLBackup 3.0.55.0: BLGData 3.0.38.0: BLLock 2.0.26.0: BLUPS 3.2.0.1: Device History 3.0.0.73: EasyTrigger 3.25.614.1: HSBuddy 3.1.0.22: MeiHarmonyHub 3.1.0.2: SDJ-Health 19.10.7.1: TPLinkSmartHome 3.0.6681.34300: UltraCID3 3.0.6644.26753: UltraLog3 3.0.6554.33094: UltraMon3 3.0.5960.36744: UltraSighthoundVideo3 3.0.7806.23606: UltraWeatherWU3 3.0.2.0: Z-Wave

    #2
    Did you try changing the binding order of the NICs?
    Mike

    Comment


      #3
      Hmmmm... not, not yet, but here is a bit of what confuses me:

      The connected speaker client "Kitchen" is not even ON the 192.168.33.x subnet..... it is on 192.168.1.x!
      HomeSeer Version: HS3 Pro Edition 3.0.0.548
      Operating System: Microsoft Windows 10 Pro - Work Station

      Enabled Plug-Ins
      3.0.0.6: AK Smart Device 3.0.1.9: AmbientWeather 2.0.63.0: BLBackup 3.0.55.0: BLGData 3.0.38.0: BLLock 2.0.26.0: BLUPS 3.2.0.1: Device History 3.0.0.73: EasyTrigger 3.25.614.1: HSBuddy 3.1.0.22: MeiHarmonyHub 3.1.0.2: SDJ-Health 19.10.7.1: TPLinkSmartHome 3.0.6681.34300: UltraCID3 3.0.6644.26753: UltraLog3 3.0.6554.33094: UltraMon3 3.0.5960.36744: UltraSighthoundVideo3 3.0.7806.23606: UltraWeatherWU3 3.0.2.0: Z-Wave

      Comment


        #4
        Sounds a bit like 2nd address is coming from a DHCP server?

        Could it be a kitchen wireless client maybe?
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
        HS4 Lite - Ubuntu 20.04 / VB W7e Jetway JBC420U591
        Fanless IntelĀ® Celeron N3160 SoC 8Gb
        HS4 Pro - V4.1.18.1 - Ubuntu 20.04/VB W7e 64 bit Intel Kaby Lake CPU - 32Gb
        HSTouch on Intel tabletop tablets

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

        Comment


          #5
          I'm beginning to believe that is exactly what is going on..... have company and just found a disconnected lan cable. Jeeze.... this is going to get interesting...
          HomeSeer Version: HS3 Pro Edition 3.0.0.548
          Operating System: Microsoft Windows 10 Pro - Work Station

          Enabled Plug-Ins
          3.0.0.6: AK Smart Device 3.0.1.9: AmbientWeather 2.0.63.0: BLBackup 3.0.55.0: BLGData 3.0.38.0: BLLock 2.0.26.0: BLUPS 3.2.0.1: Device History 3.0.0.73: EasyTrigger 3.25.614.1: HSBuddy 3.1.0.22: MeiHarmonyHub 3.1.0.2: SDJ-Health 19.10.7.1: TPLinkSmartHome 3.0.6681.34300: UltraCID3 3.0.6644.26753: UltraLog3 3.0.6554.33094: UltraMon3 3.0.5960.36744: UltraSighthoundVideo3 3.0.7806.23606: UltraWeatherWU3 3.0.2.0: Z-Wave

          Comment

          Working...
          X