Announcement

Collapse
No announcement yet.

Does the plug-in report alarm sensor alerts?

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

    #16
    And just a side note the foyer dimmer is a Homeseer dimmer which definitely reports it's on/off status back to the controller so I don't think the event is failing because it thinks the light is on.

    Comment


      #17
      Originally posted by mskvarenina View Post
      Stupid question, but how do I open the log file?

      I'm assuming I'll have to shell into the HS Controller?

      And do I need to turn on the debug log option to see all the events?
      All you need is WinSCP - do a google search and download.
      Connect to your Zee with the IP.
      Use the login/pw: homeseer/hsthsths3
      Navigate to the /usr/local/HomeSeer/Logs folder and you should see it there.

      However, I would look at the regular HS log and see if things are being triggered in there first.

      That event above looks fine to me.
      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


        #18
        Originally posted by rmasonjr View Post
        All you need is WinSCP - do a google search and download.
        Connect to your Zee with the IP.
        Use the login/pw: homeseer/hsthsths3
        Navigate to the /usr/local/HomeSeer/Logs folder and you should see it there.

        However, I would look at the regular HS log and see if things are being triggered in there first.

        That event above looks fine to me.
        Is there a MAC version?


        And there are never an Zone entries in the HS log.


        Sadly this just seems random. Sometimes I open the door (after sunset) and the light comes on, other times it doesn't.

        I have to think that HS controller isn't always getting the zone event so checking the HAI log is probably the next step.

        I keep my HAI software at the latest version (currently 4.0b)

        Comment


          #19
          Originally posted by rmasonjr View Post
          All you need is WinSCP - do a google search and download.
          Connect to your Zee with the IP.
          Use the login/pw: homeseer/hsthsths3
          So of course nothing is ever easy. I downloaded WinSCP and tried to connect.

          First, which protocol do I use? I would assume SFTP.

          Entering the login above homeseer/hsthsths3 yields an access denied.

          I took a look at the Web/HSTouch User Settings and didn't find a user "homeseer" so I created one temporarily with ADMIN + Local rights but still I could not logon...

          What am I doing wrong?

          Comment


            #20
            Or you can SSH to your RPi using Putty.

            [ATTACH]59715[/ATTACH]

            Or

            Install Webmin

            SSH to your RPi and type

            1 - wget hxxp://prdownloads.sourceforge.net/webadmin/webmin_1.831_all.deb **
            2 - sudo apt-get install perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl apt-show-versions python
            3 - sudo dpkg --install webmin_1.831_all.deb

            **=tt

            Use the file manager built in to Webmin or the text login built in to Webmin.

            [ATTACH]59717[/ATTACH]

            [ATTACH]59718[/ATTACH]

            [ATTACH]59719[/ATTACH]
            Last edited by Pete; February 23, 2017, 01:30 AM.
            - 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


              #21
              Well, I would imagine I will run into the same problems with these other if the user and password aren't letting me in...?

              Comment


                #22
                Try these combos and see if they work:

                1 - root/hsthsths3
                2 - homeseer/homeseer
                - 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


                  #23
                  OK, figured out the password tonight...guess I changed it when I originally set it up. I'll update the firmware and report back if the status codes match the descriptions shortly...

                  Comment


                    #24
                    Good news Michael.

                    While you are now in the RPi you should look at the OS and create a new username for yourself for the OS.

                    Think of managing the OS via SSH relating to upgrades/updates.

                    IE: like maybe Michael or mike?

                    1 - ssh to the RPi using homeseer
                    2 - sudo adduser mike
                    3 - sudo usermod -aG sudo mike

                    Then add mike to your homeseer user list via the Homeseer GUI.

                    Change the password to root

                    1 - sudo passwd root

                    Then try using putty to ssh or WinSCP to connect to your RPi or install Webmin.

                    After you validate that this works then copy your HomeSeer directory (with homeseer in OFF mode) to a PC.

                    Are you using the stock build of the Zee-2 that you purchased from Homeseer?
                    - 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


                      #25
                      Just did all of this and was able to update the plug-in. And yes I'm using the stock build of HS3...

                      Comment


                        #26
                        OK the test results are in, something is still off.

                        Just to restate the objective, I'm trying to cause the foyer light to come on, when the front door is opened, it's after sunset and the alarm is armed. If I code the event to say when the zone 33 becomes not ready and it's after sunset the light will come on each and every time I open and close the door. But I am having no luck either detecting the same condition and adding the alarm state (armed) or by testing a different status that comes from the zone while the alarm is armed (see 2nd set of log data below)



                        Zone 36 is my powder room.

                        I opened the door and it appears the status changed to '1', status text "NOT READY" as recorded in the log.

                        Then I closed the door and the status changed to '0', status text "SECURE" as recorded in the log.


                        (In HS, on the Status Graphics tab for zone 36, '0' has a description of Secure, '1' has a description of Secure-Bypass and '2' has a description of "Not Ready".)



                        2/25/2017 11:47:52 AM [2] [UNSOLICITED: ExtendedStatus]
                        2/25/2017 11:47:53 AM [2] [---->Zone]
                        2/25/2017 11:47:53 AM [2] [ZONE: zone=[] number=[36] status=[NOT READY]]
                        2/25/2017 11:47:53 AM [2] [Zone [36] status=[1] [1]]
                        2/25/2017 11:47:53 AM [2] [MapZoneStatus: zoneId=[36] status=[1] zoneChanged=[False] annotation=[(EX2-4/WR4)] statusText=[NOT READY] zoneType=[1] zoneTypeText=[Perimeter] name=[Powder Room] area=[1] analogLoop=[1] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[2/25/2017 11:47:53 AM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[28] hsParentRef=[11] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[NOT READY] hsZoneStatus=[0]]
                        2/25/2017 11:47:53 AM [2] [NOT READY]
                        2/25/2017 11:47:53 AM [2] [--> Zone 36 changed status. Updating Homeseer...]

                        2/25/2017 11:47:56 AM [2] [UNSOLICITED: ExtendedStatus]
                        2/25/2017 11:47:56 AM [2] [---->Zone]
                        2/25/2017 11:47:56 AM [2] [ZONE: zone=[] number=[36] status=[SECURE]]
                        2/25/2017 11:47:56 AM [2] [Zone [36] status=[0] [0]]
                        2/25/2017 11:47:56 AM [2] [MapZoneStatus: zoneId=[36] status=[0] zoneChanged=[False] annotation=[(EX2-4/WR4)] statusText=[SECURE] zoneType=[1] zoneTypeText=[Perimeter] name=[Powder Room] area=[1] analogLoop=[1] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[2/25/2017 11:47:56 AM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[28] hsParentRef=[11] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[SECURE] hsZoneStatus=[2]]
                        2/25/2017 11:47:56 AM [2] [SECURE]
                        2/25/2017 11:47:56 AM [2] [--> Zone 36 changed status. Updating Homeseer...]





                        Now, something else that is interesting (and I switched to Zone 33, front door for this analysis). While the alarm is armed, and the door is opened the status becomes NOT READY with a value 21 instead of 1. Then when the door is closed, and the alarm is armed the value becomes SECURE with a value of 20 instead of 0. 20 and 21 did not exist in the Status Graphics tab of the zone.

                        I thought I figured this out by adding both a 20 and 21 to the Status Graphics tab and coding the event for one of these statuses....but sadly still no luck...

                        2/25/2017 12:03:49 PM [2] [UNSOLICITED: ExtendedStatus]
                        2/25/2017 12:03:49 PM [2] [---->Zone]
                        2/25/2017 12:03:50 PM [2] [ZONE: zone=[] number=[33] status=[NOT READY]]
                        2/25/2017 12:03:50 PM [2] [Zone [33] status=[21] [21]]
                        2/25/2017 12:03:50 PM [2] [MapZoneStatus: zoneId=[33] status=[21] zoneChanged=[False] annotation=[(EX2-1/WR1)] statusText=[TRIPPED] zoneType=[0] zoneTypeText=[EntryExit] name=[Front Door] area=[1] analogLoop=[0] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[2/25/2017 12:03:50 PM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[25] hsParentRef=[11] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[NOT READY] hsZoneStatus=[0]]
                        2/25/2017 12:03:50 PM [2] [TRIPPED]
                        2/25/2017 12:03:50 PM [2] [--> Zone 33 changed status. Updating Homeseer...]

                        2/25/2017 12:03:50 PM [2] [UNSOLICITED: ExtendedStatus]
                        2/25/2017 12:03:50 PM [2] [---->Area]
                        2/25/2017 12:03:50 PM [2] [Area change event raised: ]


                        2/25/2017 12:03:52 PM [2] [UNSOLICITED: ExtendedStatus]
                        2/25/2017 12:03:52 PM [2] [---->Zone]
                        2/25/2017 12:03:52 PM [2] [ZONE: zone=[] number=[33] status=[SECURE]]
                        2/25/2017 12:03:52 PM [2] [Zone [33] status=[20] [20]]
                        2/25/2017 12:03:52 PM [2] [MapZoneStatus: zoneId=[33] status=[20] zoneChanged=[False] annotation=[(EX2-1/WR1)] statusText=[TRIPPED] zoneType=[0] zoneTypeText=[EntryExit] name=[Front Door] area=[1] analogLoop=[1] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[2/25/2017 12:03:52 PM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[25] hsParentRef=[11] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[SECURE] hsZoneStatus=[5]]
                        2/25/2017 12:03:52 PM [2] [TRIPPED]
                        2/25/2017 12:03:52 PM [2] [--> Zone 33 changed status. Updating Homeseer...]

                        Comment


                          #27
                          Rob, here's a question for you. Does the plug in pass all status codes it receives from the panel to HS or do you filter and/or translate some.

                          I started thinking since I saw the 20 and 21 status codes received in the log I got to wondering if they were passed to HS or if I need to do something in HS beyond adding the to the status graphics tab for them to be received and acted on in an event.

                          Comment


                            #28
                            Originally posted by mskvarenina View Post
                            Rob, here's a question for you. Does the plug in pass all status codes it receives from the panel to HS or do you filter and/or translate some.

                            I started thinking since I saw the 20 and 21 status codes received in the log I got to wondering if they were passed to HS or if I need to do something in HS beyond adding the to the status graphics tab for them to be received and acted on in an event.
                            You'll notice in the logs that there is a MapZoneStatus - that is a function I wrote to map the HAI zone status to the HS zone status from the Status Graphics tab. I need to look at that a little closer.
                            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


                              #29
                              I have this fixed in the current version. I need to get this into the updater, so I'll let you know when its available for download.
                              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


                                #30
                                Rob,

                                What actually did you fix? Do you think this fix may solve my issues with detecting a 20 and 21 status on the zones?

                                When you said getting into the updater, do you mean uploading to the HS website so people can download and install it from there?

                                Comment

                                Working...
                                X