since several years I use YAHM on a pi3 together with openhab. Some time ago I decided to switch to a pi4 and use piVCCU3 instead of YAHM. Therefore I ordered a HB-RF-USB-2, mounted my old HM-MOD-RPI-PCB on it and installed piVCCU3 via https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md.
First thing I noticed was that the installation routine only shows
I expected somehow a USB device there !? lsusb shows Bus 001 Device 003: ID 10c4:8c07 Cygnal Integrated Products, Inc which is HB-RF-USB-2 I guess.
I proceeded and selected HM-MOD-RPI-PCB, the device selection screen afterwards did not showed anything useful. So I didnt selected something and just confirmed via OK.
And what should I say? Everything worked perfectly. My devices are still there and reachable (via OpenHab).
So whats my issue? 🤔
After every reboot it stops working. The CCU3 WebUI says that some components (BidCos) do not work properly. pivccu-info yields
$ pi@cnc:~ $ sudo pivccu-info
piVCCU version: 3.51.6-41
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Not assigned to GPIO pins
HMRF Hardware: unknown
HMIP Hardware: unknown
Board serial: unknown
Radio MAC: unknown
SGTIN: unknown
State: RUNNING
PID: 1414
IP: 192.168.1.111
CPU use: 3.38 seconds
BlkIO use: 19.23 MiB
Link: vethpivccu
TX bytes: 22.76 KiB
RX bytes: 33.12 KiB
Total bytes: 55.88 KiB
All the unknowns confused me a little bit 🤷♂️ So I tried to re-run the configuration step via sudo dpkg-reconfigure pivccu3. Its the same like the first time, no USB devices and no useful output on the selection screen but it works afterwards. The output of pivccu-info looks better now (its the same like after the very first time)
$ pi@cnc:~ $ sudo pivccu-info
piVCCU version: 3.51.6-41
Kernel modules: Available
Raw UART dev: Available
Rasp.Pi UART: Not assigned to GPIO pins
HMRF Hardware: HM-MOD-RPI-PCB
HMIP Hardware: HM-MOD-RPI-PCB
Board serial: NEQ0229909
Radio MAC: 0x4708a5
SGTIN: 3014F711A061A7D5698CEA15
State: RUNNING
PID: 32498
IP: 192.168.1.111
IP: PublicIpv6AddressHere
CPU use: 20.36 seconds
BlkIO use: 100.00 KiB
Link: vethpivccu
TX bytes: 4.88 MiB
RX bytes: 695.25 KiB
Total bytes: 5.56 MiB
The only difference in outputs is the IPv6 address but I cant imagine a scenario where this matters.
Im a little bit lost now and grateful for any tips 🤗
My setup:
PI4
piVCCU 3.51.6-41
Edit: A simple restart of the service also fixes the issues 🤔
Hi,
since several years I use YAHM on a pi3 together with openhab. Some time ago I decided to switch to a pi4 and use piVCCU3 instead of YAHM. Therefore I ordered a HB-RF-USB-2, mounted my old HM-MOD-RPI-PCB on it and installed piVCCU3 via https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md.
First thing I noticed was that the installation routine only shows
I expected somehow a USB device there !?
lsusb
showsBus 001 Device 003: ID 10c4:8c07 Cygnal Integrated Products, Inc
which is HB-RF-USB-2 I guess.I proceeded and selected
HM-MOD-RPI-PCB
, the device selection screen afterwards did not showed anything useful. So I didnt selected something and just confirmed viaOK
.The CCU3 WebUI is accessible via IP and I restored a backup of my YAHM CCU2 installation. I did all the YAHM migrations things listed here https://github.com/alexreinert/piVCCU#migration-from-other-systems
And what should I say? Everything worked perfectly. My devices are still there and reachable (via OpenHab).
So whats my issue? 🤔
After every reboot it stops working. The CCU3 WebUI says that some components (BidCos) do not work properly.
pivccu-info
yieldsAll the
unknown
s confused me a little bit 🤷♂️ So I tried to re-run the configuration step viasudo dpkg-reconfigure pivccu3
. Its the same like the first time, no USB devices and no useful output on the selection screen but it works afterwards. The output ofpivccu-info
looks better now (its the same like after the very first time)The only difference in outputs is the IPv6 address but I cant imagine a scenario where this matters.
Im a little bit lost now and grateful for any tips 🤗
My setup:
Edit: A simple restart of the service also fixes the issues 🤔