Announcement

Collapse
No announcement yet.

Aeotec Smart Switch 6 - parameters solved!

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

  • Aeotec Smart Switch 6 - parameters solved!

    I just added a. Aeotec Smart switch 6 to my system and while it appears to be working, I have a couple of questions regarding it.

    1. I cannot control the color on the ring, should I be able to?
    2. What is the Switch Multi-level device that was created? I thought that this was an On/Off device, I don't want this device dimming, can I disable that somehow?

    Thank you.

  • #2
    Originally posted by sonypoolplr View Post
    I just added a. Aeotec Smart switch 6 to my system and while it appears to be working, I have a couple of questions regarding it.

    1. I cannot control the color on the ring, should I be able to?
    2. What is the Switch Multi-level device that was created? I thought that this was an On/Off device, I don't want this device dimming, can I disable that somehow?

    Thank you.
    The multi-level device is the LED ring brightness. You also should have 4 other devices for the LED, red level, blue level, green level and custom color. There also should be a setting (under settings on the Z-Wave tab) to determine the mode the LED is in. By default I think it is in the "energy" mode where the color changes based on energy usage. At low current consumption it is green. There are two other modes for the LED, night light and switch state.
    Randy Prade
    Aurora, CO
    Prades.net

    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

    Comment


    • #3
      I don't see the same setting that Randy has, so if you don't see it either, you can manually set parameter 81 to 2 and then you can control the led ring.

      Cheers
      Al
      HS 3.0.0.548: 1970 Devices 1149 Events
      Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

      Comment


      • #4
        Yes I don't see that setting either. I am assuming you mean to change it at the bottom under Change Configuration Parameters? I would select 81 and put 2 in the value box. Do I leave the Value size at auto?

        Thanks.

        Comment


        • #5
          Originally posted by sonypoolplr View Post
          Yes I don't see that setting either. I am assuming you mean to change it at the bottom under Change Configuration Parameters? I would select 81 and put 2 in the value box. Do I leave the Value size at auto?

          Thanks.
          Correct.

          Cheers
          Al
          HS 3.0.0.548: 1970 Devices 1149 Events
          Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

          Comment


          • #6
            Sorry for the length of this post. What was to be simple has taken me down a rabbit hole. As is usual with Aeotec devices, results are unpredictable, slow and inconsistent. All of this is with the device within 10 feet of the Z-Net.

            First of all, you have to be very patient when including these devices, they take forever to build the child devices. I have never seen a device take this long. It was tedious when I added it a couple of days ago and the energy reporting is odd - more on that later.

            I only have one, but I excluded/included it again this morning just to check. It took equally as long as the first time on Sunday. It almost makes you think there is a problem. When I first included it this morning it took over 15 minutes to complete the process:
            Code:
            3/3/2016	 
            Mar-03 7:35:39 AM	 	Z-Wave	Done. Node 113 Added.
            Mar-03 7:35:54 AM	 	Z-Wave	Z-Wave manufacturer information for node 113, ID: 134=86H (Aeon Labs), Type: 259=103H, ID: 96=60H
            Mar-03 7:35:54 AM	 	Z-Wave	Node: 113 Supports Class(es): ZWAVEPLUS_INFO_V2, SWITCH_BINARY, SWITCH_MULTILEVEL_V2, COLOR_CONTROL, CONFIGURATION, SWITCH_ALL, METER_V2, CLOCK, ASSOCIATION, ASSOCIATION_GRP_INFO, MANUFACTURER_SPECIFIC, VERSION_V2, FIRMWARE_UPDATE_MD, POWERLEVEL
            Mar-03 7:35:54 AM	 	Z-Wave	Node: 113 Controls Class(es): DEVICE_RESET_LOCALLY, HAIL
            Mar-03 7:35:55 AM	 	Z-Wave	Node 113 is Z-Wave version: Lib: 4.05 App: 1.3
            Mar-03 7:35:55 AM	 	Z-Wave	Node 113 is a Z-Wave Plus node. Retrieving ZWPlus Info...
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113Supports Color Capability ID Red
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113Supports Color Capability ID Green
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113Supports Color Capability ID Blue
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_V, Scale is INSTANT
            Mar-03 7:36:55 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_A, Scale is INSTANT
            Mar-03 7:36:57 AM	 	Z-Wave	Root Node Device Node 113 Z-Wave Aeon Labs Switch Binary Node 113 was created for node 113 on network 003D3409
            Mar-03 7:37:27 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:37:57 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:38:27 AM	 	Z-Wave	Associating Aeon Labs device Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root (113) to HomeSeer
            Mar-03 7:38:59 AM	 	Z-Wave	Assigning return route from node 1 to Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:39:00 AM	 	Z-Wave	Configuring Aeon Labs device Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root (113) to report Meter and Sensor data in Groups 1-3 to HomeSeer.
            Mar-03 7:39:02 AM	 	Z-Wave	Configuring Aeon Labs device Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root (113) to report Group 1 data at 10 minute intervals.
            Mar-03 7:39:03 AM	 	Z-Wave	Configuring Aeon Labs device Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root (113) to report Group 2 data at 5 minute intervals.
            Mar-03 7:39:35 AM	 	Z-Wave	The clock on Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root is currently set to today being Thursday at 7:39.
            Mar-03 7:39:35 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:40:05 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:40:37 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:41:07 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:41:38 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:42:09 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:42:40 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:43:10 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:43:42 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:44:12 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:44:43 AM	 	Z-Wave	Adding Node 113 Z-Wave kW Hours as an Energy tracking device.
            Mar-03 7:44:43 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:45:13 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:45:44 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 10 Seconds on device Node 113 Z-Wave kW Hours
            Mar-03 7:45:45 AM	 	Z-Wave	Adding Node 113 Z-Wave Watts as an Energy tracking device.
            Mar-03 7:45:45 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:46:15 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:46:46 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 24 Seconds on device Node 113 Z-Wave Watts
            Mar-03 7:46:48 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:47:18 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:47:48 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 28 Seconds on device Node 113 Z-Wave Volts
            Mar-03 7:47:50 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:48:20 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:48:50 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 30 Seconds on device Node 113 Z-Wave Amperes
            Mar-03 7:48:51 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:49:21 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:49:51 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 32 Seconds on device Node 113 Z-Wave Switch Binary
            Mar-03 7:49:53 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:50:23 AM	 	Z-Wave	Getting association information for Node 113 Z-Wave Aeon Labs Switch Binary Node 113 Root
            Mar-03 7:50:53 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 40 Seconds on device Node 113 Z-Wave Switch Multilevel
            Mar-03 7:50:54 AM	 	Z-Wave	10 out of 10 Child devices of node 113 were created successfully.
            Mar-03 7:51:07 AM	 	Z-Wave	Device: Node 113 Z-Wave kW Hours Set to 0.587 (0.587 kW Hours)
            Mar-03 7:51:10 AM	 	Z-Wave	Device: Node 113 Z-Wave Switch Binary Set to ON
            It also had to try multiple "Getting association information. It also did not create all of the child devices and attempted to set polling on devices.



            But it did create all of the same setting options.




            A "Rescan" generated all of the child devices.



            Code:
            Mar-03 7:58:12 AM	 	Z-Wave	Node: 113 Supports Class(es): ZWAVEPLUS_INFO_V2, SWITCH_BINARY, SWITCH_MULTILEVEL_V2, COLOR_CONTROL, CONFIGURATION, SWITCH_ALL, METER_V2, CLOCK, ASSOCIATION, ASSOCIATION_GRP_INFO, MANUFACTURER_SPECIFIC, VERSION_V2, FIRMWARE_UPDATE_MD, POWERLEVEL
            Mar-03 7:58:12 AM	 	Z-Wave	Node: 113 Controls Class(es): DEVICE_RESET_LOCALLY, HAIL
            Mar-03 7:58:12 AM	 	Z-Wave	Node 113 is Z-Wave version: Lib: 4.05 App: 1.3
            Mar-03 7:58:12 AM	 	Z-Wave	Node 113 is a Z-Wave Plus node. Retrieving ZWPlus Info...
            Mar-03 7:58:13 AM	 	Z-Wave	Getting association information for node 113
            Mar-03 7:58:14 AM	 	Z-Wave	Node 113 Association Group 1 can have 5 associations, and currently has 1
            Mar-03 7:58:14 AM	 	Z-Wave	Node 113 Association Group 2 can have 5 associations, and currently has 0
            Mar-03 7:58:14 AM	 	Z-Wave	All associations for node 113 have been retrieved successfully, it supports associations on these groups: 1, 2.
            Mar-03 7:58:14 AM	 	Z-Wave	Getting Z-Wave Plus Association Group Information (2 groups) from Node 113...
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113Supports Color Capability ID Red
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113Supports Color Capability ID Green
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113Supports Color Capability ID Blue
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_V, Scale is INSTANT
            Mar-03 7:58:47 AM	 	Z-Wave	Node 113 Meter is Supported for Electric_meter, Type ELECTRIC_A, Scale is INSTANT
            Mar-03 7:58:48 AM	 	Z-Wave	Configuring Aeon Labs device HomeSeer Test New seitch Root (113) to report Meter and Sensor data in Groups 1-3 to HomeSeer.
            Mar-03 7:58:51 AM	 	Z-Wave	Configuring Aeon Labs device HomeSeer Test New seitch Root (113) to report Group 1 data at 10 minute intervals.
            Mar-03 7:58:52 AM	 	Z-Wave	Configuring Aeon Labs device HomeSeer Test New seitch Root (113) to report Group 2 data at 5 minute intervals.
            Mar-03 7:59:04 AM	 	Z-Wave	10 out of 10 Child devices of node 113 were created successfully.
            The whole process was such a mess, I decided to exclude the device, restart the controller and try again. This time I included it "Non Secure".

            This time it still took as long, still tried multiple times to get association information and generated warnings. It also still attempted to set polling intervals on the devices it created.

            Code:
            Mar-03 8:15:24 AM	 	Z-Wave	Done. Node 114 Added.
            Mar-03 8:16:00 AM	 	Z-Wave	Node: 114 Supports Class(es): ZWAVEPLUS_INFO_V2, SWITCH_BINARY, SWITCH_MULTILEVEL_V2, COLOR_CONTROL, CONFIGURATION, SWITCH_ALL, METER_V2, CLOCK, ASSOCIATION, ASSOCIATION_GRP_INFO, MANUFACTURER_SPECIFIC, VERSION_V2, FIRMWARE_UPDATE_MD, POWERLEVEL
            Mar-03 8:16:00 AM	 	Z-Wave	Node: 114 Controls Class(es): DEVICE_RESET_LOCALLY, HAIL
            Mar-03 8:16:13 AM	 	Z-Wave Warning	Node 114 supports the MANUFACTURER_SPECIFIC command class but manufacturer information was not obtained. Cannot continue with this node.
            Mar-03 8:16:39 AM	 	Z-Wave Warning	Error getting version information for node 114, Send failed.
            Mar-03 8:16:39 AM	 	Z-Wave	Node 114 is a Z-Wave Plus node. Retrieving ZWPlus Info...
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114Supports Color Capability ID Red
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114Supports Color Capability ID Green
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114Supports Color Capability ID Blue
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114 Meter is Supported for Electric_meter, Type ELECTRIC_V, Scale is INSTANT
            Mar-03 8:17:24 AM	 	Z-Wave	Node 114 Meter is Supported for Electric_meter, Type ELECTRIC_A, Scale is INSTANT
            Mar-03 8:17:26 AM	 	Z-Wave	Root Node Device Node 114 Z-Wave Sigma Switch Binary Node 114 was created for node 114 on network 003D3409
            Mar-03 8:18:27 AM	 	Z-Wave	The clock on Node 114 Z-Wave Sigma Switch Binary Node 114 Root is currently set to today being Thursday at 8:18.
            Mar-03 8:18:27 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:18:57 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:19:29 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:19:59 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:20:31 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:21:01 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:21:33 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:22:03 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:22:34 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:23:04 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:23:36 AM	 	Z-Wave	Adding Node 114 Z-Wave kW Hours as an Energy tracking device.
            Mar-03 8:23:36 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:24:06 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:24:36 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 44 Seconds on device Node 114 Z-Wave kW Hours
            Mar-03 8:24:37 AM	 	Z-Wave	Adding Node 114 Z-Wave Watts as an Energy tracking device.
            Mar-03 8:24:37 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:25:08 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:25:38 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 46 Seconds on device Node 114 Z-Wave Watts
            Mar-03 8:25:39 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:26:09 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:26:39 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 48 Seconds on device Node 114 Z-Wave Volts
            Mar-03 8:26:41 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:27:11 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:27:41 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 52 Seconds on device Node 114 Z-Wave Amperes
            Mar-03 8:27:42 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:28:13 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:28:43 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 54 Seconds on device Node 114 Z-Wave Switch Binary
            Mar-03 8:28:44 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:29:14 AM	 	Z-Wave	Getting association information for Node 114 Z-Wave Sigma Switch Binary Node 114 Root
            Mar-03 8:29:44 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 56 Seconds on device Node 114 Z-Wave Switch Multilevel
            Mar-03 8:29:46 AM	 	Z-Wave	10 out of 10 Child devices of node 114 were created successfully.
            It did create all of the child devices (except for an incomplete LED multilevel control), but a completely different settings menu.





            You can also see that HomeSeer added polling intervals for the 4 energy devices, all of which report and for the switch and LED level control.




            This is proving to be troublesome. I am going to exclude the device, restart everything and try to include it a third time, this time I will do it in the normal "Secure" mode. I'll post back here in a bit.
            Randy Prade
            Aurora, CO
            Prades.net

            PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

            Comment


            • #7
              Hey Randy, which version of the z-wave plugin are you running? My results are quite a bit of different than your. I'm running .53. It only took a minute to include mine and create all of the child devices. Mine also did not setup polling on the child devices.

              Cheers
              Al
              HS 3.0.0.548: 1970 Devices 1149 Events
              Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

              Comment


              • #8
                I am running v .55 of the plugin, and it didn't take that long for the devices to be created. I used the Add/Include a Node which I am assuming is the secure mode, and I didn't get the LED mode in the settings. I am now concerned about the reading that the unit is putting out. I am far from being an engineer, but I thought W = V x A. I am currently seeing 123v, 3.4a which should be 418w, but the sensor is showing 212w. Am I correct in my thoughts?

                Thanks

                Comment


                • #9
                  OK , I restarted my Z-Net and HomeSeer. Why? Because I have noticed that the Z-Net can become troublesome and unresponsive, when multiple exclusions and inclusions are performed back to back. I wanted to see if this device took as long to include, had association problems or any other problems after starting "fresh". It took just as long, had the same multiple attempts to get association information and created polling intervals for devices that do not require polling. I really think there is something wrong in the process, it shouldn't take 15 minutes or more to include a device and generate child nodes. There is no need to poll devices that generate reports.

                  Code:
                  Mar-03 9:15:29 AM	 	Z-Wave	Done. Node 115 Added.
                  Mar-03 9:15:34 AM	 	Z-Wave	Z-Wave manufacturer information for node 115, ID: 134=86H (Aeon Labs), Type: 259=103H, ID: 96=60H
                  Mar-03 9:15:34 AM	 	Z-Wave	Node: 115 Supports Class(es): ZWAVEPLUS_INFO_V2, SWITCH_BINARY, SWITCH_MULTILEVEL_V2, COLOR_CONTROL, CONFIGURATION, SWITCH_ALL, METER_V2, CLOCK, ASSOCIATION, ASSOCIATION_GRP_INFO, MANUFACTURER_SPECIFIC, VERSION_V2, FIRMWARE_UPDATE_MD, POWERLEVEL
                  Mar-03 9:15:34 AM	 	Z-Wave	Node: 115 Controls Class(es): DEVICE_RESET_LOCALLY, HAIL
                  Mar-03 9:15:35 AM	 	Z-Wave	Node 115 is Z-Wave version: Lib: 4.05 App: 1.3
                  Mar-03 9:15:35 AM	 	Z-Wave	Node 115 is a Z-Wave Plus node. Retrieving ZWPlus Info...
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115Supports Color Capability ID Red
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115Supports Color Capability ID Green
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115Supports Color Capability ID Blue
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115 Meter is Supported for Electric_meter, Type ELECTRIC_V, Scale is INSTANT
                  Mar-03 9:16:35 AM	 	Z-Wave	Node 115 Meter is Supported for Electric_meter, Type ELECTRIC_A, Scale is INSTANT
                  Mar-03 9:16:37 AM	 	Z-Wave	Root Node Device Node 115 Z-Wave Aeon Labs Switch Binary Node 115 was created for node 115 on network 003D3409
                  Mar-03 9:17:07 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:17:37 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:18:08 AM	 	Z-Wave	Associating Aeon Labs device Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root (115) to HomeSeer
                  Mar-03 9:18:40 AM	 	Z-Wave	Assigning return route from node 1 to Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:18:41 AM	 	Z-Wave	Configuring Aeon Labs device Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root (115) to report Meter and Sensor data in Groups 1-3 to HomeSeer.
                  Mar-03 9:18:43 AM	 	Z-Wave	Configuring Aeon Labs device Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root (115) to report Group 1 data at 10 minute intervals.
                  Mar-03 9:18:44 AM	 	Z-Wave	Configuring Aeon Labs device Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root (115) to report Group 2 data at 5 minute intervals.
                  Mar-03 9:19:16 AM	 	Z-Wave	The clock on Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root is currently set to today being Thursday at 9:19.
                  Mar-03 9:19:16 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:19:46 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:20:18 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:20:48 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:21:19 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:21:49 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:22:21 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:22:51 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:23:23 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:23:53 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:24:24 AM	 	Z-Wave	Adding Node 115 Z-Wave kW Hours as an Energy tracking device.
                  Mar-03 9:24:24 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:24:55 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:25:25 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 10 Seconds on device Node 115 Z-Wave kW Hours
                  Mar-03 9:25:26 AM	 	Z-Wave	Adding Node 115 Z-Wave Watts as an Energy tracking device.
                  Mar-03 9:25:26 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:25:56 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:26:26 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 24 Seconds on device Node 115 Z-Wave Watts
                  Mar-03 9:26:28 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:26:58 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:27:28 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 28 Seconds on device Node 115 Z-Wave Volts
                  Mar-03 9:27:29 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:28:00 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:28:30 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 30 Seconds on device Node 115 Z-Wave Amperes
                  Mar-03 9:28:32 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:29:02 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:29:32 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 32 Seconds on device Node 115 Z-Wave Switch Binary
                  Mar-03 9:29:33 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:30:03 AM	 	Z-Wave	Getting association information for Node 115 Z-Wave Aeon Labs Switch Binary Node 115 Root
                  Mar-03 9:30:33 AM	 	Z-Wave	Setting a polling interval of 20 Minutes, 40 Seconds on device Node 115 Z-Wave Switch Multilevel
                  Mar-03 9:30:33 AM	 	Z-Wave	10 out of 10 Child devices of node 115 were created successfully.
                  It still took 15 minutes. It created all of the child devices and they all work correctly





                  It created the same settings page as my first attempt above





                  It failed to create associations and will not retrieve any.






                  The polling was once again set during inclusion





                  I think there is something seriously flawed in the way this device is included.
                  Last edited by rprade; March 3rd, 2016, 12:18 PM.
                  Randy Prade
                  Aurora, CO
                  Prades.net

                  PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                  Comment


                  • #10
                    One of the reasons I wanted to try this device was to monitor an individual item on a circuit that shares two kitchen appliances.

                    About energy reporting. There is a setting provided when the full settings page is generated at inclusion




                    This setting will provide instant reports when the wattage changes and seems to bypass scheduled reporting for wattage. Unfortunately, it will report the maximum inrush of a device, not the average wattage. My coffee pot warmer runs at about 160 watts and cycles on and off several times in a minute. With the box above checked, it will report 900+ watts when the warmer comes on, then about 400 watts a few seconds later, then 0. My Brultech monitor correctly reports the average wattage and cycling of the warmer.


                    Here is a graph from the GEM, the brew cycle is about 900 watts. Because our house was wired to share the counter outlet and the microwave outlet (stupid) there are spikes in the graph from warming some breakfast while the coffee is brewing/warming. The two devices running at full power at the same time is right at the threshold for the circuit (20A 2400 watts).






                    If the box is not selected for reporting if wattage value changes, the Aeotec never reports the warmer running, even at 30 second reporting intervals. It would be better if the Aeotec could average wattage for the period between reports. Since it is reporting only at that instant, it is possible to miss a fluctuating load like the coffee warmer cycling. It seems to me it should occasionally report the warmer running, but it never catches it.

                    The Amps and Watts child devices are also not in sync. they are sampled at intervals, but not at the same moment. This device will not work for what I intended it to do. The GEM provides the kind of energy snapshot of a circuit that is truly useful, the Aeotec is not good at monitoring intermittent duty resistive devices.
                    Randy Prade
                    Aurora, CO
                    Prades.net

                    PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                    Comment


                    • #11
                      Originally posted by sparkman View Post
                      Hey Randy, which version of the z-wave plugin are you running? My results are quite a bit of different than your. I'm running .53. It only took a minute to include mine and create all of the child devices. Mine also did not setup polling on the child devices.

                      Cheers
                      Al
                      I'm running .61. Either it or the one just before was supposed to fix some problems with Aeon smart switch device creation. There may be some problems with this beta.
                      Randy Prade
                      Aurora, CO
                      Prades.net

                      PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                      Comment


                      • #12
                        I'm really not in the mood to file a Bugzilla, I guess I will shelve this device for now and watch and wait.

                        It is hard to figure out whether these problems are caused by Aeon or the way HST includes Aeon devices, but For more than a year, each new Aeon device has been very challenging to get to work correctly.

                        I had the same problems with the first Aeon Smart Switch, both the Multi-sensor 5 and 6, the Aeon Smart Strip and now this new Smart Switch.

                        0 for 5 is not good. Most of the devices were eventually able to be included correctly, but each was initially a frustrating and sometimes futile process.
                        Randy Prade
                        Aurora, CO
                        Prades.net

                        PHLocation - Pushover - EasyTrigger - UltraECM3 - Ultra1Wire3 - Arduino

                        Comment


                        • #13
                          Originally posted by rprade View Post
                          This setting will provide instant reports when the wattage changes and seems to bypass scheduled reporting for wattage. Unfortunately, it will report the maximum inrush of a device, not the average wattage. My coffee pot warmer runs at about 160 watts and cycles on and off several times in a minute. With the box above checked, it will report 900+ watts when the warmer comes on, then about 400 watts a few seconds later, then 0. My Brultech monitor correctly reports the average wattage and cycling of the warmer.

                          If the box is not selected for reporting if wattage value changes, the Aeotec never reports the warmer running, even at 30 second reporting intervals. It would be better if the Aeotec could average wattage for the period between reports. Since it is reporting only at that instant, it is possible to miss a fluctuating load like the coffee warmer cycling. It seems to me it should occasionally report the warmer running, but it never catches it.

                          The Amps and Watts child devices are also not in sync. they are sampled at intervals, but not at the same moment. This device will not work for what I intended it to do. The GEM provides the kind of energy snapshot of a circuit that is truly useful, the Aeotec is not good at monitoring intermittent duty resistive devices.
                          This is consistent with what I'm seeing with these particular devices and also with other Aeotec devices, although a lot of times it misses the in-rush spike (see my graph in the Fridge Monitoring thread I started a few days ago). If it reported it consistently, it would be ok, it's the inconsistency that makes it hard to account for. Might be worth starting a ticket with Aeotec as these are things they should be able to adjust for in a firmware update.

                          Cheers
                          Al
                          HS 3.0.0.548: 1970 Devices 1149 Events
                          Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

                          Comment


                          • #14
                            Originally posted by rprade View Post
                            I'm really not in the mood to file a Bugzilla, I guess I will shelve this device for now and watch and wait.

                            It is hard to figure out whether these problems are caused by Aeon or the way HST includes Aeon devices, but For more than a year, each new Aeon device has been very challenging to get to work correctly.

                            I had the same problems with the first Aeon Smart Switch, both the Multi-sensor 5 and 6, the Aeon Smart Strip and now this new Smart Switch.

                            0 for 5 is not good. Most of the devices were eventually able to be included correctly, but each was initially a frustrating and sometimes futile process.
                            The only ones I've had trouble with were the HD switches when they first came out, all others were relatively painless. I think part of the issue is that Aeon is not consistent with their products, so HS has to account for each device differently.

                            Cheers
                            Al
                            HS 3.0.0.548: 1970 Devices 1149 Events
                            Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

                            Comment


                            • #15
                              FWIW, there is a bug with the latest z-wave plug-in and the second generation Smart Switch. 2nd generation doesn't support the RGB stuff that the 6th generation does, but sadly the latest version of the plug-in thinks the 2nd gen is the 6th gen. As a result, when you try to check Z-Wave settings, it takes 60+ seconds until the plug-in throws an error that it can't call up the RGB settings.

                              I filed a Bugzilla, but (of course) crickets. It's rather unfortunate, because I'm Leary of upgrading to the new Beta to get functionality for the new smart switch, because it makes setting the settings on the former generation immensely difficult.

                              Sigh, the life of a HomeSeer user. :\

                              Comment

                              Working...
                              X