ich habe die folgende Konfiguration. Raspberry Pi3 mit HM-MOD-RPI-PCB Modul. Auf diesem läuft derzeit bereits Pilight mit 433Mhz Sender und Empfänger sowie ein Openhab2.
Als nächstes wollte ich gerne YAHM mit HmIP Unterstützung installieren. Im Folgenden findet ihr die dazu getätigten Befehlasaufrufe. Teilweise musste ich den Parameter -f nutzen, da ich einige der Aufrufe ansonsten nicht "erfolgreich" hätte ausführen können.
Code: Alles auswählen
wget -nv -O- https://raw.githubusercontent.com/leonsio/YAHM/master/yahm-i
sudo yahm-lxc -f install
sudo yahm-network -w create_bridge
sudo yahm-network attach_bridge
sudo yahm-ctl start
sudo yahm-module -m hm-mod-rpi-pcb enable
Testhalber hatte ich auch schon mal den "Geräter anlernen" Button betätigt. Leider kann ich mich an die Reaktion nicht mehr wirklich erinnern, bin aber der Meinung, nicht auf Probleme gestoßen zu sein. Da ich HmIP benötige habe ich dann folgeden Befehl aufgerufen:
Code: Alles auswählen
sudo yahm-module -m pivccu-driver -f enable
"Die Homematic CCU ist noch nicht bereit!" ...
Wenn ich nun den "Geräte anlerenen" Button in der WebUI drücke, bekomme ich die Meldung, das der Homatic Funk Anlernmodus nicht aktiviert werden konnte. Weiterhin bekomme ich nach kurzer Zeit wieder die drei oben beschriebenen Fehlermeldungen.
Ich habe das alte Log gesichert und folgendes aufgerufen:
Code: Alles auswählen
sudo yahm-ctl stop
sudo yahm-ctl start
Code: Alles auswählen
2018/12/27 09:30:06.471 <Error> CCU2CommControllerMod::performIdentify(): Unable to determine coprocessor state.
LED Code: System start: spidev
ic200_spi
spi_eq3_gpio
spi_bitbang
mknod: spidev0.0: File exists
gpio-keys
fsl_usb2_udc.ko
tun
ehci-hcd
mxs_raw_auart
eq3_char_loop
OK
Init Firewall: Starting crond: OK
crond[78]: crond: crond (busybox 1.20.2) started, log level 8
Starting logging: OK
Starting logging: OK
Populating /dev using udev: <30>udevd[92]: starting version 182
done
Starting watchdog...
Initializing random number generator... done.
Starting network...
ip: RTNETLINK answers: File exists
sysctl: error: 'net.ipv4.tcp_timestamps' is an unknown key
eth0 carrier detected
Starting Network Interface Plugging Daemon: eth0.
Preparing start of hs485dOK
Starting setclock: 0.de.pool.ntp.org not found
try gateway 192.168.0.1
GATEWAY not found
OK
Starting eq3configd: OK
Starting lighttpd: OK
ls: /etc/config/*.keychange: No such file or directory
OK
Starting hs485d: OK
Starting multimacd:
Could not open SPI device: No such file or directory
Could not open SPI device: No such file or directory
2018/12/27 10:30:18.294 <Error> CCU2CommControllerMod::performIdentify(): Unable to determine coprocessor state.
Could not open SPI device: No such file or directory
firmware update disabled
Waiting for multimacd to get ready.sh: 314: unknown operand
.sh: 314: unknown operand
.sh: 314: unknown operand
.sh: 314: unknown operand
.sh: 314: unknown operand
Timeout while waiting for multimacd to get ready.
Starting rfd:
Waiting for rfd to get ready.sh: 342: unknown operand
.sh: 342: unknown operand
.sh: 342: unknown operand
.sh: 342: unknown operand
.rfd is ready now.
Starting HMServer: cp: can't stat '/etc/config_templates/hmip_networkkey.conf': No such file or directory
Waiting for HMServer to get ready
Init Hardware Info
OK
Starting ReGaHss: OK
System startedOK
Danke für eure Hilfe und viele Grüße
Mario
Hier noch ein paar weitere Infos:
ifconfig:
Code: Alles auswählen
eth0 Link encap:Ethernet Hardware Adresse b8:27:eb:37:f2:4c
inet Adresse:169.254.168.113 Bcast:169.254.255.255 Maske:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:4792090 errors:8 dropped:4 overruns:0 frame:8
TX packets:4217088 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenl▒nge:1000
RX bytes:2613463844 (2.4 GiB) TX bytes:2236635269 (2.0 GiB)
lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 G▒ltigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:65536 Metrik:1
RX packets:122212 errors:0 dropped:0 overruns:0 frame:0
TX packets:122212 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenl▒nge:1
RX bytes:13138508 (12.5 MiB) TX bytes:13138508 (12.5 MiB)
veth7H97VC Link encap:Ethernet Hardware Adresse fe:37:48:ec:25:e7
inet Adresse:169.254.136.42 Bcast:169.254.255.255 Maske:255.255.0.0
inet6-Adresse: fe80::2e5d:422b:1c92:3871/64 G▒ltigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:5885 errors:0 dropped:0 overruns:0 frame:0
TX packets:97140 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenl▒nge:1000
RX bytes:3987516 (3.8 MiB) TX bytes:13097355 (12.4 MiB)
wlan0 Link encap:Ethernet Hardware Adresse b8:27:eb:62:a7:19
inet Adresse:192.168.0.11 Bcast:192.168.0.255 Maske:255.255.255.0
inet6-Adresse: fe80::7198:9b00:d15c:388d/64 G▒ltigkeitsbereich:Verbindung
inet6-Adresse: fd00::4022:7b80:cfbe:793c/64 G▒ltigkeitsbereich:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:183047 errors:0 dropped:84038 overruns:0 frame:0
TX packets:11492 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenl▒nge:1000
RX bytes:30768717 (29.3 MiB) TX bytes:928010 (906.2 KiB)
yahmbr0 Link encap:Ethernet Hardware Adresse b8:27:eb:37:f2:4c
inet Adresse:192.168.0.10 Bcast:192.168.0.255 Maske:255.255.255.0
inet6-Adresse: fe80::ba27:ebff:fe37:f24c/64 G▒ltigkeitsbereich:Verbindung
inet6-Adresse: fd00::8e07:2a56:f34f:ee71/64 G▒ltigkeitsbereich:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:4732280 errors:0 dropped:97355 overruns:0 frame:0
TX packets:3454390 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenl▒nge:1000
RX bytes:2608389094 (2.4 GiB) TX bytes:2120362111 (1.9 GiB)
Zentrale CCU2
Seriennummer:
Version: 2.41.5
Copyright © 2007 - 2018
eQ-3 AG
26789 Leer
Germany
CCU Log:
Dec 27 10:30:47 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of HMIPTRXWriterWorker succeeded (52914887-e78b-49d2-9d78-6211192b67e2)
Dec 27 10:30:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of KryoPersistenceWorker succeeded (72ba72b7-9fa6-4269-a953-b309732d09c6)
Dec 27 10:30:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerPersistentDataLoader succeeded (f558c084-98a5-40f5-9c3a-a56a1fe939e5)
Dec 27 10:30:48 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Dec 27 10:30:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (9b8f9f0f-545a-4cc0-b3e3-61af8ed3ba44)
Dec 27 10:30:48 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (2612f5cf-391e-4a09-907d-cc376c967d23)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of IncomingHMIPFrameHandler succeeded (05bfd5f8-de35-4c0d-9b55-333e16b4dbe2)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of BackendCommandHandler succeeded (5661f164-36c6-490c-8424-141ab6543bbf)
Dec 27 10:30:49 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-3] SYSTEM: Firmware update directory is set to /etc/config/firmware
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (e5b7b6eb-2141-4dc0-9bd0-f7b2522aeb2d)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (d9872ed5-a3d3-43ba-9211-93aecfe1d57e)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of LegacyNotificationHandler succeeded (4916bbce-6204-4abc-9aa1-8c82e52d3dea)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (59b2d127-3992-4624-bc6b-0af83abcbf70)
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LegacyAPIWorker succeeded (bf3166de-1f2b-43c1-8f1c-def2b4264cf1)
Dec 27 10:30:49 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization ERROR [vert.x-eventloop-thread-7] Error 'LOCAL_ADAPTER_NO_SUCH_PORT' while trying to open port '/dev/ttyS0':
de.eq3.cbcs.lib.commdevice.CommDeviceException: Exception while trying to open serial port. Check configured port '/dev/ttyS0'
at de.eq3.cbcs.lib.nrjavaserialdevice.SerialCommDevice.open(SerialCommDevice.java:109)
at de.eq3.cbcs.lib.hmiptrxcommadapter.HomeMaticIPTRXCommAdapter.open(HomeMaticIPTRXCommAdapter.java:737)
at de.eq3.cbcs.lib.hmiptrxcommadapter.HomeMaticIPTRXCommAdapter.<init>(HomeMaticIPTRXCommAdapter.java:102)
at de.eq3.cbcs.server.local.base.internal.ShareableHomeMaticIPTRXCommAdapter.<init>(ShareableHomeMaticIPTRXCommAdapter.java:25)
at de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization.start(LocalServerAdapterInitialization.java:182)
at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at java.lang.Thread.run(Thread.java:745)
Caused by: gnu.io.NoSuchPortException
at gnu.io.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:294)
at de.eq3.cbcs.lib.nrjavaserialdevice.SerialCommDevice.open(SerialCommDevice.java:100)
... 12 more
Dec 27 10:30:49 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (4c3156c0-e8cf-4468-b973-048e23c438f0)
Dec 27 10:30:54 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-7] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:30:54 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:01 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 19 out of 21
Dec 27 10:31:01 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-7] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:01 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:08 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-7] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:08 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 19 out of 21
Dec 27 10:31:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-7] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Dec 27 10:31:15 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [connector.open])