The pairing process stores the unit and channel number of your remote or USB stick within your shutter.
Therefore if you change your unit or channel in your HA configuration, you need to do the following steps:
Remove your old configuration from your shutter (see manual of your master remote: remove all remotes except master).
Pair the USB stick with the new unit and channel settings
Iâve got two skylights with Becker motors. Each has its own single channel EC411-III remote.
Hereâs what Iâve done so far.
Inserted the Becker centronics stick into my server (using an 1m extension cord; distance to both windows is ~6m) and passed it to the VM that is running Home Assistant OS and rebooted. The device shows up inside of the VM.
Added the repository (v0.3.3) in HACS as a custom repository and restarted HA.
Enabled debug logging for the custom component and added the following configuration to configuration.yaml
The becker-centronic.db not created is curious. This could be a reason for your problems. Is it working when you remove the filename option? The default filename is fine as well. It should only complain once, that the database is not there. After another reboot this issue should be gone.
Do you see any debug messages when you press the key of any of your master remotes? This should be the case, as the Becker integration recieives commands from the USB stick.
Did you buy the right USB stick? The Centronic USB Stick with the Becker order number 4035 200 041 0 is the right one.
There was also a non functional USB stick in the past. Consider to send it back as non functional.
No, removing the filename option doesnât generate the DB with the default name either. Thatâs the reason why I picked a custom name in the first place.
No, I donât see any log messages when I control the blinds with my EC411-III remotes.
My USB stick has the order number 4035 000 041 0. The seller (an official Becker distributor) advertised it as âV2â and in fact, mentions the order number 4035 200 041 0 in their shop.
Later today I also used centronic-py, the python module this HA component is based upon on a different PC with the USB stick attached and tried to train it without Home Assistant, VMs and whatever in the way, following the instructions on the github. But after executing ./centronic-stick.py --send TRAIN --channel 1 nothing ever happens, like thereâs no communication at all between the stick and the remote / motor.
So, if I get you right, my USB stick with the 000 instead of 200 in the order number is simply incompatible?
Hi what was not clear for me, thats was the following:
I have 4 remotes each for one of my 4 skylights.
So my configuration lookes like this: 1:1 2:1 3:1 4:1
I pared the covers already with the original Becker Central Control CC41 Unit. So first I thought the config should already on the USB device and there is no need to pair it.
I had to pait it again in the developer mode â Service
service: becker.pair
data:
channel: 1
unit: 4
This is my configuration.yaml
[core-ssh config]$ cat configuration.yaml
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
alexa:
smart_home:
cover:
- platform: becker
device: "/dev/serial/by-id/usb-Becker-Antriebe_GmbH_CDC_RS232_v125_Centronic-if00"
covers:
dachgeschoss1:
friendly_name: "cc-de-sl-1"
channel: "1:1"
dachgeschoss2:
friendly_name: "cc-de-sl-2"
channel: "2:1"
dachgeschoss3:
friendly_name: "cc-de-sl-3"
channel: "3:1"
dachgeschoss4:
friendly_name: "cc-de-sl-4"
channel: "4:1"
logger:
default: info
logs:
# This must correspond to the folder name of your /config/custom_components/becker folder
custom_components.becker: debug
First of all, my USB Stick is a 200 model. Itâs only the sticker on the package that says 000 and I didnât look if there is a number printed on the stick at that time.
Secondly, the issue I had with the centronic-py script was my own fault. I opened a listening session in one terminal while trying to train it in another one and didnât consider that the first one would be blocking the other.
With that issue out of the way, I could train the USB stick with both motors using that python script. I could then insert the stick back into my server, reboot Home Assistant and there you go: the DB file has been created, I can read commands coming from my remotes and can control the skylights via Home Assistant.
Could you please open an issue in my GitHub repository. Please add the entire log around the decode error.
The Becker Centronic protocol relies on increasing count in each packet (except for pairing). If this is not the case because of problems with database it will not work.
Hi all,
writing this from Melbourne, Australia. I hope there are other local iusers hereâŚ
I just got 2 awnings with Becker motors and a remote.
I contacted the Australian importer/distributor about the USB stick; I asked for the one recommended by @RainerS in the GitHub page.
I was told that down here (in AU) Becker use a slightly different frequency and so instead of xxxx xxx 041 x we get xxxx xxx 051 x. That sounded ok to me - I understand that different regions have different frequency spectrums available.
Then I was told that the exact model/order number is 4034 000 051 0
Does anyone here know if thatâs correct?
@RainerS - would you be OK if I go ahead and get this stick and, if not working as expected, would you be able to help get it going?
What price were you quoted for the item ?? When I asked the mob in Canberra a couple of years ago they wanted nearly $300 so decided I didnât really need it.
I installed Home Assistant thought Virtual Machine Manager on my synology NAS.
Will the Becker Centronic USB Stick be recognized or do you suggest to migrate to a RPI4?
Hi Nico,
This should work. Others managed this as well. You need to pass the USB port used for your Becker stick into your VM. Maybe the device path is different and needs to be adjusted in your configuration.
Using a Rpi4 for Home Assistent is not the best way from my point of view.