They require two hot conductors, one for the device, and the other for the load, since there isn't a second hot bridged terminal on the device itself, two separate hots need to be supplied, total pita...
They don't need to be different though. Its the difference of volt free or not. The advantage of the new one is that you can control anything not just the circuit that it is supplied from? That's a plus in my book. You just need a bit of flex link if you want to control the same circuit, simple.
Thats not really anytning you will run into, the thought process behind this device is that the controlled circuit can be a different voltage than the device supply, however i will contend that this use case is an edge case and the majority of users will use the same supply for the device and the load.
They are simply difficult to install, I would not recommend them for a whole house deployment given the price and the dual hot requirement...
1 Like
@BorrisTheCat - I see the pluses of the Nano but , it requires 2 14g jumpers that barely fit just to make it work for the 90% of its use cases. I could see using it for some situations but not for my light switches. Plus the price is high.
Anyway - back to the Aeotec Micro, I realize the confusion. Here is a recap:
I used the built in Driver and it just caused issues. It would not allow control within Hubuitat and it created child switches that didn't work. So I had to create virtual switches, but those have the status issue. I had to use the Clean Driver to get rid of the child devices. I then tried the driver ''DSC17103 Micro' driver from another user (their name escapes me). It works as good as I've had. It works through Hubitat and Alexa, so long as I do not flip the manual switch. The status does not update in Hubitat. I then tried the Z-Wave update driver, but it does not appear to work on Micro switches. There is no response.
Anyway - unless there is another option, I am hoping someone can edit the drivers to update Parameter 80. That sounds like that is the problem. Although - from what I can tell from the code, it IS trying to update the parameter.
I'm going to try Aeotec again as well and see if they have a parameter update tool. I think I have to buy a Aeotec Z stick though.
Not sure why this is so hard. The Wink hub never had an issue with these.
Tagging @mike.maxwell
@ahavelind - something else is wrong. I had one of these working fine in Hubitat with the built-in driver. I think @mike.maxwell may still have them behind his Picos.
1 Like
agree, I have two samples of this device, both of them work correctly.
we have a tool that allows setting and reading zwave device parameters, see this post:
2 Likes
I tried the Parameter update tool. I mentioned this in an earlier reply - I know you guys get tons of emails. Tried several times, but the Parameter tool does not respond or feedback any information that it is doing anything with either of my Aeotec dual Micros. No response what so ever. Tried it on the Enerwave dual switches as well, but if I recall you said the Z-Wave update tool was only for Aeotec devices. Not work anyway.
When you say work correctly - how do you use it? Do you use the manual wall switch?
Several questions:
-
By parameter tool, do you mean @mike.maxwell's "Basic Z-Wave Tool"? Where are you looking for the response to appear? It will appear in the logs, not on the driver page.
-
Basic Z-Wave Tool isn't restricted to any specific z-wave device. But parameters and their values will differ quite a bit between devices. You cannot use Aeotec dual micro z-wave parameters on an Enerwave dual relay.
OK - I will look at the logs this time and let you know what I see.
thanks
Well - that does work better 
but it appears Parameter 80 is already set to 2.
Some interesting feedback when the driveway light turns on though. FYI - I pushed all 4 buttons so that the logs showed all the pertinent data. What do you make of this? Second to last line item...
dev:12020-06-04 08:59:58.565 pm infoCommandClassReport- class:0x60, version:2
dev:12020-06-04 08:59:58.504 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:12020-06-04 08:59:58.442 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:12020-06-04 08:59:58.378 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:12020-06-04 08:59:58.316 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:12020-06-04 08:59:58.262 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:5, nodes:[1]
dev:12020-06-04 08:59:58.035 pm infoCommandClassReport- class:0x86, version:1
dev:12020-06-04 08:59:57.504 pm infoCommandClassReport- class:0x72, version:1
dev:12020-06-04 08:59:56.990 pm infoCommandClassReport- class:0x85, version:1
dev:12020-06-04 08:59:56.466 pm infoCommandClassReport- class:0x70, version:1
dev:12020-06-04 08:59:55.954 pm infoCommandClassReport- class:0x27, version:1
dev:12020-06-04 08:59:55.437 pm infoCommandClassReport- class:0x32, version:2
dev:12020-06-04 08:59:54.943 pm infoCommandClassReport- class:0x31, version:3
dev:12020-06-04 08:59:54.463 pm infoCommandClassReport- class:0x25, version:1
dev:2922020-06-04 08:59:20.041 pm errorjava.lang.IndexOutOfBoundsException: toIndex = 8 on line 235 (parse)
dev:2922020-06-04 08:59:19.942 pm debugParsed MeterReport(scale: 0, rateType: 1, scale2: 0, deltaTime: 600, previousMeterValue: [0, 2, 46, 229], meterType: 1, precision: 3, size: 4, meterValue: [0, 2, 46, 243]) to [['name':'energy', 'value':143.091, 'unit':'kWh'], hubitat.device.HubMultiAction@13a5628]
dev:12020-06-04 08:58:50.839 pm infoVersionReport- applicationVersion:1.7
dev:12020-06-04 08:58:50.837 pm infoVersionReport- zWaveProtocolVersion:2.78
dev:12020-06-04 08:58:50.835 pm infoVersionReport- zWaveLibraryType:Routing Slave
dev:12020-06-04 08:58:19.923 pm infoConfigurationReport- parameterNumber:80, size:1, value:2
dev:12020-06-04 08:58:19.834 pm infoConfigurationReport- parameterNumber:254, size:2, value:0
dev:12020-06-04 08:58:19.772 pm infoConfigurationReport- parameterNumber:252, size:1, value:0
dev:12020-06-04 08:58:18.169 pm infoConfigurationReport- parameterNumber:200, size:1, value:0
dev:12020-06-04 08:58:15.646 pm infoConfigurationReport- parameterNumber:120, size:1, value:1
dev:12020-06-04 08:58:15.416 pm infoConfigurationReport- parameterNumber:113, size:4, value:600
dev:12020-06-04 08:58:15.360 pm infoConfigurationReport- parameterNumber:112, size:4, value:600
dev:12020-06-04 08:58:15.308 pm infoConfigurationReport- parameterNumber:111, size:4, value:600
dev:12020-06-04 08:58:15.023 pm infoConfigurationReport- parameterNumber:103, size:4, value:0
dev:12020-06-04 08:58:14.968 pm infoConfigurationReport- parameterNumber:102, size:4, value:8
dev:12020-06-04 08:58:14.918 pm infoConfigurationReport- parameterNumber:101, size:4, value:4
dev:12020-06-04 08:58:14.612 pm infoConfigurationReport- parameterNumber:92, size:1, value:10
dev:12020-06-04 08:58:14.551 pm infoConfigurationReport- parameterNumber:91, size:2, value:50
dev:12020-06-04 08:58:14.492 pm infoConfigurationReport- parameterNumber:90, size:1, value:0
dev:12020-06-04 08:58:14.434 pm infoConfigurationReport- parameterNumber:89, size:1, value:1
dev:12020-06-04 08:58:14.167 pm infoConfigurationReport- parameterNumber:80, size:1, value:2
dev:12020-06-04 08:58:11.788 pm infoConfigurationReport- parameterNumber:3, size:1, value:0
dev:12020-06-04 08:58:11.746 pm infoConfigurationReport- parameterNumber:1, size:1, value:0
dev:12020-06-04 08:57:22.504 pm debugParsed MultiChannelCmdEncap(bitAddress:false, command:3, commandClass:32, destinationEndPoint:2, parameter:[255], res01:false, sourceEndPoint:2) to [['name':switch2, 'value':'on'], ['name':'switch', 'value':'on']]
dev:1382020-06-04 08:57:21.749 pm infoDriveway was turned on
Here are the logs for the Enerwave RSM2 dual switch as well. It appears as though the Enerwave is not responding to the the z-wave tool for the Get Parameter report. This is all I get. Push all 4 buttons, but also the Parameter Report several times.
dev:1612020-06-04 09:05:54.102 pm infoCommandClassReport- class:0x27, version:1
dev:1612020-06-04 09:05:53.886 pm infoCommandClassReport- class:0x27, version:1
dev:1612020-06-04 09:05:49.195 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:49.155 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:49.037 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:48.902 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:43.895 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:43.811 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:43.478 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:42.671 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:42.251 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:41.936 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:41.209 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:41.002 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:39.528 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:39.155 pm infoCommandClassReport- class:0x85, version:2
dev:1612020-06-04 09:05:24.507 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:23.991 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:23.177 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:21.803 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:21.392 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:20.431 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:20.301 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:19.028 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:18.211 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:18.025 pm infoCommandClassReport- class:0x8E, version:2
dev:1612020-06-04 09:05:04.599 pm infoCommandClassReport- class:0x60, version:4
dev:1612020-06-04 09:05:04.107 pm infoCommandClassReport- class:0x25, version:1
dev:1612020-06-04 09:05:03.599 pm infoCommandClassReport- class:0x73, version:1
dev:1612020-06-04 09:05:03.097 pm infoCommandClassReport- class:0x5A, version:1
dev:1612020-06-04 09:05:02.542 pm infoCommandClassReport- class:0x72, version:2
dev:1612020-06-04 09:05:02.005 pm infoCommandClassReport- class:0x86, version:2
dev:1612020-06-04 09:05:01.536 pm infoCommandClassReport- class:0x5E, version:2
dev:1612020-06-04 09:04:59.768 pm infoAssociationReport- groupingIdentifier:1, maxNodesSupported:1, nodes:[1]
Any ideas on the above log files?
No help I'm afraid but I have the same issue with my aeotec dual nano switches with the new driver. I.e. switching works, parameter 80 is set to basic but still the status of the switch doesn't update unless I refresh. Did you get anywhere with this?
Nope -no one has commented since I posted the logs. I’d really like to get these working too. Not sure what is so difficult about these switches. They worked with other hubs.
Try it removing it from HE, then factory reset it and then re join it that usually fixes odd ones. Also check that your on the latest firmware.
Will give that a go this evening, thanks. I hope it works. Will report back here.
@mike.maxwell or @aaiyar - have you had a chance to look at these logs?
@Boris - the older micro switches do not have any firmware update capabilities as per Aeotec. The nano on the other hand does, so that may help @chris.parsons85
Any news on a new driver for the Aeotec dual micro as mentioned earlier?
Also - any news on a driver for a dual enerwave?
Can anyone help here?
You need to have logs open, nothing happens on the device page.
I think your issue is polling after reading this again. I assume that the micro is z-wave rather than z-wave plus? Wink does polling on all devices no matter what (not a good idea for your network) hubitat you need to add the app and specify the devices you want to pole.
When doing logs do a screen shot and hide it in the "hide details" options in the settings cog when you do a post, this will make them easier to read.
1 Like
I tried ZWave polling, but no devices show up in the drop down. I assume that means all of my devices are Z-wave Plus, so this does no good.
