angelnu
commented
5 years ago 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.
JPHsProjects
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 -cat 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.shand./deploy.sh.The following commands are executed on the host raspberry pi system:
uname -ashows:cat /etc/os-releaseshows:docker versionshows:cat /boot/cmdline.txtshows:cat /boot/config.txtshows:sudo ./deploy.shshows:docker logs -f ccu2shows:cat rfd.confshows: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 /firmwareshows (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 /firmwareshows (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 /firmwareshows (inside container execution):rfd -l 0 -cshows: