Announcement

Collapse
No announcement yet.

AEOTEC Quad WallMote ZW130 Homeseer Setup Procedure

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

  • #16
    Robert, thanxs for taking the time to explain, I find I learn so much more when people share their approaches/techniques (visual learner). Your mini-Remote example explains how your toggling your virtual device between Off/On which I will try to adapt myself. I also liked your "Smoking and Grilling" Scene! are guests welcomed? Mike
    Computer: CUK Intel NUC7i7BNH
    Op System: Windows 10 Pro - Work Station
    HS Version: HS3 Pro Edition 3.0.0.435

    Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

    Comment


    • #17
      Hey Robert, I had a chance to absorb and changed my MiniMote and WallMotes over to your scene approach which after working a few bug out seems to work swimmingly! Instead of HSTouch, I use ImperialHome App and am working on adopting your HSTouch concept to suite my scenarios. At first it seemed like I was creating a fair number of Virtual devices, Scene Control (events) based on my Wall/MiniMote devices followed by specific Scene Routines (events) that make the scenes do specific tasks. So again thanxs for sharing your methodology and approaches, Mike
      Computer: CUK Intel NUC7i7BNH
      Op System: Windows 10 Pro - Work Station
      HS Version: HS3 Pro Edition 3.0.0.435

      Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

      Comment


      • #18
        Glad to have provided a different way of thinking about it.

        As another item to consider, I don't use any grouping functions provided by device specific plugins. In other words, the grouping in Insteon does work but it is Insteon specific. The grouping in the z-wave plugin didn't work when I tested it sometime back. My devices are a mixed bag of Insteon, z-wave, and wifi so device specific grouping could never cover all the different types. The grouping in the EZTrigger plugin can cross device technologies. The dynamic grouping is really cool as long as you have some sort of standardization on naming and locations.

        Comment


        • #19
          Robert, per chance can you provide an example of how your using EZTrigger as to grouping? Mike
          Computer: CUK Intel NUC7i7BNH
          Op System: Windows 10 Pro - Work Station
          HS Version: HS3 Pro Edition 3.0.0.435

          Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

          Comment


          • #20
            Here is a group definition as well as an event that uses it. The use case is to send an email when batteries get low. Any device with Battery in teh name will be included in the group. The nice thing about the dynamic nature is that when you add a new device, you only need to get the name or location right. The event is new so the trigger is set high so I can see it work as battery levels change.

            Click image for larger version  Name:	groups_dynamic.png Views:	0 Size:	33.5 KB ID:	1320665

            Click image for larger version  Name:	groups_battery_event2.jpg Views:	0 Size:	46.5 KB ID:	1320666

            Comment


            • #21
              Thanxs Robert for the example (pic worth a thousand words!). I have a similar event to monitor batteries but not using the Group definition. Mike
              Computer: CUK Intel NUC7i7BNH
              Op System: Windows 10 Pro - Work Station
              HS Version: HS3 Pro Edition 3.0.0.435

              Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

              Comment


              • #22
                Robert, is this a plug-in if so what is it? Never mind I found it within the EasyTrigger Plug-in.

                Click image for larger version  Name:	groups_dynamic.png Views:	0 Size:	33.5 KB ID:	1320665
                Computer: CUK Intel NUC7i7BNH
                Op System: Windows 10 Pro - Work Station
                HS Version: HS3 Pro Edition 3.0.0.435

                Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                Comment


                • #23
                  That is in the config section of the EasyTrigger plugin. It is where you define a dynamic group. You define the criteria for inclusion and the plugin creates the group for you.

                  I'm a big fan of EasyTrigger. If you aren't familiar with it, here is a subforum for it where you could learn more.

                  https://forums.homeseer.com/forum/ul...sytrigger-spud




                  Comment


                  • #24
                    Thanxs Frank, I've never used this function within EasyTrigger so it was my first time, but it seemed to be rather straight forward. Thanxs for the link I will read up on Spuds plug-in, is there something I need to do to get $$GLOBALVAR's to work I don't see anything in the set, it does create the 6 etdevices but no type or values.

                    UPDATE: I'm assuming that I have to wait for the Battery devices to report sometime within every 24 hr before I will see anything within the Global Variables?
                    Attached Files
                    Computer: CUK Intel NUC7i7BNH
                    Op System: Windows 10 Pro - Work Station
                    HS Version: HS3 Pro Edition 3.0.0.435

                    Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                    Comment


                    • #25
                      Robert, I just finished working through all my light associated events and switched them from turn a specific device(s) ON or OFF methodology to controlling my specific virtual devices to ON or OFF as I did for my remotes which seems to work swimmingly, my question is when I physically turn on a light switch it simply turns the light(s) On or Off but the virtual devices that were currently using status/state doesn't reflect what was done so if I had turned a light on with my remote the VD would indicate an ON status but if I turn the same light OFF via a physical wall switch it turns the light OFF but the VD status still shows a ON condition. Any thoughts as to how one syncs the physical actions with Virtual Devices? Mike
                      Computer: CUK Intel NUC7i7BNH
                      Op System: Windows 10 Pro - Work Station
                      HS Version: HS3 Pro Edition 3.0.0.435

                      Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                      Comment


                      • #26
                        The virtual devices are associated with the scenes. The scene VD gets turned on which triggers the event which turns on/ff multiple real devices. The VD for the scene usually stays on until the sleeping scene turns them off. In my thinking, nothing happens/triggers when a scene VD gets turned off - only when they get turned on.

                        Comment


                        • #27
                          Robert, thanxs for the comeback, I'm confused on your statement "
                          In my thinking, nothing happens/triggers when a scene VD gets turned off - only when they get turned on." I thought you had Scenes that turned lights when the VD were turned OFF I guess I missed that point as I had created both ON and OFF scenes based on the VD state of ON or OFF which works great. I was going to create a scene that when a physical light switch was turned On or Off that it would trigger its appropriate VD to provide a real time state much like a remote, your thoughts? Mike
                          Computer: CUK Intel NUC7i7BNH
                          Op System: Windows 10 Pro - Work Station
                          HS Version: HS3 Pro Edition 3.0.0.435

                          Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                          Comment


                          • #28
                            As I said, I stack scenes. They often overlap so turning one off would impact an overlapping scene. If you come up with a use case that needs an event for turning a scene off, go for it. I just haven't.

                            Comment


                            • #29
                              Understand, thank-you for taking the time to explain, Mike
                              Computer: CUK Intel NUC7i7BNH
                              Op System: Windows 10 Pro - Work Station
                              HS Version: HS3 Pro Edition 3.0.0.435

                              Plug-Ins: BLBackup, BLGData, BLRoombaWifi, Device History, EasyTrigger, ImperiHome, Nest, PHLocation, Pushover 3P, Restart, Sonos, UltraCID3, UltraWeatherWU3, Z-Wave, and Jon00 scripts.

                              Comment


                              • #30
                                Hi, I've tried to follow your excellent guide, but the Add/Include process just hangs as shown below for 10-15 minutes, and then throws a warning in the end - any idea on how to fix this ? No devices are added.


                                Add Node started...
                                Activate the 'Add to Network' (Send NodeInfo) function on the node...
                                A new node has been found and is being added...
                                Adding a new SLAVE NODE...
                                DONE - Add Node Operation is Complete.
                                Done. Node 46 Added.
                                Reloading (importing) node information...
                                Synchronizing node information with HomeSeer and creating new device(s) as necessary...
                                Synchronize nodes finished. Number of device nodes to be created/added = 1
                                Z-Wave manufacturer information for node 46, ID: 134=86H (Aeon Labs), Type: 2=2H, ID: 130=82H
                                Node: 46 Supports Class(es): ZWAVEPLUS_INFO_V2, ASSOCIATION, ASSOCIATION_GRP_INFO, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V2, VERSION_V2, CONFIGURATION, MANUFACTURER_SPECIFIC, DEVICE_RESET_LOCALLY, POWERLEVEL, WAKE_UP, BATTERY, CENTRAL_SCENE, ALARM_V2, FIRMWARE_UPDATE_MD
                                Node: 46 Controls Class(es): SWITCH_BINARY, SWITCH_MULTILEVEL_V2
                                Node 46 is Z-Wave version: Lib: 4,62 App: 23
                                Node 46 is a Z-Wave Plus node. Retrieving ZWPlus Info...
                                All associations for node 46 have been retrieved successfully, it supports associations on these groups: 1, 2, 3, 4, 5, 6, 7, 8, 9.
                                Getting Z-Wave Plus Association Group Information (9 groups) from Node 46...
                                Z-Wave Plus Association Root Group Information for Group 1 retrieved successfully from Node 46 Group Name=Lifeline, Profile is General:Reserved and the group hosts 4 event commands.
                                Z-Wave Plus Association Root Group Information for Group 2 retrieved successfully from Node 46 Group Name=On/Off (Key 1), Profile is General:Reserved and the group hosts 2 event commands.
                                Warning: Device synchronization/creation aborted by timeout or by the user.
                                Finished.


                                I'm on a an Aeon Labs Z-stick, so I tried to do an "import" after the add stopped - and it ends up like this:


                                Loading network information from your Z-Wave interface...
                                Done.
                                Synchronizing network information against HomeSeer devices...
                                Getting Z-Wave node list for network 00006179...
                                Found 38 Z-Wave nodes
                                Syncing Z-Wave nodes with device list...
                                Synchronize nodes finished. Number of device nodes to be created/added = 1
                                Node: 45 Supports Class(es): ZWAVEPLUS_INFO_V2, ASSOCIATION, ASSOCIATION_GRP_INFO, MULTI_INSTANCE_ASSOCIATION, MULTI_CHANNEL_V2, VERSION_V2, CONFIGURATION, MANUFACTURER_SPECIFIC, DEVICE_RESET_LOCALLY, POWERLEVEL, WAKE_UP, BATTERY, CENTRAL_SCENE, ALARM_V2, FIRMWARE_UPDATE_MD
                                Node: 45 Controls Class(es): SWITCH_BINARY, SWITCH_MULTILEVEL_V2
                                Node 45 is a Z-Wave Plus node. Retrieving ZWPlus Info...
                                Warning: Node 45 did not respond to a request for the Command Class Version for MULTI_INSTANCE/MULTI_CHANNEL
                                Warning: The device at node 45 should result in 2 child devices being created, but the node interrogation currently has 0. This may still result in a successful child creation.
                                Finished with Z-Wave device synchronization.

                                And then the device list shows only one line for this new node...
                                Click image for larger version

Name:	2020-04-06_22-43-23.jpg
Views:	59
Size:	7.4 KB
ID:	1375584

                                Comment

                                Working...
                                X