Control4 Dimmer - On/Off not Working


(John Philips) #1

We have a small control4 system that was professionally installed. At this point, we are only using it for the 7 dimmer switches and a 6-button wireless keypad. I would like to transition to managing the light switches through SmartThings, as I can change settings when desired without calling the dealer.

I was able to pair one of the switches to my SmartThings hub, using the driver released by @pstuart (Thank you very much by the way!)

I can control dimming just fine, however, the on/off commands don’t seem to do anything. I can manually slide the dim level to 0% to turn off individual switches, but I am not able to set different scenes that turn off any lights. I believe that the switches don’t actually turn on and off, I think when you press off it is actually setting the dim level to 0%.

I am new to SmartThigns and IOT in general. Is there a getting started programming guide? I would like to send the switch a command to set dim to 0% when off is pressed and set dim to 100% when on is pressed.


(John Philips) #2

Here is the logging from when I performed the following actions through the SmartThings app:

  • Dragged dimmer state to 100%
  • Dragged back down to 0%
  • Tapped Off
  • Tapped On

[details=Summary]8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:17 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:16 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:16 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:11 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:11 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:11 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:11 AM: debug null
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:11 AM: debug Value is 0
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:11 AM: debug on()
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:09 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:09 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:09 AM: debug Execute the delayed update request
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:06 AM: debug Delay posting the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:06 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:06 AM: debug Value equals 0?
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:06 AM: trace setLevel(0)
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:06 AM: debug 0500
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:06 AM: debug 0
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:05 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:05 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:05 AM: debug Execute the delayed update request
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:02 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:00 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:00 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:02 AM: debug Delay posting the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:01 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:01 AM: debug 0
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:01 AM: debug switch is dimming 9b4 sa c4.dm.t0c 00
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:01 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:00 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:52:00 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:00 AM: debug Value equals 0?
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:00 AM: trace setLevel(0)
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:00 AM: debug 0500
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:52:00 AM: debug 0
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:43 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:43 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:43 AM: debug Execute the delayed update request
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:42 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:42 AM: debug 100
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:42 AM: debug switch is dimming 9b2 sa c4.dm.t0c 64
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:41 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:41 AM: debug 6
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:41 AM: debug switch is dimming 9b0 sa c4.dm.t0c 06
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:41 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:41 AM: debug 81
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:41 AM: debug switch is dimming 9b1 sa c4.dm.t0c 51
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:41 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:40 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:40 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:40 AM: debug Delay posting the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:51:40 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:40 AM: trace setLevel(100)
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:40 AM: debug 0500
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:51:40 AM: debug 100[/details]

Here is the logging from when I performed the following actions manually:

  • Tapped On
  • Tapped Off

[details=Summary]8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:30 AM: debug Execute the delayed update request
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:29 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:28 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:28 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:28 AM: debug 0
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:28 AM: debug switch is dimming 9bd sa c4.dm.t0c 00
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:27 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:27 AM: debug 40
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:27 AM: debug switch is dimming 9bb sa c4.dm.t0c 28
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:27 AM: debug Delay posting the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:27 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:27 AM: debug 77
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:27 AM: debug switch is dimming 9ba sa c4.dm.t0c 4d
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:26 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:26 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:26 AM: debug Execute the delayed update request
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:24 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:24 AM: debug Parse returned Middle Dimmer switch is on
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:23 AM: debug Patched device state.
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:23 AM: debug Post the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:23 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:23 AM: debug Delay posting the device state to server: f8233d16-c472-42e8-bd2a-72497afc3c9f
8448a815-7db3-4e27-b0f2-401ed3859a48 11:53:23 AM: debug Detected state change: f8233d16-c472-42e8-bd2a-72497afc3c9f
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:22 AM: debug 41
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:22 AM: debug switch is dimming 9b6 sa c4.dm.t0c 29
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:23 AM: debug 100
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:23 AM: debug switch is dimming 9b7 sa c4.dm.t0c 64
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:22 AM: error java.lang.NumberFormatException: For input string: “c4.dm.b0c” @ line 111
f8233d16-c472-42e8-bd2a-72497afc3c9f 11:53:22 AM: debug switch is dimming 9b5 sa c4.dm.b0c
152bde74-7655-4a57-9ac1-1b5cb7a6efc4 11:52:33 AM: debug getChildDevices(false), children=0
152bde74-7655-4a57-9ac1-1b5cb7a6efc4 11:52:33 AM: trace in ssdpDiscover[/details]

I see a number format exception in the manual block, but I don’t understand how to proceed.


(John Philips) #3

I was able to work around the problems with the Control3 device handler and my dimmers using CoRE.
I wouldn’t recommend this as a great long term solution, but at least the dimmer is paired and working for now.

Here is the dashboard view of my quick fixes.
I will eventually get into coding device handlers and fix this, but if anyone else is having this problem in the mean time, here is a workaround.