Configuration Rflink

Take another look to the config examples at the documentation:

Same here:

It’s all YAML format. Spaces and identation are important.

@javicalle

I have trieds this :

sensor:
  - platform: rflink
    automatic_add:false
    devices: 
      oregontemphygro_22866_temp:
        sensor_type: temperature
        name: Température
      oregontemphygro_22866_hum:
        sensor_type: humidity
        name: Humidité
      oregontemphygro_22866_hstatus:
        sensor_type: humidity_status
        name: Statut humidité
      oregontemphygro_22866_bat:
        sensor_type: battery
        name: Niveau batterie
      oregontemphygro_22866_update_time:
        name: Update Time

And it’s put me un error.

can not read a block mapping entry; a multiline key may not be an implicit key at line 39, column 12:
        devices: 
               ^

For this one

##Liste Capteur Binaire

#Capteur Alarme Etiger
# Alarme Etiger
binary_sensor:
  - platform: rflink
    devices:
      chuango_2ebf59_02:
        name: Capteur mouv salon
        device_class: motion
        off_delay: 5

No errors found, but it’s wont give me acces to him in entities …
So i could not use him in automation …

Edit My bad the motion sensor works fine

Edit:

sensor:
  - platform: rflink
    devices:
      oregontemphygro_22866_temp:
        sensor_type: temperature
        name: Température
      oregontemphygro_22866_hum:
        sensor_type: humidity
        name: Humidité
      oregontemphygro_22866_hstatus:
        sensor_type: humidity_status
        name: Statut humidité
      oregontemphygro_22866_bat:
        sensor_type: battery
        name: Niveau batterie
#     oregontemphygro_22866_update_time:
#       sensor_type: ???
#       name: Update Time

There is only one errors left, i don’t know what type to use, to show update time …
I have found my errors :), but still this one left.

Anyone know how to add, a Dio Chacon 54785
Anyway thanks for your help @javicalle

Now there is another problem on oregon …
i have no data coming, and when i look in the debug log, i have some data from him …

2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] got packet: 20;05;F007_x;ID=faf82;TEMP=80ee;HUM=48;BAT=OK;
2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'f007_x', 'id': 'faf82', 'temperature': -23.8, 'temperature_unit': '°C', 'humidity': 48, 'humidity_unit': '%', 'battery': 'ok'}
2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'f007_x_faf82_temp', 'sensor': 'temperature', 'value': -23.8, 'unit': '°C'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'f007_x_faf82_temp', 'sensor': 'temperature', 'value': -23.8, 'unit': '°C'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['sensor.f007_x_faf82_temp']
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] passing event to sensor.f007_x_faf82_temp
2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'f007_x_faf82_hum', 'sensor': 'humidity', 'value': 48, 'unit': '%'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'f007_x_faf82_hum', 'sensor': 'humidity', 'value': 48, 'unit': '%'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['sensor.f007_x_faf82_hum']
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] passing event to sensor.f007_x_faf82_hum
2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'f007_x_faf82_bat', 'sensor': 'battery', 'value': 'ok', 'unit': None}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'f007_x_faf82_bat', 'sensor': 'battery', 'value': 'ok', 'unit': None}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['sensor.f007_x_faf82_bat']
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] passing event to sensor.f007_x_faf82_bat
2020-07-29 00:21:13 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'f007_x_faf82_update_time', 'sensor': 'update_time', 'value': 1595974874, 'unit': 's'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id': 'f007_x_faf82_update_time', 'sensor': 'update_time', 'value': 1595974874, 'unit': 's'}
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['sensor.f007_x_faf82_update_time']
2020-07-29 00:21:13 DEBUG (MainThread) [homeassistant.components.rflink] passing event to sensor.f007_x_faf82_update_time

How it’s possible ?

I think that you can configure it without sensor_type :

When i put without sensor type, i can’t reboot hass :\

Invalid config for [sensor.rflink]: required key not provided @ data[‘devices’][‘oregontemphygro_22866_update_time’][‘sensor_type’]. Got None. (See ?, line ?).

Ummm, you are rigth…

Try with:

    oregontemphygro_22866_update_time:
      sensor_type: timestamp
      name: Update Time

RFLink sometimes detect the same device with multiples IDs.
Because of this, there is an aliases attribute:

sensor:
  - platform: rflink
    devices:
      oregontemphygro_22866_temp:
        sensor_type: temperature
        name: Température
        aliases:
          - f007_x_faf82_temp

