Announcement

Collapse
No announcement yet.

Panel disconnect after burglar alarm

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

    #16
    Yeah here tried both an all on and all off and did not see anything in the Omni Logs on the two instances of the Omni plugin.

    From way back the assumption was that the all on and all off worked with my X10 but did not work with my UPB so I manually configured (via one link) it when the alarm was triggered.
    - 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 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #17
      Noticed a bunch of network disconnect emails here from the HAILogger program when testing above earlier today.

      The HAILogger program connects to the Omni Pro 2 panel and the Samsung Smartthings hub.


      CoreServer: CONNECTION STATUS: No Reply

      [ATTACH]64739[/ATTACH]

      Created an ALL ON and ALL OFF button. I was able to replicate the error above pressing ALL ON.


      HAI Logger - Error
      Today, 6:48 PM
      CoreServer: CONNECTION STATUS: No Reply

      Hit the all on button a few times and watched some pings...no disconnects seen but it slowed down a bit.

      Note that this is between the microrouter LAN interface and the OmniPro NIC interface.

      64 bytes from 192.168.1.2: seq=26 ttl=64 time=2.820 ms
      64 bytes from 192.168.1.2: seq=27 ttl=64 time=39.500 ms
      64 bytes from 192.168.1.2: seq=28 ttl=64 time=8.440 ms
      64 bytes from 192.168.1.2: seq=29 ttl=64 time=2.820 ms
      64 bytes from 192.168.1.2: seq=30 ttl=64 time=28.600 ms
      64 bytes from 192.168.1.2: seq=31 ttl=64 time=4.481 ms
      64 bytes from 192.168.1.2: seq=32 ttl=64 time=4.700 ms
      64 bytes from 192.168.1.2: seq=33 ttl=64 time=4.520 ms
      64 bytes from 192.168.1.2: seq=34 ttl=64 time=28.221 ms
      64 bytes from 192.168.1.2: seq=35 ttl=64 time=20.041 ms
      64 bytes from 192.168.1.2: seq=36 ttl=64 time=4.460 ms
      64 bytes from 192.168.1.2: seq=37 ttl=64 time=6.020 ms
      64 bytes from 192.168.1.2: seq=38 ttl=64 time=27.441 ms

      Personally thinking this is an issue with the bus that is affecting the NIC on the OmniPro 2 panel.

      I only see a disconnect happening with the HAILogger program. I do have a microrouter between the OP2 LAN interface and the main network here.

      Running HS3 lite here on an ARM 64bit Ubuntu computer so it is a bit faster than an RPi2&3.
      Last edited by Pete; November 27, 2017, 11:42 PM.
      - 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 22.04 / Lenovo Tiny M900 / 32Gb Ram

      HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
      HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

      Comment


        #18
        Any volunteers out there for testing this issue?

        Ideally a tester will:

        1 - create an all on button
        2 - press it a few times and see if you get a disconnect from the Omni Plugin.

        Even easier just do a continuous ping to you Omni panel while pressing the button from your HS3 box (whether running windows or linux).

        I am looking to prove up a ticket to Leviton relating to an issue with the bus and network interface and hopefully a fix by Leviton on their next firmware release.
        - 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 22.04 / Lenovo Tiny M900 / 32Gb Ram

        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

        Comment


          #19
          Bump.
          - 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 22.04 / Lenovo Tiny M900 / 32Gb Ram

          HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
          HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

          Comment

          Working...
          X