Announcement

Collapse
No announcement yet.

Zone device does not update

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

    #16
    No I just log in occasionally to compare results.
    HS4Pro Win10 | Fire Tablet touchscreen client, Android Phones and Tablets | Jon00 | Smartthings | Philips Hue | Trane | Caseta | Nanoleaf | Ring | August | Evolve | Aladdin | Amazon Alexa/IFTT

    Comment


      #17
      when the problem occurs, can you arm/disarm through Homeseer?
      do you get notifications of armed / disarmed events?

      Comment


        #18
        I hadn't tried as I've never armed it through HS. I'll try it when it starts acting up. It seems to working fine at the moment.

        11/8/2013 5:07:15 PM EnvisaLink DEBUG Request: Poll
        11/8/2013 5:07:16 PM EnvisaLink DEBUG CommandAcknowledge 000
        11/8/2013 5:07:30 PM EnvisaLink DEBUG ZoneOpen 004
        11/8/2013 5:07:30 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
        11/8/2013 5:07:32 PM EnvisaLink DEBUG ZoneRestored 004
        11/8/2013 5:07:32 PM EnvisaLink DEBUG PartitionReady 1
        11/8/2013 5:07:34 PM EnvisaLink DEBUG ZoneOpen 004
        11/8/2013 5:07:34 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
        11/8/2013 5:07:34 PM EnvisaLink DEBUG ZoneOpen 003
        11/8/2013 5:07:34 PM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
        11/8/2013 5:07:34 PM EnvisaLink DEBUG PartitionNotReady 1
        11/8/2013 5:07:35 PM EnvisaLink DEBUG ZoneRestored 004

        What is that force arming enabled one? That's the only thing I hadn't noticed before. By the way zone 4 is a motion detector.
        HS4Pro Win10 | Fire Tablet touchscreen client, Android Phones and Tablets | Jon00 | Smartthings | Philips Hue | Trane | Caseta | Nanoleaf | Ring | August | Evolve | Aladdin | Amazon Alexa/IFTT

        Comment


          #19
          PartitionReadyForceArmingEnabled 1 means the partition 1 is ready to be armed in stay mode only, i.e. one interior zone is opened.

          Comment


            #20
            Its been working fine all day today. Don't know why other than maybe it just needed a day to shake it all out?

            I'll keep an eye on it but it was odd. It seemed to become unresponsive randomly and required a reset. I could never figure out the cause.
            HS4Pro Win10 | Fire Tablet touchscreen client, Android Phones and Tablets | Jon00 | Smartthings | Philips Hue | Trane | Caseta | Nanoleaf | Ring | August | Evolve | Aladdin | Amazon Alexa/IFTT

            Comment


              #21
              Sort of the same issue...

              I am using the EnvisaLink Driver "HSPI_ENVISALINK" Version: 1.0.0.10

              I can ARM and DISARM the alarm. I use Events to do this through HSTouch.

              I am not seeing any change on the STATUS web page.

              With the plugin set to log mode DEBUG an I open a window I get:

              12/28/2013 11:48:08 AM EnvisaLink DEBUG ZoneOpen 026
              12/28/2013 11:48:08 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 80
              12/28/2013 11:48:08 AM EnvisaLink DEBUG PartitionNotReady 1


              So why when I go to the Status Page and even Refresh it still shows the window CLOSED?

              I closed and restarted Homeseer with the window still open and the status page still shows the window as CLOSED (yes I did refresh/reload the page).

              So I closed the window and the log shows it closed and the Event I have that updates the Alarm Status virtual device triggers. So all of that is working.

              12/28/2013 11:59:08 AM EnvisaLink DEBUG ZoneRestored 026
              12/28/2013 11:59:08 AM EnvisaLink DEBUG KeypadLedStatePartition1Only 81
              12/28/2013 11:59:08 AM EnvisaLink DEBUG PartitionReady 1
              12/28/2013 11:59:08 AM Event Event Trigger "Alarm Status"
              12/28/2013 11:59:08 AM Event Running script and waiting: SetAlarmStatus

              I need to try and show all of this on my HSTouch screen...

              Thanks
              Rich

              Comment


                #22
                Make sure you didn't change the number of zones by mistake. It should be something greater than 26, since your logs shows you have a zone #26.

                If this is not the problem, try to delete your zone devices and then restart the plugin. Are they correctly recreated? Does that fix your problem?

                Comment


                  #23
                  LOL

                  OK we can start laughing again....

                  As the story goes... I have a new ISY994iIR/Pro and moved all mu Alarm stuff over to it about a week or less ago. So I uninstalled the EnvisaLink from HS2 so as to not conflict. Well after trying a third party DSCLink plugin that worked great but finding out there was NO suport for the DSC on ISY and worst yet, NO product such as HSTouch to create my own interface and the only way to manage the Alarm was to create events and have them on their own page as ugly event items etc...... I decided it was tome to re-install the EnvisaLink plugin after I restored HS2 from a backup....

                  Guess I neglected to increase the Zone Count from 1....

                  Sorry for the trouble, hope this crazy entry helps another that pulls the same Army of 1... I mean Zone of 1 stunt...

                  Rich

                  Comment

                  Working...
                  X