Aeotec Nano Dual as a virtual switch

Devices & Integrations Connected Things
1

I have one Aeotec Nano Dual Switch behind a double gang controlling 2x Hue lights. I knew that you could turn off live-load control in the Aeotec switches using a tweaker; however when I modify that parameter, the switch simply stops sending status updates to smart things.

Ideally I’d like to be able to flick the external physical switch and have smart things turn off the hue lights without literally cutting the live load and disconnecting the lights completely. I live in Australia, our options for remotes are either the ikea remote or the lifx stick on remote. We don’t even have the full Hue remote range last I checked (which I wouldn’t want anyway as all my automations are on an ST3)

I have tried adding the hub ID to association groups 3 and 4, which didn’t change anything. I tried adding the switch itself to the association groups as well which unsurprisingly didn’t do anything either. Then I thought what if I added a virtual switch to act as a controller? Well the virtual switches don’t darn well have a Network ID apparently!

I am extremely new to all this. I have poured over the manuals multiple times. I have a feeling this is simply a case of me not knowing what exactly it is I don’t know. Any guidance would be much appreciated!

Til then I suppose I’m going back to Dumb Light+

2

Can I please get some help on this? I asked on reddit as well but everyone there is answering the question they think they thought I meant instead of the question I asked. I’ve seen similar questions/answers on here, so I know there are people that have a similar set up, however they were from back before edge drivers were introduced and none of their steps are replicable to me now.

I’m just super frustrated by this situation! So if you have an aeotec switch connected to smart lights your input would be extremely helpful.

3

Hi @Jessa

I guess you mean parameter 122 (0x7A) with value = 2

0x7A (122) Set the control destination for external switch
1 = control the output loads of itself.
2 = control the other nodes.
3 = control the output loads of itself and other nodes

If when you do this it stops sending reports to the hub then, as you say, it should work by associating the groups 3 and 4 to the Hub.

When you associated groups 3 and 4 to the hub, did you also set the parameters 120 (0x78) and 121 (0x79) to a value other than 0? to value 1 for example.

Group 3 [1,5] Single
Cast
Send Basic Set (enabled by Configuration parameter 0x51)
to the associated nodes in Group 3 when the external switch
S1 is operated.
Note: The Switch Mode of external switch S1 should be identified
successfully, which means that the value of Configuration
parameter 0x78 should be non-zero, then the Basic Set can be sent
to the associated nodes in Group 3 via triggering the S1 switch.

Group 4 [1,5] Single
Cast
Send Basic Set (enabled by Configuration parameter 0x52)
to the associated nodes in Group 4 when the external switch
S2 is operated.
Note: The Switch Mode of external switch S2 should be identified
successfully, which means that the value of Configuration
parameter 0x79 should be non-zero, then the Basic Set can be sent
to the associated nodes in Group 3 via triggering the S2 switch.

What you want to do is the same as if you physically disconnect output 1 and 2 of the switch and connect them directly to line L.

This is much easier, but I don’t know if it is legal in australia to install a light bulb without a switch to control it.

image
image712×607 26 KB

My Z-wave Switch and Child Mc driver allows you to optionally and temporarily create a virtual device to easily configure parameters and association groups and test without having to change drivers.

4

thank you for the reply @Mariano_Colmenarejo !!

yes I have adjusted the parameters as you’ve described. it’s 122 and 123 on the dual switch (122 for S1 & 123 for S2). In aus a permanent live is only possible on a specific isolated circuit which is for emergency things like alarms. I asked my electrician, he looked at me like I was insane haha

do you know if I should have to add anything to the ass. groups 3 & 4 to have it send the basic set to the hub? or should it do it by default? I know you can, for example, use AGs to mirror two switches directly by referencing network IDs in hex.

I’ll try your driver after work tomorrow and let you know how that goes.

5

You need set parameters 120 and 121 to value non-zero, 0 is the default value.
Set to value = 1 for toggle switch

6

yes those are both set to 3 at the moment for bell switch; the nano identifies that itself on install.

7

Screenshot_20230428-192641
Screenshot_20230428-1926411440×3120 392 KB

you can see here parameters 81/82 are set to 1, which is basic set. Parameters 120/121 are both set to 3, which is momentary (or if you are a redstone nerd, a t flipflop lol). Parameters 122/123 are set to 2 which should be groups but not live control.

When I push the physical switch it does nothing; the status of the switch in smart things does not change between on and off. When I turn it off in smart things, the live load is modified.

Are there any other steps you can think I might have to take? Because literally all I’ve done is adjust these parameters and make a couple routines for the bulbs to turn off when the status of the switch is changed.

8

Hi @Jessa

If you haven’t, now you have to associate groups 3 and 4 with the hub (node 1)

9

@Mariano_Colmenarejo See I knew I was missing a step! Can you tell me how to do that?

10

In the configurator, preferences, choose the option “Device Association Groups Scan” to see what associations and groups the device has made. Close the app, clear the cache and reopen the app to show the new profile if it does so automatically.
On this screen you will see the node ID of the Hub in hexadecimal, normally =1

To configure the groups now choose the option: "Device Association Groups Configure".

  • Write the group number: 3

  • Write the node of the hub: 1

  • In this case, you can leave node endpoint blank

  • Choose Single channel association

  • Select “Set” in Goup command option and press the action button.

  • Repeat the same for the group: 4

You can choose the Get option to verify that the device has accepted the association.

1 Like
11

Screenshot_20230428-212356
Screenshot_20230428-2123561440×3120 331 KB

Still no luck :frowning:

12

If you want to send me the logs with the CLI when you click on the physical switch, then I’ll look at it to see what the device is sending.

now i have to quit

14

Thanks for the help! Here’s the log. Below I have logs for flicking the physical switch twice (“on” and “off” supposedly) and also the app power button, off and back on. My guess is the hub/driver is receiving the basic set, it just doesn’t know what to do with it? That makes two of us.

Physical Log

2023-04-28T11:53:35.198040970+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:53:35.205559303+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=0}, cmd_class=“BASIC”, cmd_id=“SET”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-04-28T11:53:35.213665636+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:53:39.081605305+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:53:39.090270638+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“SET”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-04-28T11:53:39.120934305+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled

App Log

