• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


CLOSED: Unbranded White Programmable plug-in wall switches
#1
Hi, I would love to have these supported they are very cheap 1KW outlets that have reliable & quick switching. They are labelled 1 to 5 but they are programmable and presumably support more than 5 IDs.

Photo:

.jpg   200788-4.jpg (Size: 15.68 KB / Downloads: 37)


They are being incorrectly identified right now. Below is the result from pilight-receive for device 1:

on

Code:
{
   "message": {
       "id": "F2",
       "unit": 30,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "clarus_switch",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}
{
   "message": {
       "systemcode": 30,
       "programcode": 8,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "impuls",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}
{
   "message": {
       "id": "F2",
       "unit": 30,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "clarus_switch",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 2
}
{
   "message": {
       "systemcode": 30,
       "programcode": 8,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "impuls",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 2
}

and off

Code:
{
   "message": {
       "id": "F2",
       "unit": 30,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "clarus_switch",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}
{
   "message": {
       "systemcode": 30,
       "programcode": 8,
       "state": "on"
   },
   "origin": "receiver",
   "protocol": "impuls",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}
{
   "message": {
       "id": "F2",
       "unit": 30,
       "state": "off"
   },
   "origin": "receiver",
   "protocol": "clarus_switch",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}
{
   "message": {
       "systemcode": 30,
       "programcode": 8,
       "state": "on"
   },
   "origin": "receiver",
   "protocol": "impuls",
   "uuid": "0000-02-1d-b4-7d832f",
   "repeats": 1
}

pilight doesn't register any button press for devices 3-5.

I've attached a tarball with all possible button presses on this 5 device on - off remote -
.gz   white-unbranded.tar.gz (Size: 2.07 KB / Downloads: 6)
 
Reply
#2
I'm looking in to getting this protocol working myself.

I have zero experience of this so my first step is to figure out a process..

I'm thinking capture 20 or so raw codes for each button, find typical/average values for them and then begin to look for patterns ..?

What's strange is If I send any of the captured codes the switches are not responding. (Sending via pilight nano firmware). I've not sent any raw codes before so perhaps something is broken somewhere. I can send known protocols just fine via pilight.
 
Reply
#3
The raw codes need to work, so that you know that they are valid when trying to figure out the protocol.

After you have gotten several valid raw codes, you need enough other devices to be able to figure out what section of the signal carries what information. So you might need to get more codes from other users.
 
Reply
#4
Thanks for the advice

First thing I'll do is confirm that I can send a known working protocol as a raw message.
 
Reply
#5
So I recorded some known working sequences using another usb nano.

e.g.
Code:
time:        Wed May  4 21:36:49 2016
hardware:    433nano
pulse:        3
rawlen:        50
pulselen:    335

Raw code:
320 1020 320 320 320 1020 320 320 320 1020 320 320 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 320 320 1020 320 320 320 1020 320 1020 320 11400

I then sent them via the main usb-nano using

Code:
pilight-send -p raw -c "320 1020 320 320 320 1020 320 320 320 1020 320 320 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 1020 320 320 320 1020 320 320 320 1020 320 1020 320 11400"

But the signal is not being sent correctly, or I've captured it wrong somehow. The device is not responding to the raw sequence.

Is sending raw sequences using the latest usb nano firmware known to be working fine?

Just to be clear that capture above is from a working device which I'm using pilight to control.
 
Reply
#6
Hello,

I'm attempting to tackle supporting these in pilight again.

I've made some progress. I can control them using the RCSwitch on Arduino library if I pass in tri-state codes or binary codes.

I learned these by capturing them via RCSwitch. What I can't figure out is how to map devices 1-5 into binary, in order to see if there's the potential in the encoding to support more than 5 individual devices.

Here is everything I have discovered from the remote control. One other thing to mention is they can each store 3 learned codes, which leaves an opportunity for group control, should I be able to decipher what the encoding is.

Any help would be massively appreciated. I have other devices working well with pilight, but they are expensive and tend to die (Klikanklut) as they are dimmers. I like these because they are very simple inside, just a 10Amp relay, so should last much longer.

Code:
White 10A Unbranded Sockets
---------------------------

PulseLength = 182µs

bin 0: HIGH LOW LOW LOW
        _
bin 0: | |___

bin 1: HIGH HIGH HIGH LOW
        ___
bin 1: |   |_
       
Dev 1 ON  - bin: 010000000001010100110011
Dev 1 OFF - bin: 010000000001010100111100
Dev 2 ON  - bin: 010000000001010111000011
Dev 2 OFF - bin: 010000000001010111001100
Dev 3 ON  - bin: 010000000001011100000011
Dev 3 OFF - bin: 010000000001011100001100
Dev 4 ON  - bin: 010000000001010100000011
Dev 4 OFF - bin: 010000000001010100001100
Dev 5 ON  - bin: 010000000011010100000011
Dev 5 OFF - bin: 010000000011010100001100

Dev 1 ON  - tri: F 0 0 0 0 F F F 0 1 0 1
Dev 1 OFF - tri: F 0 0 0 0 F F F 0 1 1 0
Dev 2 ON  - tri: F 0 0 0 0 F F F 1 0 0 1
Dev 2 OFF - tri: F 0 0 0 0 F F F 1 0 1 0
Dev 3 ON  - tri: F 0 0 0 0 F F 1 0 0 0 1
Dev 3 OFF - tri: F 0 0 0 0 F F 1 0 0 1 0
Dev 4 ON  - tri: F 0 0 0 0 F 1 F 0 0 0 1
Dev 4 OFF - tri: F 0 0 0 0 F 1 F 0 0 1 0
Dev 5 ON  - tri: F 0 0 0 0 1 F F 0 0 0 1
Dev 5 OFF - tri: F 0 0 0 0 1 F F 0 0 1 0

I think I must be dense. The answer was staring me in the face.

These operate identically to the intertechno protocol, with one difference, the last two tri states must be 01 for on, and 10 for off, unlike intertechno which is FF and F0.

Testing with random permutations of tri-states, they seem to support pretty much any variation of codes, assuming the on and off are correct.

Without knowing anything about the Intertechnos, I'm not sure if the 'group' has any meaning and whether or not they support built in 'group' messages or not.

But it makes the supporting these a whole lot easier! Patch intertechno protocol to support passing in the pulselength and change the last 4 bits. I can patch it as an option in config.json.

Edit: I just looked at your implementation of intertechno and it's totally different to RCSwitch.

You do LOW HIGH LOW LOW for 1 and LOW LOW LOW HIGH for 0

Bit confused about that..
 
Reply
#7
HUGE EDIT


Please ignore all the noise. These are using the clarus_switch protocol. It just seems that there is something funky with the decoding of these, as you don't recognise the state correctly (always shows "on"), and didn't recognise the 4th and 5th device codes at all.

Sending is working perfectly with what seems a huge number of possible codes, I'm now going to buy a bunch more of these.

If I can help fix that, let me know what to do! I'd love to get receiving fixed as the remotes are handy and have lots of buttons.

I'll leave a reply on the clarus fully supported thread..
 
Reply
#8
I assume that your problem is most probably caused by inaccurate pulse durations of the usbNano or some (yet) missing information.

Looking at the various data information you posted, in particular the tar ball archive, i am relatively sure that 182µS are most probably a usable unit value for a pulse duration.

I have added to the Electronics section of the WIKI a brief introduction into Encoding/Decoding of waveforms.
 
Reply
#9
(11-13-2016, 11:25 PM)wo_rasp Wrote: I assume that your problem is most probably caused by inaccurate pulse durations of the usbNano or some (yet) missing information.

Looking at the various data information you posted, in particular the tar ball archive, i am relatively sure that 182µS are most probably a usable unit value for a pulse duration.

I have added to the Electronics section of the WIKI a brief introduction into Encoding/Decoding of waveforms.

I've been considering switching to a attiny prefillter and the gpio ports on the pi in order to save a bit of room. 

Ill give that a try and report back in the clarus thread.

Sending via the nano works perfectly though.

Ill give the WIKI a read over too. I have a scope just not particularly skilled at using it.

Thanks for the reply
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Owsoo Wall Switch (Push Button / Sold for Sonoff devices with 433MHz)) hawkeyexp 0 341 10-14-2019, 10:32 PM
Last Post: hawkeyexp
  Unitec Switches rien-ne-va-plus 48 33,842 05-29-2019, 02:16 PM
Last Post: bitboy
  RSL366T Switches juri 60 31,446 05-24-2018, 06:48 PM
Last Post: bobg
  [Fully Supported] Clarus Switches Marcin 69 30,980 01-30-2018, 07:10 PM
Last Post: Niek
  Unitec / Intertek Switches dieterhatn 1 1,456 03-07-2017, 07:04 PM
Last Post: pilino1234
Brick Aukey Switches VrahoK 5 2,352 11-01-2016, 06:56 AM
Last Post: curlymo
  eHome Switches ligi 95 39,889 12-01-2014, 04:40 PM
Last Post: curlymo
  DBPower Switches joaoasilva 5 3,543 09-25-2014, 08:45 PM
Last Post: joaoasilva
  Support for Schwaiger/Goobay switches plinden 10 6,787 05-16-2014, 11:20 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)