Announcement

Collapse
No announcement yet.

OMNI Plugin v3.0.2.14

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    OMNI Locks Hard Wired

    I still don't have locks working. They appear in the plug-in config and I can add them to HS3, but lock/unlock doesn't feedback to HS3.

    Plug-in Log
    14/07/2018 14:03:13 [2] [-->LOCK: 0 / LOCKED]
    14/07/2018 14:03:13 [2] [-->LOCK: 0 0 0/-]
    14/07/2018 14:03:13 [2] [-->LOCK:]
    14/07/2018 14:03:13 [2] [---->AccessControlLock]
    14/07/2018 14:03:13 [2] [UNSOLICITED: ExtendedStatus]
    14/07/2018 14:03:09 [2] [-->LOCK: 1 / UNLOCKED]
    14/07/2018 14:03:09 [2] [-->LOCK: 0 0 0/-]
    14/07/2018 14:03:09 [2] [-->LOCK:]
    14/07/2018 14:03:09 [2] [---->AccessControlLock]
    14/07/2018 14:03:09 [2] [UNSOLICITED: ExtendedStatus]

    The HS3 device attached to this lock shows value 0 regardless.

    If I select LOCK/UNLOCK from HS3 device then the locks do indeed lock and unlock but again HS3 device doesn't update and always shows

    Status 0 = OFF
    Value 0 = "Unlocked"

    I've removed the HS3 devices and re-added them via the plug-in, no change.

    Any idea's?

    Comment


      #17
      Relating to the alarm on and off and lights on or off thingy many long time OmniPro users have gone to using a tiny keychain 4 button FOB rather than using keypad or touchscreen using Leviton / HAI wireless receiver or propietary 4 channel button to 4 relay board. The audio beeps are enabled and you do hear them fine when exiting premises.

      Personally here and due to WAF it has remained at the basic HAI keypad use here and wife has stayed away from my over to the top HSTouch screens (she is afraid of breaking the house).

      - 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
        @Graham,

        When connected to PCA do you see any connection issues with the software to panel connection? It'll blink disconnected and reconnecting on the bottom of the PCA screen.

        Do you have any other Ethernet connected devices to your Panel that you see issues with?

        One physical problem I have seen is that the RJ-45 terminal on the top of the panel is related to sometimes pulling on it and it does come off the main board of the panel and appears to be held in place by the 8 (or less) network wires to the board. Over time it could break the leads. I have had issues relating to using a hooded RJ-45 cable cuz I cannot reach the top well as it is adjacent to the HAI media can.

        Here still doing the micro router (layer 2 layer 3 thing) self powered by panel thing. Topology is OP2 NIC plugged in to the microrouter never touched and the ethernet port on the micro router which is to the side and middle of the HAI can easy access but never touching it.
        - 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
          Rob,

          I've been seeing weird behavior with some of my HS3 events not working the past few days. What I found is when I set an Omni light to "on" in the web portal (also via an event or HStouch) it comes on briefly, then turns back off. I sent you a log with this issue. I saw a weird error about Zone 25. I need to look into that separately. All of my omni lights are UPB. Off works fine, it is turning them back on that does not work.

          Knowing some people had issues with lights dimming I tried to see if this behavior changed with UPB dim enabled or disabled. Does not matter. If dimming is enabled or not the lights behave the same way.

          Thanks,

          Guy

          Comment


            #20
            @Pete,

            I'm not trying to investigate the connectivity issue. My HS runs on a VM and this disconnect is when a regular (nightly) snapshot is taken of the machine. I've been doing this for many years and for the majority of the time the HAI plugin has reconnected fine. I had this problem many versions ago and it was fixed by Rob, then it returned.

            Comment


              #21
              Originally posted by GEN View Post
              I still don't have locks working. They appear in the plug-in config and I can add them to HS3, but lock/unlock doesn't feedback to HS3.

              Plug-in Log
              14/07/2018 14:03:13 [2] [-->LOCK: 0 / LOCKED]
              14/07/2018 14:03:13 [2] [-->LOCK: 0 0 0/-]
              14/07/2018 14:03:13 [2] [-->LOCK:]
              14/07/2018 14:03:13 [2] [---->AccessControlLock]
              14/07/2018 14:03:13 [2] [UNSOLICITED: ExtendedStatus]
              14/07/2018 14:03:09 [2] [-->LOCK: 1 / UNLOCKED]
              14/07/2018 14:03:09 [2] [-->LOCK: 0 0 0/-]
              14/07/2018 14:03:09 [2] [-->LOCK:]
              14/07/2018 14:03:09 [2] [---->AccessControlLock]
              14/07/2018 14:03:09 [2] [UNSOLICITED: ExtendedStatus]

              The HS3 device attached to this lock shows value 0 regardless.

              If I select LOCK/UNLOCK from HS3 device then the locks do indeed lock and unlock but again HS3 device doesn't update and always shows

              Status 0 = OFF
              Value 0 = "Unlocked"

              I've removed the HS3 devices and re-added them via the plug-in, no change.

              Any idea's?
              Your logs look exactly like another user's logs - that entry LOCK: 0 0 0/- shows that the lock number is not coming back from the panel/SDK. I'm still looking into this to see how to handle.
              HS4Pro on a Raspberry Pi4
              54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
              Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

              HSTouch Clients: 1 Android

              Comment


                #22
                Originally posted by cowsr4eating View Post
                Rob,

                I've been seeing weird behavior with some of my HS3 events not working the past few days. What I found is when I set an Omni light to "on" in the web portal (also via an event or HStouch) it comes on briefly, then turns back off. I sent you a log with this issue. I saw a weird error about Zone 25. I need to look into that separately. All of my omni lights are UPB. Off works fine, it is turning them back on that does not work.

                Knowing some people had issues with lights dimming I tried to see if this behavior changed with UPB dim enabled or disabled. Does not matter. If dimming is enabled or not the lights behave the same way.

                Thanks,

                Guy
                Thanks - I received the logs and will see what I can find out.
                HS4Pro on a Raspberry Pi4
                54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                HSTouch Clients: 1 Android

                Comment


                  #23
                  Originally posted by madas View Post
                  Still having the disconnect problem. Once my HS and HA lose connection it never returns. I pm'd you the full log but here are the last few entries

                  7/14/2018 2:47:53 AM [2] [CONNECTION STATUS: Connection Reset By Peer]
                  7/14/2018 2:47:56 AM [2] [CONNECTION STATUS: Retrying]
                  7/14/2018 2:48:01 AM [2] [CONNECTION STATUS: Disconnected]

                  Then it sat till 7AM and i had to restart the plugin
                  I'm not sure what else to try. It looks like it tried to reconnect for 5 seconds then gave up. I'll see if there are any connection settings I'm missing.
                  HS4Pro on a Raspberry Pi4
                  54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                  Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                  HSTouch Clients: 1 Android

                  Comment


                    #24
                    Originally posted by rmasonjr View Post
                    I'm not sure what else to try. It looks like it tried to reconnect for 5 seconds then gave up. I'll see if there are any connection settings I'm missing.
                    Is it supposed to retry indefinitely? or just a single retry?

                    Comment


                      #25
                      Rob,

                      I disabled/enabled the Omni plugin and rebooted the HS3 server. Same problem turning on lights via HS3. Snaplink works fine.

                      I restored backup and v3.0.2.13 controls lights for me. Since no one else is reporting this problem I'm a little stumped as to what would be unique to my config. I re-ran the same test with debug level logging. Logs identical except for one line:
                      vx.x.x.14 (does not work):
                      [-->Unsolicited: Unit=[4] status=[100]/[LEVEL 0%] type=[4] / []]

                      vx.x.x.13 (does work):
                      [-->Unsolicited: Unit=[4] status=[200]/[LEVEL 100%] type=[4] / []]

                      Full .13 log emailed to you for comparison.

                      Guy

                      Comment


                        #26
                        Originally posted by cowsr4eating View Post
                        Rob,

                        I disabled/enabled the Omni plugin and rebooted the HS3 server. Same problem turning on lights via HS3. Snaplink works fine.

                        I restored backup and v3.0.2.13 controls lights for me. Since no one else is reporting this problem I'm a little stumped as to what would be unique to my config. I re-ran the same test with debug level logging. Logs identical except for one line:
                        vx.x.x.14 (does not work):
                        [-->Unsolicited: Unit=[4] status=[100]/[LEVEL 0%] type=[4] / []]

                        vx.x.x.13 (does work):
                        [-->Unsolicited: Unit=[4] status=[200]/[LEVEL 100%] type=[4] / []]

                        Full .13 log emailed to you for comparison.

                        Guy
                        Good info, Guy - thanks
                        HS4Pro on a Raspberry Pi4
                        54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                        Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                        HSTouch Clients: 1 Android

                        Comment


                          #27
                          Originally posted by madas View Post
                          Is it supposed to retry indefinitely? or just a single retry?
                          I'm not real sure. The SDK hides some of the connection routines for me, so I'm not sure. Going to dig around a little and see what I can find out...
                          HS4Pro on a Raspberry Pi4
                          54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                          Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                          HSTouch Clients: 1 Android

                          Comment


                            #28
                            I did not state, but what I did on both cases was click the "on" button in the HS3 web portal. I used the same device to be consistent, but all of my HS3 light/fan devices behave the same way.

                            Light come on for maybe 1 second, then go off. In the web portal the lights show as "on" briefly, then go back to "off".

                            Comment


                              #29
                              Here tested my test hallway UPB light switch.

                              On works. Off works. Dim dims for a second or two then shuts off the lamp.

                              Here is the debug stuff.

                              ON


                              7/16/2018 4:20:17 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                              7/16/2018 4:20:17 PM [2] [-->Unsolicited: Unit=[51] status=[1]/[ON] type=[4] / []]
                              7/16/2018 4:20:17 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                              7/16/2018 4:20:17 PM [2] [---->Unit]
                              7/16/2018 4:20:17 PM [2] [UNSOLICITED: ExtendedStatus]
                              7/16/2018 4:20:17 PM [2] [Unit_On: unitId=51 ]
                              7/16/2018 4:20:17 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[255]]

                              OFF

                              7/16/2018 4:20:34 PM [2] [UNSOLICITED: ExtendedStatus]
                              7/16/2018 4:20:33 PM [2] [Unit_Off: unitId=51 ]
                              7/16/2018 4:20:33 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[0]]

                              DIM

                              7/16/2018 4:20:40 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                              7/16/2018 4:20:40 PM [2] [-->Unsolicited: Unit=[51] status=[100]/[LEVEL 0%] type=[4] / []]
                              7/16/2018 4:20:40 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                              7/16/2018 4:20:40 PM [2] [---->Unit]
                              7/16/2018 4:20:40 PM [2] [--> unitType=4]


                              7/16/2018 4:20:40 PM [2] [Unit_Dim: unitId=51 dimVal=45]
                              7/16/2018 4:20:40 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[45]]
                              7/16/2018 4:20:34 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                              7/16/2018 4:20:34 PM [2] [-->Unsolicited: Unit=[51] status=[0]/[OFF] type=[4] / []]
                              7/16/2018 4:20:34 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                              7/16/2018 4:20:34 PM [2] [---->Unit]
                              - 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


                                #30
                                Originally posted by Pete View Post
                                Here tested my test hallway UPB light switch.

                                On works. Off works. Dim dims for a second or two then shuts off the lamp.

                                Here is the debug stuff.

                                ON


                                7/16/2018 4:20:17 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                                7/16/2018 4:20:17 PM [2] [-->Unsolicited: Unit=[51] status=[1]/[ON] type=[4] / []]
                                7/16/2018 4:20:17 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                                7/16/2018 4:20:17 PM [2] [---->Unit]
                                7/16/2018 4:20:17 PM [2] [UNSOLICITED: ExtendedStatus]
                                7/16/2018 4:20:17 PM [2] [Unit_On: unitId=51 ]
                                7/16/2018 4:20:17 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[255]]

                                OFF

                                7/16/2018 4:20:34 PM [2] [UNSOLICITED: ExtendedStatus]
                                7/16/2018 4:20:33 PM [2] [Unit_Off: unitId=51 ]
                                7/16/2018 4:20:33 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[0]]

                                DIM

                                7/16/2018 4:20:40 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                                7/16/2018 4:20:40 PM [2] [-->Unsolicited: Unit=[51] status=[100]/[LEVEL 0%] type=[4] / []]
                                7/16/2018 4:20:40 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                                7/16/2018 4:20:40 PM [2] [---->Unit]
                                7/16/2018 4:20:40 PM [2] [--> unitType=4]


                                7/16/2018 4:20:40 PM [2] [Unit_Dim: unitId=51 dimVal=45]
                                7/16/2018 4:20:40 PM [2] [SetIOMulti: CC.Ref=[1816] CC.ControlValue=[45]]
                                7/16/2018 4:20:34 PM [2] [--> Unit 51 changed status. Updating Homeseer...]
                                7/16/2018 4:20:34 PM [2] [-->Unsolicited: Unit=[51] status=[0]/[OFF] type=[4] / []]
                                7/16/2018 4:20:34 PM [2] [-->UNIT: desc=[] number=[51] name=[Hallway Back]]
                                7/16/2018 4:20:34 PM [2] [---->Unit]
                                Thanks Pete - would you try something for me?

                                Delete the device in the plugin config screen - just click the little checkbox.
                                Re-create the device with the checkbox.
                                Go through your ON/OFF/Dim again and see if you get the same results.
                                HS4Pro on a Raspberry Pi4
                                54 Z-Wave Nodes / 21 Zigbee Devices / 108 Events / 767 Devices
                                Plugins: Z-Wave / Zigbee Plus / EasyTrigger / AK Weather / OMNI

                                HSTouch Clients: 1 Android

                                Comment

                                Working...
                                X