2023-04-28T11:55:00.709823010+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler capability
2023-04-28T11:55:00.722876344+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(510caa6d) queued for radio transmission: CC:Switch Binary, CID:0x01
2023-04-28T11:55:00.730824677+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“main”,“positional_args”:{}}
2023-04-28T11:55:00.733397344+00:00 TRACE Z-Wave Switch and Child Mc Found CapabilityCommandDispatcher handler in zwave_switch
2023-04-28T11:55:00.734671010+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_off_handler in main driver >>>>>>>
2023-04-28T11:55:00.735864010+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_set_helper in main driver >>>>>>>
2023-04-28T11:55:00.738727677+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> sending Z-Wave command: {args={duration=0, target_value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“SET”, dst_channels={1}, encap=“AUTO”, payload=“\x00\x00”, src_channel=0, version=2}
2023-04-28T11:55:00.756896677+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:00.761792010+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:00.822572011+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(510caa6d) transmit status: TRANSMIT_COMPLETE_OK
2023-04-28T11:55:01.916389011+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(d7dde217) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-04-28T11:55:01.919580011+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={1}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-04-28T11:55:01.956324011+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:01.960742011+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:55:01.969055011+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=0}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x00”, src_channel=1, version=1}
2023-04-28T11:55:02.045205754+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-04-28T11:55:02.048922188+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-04-28T11:55:02.056413715+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-04-28T11:55:02.070503051+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(d7dde217) transmit status: TRANSMIT_COMPLETE_OK
2023-04-28T11:55:02.077965142+00:00 WARN Z-Wave Switch and Child Mc Attempted to generate event for bde79027-4d83-4743-a28b-3eba8efbcf81.main but it does not support capability Switch
2023-04-28T11:55:02.089532239+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:02.120665804+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:55:02.121511894+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x00”, src_channel=1, version=1}
2023-04-28T11:55:02.146839217+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-04-28T11:55:02.147670966+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-04-28T11:55:02.153217405+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-04-28T11:55:02.166252919+00:00 WARN Z-Wave Switch and Child Mc Attempted to generate event for bde79027-4d83-4743-a28b-3eba8efbcf81.main but it does not support capability Switch
2023-04-28T11:55:02.167766009+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:04.329496335+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler capability
2023-04-28T11:55:04.347121810+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(874145be) queued for radio transmission: CC:Switch Binary, CID:0x01
2023-04-28T11:55:04.360047936+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2023-04-28T11:55:04.363402279+00:00 TRACE Z-Wave Switch and Child Mc Found CapabilityCommandDispatcher handler in zwave_switch
2023-04-28T11:55:04.367566027+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_on_handler in main driver >>>>>>>
2023-04-28T11:55:04.369614050+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_set_helper in main driver >>>>>>>
2023-04-28T11:55:04.379644730+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> sending Z-Wave command: {args={duration=0, target_value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“SET”, dst_channels={1}, encap=“AUTO”, payload=“\xFF\x00”, src_channel=0, version=2}
2023-04-28T11:55:04.390359084+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:04.397468304+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:04.431913851+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(874145be) transmit status: TRANSMIT_COMPLETE_OK
2023-04-28T11:55:05.140502969+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:55:05.146204151+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=255}, cmd_class=“BASIC”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\xFF”, src_channel=1, version=1}
2023-04-28T11:55:05.238889471+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-04-28T11:55:05.240167443+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-04-28T11:55:05.241379048+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-04-28T11:55:05.252304508+00:00 WARN Z-Wave Switch and Child Mc Attempted to generate event for bde79027-4d83-4743-a28b-3eba8efbcf81.main but it does not support capability Switch
2023-04-28T11:55:05.253628170+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:05.381362005+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(54a9cc5b) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-04-28T11:55:05.388121717+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={1}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-04-28T11:55:05.389727853+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled
2023-04-28T11:55:05.552821692+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(54a9cc5b) transmit status: TRANSMIT_COMPLETE_OK
2023-04-28T11:55:05.579896556+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-04-28T11:55:05.580754985+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\xFF”, src_channel=1, version=1}
2023-04-28T11:55:05.627233880+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-04-28T11:55:05.628600896+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-04-28T11:55:05.629852188+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: 53f9ce10-31fc-486b-8173-0c2d3fe2521e [0A] (Aeotec Smart Switch Gen5)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-04-28T11:55:05.654510511+00:00 WARN Z-Wave Switch and Child Mc Attempted to generate event for bde79027-4d83-4743-a28b-3eba8efbcf81.main but it does not support capability Switch
2023-04-28T11:55:05.656287733+00:00 DEBUG Z-Wave Switch and Child Mc Aeotec Smart Switch Gen5 device thread event handled

Edit: deleted cause I pasted an --all log instead of the driver specific log because I’m a dummy.

15

Hi @Jessa

If you have tried switch -1, I think the problem is that the device sends the basic Set command and the driver expects a basic Report.
It also arrives as source channel=0 and the driver needs to identify source channel 1 or 2.

Could you now try switch-2 to see which source channel sends to the driver?

This worked with the DTH?

16

S2 doesn’t send anything at all. Like even in --all logs, nothing comes through. I’m going to switch it back to the aeotec provided driver to see if that changes anything.

17

Hi @Jessa

With association groups, a Basic Set On or Off command is sent directly to the associated device, switch, bulb…
The hub, driver, does not execute the Basic Set commands, it waits for a Basic Report command, for example to emit a device status event.

I think that if instead of Hue, zigbee bulbs, you used Zwave bulbs, you could associate a bulb to group 3 and another to group 4, then they would directly execute the commands sent by the switch to groups 3 and 4