But, be carefull, because although it may seem like it, the signal does not come from the same device. I recommend checking it twice before adding an alias to your device.

If I am not mistaken, the Dio Chacon is a plug.
To control it you would need to do one of the following options:

  1. capture the ID of the remote that controls it and create a switch in HA
  2. generate a new switch in HA and pair it with the plug

You can get the remote ID from the logs. Pressing the remote buttons, will show the logs in HA.

For timestamp that was good thanks :smiley:

For data from oregon, i don’t understand ,
i can see them in entities now. But no data.
Can it be a auto add problem ?

I can’t see data from oregon in debug log …

Yeah the chacon is a plug. I can’t see nothing from him in log for the moment… (using the button on him )

Edit:
When i push out, and push in another battery pack in oregon. The id change, ( it’s for try to have new data incoming in rflink )…

Edit:
I wrote the id like this :

sensor:
  - platform: rflink
    automatic_add: false
    devices:
      oregontemphygro_22806_temp:
        sensor_type: temperature
        name: Température
      oregontemphygro_22806_hum:
        sensor_type: humidity
        name: Humidité
      oregontemphygro_22806_hstatus:
        sensor_type: humidity_status
        name: Statut humidité
      oregontemphygro_22806_bat:
        sensor_type: battery
        name: Niveau batterie
      oregontemphygro_22806_update_time:
        sensor_type: timestamp
        name: Update Time

And have no data incoming. If i delete automatic_add . I can see them in home-assistant.log when i take out the battery, and push them inside another time. But the id change.
And no data in Card :frowning:

Why is it so hard XD

That is because RFLink, sometimes populate the data from one device (the oregontemphygro_22866 in your case) as if they were several devices (2, 3 or even 4 different devices).
It is not an HA problem, it is how RFLink works.
To solve it, the ‘others’ devices can be configured as aliases of the known device. This way, the data from ‘all’ devices will be grouped into the main device.

It is best to do the test. In the traces you will see how the data from the ‘alias’ device is added to your oregon device.

I’m going to look in the doc about this.
id of oregon changing when i change battery is normal ?

Yes, it is pretty normal to any RF sensor to change the ID when you replace batteries.

How ok, i’m bad sorry.

So why i can’t add it properly ?
automatic_add: true let me see the oregon in logs
then i use the id found and i put them in configuration.yaml
Then i have no data coming on cards.
And it dissapear from logs …

If i do :
automatic_add: false
i can see nothing from oregon…

I don’t know why but now it’s working.
i haven’t change anything .

for the Chacon i have found this. But i don’t know where is
https://media.discordapp.net/attachments/706968301334560829/737430082641068032/Template.png?width=508&height=662

But they said to launch a command in Developpement tools, template. But i can’t find it :frowning:

Thanks again for help @javicalle

Sorry, but I’m not sure if I’m understanding you.

I think that your sensor already works for you, is it?
In any case, in the logs (at debug level) you should be able to see the signals that arrive to you, regardless of how you have configured the automatic_add property.

The image that you attach is for the rfxtrx. It’s similar to RFLink but don’t work the same way.

The ‘Developer tools’ tab it’s on the left panel (with a hammer icon). I think it doesn’t show unless you are an admin user.
You should be able to access it through the URL:
http://<your_ip>:<your_port>/developer-tools

I’m sorry about that, i’m french and pretty bad in English.
The sensors looks like to works, only oregon looks like to work sometime yes, sometimes no :frowning:

oregon

In logs at debug level, i can’t see my chacon dio using the plug button.
I have to found how to do, or i’ll give it back to amazon :frowning:

I have success added sensor form my alarm system, and trying to understand how to have
the rf signal between panel_button and the air-raid siren

Too many topics at once.

Let’s go one by one.
The sensors should leave traces on the logs. That information will tell you which ID is exposing RFLink for your devices.

You can check all your devices status at “states” tab in “Developer tools” view:

  • https://<your_ip>:<your_port>/developer-tools/state
    Here you must see your device status (temp, hum, etc)

Once you can see here your devices, can be added at your frontend.

1 Like

Sorry i have reach max response on same subject for a day…

All works Oregon works fine now.
Only one things really strange update time is in second, so the value is so big

1596045940 s
That’s have no sense, i will search how to change it :).

This value is a timestamp (seconds from 01/01/1970 00:00:00).
You can try an online converter like:

I have found this:

I will try to understand.