-
Notifications
You must be signed in to change notification settings - Fork 14
How to troubleshoot "BidCos-RF : Eine Komponente der Homematic Zentrale reagiert nicht mehr."? #23
Comments
Hi @JPHsProjects : I also get the same warning but the wireless connection to Homematic devices still works. Are you able to also discover your wireless devices or are you only using wired homematic devices? The error comes because the wired controler is not getting initialised. The virtual devices do not work because they depend on the new dual stack for Homematic IP which depends on a kernel module on the host (so not really good handling with docker). I think it should be able to disable the wired stack controller in rega so the warning does not show up - I tried some months ago but I quickly gave up since the error was only a cosmetic problem for me. I am planning to add support for the Homematic IP USB controller during the vacations so I can run one container for Homematic and another for Homematic IP (and avoid depending on kernel modules). I will keep an eye on finding a way to disable the error pop-up. |
Hello @angelnu, thank you very much for your quick response! The screenshot shows the view with CCU2 in the Docker container: The PIVCCU based installation looks more complete - using the same RF module on the same raspberry Pi: I could compare a little between the two (not fully, as PIVCCU is based on an Lxc container, but I can reach at least both consoles to check something out...), but I need some hints what to check out. Is there some command to inspect the messages or debug information from the CCU2 console? |
I just learned that the SSH console of the CCU2 does not expose the same file system as if logged into the root of the container. To get to the SSH shell, I moved the port for the Raspberry shell to elsewhere, added So from the SSH shell of the CCU, I found some hints:
|
the log in your first post shows the problem starting the rfd daemon: it fails to connect to the antenna module. From your boot settings I do not see that you disabled the Bluetoth device so I expect it is using the same UART as the Homematic adapter. Please check this link from the readme. Btw: I just got the USB adapter for Homematic IP to work so it will be possible to use both with my docker container. Unfortunately not with only one antenna.... |
@angelnu Thank you for your quick response! The container is running on a Raspberry Pi 2, which has no Bluetooth module, so there is nothing to disable. That the If I issue
Just in case this tells something... |
Ok, I had not see that you were in Raspberry 2 - no Bluetoth there :-) but the rfd is still getting traffic that it should not: When you tried to manually start rfd, did you check before that there was not other instance of rfd running? |
That's a very valid point. But as the rfd service does not start properly it was off when i tested the commands above. |
@JPHsProjects - could you please test with the mayor upgrade I just released? The log now contains way more information and I have tested again with all my ARM boards at home. |
I installed the latest build on a fresh Rasbbian Stretch. Unfortunately, the issue stays: I can open the Homematic GUI, but the device discovery dialog is still empty. Now, for unknown reasons, I cannot enter the SSH console anymore (Permission denied). The port is exposed and reacts normal - just my password given tin the Homematic GUI is not accepted. So it's hard to provide useful debug information. |
@JPHsProjects - I did not test ssh since I usually do Did you extend the deploy.sh script to add port 22? If you manually start the docker container please notice that the command has changed in order to have access to the GPIO and the eq3 loop device for HomematicIP. |
Yes, I added My current log looks like this, but I was fiddling around with pivccu3 modules, so I might have broken something else...
|
I should mention that one thing did not run through the deploy.sh: |
I think I now understand the problems:
The broken shadow file looks like this:
while the right one from /etc/config_templates looks like this:
|
Please use the updated deploy.sh:
|
After a fresh install I build and deployed the latest version. It works now! This is the output of
|
@angelnu A big thank you for fixing this issue and spending all the effort into the CCU docker images! Thank you also for your fast responses! I close this issue, as I can properly discover Homematic devices now (ssh works also fine again): |
Acknowledgement:
First, I would like to thank Angelnu for this great repository! Binning the CCU2 into a docker container is one of the best and most flexible solutions for systems that should run multiple services in parallel.
Issue:
I think I got it almost running, but there is a piece missing. I can log into the web GUI fine, but after one minute several pop up messages appear from which this one is probably the most severe one: "BidCos-RF : Eine Komponente der Homematic Zentrale reagiert nicht mehr." Others had this issue as well, but all solutions I tried, did not help in my case: The BidCos-RF seems not to initialize properly with the HM-MOD-RPI-PCB (see log of
rfd -l 0 -c
at the far end of this post).Below you find my log files and the things I checked. The HM-MOD-RPI-PCB is working fine with another Raspberry Pi based installation on PIVCCU. The module seems also to respond to firmware queries from inside the container.
My question is, how can I diagnose the issue further to resolve this issue?
Logs and Data:
I installed a fresh Raspbian Stretch on a Raspberry 2 B V1.1, disabled the serial console but enabled the serial port. Then installed docker and created the docker container with
./build.sh
and./deploy.sh
.The following commands are executed on the host raspberry pi system:
uname -a
shows:cat /etc/os-release
shows:docker version
shows:cat /boot/cmdline.txt
shows:cat /boot/config.txt
shows:sudo ./deploy.sh
shows:docker logs -f ccu2
shows:cat rfd.conf
shows:The following commands were executed inside the docker container, which was entered by the command:
docker exec -it ccu2 /bin/sh
.Retrieving the serial number from the HM-MOD-RPI-PCB by the command
eq3configcmd update-coprocessor -p /dev/mmd_bidcos -c -se -d /firmware
shows (inside container execution):Retrieving the firmware version from the HM-MOD-RPI-PCB by the command
eq3configcmd update-coprocessor -p /dev/mmd_bidcos -c -v -d /firmware
shows (inside container execution):Triggering the firmware update for the HM-MOD-RPI-PCB by the command
eq3configcmd update-coprocessor -p /dev/mmd_bidcos -c -u -d /firmware
shows (inside container execution):rfd -l 0 -c
shows:The text was updated successfully, but these errors were encountered: