-
Notifications
You must be signed in to change notification settings - Fork 14
question about the homematic radio module #30
Comments
You can look at the docker logs: docker log ccu You should also check if the /dev/raw_uart is there. |
yes /dev/raw_uart exists. the erroes are:
|
May be this is the interresting part?
I assume the RF hardware is the radio module, am I right? But it looks like it is disabled. How I can enable it? |
You can Dissable means that not all required devices could be found within the container. If raw_uart is there then the second to check is e3q_loop. |
The naming of the device files a a bit different here:
|
Here the scripts output: And thx for your help! |
this did not work too: looks like the RF module is nor detected, did I need to load a kernel module for it? Or should I gif this a try? |
After updating the CCU firmware now change: |
May I should try this: |
I checked this too now, the FW update seems to be worked - I don't got a error message. Any ideas or tips what else i can check or try? |
Hi, after a test with the new RPI-RF-MOD I went back to the small HM-MOD-UART and run into the same issue as you: multimacd would not start. I personally came into this problem because I flashed the wrong firmware. To force the update you need to: |
also no luck :(, here the output of the commands:
I hope i tried it the right way? |
What is the content of your '/var/hm_mode ' and what type of radio module are you using (the old one or the new one with battery)? Mine (with the old radio module) looks like:
|
the values in my hm_mode are almost all empty. My radio module is ~3 years old without a byttery. I now tested with your settings in /var/hm_mode with this result:
|
did you also use raspbian stretch? What are your dtoverlay settings and did you had to change the kernel commandline settings in /boot/cmdline.txt to get it working? |
The values for /var/hm_mode are written by I am currently using an odroid HC1 with an USB adapter and armbian. Before I used an OrangePi with the same antenna as yours. Only initially I had a PI with raspbian used for Homematic. It looks like the homematic tools are not able to communicate with the device and therefore the firmware update fails. You said that the /dev/raw-uart is present inside the docker, correct? If this the case then What versions of the pivccu modules do you have? They should take care of configuring the cmdline and overlays correctly... |
@horchi - I think I have found the issue: the realtime scheduler in the kernel. Without it the multimac module was not able to connect sucesfully to the antenna. I have extended the deploy.sh script to enable the realtime scheduler. Could you please see if helps you? In my case I also had problems with one of my antenna modules: I had managed to load a broken firmware so I had to manually load the firmware before it worked again: the CCU scripts spect to at least be able to query the version which is not possible when the firmware is damaged. |
This is fixed in the latest deploy.sh script |
Hi,
I just cloned the docker-ccu master branch, called build.sh and deploy.sh on a raspberry 3b
Then I imports the settings from my ols instaltion (also on a raspberry).
After that i can see my devices and programms on the web interface :)
Then I shutdown and installes the homematic radio module (which I used before at the old raspberry) andd booted again.
After logging in to the web interface I get the Message:
The /dev/ttyS0 is present, the cmdline.txt looks like:
dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f14d53a-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles usbhid.mousepoll=0
and dtoverlay ist set to:
root@dashboard:/boot# grep dtov config.txt dtoverlay=pivccu-raspberrypi dtoverlay=pi3-miniuart-bt
Any hint what is going wrong? Is there someting like a homatic log file which can help? In the syslog i calt find a hint about the problem.
May I have to use the ccu2 branch instead of master?
Thx and regards Jörg
The text was updated successfully, but these errors were encountered: