Rflink - chacon dio

Hello,

I create a new topic for a new problem.
I have bought a chacon dio 54785 .

I use the protocol to add him on se platform rflink. And try to found the entities id, debug logs.
And i can’t see anything, how can i find elements to add this plug 433,92mhz !!

Thanks a lot for helps

Hi here too!

If I’m not mistaken, this device is a plug, correct?
In addition to the plug, do you have a remote to turn it on and off? (the button of the plug don’t count to what we need)

If you have a remote, you can use the device_id of the remote control to control it from HA or generate a new one in HA.

If you do not have a remote, you will need someone to indicate the ‘format’ of the device_id that accepts this type of plug in HA.

Hey,

no i do not have remote for this plug …

Ok.

It would be easier if someone told us what protocol supports this device, or if it has any limitations.

If we don’t get that information, you can try to go blind with some protocol waiting for it to work.

In any case, you will need to register a new switch type device in HA.
Once the device is configured in HA you will have to pair it with the plug. The procedure should come in the instructions. To pair it, I think it’s better if you use the “Developer tools” and invoke whatever service (for example: switch.turn_on):

  • http://<your_ip>:<your_port>/developer-tools/service
  • service: switch.turn_on
  • entity: switch.your_new_entity

I think you lose nothing by trying any of the following device_id:

  • Powerfix_000080_0
  • Kaku_00004d_1
  • NewKaku_00c142_1
  • NewKaku_128ac4d_1

Refs:

As far as I know, the chacon dio’s use newkaku.

* http://<your_ip>:<your_port>/developer-tools/service
* service:  `switch.turn_on`
* entity:  `switch.your_new_entity`

I think you lose nothing by trying any of the following  `device_id` :

* Powerfix_000080_0
* Kaku_00004d_1
* NewKaku_00c142_1
* NewKaku_128ac4d_1

I have tried all this, in switch.turn_on
and doesn’t works :frowning:

https://xxxxsxxxxx:xxxx/developer-tools/service

switch.turn_on
switch.NewKaku_00c142_1

and nothing
Does the chacon plug waiting for a key ?

Have you first created the switch in HA?
Have you tried pairing the switch? You must first put the plug into pairing mode.
What does the manufacturer’s procedure say?
Any logs?

Awww i didn’t undertand that :sweat_smile: :sweat_smile:
I have to create the switch before using those command ?

My bad :smile: :smile:

  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 125, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1235, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 208, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 287, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 283, in _exec
    v = func(v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)

with switch.NewKaku_00c142_1

In the manufacturer’s : ( I will try google translate )

Learning the code:
1 Approach the receiver transmitter, press the receiver socket learning button.
2 The receiver led flashes slowly and press the transmitter on button
3 The light connected to the receiver flashes twice, the code is confirmed and the led stops flashing.

Yes, that was the idea.

But I think we can take another approach. Let’s try this, instead of creating the switchin HA, we can call the rflink.send_command service.
At the “developer tools” > “services”, you can find the rflink.send_command service.
There is an option at the bottom “Fill example data”, push it to fill the config part.
Now, you can try to pair any device_id without creating it first in HA.

You need to find a valid device_id, so you have to repeat the whole process for each ID you want to test.

The steps will be (more o less according to your info):

  1. Approach the receiver transmitter, press the receiver socket learning button.
  2. While the receiver led flashes slowly, call the rflink.send_command service in HA
  3. The socket led will flash twice. If not, repeat the rflink.send_command again. You need to see the led flashing twice.

Once paired (the socket have paired twice), verify that you can switch on and off the socket with the rflink.send_command (changing the command: 'on' to off).
If it works as expected, then create in HA the new switch with the device_id paired.

It’s make some data in logs:
But i can’t understand them :smile:

2020-07-30 13:40:30 DEBUG (MainThread) [rflink.protocol] sending command: {'protocol': 'NewKaku', 'id': '128ac4d', 'switch': '1', 'command': 'on'}
2020-07-30 13:40:30 DEBUG (MainThread) [rflink.protocol] writing data: '10;NewKaku;128ac4d;1;on;\r\n'
2020-07-30 13:40:30 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2020-07-30 13:40:31 DEBUG (MainThread) [rflink.protocol] received data: 20;2C;OK;
2020-07-30 13:40:31 DEBUG (MainThread) [rflink.protocol] got packet: 20;2C;OK;
2020-07-30 13:40:31 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-07-30 13:40:31 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-07-30 13:40:31 DEBUG (MainThread) [rflink.protocol] packet acknowledged
2020-07-30 13:40:52 DEBUG (MainThread) [homeassistant.components.rflink] Rflink command for {'command': 'on', 'device_id': 'newkaku_0000c6c2_1'}
2020-07-30 13:40:52 DEBUG (MainThread) [rflink.protocol] sending command: {'protocol': 'newkaku', 'id': '0000c6c2', 'switch': '1', 'command': 'on'}
2020-07-30 13:40:52 DEBUG (MainThread) [rflink.protocol] writing data: '10;newkaku;0000c6c2;1;on;\r\n'
2020-07-30 13:40:52 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] received data: 20;2D;O
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] received data: K;
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] got packet: 20;2D;OK;
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-07-30 13:40:53 DEBUG (MainThread) [rflink.protocol] packet acknowledged

Those traces are only reporting that you have sent the on command for the device_id NewKaku_128ac4d_1 and newkaku_0000c6c2_1.

Are you familiar with the procedure of pairing a new device?
Have you tried to pair your plug?
The HA traces are not going to tell you anything since that part is working as expected (is sending the command that you want). I think at this point your problem has nothing to do with HA.

When i push Fill example data
it’s auto add this line :

service

I have tried to use the button to add him. (on the plug i mean )

Please, if you do not try to provide all the requested information, it is very difficult to try to help you.

Have you put the plug into pairing mode?
Was the plug led flashing slowly when you tried to pair?
Have you seen if the plug led blinked twice when invoking the command from HA?

I think you are having trouble understanding the device pairing procedure and that has nothing to do with HA. I recommend to find a video tutorial for your plug.
When you know the procedure, it will be easier for you to do it with HA.

1 Like

Are you familiar with the procedure of pairing a new device?
Yes, pressing pairing button, and led flash.

Have you put the plug into pairing mode?
Yes

Was the plug led flashing slowly when you tried to pair?
Yes

Have you seen if the plug led blinked twice when invoking the command from HA?
No
I think you are having trouble understanding the device pairing procedure and that has nothing to do with HA. I recommend to find a video tutorial for your plug.
If him wondering in this forum, it’s because i have tried to find tutorial, and vidéos but i couldn’t.

When you know the procedure, it will be easier for you to do it with HA.

Yeah, sure.
Sorry about the fact, i’m newb in this system.
Thanks a lot for help.

The normal procedure for these kind of device : pair the plug with the remote, and let HA (rflink) capture the remote signal. But since you don’t have the remote. It should be possible, the problem is finding a correct signal.

Well hard to says, if i had to buy a remote.
I’ll give this plug back to amazon and take a zwave one :frowning:

A WiFi, ZigBee or zwave plug is always better than a Rf433 one. Rf433 does not give feedback if they are on or off, the others do.

yeah but witch model is the best offer price/quality
And with good protection ( French ground ).

I have zwave/zigbee platform. And wifi can be too :slight_smile:

I have 5 of these, use them with zigbee2mqtt

Although in France they are half the price of here.

1 Like

Thanks :slight_smile:
@javicalle Thanks a lot for your help, and sorry for my english again.
@francisp Thanks, but i’ll try to find one with electricity data…

Sorry for the inconvenience. :slight_smile: