HE107 switch?

Thanks Andrew but these didn't work, however good old persistence did.

I used the arduino code linked in the wiki to reverse out the stream and had to tweak the timings back 10% as per Brett's previous comments regarding URF. All good now. 

Codes for interest are

on= 010200FA09C400FA00FA00FA044C00FA00000C012710421999999A5999A5A5A599A659A59A65A580

off=010200FA09C400FA00FA00FA044C00FA00000C012710421999999A5999A5A5A599A659A599A5A580

(worth adding to wiki?)

now for dimming ?!

Garry

Derek,

I cannot edit the Wiki but would be happy to if you give me access, alternatively I have included the write up here for info anyhow.

Note: This has been tested on HE307dimming wall sockets that use the advanced protocol only.

I have tweaked the pulse definition back ~10% to the following:

Which gives a pulse definition of: 0200FA09C400FA00FA00FA044C00FA0000

For simple ON/OFF control, the protocol itself is built up as follows:

A “0” Bit is sent as 250Hi 250Lo then 250Hi 1100Lo (i.e. two frames, 1 then 2 from above)

A “1” Bit is sent as 250Hi 1100Lo then 250Hi 250Lo (i.e. two frames, 2 then 1 from above)

The stream is made up of:

A latch signal to start – 250hi 2500lo = frame 0 from above

Then 26 group code bits – i.e 272946 or in binary 00000001000010101000110010

Which gives: 1,2,1,2,1,2,1,2,1,2,1,2,1,2,2,1,1,2,1,2,1,2,1,2,2,1,1,2,2,1,1,2,2,1,1,2,1,2,1,2,2,1,2,1,1,2,1,2,2,1,1,2 as frames, using  0 = 1,2 and 1 = 2,1 as shown above.

There is next a group ID bit, I set this to 0. i.e. 1,2 as frames (not sure what this is for!).

Then comes the on/off code bit. On = 1 which is 2,1 as frames, Off = 0 which is 1,2 as frames.

Next  follows a four bit address code, I used 1010 or 2,1,1,2,2,1,1,2 as frames.(I assume you can change this for different devices)

Finally we send the latch signal again, frame 0

Add together and you get 33 bits or 66 frames in total.

If you use the RF helper to pack this up as follows:

Stream =              1999999A5999A5A5A599A659A59A65A580

PulseDef = 0200FA09C400FA00FA00FA044C00FA0000

Burst count  = 12

Interburst delay = 10000

Frames = 66

You should get: 010200FA09C400FA00FA00FA044C00FA00000C012710421999999A5999A5A5A599A659A59A65A580

For dimming, the protocol is altered as follows:

Change the on/off bit from either 2,1(on) or 1,2(off) to 1,1(the dim setting)

After the four ID bits but before the end latch signal add four further bits as follows:

Convert dim setting (0-10) to binary then to frames;

i.e level 7 = 0111, which is 1,2,2,1,2,1,2,1 as frames or

level 5 = 0101, which is 1,2,2,1,1,2,2,1 as frames.

Add this together and you now get  37 bits or 74 frames in total.

Via the RF helper, the 50% dim stream is:              1999999A5999A5A5A599A659A59965A59A5A40

To test this I added a new RF device with the on / off codes set to 50% and 70% dimming. This is not terribly useful and therefore my next job is to write a lua script to setup an endpoint and use the Level value to send the appropriate dim code. I will post when completed.

Enjoy!.

Garry

Ps Brett, this URF code structure is pure genius!.

As promised. Lua script to generate an endpoint for dimming HE units using advanced protocol.

I'm sure there are better ways but this seems to work.

Garry

Excellent, good luck

i love mine, use it daily as the "big light" control via level sliders. 

Cool for impressing guests!

G.

Well I use sliders via the MOTE app on ios, but yeah slider on joggler would work also.

not used the sliders on joggler for a while but did get them to work for my thermostat setting so can't see why they wouldn't work for this application also.

Garry

Thanks for this Mark, good work.

it was difficult to decode as I had no remote and was working off internet arduino snippets. Good to know we have 15levels and I did notice sending an on code whilst already on sent it into auto dim but didn't have a solution.

I'm very interested in your mods.

cheers

Garry