Autor Thema: Homematic und Homematic IP am Raspberry  (Gelesen 32481 mal)

Offline Calle78

  • Full Member
  • ***
  • Beiträge: 191
  • FHEM Begeistert
    • Über mich
Antw:Homematic und Homematic IP am Raspberry
« Antwort #45 am: 13 Januar 2019, 22:56:47 »
Wie ihr an der fortgeschrittenen Zeit seht, läufts leider noch nicht rund. Anlernen funktioniert leider weder mit HMIP noch mit HM, er erkennt nichts. Der Geräte-Posteingang hat eine (2) ist aber leer, die Startseite Spinnt unendlich. Auf Anhieb fällt mir nur das
SGTIN:          unknown
auf.

Hat jemand eine Idee?

ciao Carlo
5.9,RPi3,Stretch,HMLAN,HMIP,HUE,ZigBee,piVCCU,C868,C433,JEELINK,ESA2000,IRT1500,HMSECSC2,HMCCTC,HMSECSD,HM132030,HMSCI3FM,HMPB2WM55-2,FHT80,FBAHA,WithingsWS50,Jalousien,Siri,HMS100WD,Fritzbox,Harmony,Twilight,Weather,PushBullet,FHT-9998,HM-CC-TC,Trackr,RolloPort

Todo:ZWave(MieleOfen),LEDWIFI

Offline deimos

  • Full Member
  • ***
  • Beiträge: 109
Antw:Homematic und Homematic IP am Raspberry
« Antwort #46 am: 14 Januar 2019, 06:07:48 »
Hi,

hattest du vorher eine HmRF only Firmware auf dem Funkmodul? Das würde das Problem erklären, da reicht dann vermutlich eim Neustart.

starte mal den Pi neu und dann nach ca. 5 Minuten:
sudo pivccu-info
sudo pivccu-attach cat /var/hm_mode
sudo pivccu-attach cat /var/log/messages
sudo pivccu-attach cat /var/log/hmserver.log
sudo cat /proc/meminfo

Hintergrund für den Neustart: Die CCU Firmware hat ein rotierendes Log und die interessanten Einträge vom Start werden da recht schnell verdrängt.

Viele Grüße
Alex
Gefällt mir Gefällt mir x 1 Liste anzeigen

Offline Calle78

  • Full Member
  • ***
  • Beiträge: 191
  • FHEM Begeistert
    • Über mich
Antw:Homematic und Homematic IP am Raspberry
« Antwort #47 am: 14 Januar 2019, 22:01:10 »
Danke dir deimos, ein SGTIN ist jetzt wirklich da, aber sonst hat sich leider noch nichts geändert. Ich hab kein Firmwareupdate o.ä. gemacht.

pi@SmartHome:~ $ sudo pivccu-info
piVCCU version: 3.41.11-15
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
HMIP Hardware:  HM-MOD-RPI-PCB
Board serial:   OEQ0610968
Radio MAC:      0x5c7f50
SGTIN:          3014F711A061A7D70992BA98
State:          RUNNING
PID:            5401
IP:             192.168.178.55
IP:             2a0a:a540:acd3:0:185d:f3ff:fe21:74b
CPU use:        187.43 seconds
BlkIO use:      564.00 KiB
Link:           vethGJCVGF
 TX bytes:      9.74 MiB
 RX bytes:      8.48 MiB
 Total bytes:   18.21 MiB
