• 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


[Fully Supported] Elro 800 Series
#31
(06-13-2014, 11:56 PM)curlymo Wrote: and to lcd4linux.
Yes ! Thx !

(06-13-2014, 11:56 PM)curlymo Wrote: You can also change the send-repeats in the settings.json.
I must say, it didnt work for me, I tried 5 , 10, 15 , 20 repeats and nothing, bash do the work. Smile
 
Reply
#32
Here are the promised outputs from pilight-debug and pilight-learn.

pilight-debug:
1 on: http://pastebin.com/5S7uaVPq
1 off: http://pastebin.com/d1TFEcEq
2 on: http://pastebin.com/U9Z9j4FG
2 off: http://pastebin.com/9yXjwdhc
3 on: http://pastebin.com/fHn7wWMi
3 off: http://pastebin.com/tgpwTL8H
4 on: http://pastebin.com/n0dEbsCr
4 off: http://pastebin.com/VxQPByr6
all on: http://pastebin.com/AVxUqiMQ
all off: http://pastebin.com/PsvmNEY0

pilight-learn:
Code:
--[RESULTS]--

hardware:    433gpio
pulse:        7
rawlen:        58
binlen:        14
plslen:        146

on-off bit(s):    4 9 10 11
all bit(s):    6
unit bit(s):    0 2 3 5 7 8 12

Raw code:
1314 1168 876 438 876 438 146 1168 146 1168 876 438 730 438 146 1168 730 438 146 1168 876 438 146 1168 730 438 146 1168 876 438 146 1168 730 438 730 438 876 438 146 1168 146 1168 146 1168 876 438 146 1022 876 438 146 1168 876 438 146 1022 146 4964
Raw simplified:
On:    0101000101000101010100000000000101000000010000010101000101
Off:    0101000101000101010100000000000101000000010000010101000101
All:    0001000101000101000101010101010100010100010001010000010101
Unit 1:    0101000101000000010100000101000001000100000101000000000101
Unit 2:    0101110101110111110101011111010101011101110101010111011101
Unit 3:    0100000101000001000100010001000100000001010100010001000101
Binary code:
On:    11011001000111
Off:    11010001011011
All:    11011111100101
Unit 1:    11001010001001
Unit 2:    11111111111111
Unit 3:    01011111011111


lcd4linux
 
Reply
#33
Hi,

i had some issues with the elro_he protocol, but i got it to work with help of wo_rasp. (Link)

The follwoing output was printed by pilight-receive while hitting the A-Off-Button. The first repeats are fine, but then the state changes to "on" and some repeats further the unitcode is changing to "0". Because of this the webgui isn't updated properbly sometimes. It is changing to "off" for a very short time and going back to "on" immediatly.

Code:
A-Off

{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 1
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 2
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 3
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 4
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 5
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 6
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 7
}

i changes some lines in the elro_he protocol. is it possible the problem is related to it? the changes are shown in the thread linked above.

The follwing outputs are for A-On, B-On and B-Off. They are showing the same failure.

Code:
A-On

{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 1
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 2
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 3
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 1,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 4
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 5
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 6
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 7
}

Code:
B-On

{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 1
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 2
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 3
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 4
}

Code:
B-Off

{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 1
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 2
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 3
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 4
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 2,
                "state": "off"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 5
}
{
        "code": {
                "systemcode": 6,
                "unitcode": 0,
                "state": "on"
        },
        "origin": "receiver",
        "protocol": "elro_he",
        "uuid": "0000-00-00-6a-b9fd5e",
        "repeats": 6
}

Someone has an idea about that?

Thanks and Greetings,
tobid
 
Reply
#34
(10-12-2014, 04:08 PM)tobid Wrote: I changed some lines in the elro_he protocol. Is it possible that the problem is related to it? The changes are shown in the thread linked above.
In my opinion, no, but you can try the following:
Below that line
Code:
protocol_plslen_add(elro_he, 288);
you added:
Code:
protocol_plslen_add(elro_he, 278);
Only keep the line with 278 and remove all the others.

You will find more info in the pilight documentation here.
 
Reply
#35
Is this still applicable or is the HE8xx protocol implemented in newer versions of pilight?
 
Reply
#36
(11-12-2014, 04:08 PM)alexschomb Wrote: Is this still applicable or is the HE8xx protocol implemented in newer versions of pilight?

Yes, the protocol isn't finished yet.

(06-12-2014, 08:59 PM)curlymo Wrote: Can some of you post additional pilight-debug output for all buttons.

Here are the additional pilight-debug output for all buttons.


lcd4linux
 
Reply
#37
Hi, maybe a bit off-topic, but your wiki brought me here Big Grin

I have an Elro HE contact sensor (the one mentioned in the wiki), and it actually works quite well, it already has a pre-set system code and unit code (actually, tried to "learn" that, but no luck - there is no foolproof description how to learn that one .. anyway). pilight-receive tells me this is an "elro_he" switch, and it is also working like one. Adding this to pilight makes it a switch. But, since this is a contact sensor, is there a possibility to make this like "elro_he_contact" not to be able to switch that from gui? Currently this is "worked-around" by setting "gui-readonly", but is there maybe a "native" support?
It is actually quite useful if a switch should be turned on when window opened, but until that ...

Thx Smile
 
Reply
#38
Can you create a new topic called Elro HE Contact with this question. Since the new eventing contact sensors are implemented slowly.
 
Reply
#39
(12-04-2014, 10:22 AM)curlymo Wrote: Can you create a new topic called Elro HE Contact with this question. Since the new eventing contact sensors are implemented slowly.

No problem, will do straight away. If you need an output .. well.. I am still waiting for the BPF Smile
 
Reply
#40
If the sensor is the same as the switch then only need to know if "on" matches "open" and "off" matches "closed"
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Partially Supported] TFA / Conrad Weather Yves 184 9,292 03-31-2019, 05:22 PM
Last Post: curlymo
  [Fully Supported] DHT22 IcedEarth 86 30,479 11-18-2018, 09:33 AM
Last Post: curlymo
  [Fully Supported] Arctech Old Martin 111 34,171 03-27-2018, 04:43 PM
Last Post: genfersee
  [Fully Supported] Clarus Switches Marcin 69 23,463 01-30-2018, 07:10 PM
Last Post: Niek
  [Fully Supported] Remote Control Socket (RC101-U/RC201) Sean 18 10,332 01-04-2018, 06:18 AM
Last Post: ettman8
  Elro/Flamingo FA20RF Smoke detector meloen 76 37,094 12-16-2017, 07:07 PM
Last Post: pilino1234
  [Fully Supported] LM75 and LM76 temperature sensor horst_dieter 64 24,411 11-19-2017, 08:54 PM
Last Post: edepi
  [Fully Supported] No-brand temp/humidity sensor (alecto_ws1700) meloen 57 34,232 12-25-2016, 09:53 PM
Last Post: creamers
Lightbulb [Fully Supported] Kaku Door sensor (AMST-606) geerttttt 50 23,385 11-29-2016, 06:52 AM
Last Post: curlymo
  [Fully Supported] Impuls/SelectRemote Bram 113 46,166 05-28-2016, 02:53 PM
Last Post: Puuu

Forum Jump:


Browsing: 1 Guest(s)