Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot pair or receive packets with Centronic USB 4035 200 041 0 (24-37) #54

Open
marcow1601 opened this issue Nov 28, 2024 · 4 comments

Comments

@marcow1601
Copy link

marcow1601 commented Nov 28, 2024

I have bought a Becker Centronic V2 USB-Stick. The box says 4035 000 041 0, however the label on the USB stick itself says 200 instead of 000. I installed the HASS Becker integration as explained via HACS.

I have also added two covers in the configuration.yaml, however, when trying to pair via the service, I do not get any feedback from my Roto shutters. One "clack" after activating pairing mode through my EC411-III master remote - no clacks afterwards.

The log shows that some data is being sent:
2024-11-28 14:30:48.072 DEBUG (Thread-2) [custom_components.becker.pybecker.becker_helper] Sent packet: unit_id: 1737B, channel: 5, command: TRAIN, argument: 1, packet: b'\x020000000002010B00140000001737B021010500813B\x03'
2024-11-28 14:30:48.374 DEBUG (Thread-2) [custom_components.becker.pybecker.becker_helper] Sent packet: unit_id: 1737B, channel: 5, command: RELEASE, argument: 0, packet: b'\x020000000002010B00150000001737B02101050000BB\x03'
2024-11-28 14:30:48.676 DEBUG (Thread-2) [custom_components.becker.pybecker.becker_helper] Sent packet: unit_id: 1737B, channel: 5, command: TRAIN, argument: 1, packet: b'\x020000000002010B00160000001737B0210105008139\x03'

However, when pushing buttons on my master remote, I do not get any Received packets in the Debug log. This leads me to believe that the communication with the USB stick is not working as it should.

In the HASS hardware overview I can see it as follow:
ID: /dev/serial/by-id/usb-Becker-Antriebe_GmbH_CDC_RS232_v125_Centronic-if00

My configuration.yaml:
cover:

  • platform: becker
    device: "/dev/serial/by-id/usb-Becker-Antriebe_GmbH_CDC_RS232_v125_Centronic-if00"
    filename: "centronic-stick.db"
    covers:
    kueche:
    friendly_name: "Küche Dachrolladen"
    channel: "1"
    schlafzimmer:
    friendly_name: "Schlafzimmer Dachrolladen"
    channel: "5"

Any hints as to what I could do to solve this issue? :(

@marcow1601
Copy link
Author

I have an update myself here:

For debugging purposes I connected the Centronic USB to a Raspberry Pi and installed ole1986's CentronicPy.
Running the listening command with his script I am receiving Data Packets when pushing buttons on my EC411 sender.

@marcow1601
Copy link
Author

marcow1601 commented Dec 3, 2024

Pairing and controlling the two shutters on channels 1 and 2 is also successful using CentronicPy on the BananaPi

Question: Should it now be possible to move the USB stick to my HASS device and be able to control the shutters without retraining them? I feel this should be possible, but please correct me if I'm wrong.

@RainerStaude
Copy link
Owner

RainerStaude commented Dec 3, 2024

It should work with the integration as well, if it works with the script.
A common mistake is a wrong order of unit and channel between the becker.pair service and the configuration.
If you have successfully trained with the script, you don't need to train again with the becker integration.
You might need to press HALT several times to sync.

If you don't receive any packets, please try to perform a full reboot (not only home assistant, fully reboot the system). Maybe re-plug the USB stick before.

@marcow1601
Copy link
Author

Indeed, it works perfectly well inside HomeAssistant now.

However, I do not think the mistakenly switched order of data parameters can be the reason. Since I am using unit 1, channel 1 and loaded the "example data" for the service call, I believe it is impossible to switch something by accident. Would you agree?

I also did multiple restarts/re-plugs/re-loads in between... but of course there were a few more in the meantime, so who knows...

I am now unsure if I should mark this issue as solved? I feel (hope) it is solved for me at this point, however, for someone else stumbling upon the same problem, binding the USB stick with a separate Linux device might not be a suitable solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants