Switched to a RasPi 4 recently. Had to change the config.txt options to
dtoverlay=uart1
dtoverlay=disable-bt
Unfortunately now bluetooth does not work (okay - nobrainer, as I disabled it). Anyone got an idea?
Switched to a RasPi 4 recently. Had to change the config.txt options to
dtoverlay=uart1
dtoverlay=disable-bt
Unfortunately now bluetooth does not work (okay - nobrainer, as I disabled it). Anyone got an idea?
hi,
I’m trying to get rid of the extra pi for the ccu and achieving a all in one solution.
So I’m also struggling with the integration and the HM-MOD-RPI-PCB modul, config.txt is still edited, but now afraid to made the FW update mentioned above, as it might not work and want to go back to my old pivccu setup and it may broke due to the FW update. how can i go back to old FW?
thanks in advance!
I am also interested in the process with the PCB Module and a Raspi 4 to get rid of the CCU2 in my case.
Thanks
is this still valid ? or do you have issues?
I tested my module with raspberrymatic, it works on the Raspberry Pi 3.
The firmware version of the module is 2.8.5 - so it got successfully upgraded by raspberrymatic.
Now back on HA - I added the following to the config.txt
enable_uart=1
dtoverlay=pi3-miniuart-bt
But still, getting this
[14:18:59] INFO: Starting rfd...
2021/02/03 14:18:59.759 <Info> BidCoS-Service started
2021/02/03 14:18:59.760 <Info> XmlRpc Server is listening on TCP port 2001
2021/02/03 14:18:59.761 <Debug> CCU2CommController::init() - Legacy initialization.
2021/02/03 14:19:04.762 <Debug> () CCU2CommController::startCoprocessorApp(): Trying to start coprocessor application
2021/02/03 14:19:05.263 CCU2CommController::startCoprocessorAppThreadFunction(): Send start command
2021/02/03 14:19:05.263 CCU2CommController::SendSystemCommdand()
2021/02/03 14:19:05.263 CCU2CommController::SendSystemCommdand() sending: fd 00 03 00 00 03 18 0a
2021/02/03 14:19:06.263 <Debug> () CCU2CommController::waitForCoProcessorResponse(): Timeout while waiting for response.
2021/02/03 14:19:08.263 CCU2CommController::startCoprocessorAppThreadFunction(): Retrying to send start command
2021/02/03 14:19:08.263 CCU2CommController::startCoprocessorAppThreadFunction(): Send start command
2021/02/03 14:19:08.263 CCU2CommController::SendSystemCommdand()
2021/02/03 14:19:08.263 CCU2CommController::SendSystemCommdand() sending: fd 00 03 00 01 03 9e 09
2021/02/03 14:19:09.263 <Debug> () CCU2CommController::waitForCoProcessorResponse(): Timeout while waiting for response.
2021/02/03 14:19:09.763 <Fatal error> CCU2CommController::init(): Init failed. Cannot start coprocessor application.
2021/02/03 14:19:09.763 CCU2CommController::SendSystemCommdand()
2021/02/03 14:19:09.764 CCU2CommController::SendSystemCommdand() sending: fd 00 04 00 02 0a 00 3d 10
2021/02/03 14:19:10.764 <Debug> () CCU2CommController::waitForCoProcessorResponse(): Timeout while waiting for response.
2021/02/03 14:19:10.764 <Error> () CCU2CommController::setCSMACAEnabled(): Error disabling CSMA/CA.
2021/02/03 14:19:10.764 <Error> No BidCoS-Interface available
2021/02/03 14:19:10.765 <Warning> Error initializing interfaces
2021-02-03 14:19:10,766 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java
2021-02-03 14:19:10,769 [ERROR] BidCosRpcDispatcher - Could not register BidCos-RF_java
What is wrong with my setup ?
I am still working on getting the module running on a RPI4 and RPI3+ but I found something interesting
This information, at least, allowed me to use this Docker Images to flash the Module with a “supported” firmware
But anyhow still trying to figure out the rest, so perhaps this helps someone to get the module running (perhaps even with bluetooth activated).
Cheers
update 08.02.2021 19:41
Here I have collected some more information, I am now at the point were I can use the docker container to make a firmware upgrade and be able to start the addon without errors on my RPi 3+
The Webui is not stuck