pi@SmartHome:~ $ sudo pivccu-attach cat /var/hm_mode
HM_HMIP_ADDRESS='0x5c7f50'
HM_HMIP_DEV='HM-MOD-RPI-PCB'
HM_HMIP_DEVNODE='/dev/raw-uart'
HM_HMIP_SERIAL='OEQ0610968'
HM_HMIP_SGTIN='3014F711A061A7D70992BA98'
HM_HMIP_VERSION='2.8.6'
HM_HMRF_ADDRESS='0x5c7f50'
HM_HMRF_DEV='HM-MOD-RPI-PCB'
HM_HMRF_DEVNODE='/dev/raw-uart'
HM_HMRF_SERIAL='OEQ0610968'
HM_HMRF_VERSION='2.8.6'
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=''
pi@SmartHome:~ $ sudo pivccu-attach cat /var/log/messages
Jan 14 20:45:17 piVCCU syslog.info syslogd started: BusyBox v1.28.4
Jan 14 20:45:18 piVCCU user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Jan 14 20:45:18 piVCCU syslog.info syslogd exiting
Jan 14 20:45:18 ccu3-webui syslog.info syslogd started: BusyBox v1.28.4
Jan 14 20:45:18 ccu3-webui user.notice kernel: klogd started: BusyBox v1.28.4 (2018-11-12 09:49:13 CET)
Jan 14 20:45:18 ccu3-webui daemon.err udhcpc[180]: started, v1.28.4
Jan 14 20:45:18 ccu3-webui daemon.err udhcpc[180]: sending discover
Jan 14 20:45:18 ccu3-webui daemon.err udhcpc[180]: sending select for 192.168.178.55
Jan 14 20:45:18 ccu3-webui daemon.err udhcpc[180]: lease of 192.168.178.55 obtained, lease time 864000
Jan 14 20:45:20 ccu3-webui user.info firewall: iptables v1.6.2: invalid port/service `310000' specified Try `iptables -h' or 'iptables --help' for more information.
Jan 14 20:45:20 ccu3-webui user.info firewall: ip6tables v1.6.2: invalid port/service `310000' specified Try `ip6tables -h' or 'ip6tables --help' for more information.
Jan 14 20:45:20 ccu3-webui user.info firewall: configuration set
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: ifplugd 0.28 initializing.
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: Using interface eth0/1A:5D:F3:21:07:4B with driver <veth> (version: 1.0)
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: Using detection mode: SIOCETHTOOL
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: Initialization complete, link beat detected.
Jan 14 20:45:20 ccu3-webui daemon.warn ifplugd(eth0)[263]: Could not open /dev/tty, cannot beep.
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jan 14 20:45:20 ccu3-webui daemon.warn ifplugd(eth0)[263]: client: ifup: interface eth0 already configured
Jan 14 20:45:20 ccu3-webui daemon.info ifplugd(eth0)[263]: Program executed successfully.
Jan 14 20:45:29 ccu3-webui daemon.notice ntpdate[271]: step time server 193.141.27.6 offset -0.002078 sec
Jan 14 20:45:29 ccu3-webui daemon.notice ntpd[272]: ntpd 4.2.8p11@1.3728-o Mon Nov 12 09:31:16 UTC 2018 (1): Starting
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[272]: Command line: /usr/sbin/ntpd -g 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: proto: precision = 0.989 usec (-20)
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listen and drop on 0 v6wildcard [::]:123
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listen normally on 2 lo 127.0.0.1:123
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listen normally on 3 eth0 192.168.178.55:123
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listen normally on 4 lo [::1]:123
Jan 14 20:45:29 ccu3-webui daemon.info ntpd[274]: Listening on routing socket on fd #21 for interface updates
Jan 14 20:45:29 ccu3-webui daemon.err xinetd[289]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Jan 14 20:45:29 ccu3-webui daemon.crit xinetd[289]: 289 {init_services} no services. Exiting...
Jan 14 20:45:29 ccu3-webui user.info root: Updating RF Lan Gateway Coprocessor Firmware
Jan 14 20:45:29 ccu3-webui user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Jan 14 20:45:29 ccu3-webui user.info root: Updating RF Lan Gateway Firmware
Jan 14 20:45:29 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Jan 14 20:45:29 ccu3-webui user.info root: Updating Wired Lan Gateway Firmware
Jan 14 20:45:29 ccu3-webui user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Jan 14 20:45:29 ccu3-webui daemon.info snmpd[348]: Created directory: /var/lib/snmp
Jan 14 20:45:29 ccu3-webui daemon.info snmpd[348]: Created directory: /var/lib/snmp/cert_indexes
Jan 14 20:45:29 ccu3-webui daemon.info snmpd[348]: Created directory: /var/lib/snmp/mib_indexes
Jan 14 20:45:29 ccu3-webui daemon.info snmpd[348]: Turning on AgentX master support.
Jan 14 20:45:29 ccu3-webui daemon.err snmpd[348]: /etc/config/snmp/snmpd.conf: line 20: Error: Included file '/etc/config/snmp/snmpd-ccu3.conf' not found.
Jan 14 20:45:29 ccu3-webui daemon.info snmpd[350]: NET-SNMP version 5.7.3
Jan 14 20:45:30 ccu3-webui user.info kernel: [ 2339.059267] eq3loop: created slave mmd_hmip
Jan 14 20:45:30 ccu3-webui user.info kernel: [ 2339.061551] eq3loop: created slave mmd_bidcos
Jan 14 20:45:57 ccu3-webui user.info kernel: [ 2366.100227] eq3loop: eq3loop_open_slave() mmd_hmip
Jan 14 20:45:57 ccu3-webui user.info kernel: [ 2366.100563] eq3loop: eq3loop_close_slave() mmd_hmip
Jan 14 20:45:57 ccu3-webui user.info kernel: [ 2366.106748] eq3loop: eq3loop_open_slave() mmd_hmip
Jan 14 20:45:57 ccu3-webui user.info kernel: [ 2366.107018] eq3loop: eq3loop_close_slave() mmd_hmip
Jan 14 20:45:57 ccu3-webui user.info kernel: [ 2366.128324] eq3loop: eq3loop_open_slave() mmd_hmip
Jan 14 20:45:57 ccu3-webui user.notice kernel: [ 2366.132638] eq3loop: eq3loop_ioctl_slave() mmd_hmip: unhandled ioctl 0x5459
Jan 14 20:46:07 ccu3-webui daemon.err ntpd[274]: bind(24) AF_INET6 2a0a:a540:acd3:0:185d:f3ff:fe21:74b#123 flags 0x11 failed: Cannot assign requested address
Jan 14 20:46:07 ccu3-webui daemon.err ntpd[274]: unable to create socket on eth0 (5) for 2a0a:a540:acd3:0:185d:f3ff:fe21:74b#123
Jan 14 20:46:07 ccu3-webui daemon.info ntpd[274]: failed to init interface for address 2a0a:a540:acd3:0:185d:f3ff:fe21:74b
Jan 14 20:46:09 ccu3-webui daemon.info ntpd[274]: Listen normally on 6 eth0 [2a0a:a540:acd3:0:185d:f3ff:fe21:74b]:123
pi@SmartHome:~ $ sudo pivccu-attach cat /var/log/hmserver.log
Jan 14 20:45:40 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Jan 14 20:45:40 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Jan 14 20:45:40 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Jan 14 20:45:49 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default
Jan 14 20:45:49 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default
Jan 14 20:45:49 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default
Jan 14 20:45:49 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default
Jan 14 20:45:49 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 21 classes to Vert.x
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 21 VertxDeployers initialized
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of HMIPTRXWriterWorker succeeded (117a53ee-f92b-459c-9a4d-85c5140e8185)
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (b1b9692a-88e2-4aa6-b6f3-03085bafb36a)
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (95346c1f-915b-450d-955b-9dcc8edd266f)
Jan 14 20:45:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (132a1601-ac89-4208-89b1-a5c7089bf326)
Jan 14 20:45:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (392e6a11-e435-4088-a4c0-35967f5bd3b5)
Jan 14 20:45:50 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Jan 14 20:45:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KeyServerWorker succeeded (8e452804-185a-497b-9653-866f60a17b2d)
Jan 14 20:45:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of KryoPersistenceWorker succeeded (4a38c51d-fdc1-4449-b18e-4048bf7294d1)
Jan 14 20:45:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (98df2982-7aa5-4419-af8f-c4279fcc2b23)
Jan 14 20:45:51 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-6] SYSTEM: DeviceLiveUpdateSubsystem started
Jan 14 20:45:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CheckDeviceExistHandler succeeded (f82380e2-68fd-4d3f-8023-6d14089473bf)
Jan 14 20:45:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (6694a9e4-2e23-453a-a687-d0a0525f1638)
Jan 14 20:45:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (a791e2d6-1de0-45a7-9ed1-76c8be9af980)
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (f4bb75a8-f28f-4456-a0ff-715d56a558ed)
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of IncomingHMIPFrameHandler succeeded (89733470-fb6f-4dde-b023-3834b1ec7928)
Jan 14 20:45:52 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-4] SYSTEM: Firmware update directory is set to /etc/config/firmware
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LegacyBackendNotificationHandler succeeded (3b51b337-6815-482f-b1c4-784e0e045cf4)
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendCommandHandler succeeded (e48c5255-9283-4f36-a143-728fc9c8e3a6)
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of FirmwareLoaderFileSystem succeeded (d32aab27-e5bf-4dc1-be28-2acc24fe0d3c)
Jan 14 20:45:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyNotificationHandler succeeded (c4f623c9-3bc1-40a6-b373-c4c78a825a30)
Jan 14 20:45:53 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (20381e0d-2b34-4993-b3f6-4c18a0e7ee9b)
Jan 14 20:45:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open])
Jan 14 20:45:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open])
Jan 14 20:45:57 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerAdapterInitialization succeeded (aa4d98db-8cd3-42b0-953d-27b24d866336)
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ...
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12066613...
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D70992BA98 to 3
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version...
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 3.5
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 300992
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 301968
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 2 link partners
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D70992BA98 initialized
Jan 14 20:45:57 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized
Jan 14 20:45:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (98d820cb-0079-4fa3-9c2a-e28c475690f7)
Jan 14 20:45:58 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem WARN  [vert.x-worker-thread-1] SYSTEM: Firmware update directory in config file is no valid directory: /etc/config/firmware
Jan 14 20:45:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LegacyInitializion succeeded (312f23dd-ef0d-4902-9e09-aa124805c00b)
Jan 14 20:45:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Checking all devices on all accesspoints for updates
Jan 14 20:45:58 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: There are 0 APs queued with updatable devices
Jan 14 20:45:58 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of CouplingRequestWorker succeeded (4f31999a-78a1-4632-aecd-8ec773f1d1d9)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (229c2f9e-48b0-4d65-98f2-dd36fb66e4bf)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendWorker succeeded (11ff1bd5-62a9-474b-8319-eb594ecdec4e)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RegaClientWorker succeeded (dbfb14d7-9044-427b-8b27-f3a5bab274bb)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of EnergyPriceRequestWorker succeeded (9cc1253b-cb6e-4dbf-bedd-597e8c3682a5)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of StorageRequestWorker succeeded (e838f565-29c2-421a-8f2b-68b85660b33c)
Jan 14 20:46:00 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of GroupRequestWorker succeeded (f194e32d-04d2-423a-989d-463562ba7f54)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (4b982fbe-ac80-45fd-aedc-3dd256ec69fb)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DiagramRequestWorker succeeded (8ed12a11-2235-4065-aaa4-b406f4b8a999)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (26f0e521-5480-4329-abe3-f05833916de4)
Jan 14 20:46:00 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292
Jan 14 20:46:00 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration
Jan 14 20:46:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher
Jan 14 20:46:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache
Jan 14 20:46:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler
Jan 14 20:46:04 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing...
Jan 14 20:46:04 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Jan 14 20:46:04 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Jan 14 20:46:04 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device
Jan 14 20:46:04 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler
Jan 14 20:46:06 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler
Jan 14 20:46:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos
Jan 14 20:46:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished
Jan 14 20:46:06 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java
Jan 14 20:46:07 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient HmIP-RF_java -> 8 device addresses will be added
Jan 14 20:46:07 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done
Jan 14 20:46:15 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999
Jan 14 20:46:15 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] Added InterfaceId: 1008
Jan 14 20:46:15 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Jan 14 20:46:25 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999
Jan 14 20:46:25 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished
Jan 14 20:46:25 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: 1009
Jan 14 20:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 20:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 20:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 20:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 20:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 20:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:00:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:00:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:00:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:05:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:05:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:05:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:10:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:10:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:10:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:15:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:15:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:15:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:20:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:20:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:20:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:25:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:25:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:25:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:30:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:30:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:30:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:35:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:35:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:35:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:40:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:40:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:40:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:45:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:45:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:45:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:50:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
Jan 14 21:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue
Jan 14 21:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
Jan 14 21:55:51 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used
pi@SmartHome:~ $ sudo cat /proc/meminfo
MemTotal:         949448 kB
MemFree:          528048 kB
MemAvailable:     677116 kB
Buffers:           29524 kB
Cached:           172724 kB
SwapCached:            0 kB
Active:           290600 kB
Inactive:          90456 kB
Active(anon):     180760 kB
Inactive(anon):    12052 kB
Active(file):     109840 kB
Inactive(file):    78404 kB
Unevictable:        1760 kB
Mlocked:            1760 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                12 kB
Writeback:             0 kB
AnonPages:        180616 kB
Mapped:            68640 kB
Shmem:             12592 kB
Slab:              23756 kB
SReclaimable:      11752 kB
SUnreclaim:        12004 kB
KernelStack:        1680 kB
PageTables:         1968 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      474724 kB
Committed_AS:     400580 kB
VmallocTotal:    1114112 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
CmaTotal:           8192 kB
CmaFree:            6656 kB
5.9,RPi3,Stretch,HMLAN,HMIP,HUE,ZigBee,piVCCU,C868,C433,JEELINK,ESA2000,IRT1500,HMSECSC2,HMCCTC,HMSECSD,HM132030,HMSCI3FM,HMPB2WM55-2,FHT80,FBAHA,WithingsWS50,Jalousien,Siri,HMS100WD,Fritzbox,Harmony,Twilight,Weather,PushBullet,FHT-9998,HM-CC-TC,Trackr,RolloPort

