Closed passuff closed 6 years ago
treid with several browser. iexplorer gave me an errror message (translated from DE): failed with restore: there is no coprocessor available.
Please provide more information:
sudo pivccu-info
sudo pivccu-attach cat /var/hm_mode
sudo pivccu-attach cat /var/log/hmserver.log
sudo pivccu-attach cat /var/log/messages
I'm using a Raspberry Pi 3 Modell B+.
sudo pivccu-info piVCCU version: 3.37.8-3 Kernel modules: Available Raw UART dev: Available Rasp.Pi3 UART: Assigned to GPIO pins HMRF Hardware: unknown HMIP Hardware: unknown Board serial: unknown Radio MAC: unknown SGTIN: unknown State: RUNNING PID: 760 IP: 192.168.178.55 IP: 2a02:xxx:xxxx:xxx:xxxx:xxxx:xxxx:xxxx CPU use: 191.63 seconds BlkIO use: 36.91 MiB Link: vethpivccu TX bytes: 5.28 MiB RX bytes: 10.48 MiB Total bytes: 15.76 MiB
sudo pivccu-attach cat /var/hm_mode HM_HMIP_ADDRESS='' HM_HMIP_DEV='' HM_HMIP_DEVNODE='' HM_HMIP_SERIAL='' HM_HMIP_SGTIN='' HM_HMIP_VERSION='' HM_HMRF_ADDRESS='' HM_HMRF_DEV='' HM_HMRF_DEVNODE='' HM_HMRF_SERIAL='' HM_HMRF_VERSION='' HM_HOST='rpi3' HM_HOST_GPIO_RESET='' HM_HOST_GPIO_UART='/dev/raw-uart' HM_LED_GREEN='' HM_LED_RED='' HM_LED_YELLOW='' HM_MODE='NORMAL' HM_RTC=''
sudo pivccu-attach cat /var/log/hmserver.log Oct 16 05:06:14 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloo p-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configurati on - currently deployed 18 out of 20 Oct 16 05:06:14 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloo p-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareU pdateInitialization still not met - check deployment configuration (still unful filled: [connector.open]) Oct 16 05:06:14 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloo p-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion s till not met - check deployment configuration (still unfulfilled: [connector.op en]) Oct 16 05:06:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloo p-thread-6] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareU pdateInitialization still not met - check deployment configuration (still unful filled: [connector.open]) Oct 16 05:06:21 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloo p-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion s till not met - check deployment configuration (still unfulfilled: [connector.op en])
sudo pivccu-attach cat /var/log/messages Oct 15 22:28:15 piVCCU syslog.info syslogd started: BusyBox v1.28.4 Oct 15 22:28:15 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-08-29 11:23:30 CEST) Oct 15 22:28:15 piVCCU syslog.info syslogd exiting Oct 15 22:28:15 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4 Oct 15 22:28:15 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-08-29 11:23:30 CEST) Oct 15 22:28:15 ccu3-webui daemon.err udhcpc[150]: started, v1.28.4 Oct 15 22:28:15 ccu3-webui daemon.err udhcpc[150]: sending discover Oct 15 22:28:15 ccu3-webui daemon.err udhcpc[150]: sending select for 192.168.178.55 Oct 15 22:28:15 ccu3-webui daemon.err udhcpc[150]: lease of 192.168.178.55 obtained, lease time 864000 Oct 15 22:28:16 ccu3-webui user.info firewall: 'modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/4.14.70-v7+ ip6tables v1.6.2: can't initialize ip6tables table
filter': Table does not exist (do you need to insmod?) Perhaps ip6tables or your kernel needs to be upgraded.'
Oct 15 22:28:16 ccu3-webui daemon.info ifplugd(eth0)[198]: ifplugd 0.28 initializing.
Oct 15 22:28:16 ccu3-webui daemon.info ifplugd(eth0)[198]: Using interface eth0/9A:C6:96:91:4A:94 with driver
Which RF hardware are you using? The output of pivccu-info indicates, that you have no RF hardware connected to the Pi.
I'm waiting to finish the restore to connect it. its currently connected to the piVCCU2 raspi.
This explains your issue: The CCU3 firmware has some validations on the restore, which require a RF module. I do not really know, what this validation do exactly, as they are inside the closed source of eQ-3.
OK, I think it was different for the CCU2 firmware as this is my usual (failsafe) update procedure. Anyway I will try again with the hardware connected.
Any news?
Please reopen, if there are still issues with connected hardware.
Sorry for the late feedback. After installing the RF Module everything worked fine.
Tried to restore a backup from piVCCU2 2.35.16 but piVCCU3 always freezes while uploading. Anyone else had this issue?