Request: Edge Drivers for Aeotec Smart Switch 6 and and Multisensor 6

[23dash (Dave)]

It depends what you assign in 101 Group 1 Sensors (I have assigned illuminance) and I’ve set 111 as 60 so illuminance updates every 60s.

[Cresu]

Yes, if these sensors are newly added, they seem to be added with Wake Up Interval Set CC set to 3600.

I got it fixed by changing Wake Up Interval to 240 using this driver:

(EDGE Driver-Mc): Z-Wave Device Config Mc

New Update for Edge driver Z-Wave Device Config Mc: Improvements and changes: Added new profile for WAKE_UP Interval Get and Set functions [Screenshot_20230401-175903] In devices that do not support the WAKE_UP Command Class, a message will be displayed stating that this Command Class is not supported and will not execute anything. [Screenshot_20230401-132045] If the Command Class WAKE_UP is supported you can read the current value of the WakeUp interval or set a new one within the range allowed by the Zwave and device specification. As these devices are usually asleep, both Get and Set have to be woken up manually according to the documentation. If we select the Get or Set values and the new interval in seconds, when we wake up the device the code to sending of the Get or Set …

In addition, I changed parameter 111 to 240 (4minutes).

This is from multisensor 6 manual, so this seems to be intended behaviour (but before edge drivers these devices were definately added with wake up interval Set CC 240):

If battery power, the minimum interval time is 60 minutes by default, for
example, if the value is set to be more than 5 and less than 3600, the
interval time is 60 minutes, if the value is set to be more than 3600 and less
than 7200, the interval time is 120 minutes. You can also change the
minimum interval time to 4 minutes via setting the interval value(3 bytes) to
240 in Wake Up Interval Set CC.

[PaulNZ (Paul Ayres)]

@CommanderQ

I feel bad asking, but did the old Aeotec Garage Door Controller Gen 5 make it onto the project list. Would love to have this working again.

Regards, Atomic Snail

[sulisenator (Matteo Sulis)]

Yes it works perfectly, it’s using a SmartThings driver, it was automatically switched during the transition.

[rebootx (Rex)]

@sulisenator, I have issues with the Aeotec Z-Wave Garage Door Controller since migration to Edge drivers. How did you manage to get it working?

[sulisenator (Matteo Sulis)]

It simply got transferred to an Edge driver during the transition.

[rebootx (Rex)]

My Aeotec Garage Opener is also using SmartThings provided Edge driver which only open function works in new Smarththings IDE portal. Close function and tilt sensor reporting not working. If I switch the driver to SmartThings virtual switch both open and close function for controller but not tilt sensor status. It appears you may using a different driver. My current edge driver version is 2023-09-12T18:12:07.040398766

[sulisenator (Matteo Sulis)]

2023-09-05T18:47:27 for me.
SMartThings Drivers (beta) channel

[rebootx (Rex)]

How did you get the device to stay on Smartthings beta drivers?

[CommanderQ (Mike McMahon)]

Hi @PaulNZ ,

Sorry for the delay. I do have this on my To Do list and am working on scrounging up some free time to dive in, assuming this is still needed?

[PaulNZ (Paul Ayres)]

Hi @CommanderQ ,

Using Mariano’s zwave Garage Door Opener MC driver at the moment. I think it was updated at some point as I didn’t have any luck with it yhe last time I tried. Would have been maybe a year ago.

Only issue currently is that as its generic, it doesn’t expose any settings and also had issues trying to use the state of the open/close sensor in other automations.
So yeah, a specific driver would be great with the AU/NZ fingerprint included.

Happy New Year Mike.

Best regards, Paul in NZ