Todo:ZWave(MieleOfen),LEDWIFI

Offline deimos

  • Full Member
  • ***
  • Beiträge: 109
Antw:Homematic und Homematic IP am Raspberry
« Antwort #48 am: 15 Januar 2019, 06:20:02 »
Hi,

laut dem Log läuft jetzt alles einwandfrei. Hast du mal den Browsercache geleert und mit Strg+F5 die Seite neu geladen?

Viele Grüße
Ale

Offline Frini

  • Full Member
  • ***
  • Beiträge: 238
Antw:Homematic und Homematic IP am Raspberry
« Antwort #49 am: 15 Januar 2019, 07:05:15 »
Sicher das FHEM und pivccu gleichzeitig auf das Funkmodul zugreifen können? Dies hatte bei meine Versuchen nämlich nicht funktionert.

Offline deimos

  • Full Member
  • ***
  • Beiträge: 109
Antw:Homematic und Homematic IP am Raspberry
« Antwort #50 am: 15 Januar 2019, 07:14:59 »
Hi,

ein gleichzeitiger Zugriff funktioniert definitiv nicht.

Viele Grüße
Alex

Offline Calle78

  • Full Member
  • ***
  • Beiträge: 191
  • FHEM Begeistert
    • Über mich
Antw:Homematic und Homematic IP am Raspberry
« Antwort #51 am: 15 Januar 2019, 22:49:58 »
Hey zusammen, danke euch schonmal. Warum denkt ihr, dass ich gleichzeitig Zugreife? Missverständnis oder seht ihr was in den Logs? Ich hab in FHEM den HMLAN und HMUART auskommentiert, in der config.txt dtoverlay=pivccu-raspberrypi einkommentiert und neu gestartet. Dennoch lässt sich in pivccu nichts anlernen. Ich machs jetzt nochmal und versuchs im Incognito um jeden Cache auszuschließen :)
5.9,RPi3,Stretch,HMLAN,HMIP,HUE,ZigBee,piVCCU,C868,C433,JEELINK,ESA2000,IRT1500,HMSECSC2,HMCCTC,HMSECSD,HM132030,HMSCI3FM,HMPB2WM55-2,FHT80,FBAHA,WithingsWS50,Jalousien,Siri,HMS100WD,Fritzbox,Harmony,Twilight,Weather,PushBullet,FHT-9998,HM-CC-TC,Trackr,RolloPort

Todo:ZWave(MieleOfen),LEDWIFI

Offline Calle78

  • Full Member
  • ***
  • Beiträge: 191
  • FHEM Begeistert
    • Über mich
Antw:Homematic und Homematic IP am Raspberry
« Antwort #52 am: 15 Januar 2019, 23:21:36 »
ICH DREH DURCH, es lag wirklich nur am BrowserCache. Ey Leute wir haben 2019 - HomeMatic bitte sucht euch ein paar Entwickler die Webentwicklung können oder meldet euch wenn ihr Hilfe braucht. Ok, dann gehts jetzt weiter - danke!

@deimos ich schulde dir ein Bier oder zwei :)

ciao Carlo
5.9,RPi3,Stretch,HMLAN,HMIP,HUE,ZigBee,piVCCU,C868,C433,JEELINK,ESA2000,IRT1500,HMSECSC2,HMCCTC,HMSECSD,HM132030,HMSCI3FM,HMPB2WM55-2,FHT80,FBAHA,WithingsWS50,Jalousien,Siri,HMS100WD,Fritzbox,Harmony,Twilight,Weather,PushBullet,FHT-9998,HM-CC-TC,Trackr,RolloPort

Todo:ZWave(MieleOfen),LEDWIFI

Offline deimos

  • Full Member
  • ***
  • Beiträge: 109
Antw:Homematic und Homematic IP am Raspberry
« Antwort #53 am: 16 Januar 2019, 11:44:40 »
Hi,

ICH DREH DURCH, es lag wirklich nur am BrowserCache. Ey Leute wir haben 2019 - HomeMatic bitte sucht euch ein paar Entwickler die Webentwicklung können oder meldet euch wenn ihr Hilfe braucht. Ok, dann gehts jetzt weiter - danke!

Das ist leider nur die Spitze des Eisbergs, wenn die ihren Job richtig machen würden, bräuchte es Dinge wie piVCCU oder RaspberryMatic gar nicht.

@deimos ich schulde dir ein Bier oder zwei :)

Lieber Kaffee oder Süßkram, siehe Wunschzettel auf der piVCCU Github Seite.  ;D

Viele Grüße
Alex

Offline Calle78

  • Full Member
  • ***
  • Beiträge: 191
  • FHEM Begeistert
    • Über mich
Antw:Homematic und Homematic IP am Raspberry
« Antwort #54 am: 16 Januar 2019, 11:51:42 »
Perfekt, Schokolade ist unterwegs ;)

ciao Carlo
5.9,RPi3,Stretch,HMLAN,HMIP,HUE,ZigBee,piVCCU,C868,C433,JEELINK,ESA2000,IRT1500,HMSECSC2,HMCCTC,HMSECSD,HM132030,HMSCI3FM,HMPB2WM55-2,FHT80,FBAHA,WithingsWS50,Jalousien,Siri,HMS100WD,Fritzbox,Harmony,Twilight,Weather,PushBullet,FHT-9998,HM-CC-TC,Trackr,RolloPort

Todo:ZWave(MieleOfen),LEDWIFI

Offline deimos

  • Full Member
  • ***
  • Beiträge: 109
Antw:Homematic und Homematic IP am Raspberry
« Antwort #55 am: 16 Januar 2019, 14:58:08 »
Hi,

Perfekt, Schokolade ist unterwegs ;)

Vielen Dank!

Viele Grüße
Alex

Offline tkaiser

  • Jr. Member
  • **
  • Beiträge: 77
Antw:Homematic und Homematic IP am Raspberry
« Antwort #56 am: 29 Januar 2019, 21:02:51 »
hallo Leute
ich bin Laie mit der installation der vccu3
ich habe nach der Anleitung hier aus dem Post installiert, leider bekomme ich: RPCState inactive, State Initialized
pi@raspberrypi:~ $ sudo pivccu-info
piVCCU version: 3.41.11-16
Kernel modules: Available
Raw UART dev:   Available
Rasp.Pi3 UART:  Assigned to GPIO pins
HMRF Hardware:  HM-MOD-RPI-PCB
HMIP Hardware:  HM-MOD-RPI-PCB
Board serial:   PEQ0533766
Radio MAC:      0x6a56c2
SGTIN:          3014F711A061A7D8A9918D06
State:          RUNNING
PID:            1015
IP:             192.168.178.48
CPU use:        350.81 seconds
BlkIO use:      62.61 MiB
Link:           vethpivccu
 TX bytes:      5.09 MiB
 RX bytes:      10.09 MiB
 Total bytes:   15.18 MiB

