Paddle switch to trigger automation?

Hi Eric so I have got my switch and got it running as you outlined. Couple questions:

  1. What is the best way to implement dimming without z wave association. Given the delay is it practical to use a hold down or will I have to do something like two taps to dim 30% 3 taps 100%

  2. I’m on fiber and the delay between when I press the button and when the light turns on is about 1.8 seconds. This is probably not going to be workable as people tend to push the button several times.

When using the wiz app which talks direct on the wifi it’s less than 100ms. I understand the route is switch, hub, samsung, wiz, lights. But is there anything I can do to make this faster? Otherwise I don’t think this is going to work for me.

thanks!

Charles

Hi Richard

Have got this going now, but the latency is about 1.8 seconds from push button to light on. Are you finding the same thing?

thanks

Charles

Hey Charles,

1.8 may be the fastest you can get unfortunately. While I know you have fiber (that does help), it takes time to convert the Z-Wave signal to WiFi (I think that’s what Wiz uses) or ZigBee and vice versa plus processing times on ST’s server.

I may be able to get you down to around 1 second or so until ST moves locally.

If you have the device handler installed, you can tweak the settings to eliminate the 700ms delay that’s built in for scene control. The caveat is that you’ll lose multi-taps, but you’ll still be able to use a single tap up/down (for on/off) and hold (for dimming) + the config button (for favorites).

To eliminate it, there’s a spot in the settings called, “Disable Physical On/Off Delay”.

If you want the double-triple taps, you can minimize the 700ms delay all the way down to 100ms (or however long you think it takes for you to push/release/push/release a scene on the paddle). This section is called, “Configure Physical On/Off Delay”.

Outside of these settings, it’s going to be difficult to get any better than what you have unless someone in WiFi comes out with a switch that does the exact same things as us or you switch to a Z-Wave bulb :confused:

thank you, I think 700ms would make the difference. If I can get that working and the hold dimming even with a delay that will be fine.

I changed the disable physical on/off delay setting in the ST app and also tried 100ms but it’s not changing the behavior. Is there a delay in that being sent to the switch?

Also, I noticed at the bottom of the settings there is a powerOnState and RampRate setting that is different to the one closer to the top (with the same name and detailed explanation). I’m not able to edit any of these settings at the bottom now. Is this just leftover functionality or is this a potential bug. It’s worth noting that I played with these two settings prior to installing the device handler and the bottom ramp rate setting is locked on 100. Is that ignored and replaced with the new setting further up? or could this be part of my problem.

thanks

Hmmm… there shouldn’t be.

Can you post your parameters from IDE so I can make sure it took properly? If you’d like to send me a PM with that info that’s ok too.

Could you post a screenshot?

Tagging @erocm1231 too just in case there’s a bug in the device handler.

Hang in there, we’ll get it up and running for you!

Preferences (edit) Name Type Value
paragraph
paragraph
debugEnable boolean
disableLocal enum 1
disableRemote enum 1
enableDefaultLocalChild boolean
enableDefaultZWaveChild boolean
enableDisableLocalChild boolean
enableDisableRemoteChild boolean
enableLED1Child boolean
enableLED1OffChild boolean
infoEnable boolean
parameter1 number
parameter10 number
parameter11 number
parameter12 number
parameter13 enum 234
parameter13custom number
parameter14 enum 10
parameter15 enum 1
parameter16-1a enum
parameter16-1b enum
parameter16-1c enum
parameter16-1d enum
parameter16-2a enum
parameter16-2b enum
parameter16-2c enum
parameter16-2d enum
parameter16-3a enum
parameter16-3b enum
parameter16-3c enum
parameter16-3d enum
parameter16-4a enum
parameter16-4b enum
parameter16-4c enum
parameter16-4d enum
parameter16-5a enum
parameter16-5b enum
parameter16-5c enum
parameter16-5d enum
parameter17 enum
parameter18 number
parameter19 number
parameter2 number
parameter20 number
parameter21 enum
parameter22 enum
parameter3 number 0
parameter4 number 0
parameter5 number
parameter50 enum 1
parameter51 enum 0
parameter52 enum 2
parameter6 number
parameter7 enum
parameter8 number
parameter9 number
powerOnState 101
rampRate 100

Thanks very helpful – let’s try something out real fast.

Steps:

  • Change Parameter 50 to 7 (default) and Parameter 51 to 1
  • Turn the light on/off and time it (I’m assuming the 1.8 seconds)
  • Change Parameter 51 to 0 (don’t touch 50 for now)
  • Turn the light on/off and time it

From what I’m gathering from your previous posts, they seem to be the same time – I just want to confirm it first before troubleshooting.

Your parameters look good above, so I’m a bit stumped.

The Wiz lights also have a ramp up setting in their own app… set this to not be the 500ms that is the default and this will also remove some of the lag. The lag for me using Inovelli button press through SmartThings ‘Smart Lighting’ app is less than 1 second.

NOTE: when using automations like “when specific light turns off also turn off Wiz lights” (mirror setting in Smart Lighting)… can be up to a minute to respond" But directly controlling the Wiz light through SmartThings app device control page is pretty instant.