kazze
March 27, 2018, 8:41am
1
Hi,
I am trying to install a cheap door contact (https://www.clasohlson.com/se/Magnetkontakt-Cotech-Smart-Home/36-6048 ) following the instructions here:https://www.home-assistant.io/components/binary_sensor.rfxtrx/
br
2018-03-26 23:02:42 DEBUG (Thread-12) [homeassistant.components.rfxtrx] Receive RFXCOM event from (Device_id: 969220 Class: LightingDevice Sub: 0, Pkt_id: 09130000969220017a70)
lolouk44
March 27, 2018, 8:48am
2
One of the Pkt_id should be the one you need to manually register your sensor
- platform: rfxtrx
automatic_add: True
devices:
[insert pkt_id here]:
name: Door Sensor
device_class: opening
If that doesn’t work, you may need to set your logs to debug for the RFX to get more data, when you open/close you should see the device ID:
logger:
default: error
logs:
homeassistant.components.rfxtrx: debug
kazze
March 27, 2018, 1:33pm
3
Thanks a lot, I will try it tonight and post the results.
You cannot use the full packet because there is an incrementing sequence number in the RFXtrx packets.
09130000969220017A70 decodes as:
Important parts in the packet are:
kazze
March 28, 2018, 8:00pm
5
Hi again,
so here is an update: ‘binary sensor’ does not seem to be the way to go. But if I configure automatic add for the rfxtrx controll for SWITCH (not binary sensor as before) I get 4 different switches added (as shown in the logs below) - 2 for ‘open’ and 2 for ‘close’.
if Pkt_id contains (or even ‘startsWith’) “09130006” and Device_id in (98b440, 9e16b0) then set a virtual door/switch/switch to ‘open’
2018-03-28 21:34:43 WARNING (MainThread) [homeassistant.bootstrap] Python 3.4 support has been deprecated and will be removed in the beginning of 2018. Please upgrade Python or your operating system. More info: https://home-assistant.io/blog/2017/10/06/deprecating-python-3.4-support/
Thanks for your time and advice!
alexcf
September 15, 2018, 10:34am
6
Having the same issue, any pointers would be appreciated!
shakoke
September 17, 2018, 4:29am
7
Hi kazze and alexcf , did you finally manage to have your door contact recognized as binary sensor?
I’m trying to let HA recognize my 433MHz KERUI P829 motion detector and get a similar error as you.
My binary sensor rfxtrx config looks as follows:
binary_sensor:
platform: rfxtrx
automatic_add: True
The other rfxtrx sensor types (switch, sensor) have their option “automatic_add” set to False
This is the DEBUG output I get in the HA log file:
2018-09-16 08:43:07 INFO (Thread-2) [homeassistant.components.binary_sensor.rfxtrx] Added binary sensor 09130038df784a00da70 (Device ID: df784a Class: LightingDevice Sub: 0)Unknown command (0xdf784a)
The binary sensor is actually added and visible on the HA UI and has state on , but the state is never updated
I found one more post related this topic but without replies: add-remote-led-single-color-dimmer-with-rfx
Is there anyone who can point me to the next best step to take in debugging?
Any help is appreciated!
I’m running HA version 0.77.3
kazze
September 17, 2018, 6:36am
8
Hi guys,
unfortunately I gave up HA, this was my second try to setup HA and learn it in more detail. Since script languages are not my preferred weapon, this is a dead-end for me now (especially since this device is detected and configured properly by Domoticz). But I am monitoring this thread and I would gladly test it again if somebody else finds something useful.
br
shakoke
September 18, 2018, 11:40am
9
Good news, I managed to configure the PT2262 device in HA
The problem was that:
I don’t know much about protocols yet
I didn’t know if my device was sending an ‘off’ command, and so I didn’t know if I had to configure the command_off property
So I started playing with RFXmngr.exe that comes with the rfxcom transceiver and triggered both motion and tamper alarm with my motion detector.
With Lighting4 and X10 enabled I triggered motion and alarm and received following 2 packages:
With Lighting4 and X10 enabled
18-9-2018 12:28:28:292
Packettype = Security1
subtype = X10 security
Sequence nbr = 30
id1-3 = DF7840 decimal:14645312
status = Motion
battery level = OK
Signal level = 7 -64dBm
------------------------------------------------
18-9-2018 12:33:29:424
Packettype = Security1
subtype = X10 security
Sequence nbr = 85
id1-3 = DF7840 decimal:14645312
status = Alarm + Tamper
battery level = OK
Signal level = 7 -64dBm
------------------------------------------------
I’m not sure if it means something, but the id1-3 is the same for both motion and alarm, while I expected them to be unique
With Lighting4 enabled and X10 disabled I triggered motion and alarm and received following 2 packages:
With Lighting4 enabled and X10 disabled
18-9-2018 12:28:41:482
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 32
Code = DF784A decimal:14645322
S1- S24 = 1101 1111 0111 1000 0100 1010
Pulse = 313 usec
Signal level = 7 -64dBm
------------------------------------------------
18-9-2018 09:13:29:237
Packettype = Lighting4
subtype = PT2262
Sequence nbr = 54
Code = DF784B decimal:14645323
S1- S24 = 1101 1111 0111 1000 0100 1011
Pulse = 313 usec
Signal level = 7 -64dBm
------------------------------------------------
Now I was clearly seeing two id’s. One for motion DF784A and one for alarm DF784B. The one for motion I recognized seeing in HA before. I liked the idea of unique id’s so I chose to keep X10 disabled at least during integration with HA.
It turned out that HA correctly recognized DF784A before and I just had to mark the letter A as command_on for motion and letter B as command_on for alarm (or problem). I also looked up the device id’s again on the dev states page and configured them as devices:
binary_sensor:
platform: rfxtrx
automatic_add: false
devices:
09130029df784a013670:
name: sensor_berging_beweging
device_class: motion
off_delay:
seconds: 5
data_bits: 4
command_on: 0xa
09130073df784b013970:
name: sensor_berging_sabotage
device_class: problem
off_delay:
seconds: 5
data_bits: 4
command_on: 0xb
Using this configuration the motion sensor is correctly firing for both movement and alarm in my case.
Note:
I’m not sure if I really had to disable the X10 protocol.
The binary sensor update message is still shown in the logs, but does not seem to affect the detection of motion or alarm
Results:
no motion
with motion,
1 Like
kazze
September 20, 2018, 11:38am
10
This is really good news, I will start all over with my testing as soon as I get a new installation in place and update my results, thanks for sharing!!
/Kazze
kazze
October 23, 2018, 6:37am
11
Ok, so I also managed to get my door contact working. I enabled debug logging and disabled X10 protocol (as suggested earlier, just to be sure) and started to monitor. It showed that there was a limited number of id’s after all (16!).
0913000 6 98b440018a70
0913000 a 98b440017a70
0913000 e 98b440017a70templates and stuff works, the syntax to configure devices in Homeassistant is not trivial for newbies ;-). The idea is to replace (hide the ‘original’ devices) with one 'door-icon" virtual device and make it react to the open/close devices above. My first tries so far have been futile