Im fhem log steht
No I/O device found for myVCCU
HMCCU: [d_ccu] HMCCU: Initializing devices
 2: HMCCU: HMScript failed. 401 Unauthorized
 1: HMCCU: [d_ccu] HMCCU: Error while reading device list from CCU 192.168.178.48

hat jemand eine Ahnung
Gruß
HM-ES-PMSw1-Pl, HM-TC-IT-WM-W-EU, HM-CC-RT-DN,
HM-LC-DIM1T-FM, HM-SEC-SCo, Harmony-Hub,Raspi3.
CUL 868, nanoCUL 433

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2966
    • HMCCU
Antw:Homematic und Homematic IP am Raspberry
« Antwort #57 am: 29 Januar 2019, 21:13:36 »
Du musst in der Systemsteuerung der CCU Weboberfläche die Authentifizierung abschalten.
2xCCU3, diverse Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für CCU Integration.
IOBroker für UI (VIS), Hue, Sonos usw.
Maintainer der Module FULLY, Meteohub und HMCCU (Schnittstelle CCU-FHEM = best of both worlds approach

Offline MCh76

  • Jr. Member
  • **
  • Beiträge: 91
Antw:Homematic und Homematic IP am Raspberry
« Antwort #58 am: 31 Januar 2019, 00:34:51 »
hallo zusammen,

ich hänge genau an der stelle wie calle aus antwort #39
ich wollte ein update auf piVCCU3 machen gemäßt dieser anleitung:
https://technikkram.net/2018/10/homematic-pivccu-update-auf-pivccu3

zuvor lief die "alte version" von piVCCU ohne probleme.
egal was ich versuchte, es kam immer zu der fehlermeldung die auch calle bekam.
wenn ich nun versuche pivvu bzw. pivvu3 zu entfernen erhalte ich folgenden fehler.
irgendwie geht es weder vor noch zurück...kann mir jemand einen wertvollen tipp geben?

sudo apt remove pivccu3

Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  debootstrap dns-root-data dnsmasq-base liblxc1 libpam-cgfs lxc lxcfs python3-lxc uidmap
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
pivccu-modules-dkms (1.0.22) wird eingerichtet ...

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.9.35-v7+ ARCH=arm all....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.9.35-v7+ (armv7l)
Consult /var/lib/dkms/pivccu/1.0.22/build/make.log for more information.
dpkg: Fehler beim Bearbeiten des Paketes pivccu-modules-dkms (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 zurück
Fehler traten auf beim Bearbeiten von:
 pivccu-modules-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)


und wenn ich dann in die benannte make.log datei schaue kommen folgende fehler:
DKMS make.log for pivccu-1.0.22 for kernel 4.9.35-v7+ (armv7l)
Do 31. Jan 00:50:14 CET 2019
make -C /lib/modules/4.9.35-v7+/build M=/var/lib/dkms/pivccu/1.0.22/build modules
make[1]: Verzeichnis „/usr/src/linux-headers-4.9.35-v7+“ wird betreten
  CC [M]  /var/lib/dkms/pivccu/1.0.22/build/eq3_char_loop.o
  CC [M]  /var/lib/dkms/pivccu/1.0.22/build/plat_eq3ccu2.o
  CC [M]  /var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.o
  CC [M]  /var/lib/dkms/pivccu/1.0.22/build/pl011_raw_uart.o
  CC [M]  /var/lib/dkms/pivccu/1.0.22/build/dw_apb_raw_uart.o
/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.c: In function ‘generic_raw_uart_get_gpio_pin_number’:
/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.c:720:36: error: implicit declaration of function ‘dev_fwnode’ [-Werror=implicit-function-declaration]
     struct fwnode_handle *fwnode = dev_fwnode(dev);
                                    ^~~~~~~~~~
/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.c:720:36: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.c:722:31: error: too many arguments to function ‘fwnode_get_named_gpiod’
     struct gpio_desc *gpiod = fwnode_get_named_gpiod(fwnode, label, 0, GPIOD_ASIS, label);
                               ^~~~~~~~~~~~~~~~~~~~~~
In file included from ./include/asm-generic/gpio.h:13:0,
                 from ./arch/arm/include/asm/gpio.h:9,
                 from ./include/linux/gpio.h:48,
                 from /var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.c:39:
./include/linux/gpio/consumer.h:137:19: note: declared here
 struct gpio_desc *fwnode_get_named_gpiod(struct fwnode_handle *fwnode,
                   ^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
scripts/Makefile.build:299: die Regel für Ziel „/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.o“ scheiterte
make[2]: *** [/var/lib/dkms/pivccu/1.0.22/build/generic_raw_uart.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet...
Makefile:1490: die Regel für Ziel „_module_/var/lib/dkms/pivccu/1.0.22/build“ scheiterte
make[1]: *** [_module_/var/lib/dkms/pivccu/1.0.22/build] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-headers-4.9.35-v7+“ wird verlassen
Makefile:23: die Regel für Ziel „all“ scheiterte
make: *** [all] Fehler 2


vielen dank und grüße,
Chris
« Letzte Änderung: 31 Januar 2019, 00:55:03 von MCh76 »

Offline zap

  • Developer
  • Hero Member
  • ****
  • Beiträge: 2966
    • HMCCU
Antw:Homematic und Homematic IP am Raspberry
« Antwort #59 am: 31 Januar 2019, 07:28:44 »
Das sind jetzt sehr piVCCU spezifische Fragen. Möglicherweise bekommst du eher hier eine Antwort:

Homematic Forum, Unterforum Homematic OCCU, Unterforum piVCCU.
2xCCU3, diverse Komponenten (Fenster, Rolladen, Themostate, Stromzähler, Steckdosen ...)
FHEM mit Raspi für CCU Integration.
IOBroker für UI (VIS), Hue, Sonos usw.
Maintainer der Module FULLY, Meteohub und HMCCU (Schnittstelle CCU-FHEM = best of both worlds approach