X10 - Slimline Wireless Wall Switch - SS13U

Hi Lolodomo

I have a strange issue with the SS13U X10 device. The first three buttons on the unit register fine on the dashboard of Vera, but the 4th one is hit or miss and does not appear as a binary light. It appeared as a scene controller.

Assuming this was just an error I changed the device type to a binary light to see if that would help but it didn’t, I have repeatedly removed it and tried again. Each time it comes back as a Scene Controller (L1.0/A)

Below is an extract from the logs when I press each of the four buttons in order 1, 2, 3 and then 4

Any ideas?

50 04/21/13 7:46:02.585 luup_log:39: RFXtrx: Received message: 07 10 00 7B 41 01 01 60 <0x3030e680> 06 04/21/13 7:46:02.586 Device_Variable::m_szValue_set device: 39 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 08 50 02 7A 27 04 00 94 69 now: 07 10 00 7B 41 01 01 60 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3030e680> 50 04/21/13 7:46:02.587 luup_log:39: RFXtrx: cmds: L1.0/A01 On L1.0/A SceneOn 1 <0x3030e680> 06 04/21/13 7:46:02.591 Device_Variable::m_szValue_set device: 160 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 102 now: 1 #hooks: 0 upnp: 0 v:0xb19d58/NONE duplicate:0 <0x3030e680> 06 04/21/13 7:46:02.594 Device_Variable::m_szValue_set device: 86 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xbb3da8/NONE duplicate:0 <0x3030e680>

50 04/21/13 7:46:03.475 luup_log:39: RFXtrx: Received message: 07 10 00 7C 41 02 01 60 <0x3030e680>
06 04/21/13 7:46:03.476 Device_Variable::m_szValue_set device: 39 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 07 10 00 7B 41 01 01 60 now: 07 10 00 7C 41 02 01 60 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3030e680>
50 04/21/13 7:46:03.477 luup_log:39: RFXtrx: cmds: L1.0/A02 On L1.0/A SceneOn 2 <0x3030e680>
06 04/21/13 7:46:03.482 Device_Variable::m_szValue_set device: 160 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 2 #hooks: 0 upnp: 0 v:0xb19d58/NONE duplicate:0 <0x3030e680>
06 04/21/13 7:46:03.535 Device_Variable::m_szValue_set device: 89 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xbb3da8/NONE duplicate:0 <0x3030e680>

50 04/21/13 7:46:04.595 luup_log:39: RFXtrx: Received message: 07 10 00 7D 41 03 01 60 <0x3030e680>
06 04/21/13 7:46:04.596 Device_Variable::m_szValue_set device: 39 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 07 10 00 7C 41 02 01 60 now: 07 10 00 7D 41 03 01 60 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3030e680>
50 04/21/13 7:46:04.597 luup_log:39: RFXtrx: cmds: L1.0/A03 On L1.0/A SceneOn 3 <0x3030e680>
06 04/21/13 7:46:04.601 Device_Variable::m_szValue_set device: 160 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 2 now: 3 #hooks: 0 upnp: 0 v:0xb19d58/NONE duplicate:0 <0x3030e680>
06 04/21/13 7:46:04.619 Device_Variable::m_szValue_set device: 88 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xbb3da8/NONE duplicate:0 <0x3030e680>

50 04/21/13 7:46:05.693 luup_log:39: RFXtrx: Received message: 07 10 00 7E 41 00 03 60 <0x3030e680>
06 04/21/13 7:46:05.694 Device_Variable::m_szValue_set device: 39 service: urn:rfxcom-com:serviceId:rfxtrx1 variable: LastReceivedMsg was: 07 10 00 7D 41 03 01 60 now: 07 10 00 7E 41 00 03 60 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3030e680>
50 04/21/13 7:46:05.695 luup_log:39: RFXtrx: cmds: L1.0/A SceneOn 103 <0x3030e680>
06 04/21/13 7:46:05.697 Device_Variable::m_szValue_set device: 160 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 3 now: 103 #hooks: 0 upnp: 0 v:0xb19d58/NONE duplicate:0 <0x3030e680>

The fourth button of this remote is a dim/bright button. So it is normal to not create a light device. Only the remote/scene controler device is notified with the right event. In your example, a BRIGHT event is notified.

PS: changing the type of a device managed by the plugin can only lead to a no way. My plugin is not enough clever to handle every devide type that a user can set…