RaspberryMatic 3.57.5.20210424 – Neue Version

Einrichtung, Nutzung und Hilfe zu RaspberryMatic (OCCU auf Raspberry Pi)

Moderatoren: jmaus, Co-Administratoren

Benutzeravatar
jmaus
Beiträge: 7422
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 212 Mal
Danksagung erhalten: 808 Mal
Kontaktdaten:

RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von jmaus » 24.04.2021, 18:16

Hallo,

es ist mal wieder soweit und soeben habe ich eine neue offizielle RaspberryMatic Version (3.57.5.20210424) für alle unterstützten Hardwareplattformen freigegeben. Bei dieser Version handelt es sich um ein "Maintenance"-Release, welches einige Verbesserungen und Bugfixes mit sich bringt.

Neben diesen Maintenance Änderungen bringt diese Version auch Kompatibilität zur eQ3 OCCU/CCU3 3.57.5 Firmware die vor kurzem auch für die CCU3 freigegeben wurde. Ein weiteres Highlight dieser Version ist auch die hinzugefügte Unterstützung der Single Board Computer von Hardkernel, die sogenannte "ODROID" Linie, sodaß RaspberryMatic nun auch auf einem ODROID-N2/N2+, ODROID-C4 und ODROID-C2 Board voll lauffähig ist.

Auch wurden in dieser Version wieder einige kleinere und größere Verbesserungen an der WebUI vorgenommen. Aber auch an anderen Stellen gab es nennenswerte Verbesserungen und Bugfixes an der allgemeinen WebUI.

:construction: Änderungen:

Wie immer kann die komplette Liste aller in dieser Version umgesetzten Änderungen/Bugfixes im Folgenden eingesehen werden. Momentan kann ich diese Auflistung auf Grund von Zeitmangel jedoch nur in Englisch liefern. Eine Übersetzung werde ich dann hier zeitnah nachpflegen (wer das gerne zur Unterstützung für mich erledigen will, kann mir gerne die deutschen Übersetzungen natürlich dankenswerterweise per PN schicken :).

CCU/HomeMatic-System Änderungen:
  • updated OCCU version to 3.57.5-1 integrating full compatibility to the CCU3 3.57.5 firmware which comes with the following changes:
    • after device reset config data was not correctly transmitted to HomeMatic/homematicIP devices anymore.
    • when editing device configuration values where devices accepted value < 0 ended up in not being able to enter 0 anymore.
    • when adding channel 1 of a HmIP(W)-FAL device also channel 2 was accidentally added in the direct channel connection which did not have any function.
  • modified the "Clone System" operation in the recovery system to also deal with clone operations where the target device is smaller than the source device. In this case the user partition will be created smaller before using rsync to copy the userfs data from source to destination.
  • fixed the firmware update/install routines in the recovery system to write the bootloader for any partitioning scheme where the boot partition starts >= 2048.
  • integrated a minor fix which could have lead to an empty `HM_HMIP_ADDRESS_ACTIVE` variable entry in `/var/hm_mode` in case no `/etc/config/hmip_address.conf` file exists upon bootup.
WebUI Änderungen:
  • changed 0119-WebUI-Fix-ProofAndSetValue WebUI bugfix patch with more fixes for the `ProofAndSetValue` function not correctly allowing to deal with all device relevant value boundaries in the WebUI device configuration dialogs (#1231, @theimo1221, @Baxxy13).
  • integrated a fix in the 0111-WebUI-Fix-Translation-Performance WebUI patch which should fix issues where empty translation strings resulted issue that which should finally fix #1155.
  • modified 0060-WebUI-Fix-SessionLogoutSave WebUI patch to not patch the `Session.logout()` JSON RPC to use `system.ClearSession()` rather than `system.ClearSessionID()` because using the non-ID version causes the regadom to be saved under all circumstances and for the remote API this might not be something we actually want (#1192).
Betriebsystem Änderungen:
  • added hardware support for the Hardkernel ODROID line of SBC platform (ODROID-N2/N2+, ODROID-C4, ODROID-C2)
  • added hardware support for the Intel NUC Gen 11 (Panther Canyon) hardware.
  • integrated support for evaluating a global `/etc/sysctl.conf` file to tune certain linux system/kernel parameters.
  • moved the `fstrim` cronjob to run at 04:00 each saturday and the badblock check to 01:59 to make sure it is run even during DST switch times. This closes #1204.
  • updated `rpi-eeprom` package to incorporate latest `pieeprom-2021-03-18.bin` RaspberryPi4 EEPROM fixing potential issues with older pi4 board revisions.
  • integrated certain fixes and enhancements for running RaspberryMatic as a full-fledged HomeAssistant Add-on.
  • when running as a HomeAssistant Add-on we don't use `udev` anymore because the host OS is running its' own `udev` which could conflict otherwise.
  • on the corresponding platforms we reset the board upon an U-Boot boot failure so that systems won't stall in the bootloader.
  • updated `generic_raw_uart` to latest master version and removed our manual GPIO reset routine in the `InitRFHardware` init scripts because the newer `generic_raw_uart` handles the different reset pin layout of the `RPI-RF-MOD` vs. `HM-MOD-RPI-PCB` modules internally using a dedicated 'alt_reset_pin' device tree node entry now.
  • removed the dedicated `rx8130` buildroot package in favour of using the kernel mainline `ds1307,rx8130` module which since 5.10.x supports supercap charging (cf. https://lore.kernel.org/linux-rtc/20200 ... onix.de/T/).
  • bumped `lighttpd` web server to latest stable 1.4.59 which fixes an issue with lengthy request field sizes resulting in not being able to updated HomeMatic device parameters (cf. https://redmine.lighttpd.net/issues/3059, #1189).
  • bumped buildroot version to latest 2021.02.1 version.
  • bumped 5.10.x LTS kernel to 5.10.32 for all appropriate platforms (Tinkerboard, ODROID, intelNUC, OVA).
  • bumped 5.10.x LTS kernel for RaspberryPi to latest 1.20210303-1 version including the corresponding bootloader/firmware files.
  • bumped U-Boot version to latest 2021.04 version including u-boot related patch updates for the tinkerboard target.
  • bumped JAVA version to latest 8.54.0.21-ca-jdk8.0.292 LTS for appropriate platforms.
:family: Mitwirkende (diese Version, alphabetisch):
:memo: Support:
Hier sei auch noch einmal auf die umfangreiche Dokumentation von RaspberryMatic hingewiesen an der bereits seit einiger Zeit gearbeitet wird und die auch sukzessive mit jeder Version verbessert wird. Zu erreichen ist die Dokumentation unter folgender Stelle:
Wie die URLs schon vermuten lassen, handelt es sich hierbei teils um einen öffentlichen Wiki an dem sich wirklich jeder gerne (nach entsprechender technischer Selbst-Einarbeitung) beteiligen kann um Anderen vor allem den Einstieg rund um das Thema "RaspberryMatic" zu erleichtern.

:package: Download:

Die neue Version kann wie gehabt von folgender URL als *.zip Datei für die verschiedenen RaspberryPi Modelle heruntergeladen und installiert werden:

https://github.com/jens-maus/RaspberryM ... ses/latest

Zu beachten gilt, das auf Grund der Unterstützung unterschiedlicher Geräte es getrennte Installationsarchive (*.zip Dateien) gibt die für die folgende Hardware jeweils einheitlich ist:
Update/Upgrade:
Das Update auf diese Version kann bei Einsatz einer Vorversion unter "Einstellungen->Systemsteuerung->Zentralen-Wartung" durch Upload der jeweiligen *.zip oder *.tgz Datei (Nicht ausgepackt!) erfolgen. Alternativ kann natürlich weiterhin auch einfach eine neue SD-Karte verwendet werden und das im Archiv befindliche *.img auf die neue SD Karte kopiert werden um dann von dort aus neu zu booten und via Backup-Restore das jeweils aktuelle Backup wiederherstellen zu lassen.

Hinweis:
Bitte beachten, dass natürlich vor jedem Update erst einmal ein manuelles Backup erfolgen sollte damit bei eventl. Fehlschlagen des WebUI-basierten Updates man mittels einer neuen SD-Karte dann sein aktuellstes Backup einfach wieder einspielen kann.

Für Bugreports und Featurerequests bitte den GitHub Issue-Tracker nutzen damit ich die Anfragen geordnet abarbeiten kann. Support- und Hilfeanfragen bei vermeintlichen Nutzungsproblemen bitte weiterhin hier als erstes im Forum platzieren und erst daraus ein Bugreport im GitHub machen wenn das Problem von anderen Nutzern bestätigt werden konnte.

Viel Spass mit der neuen RaspberryMatic Version!
RaspberryMatic 3.59.6.20210703 @ ESXi, ~190 Hm-RF/HmIP-RF/HmIPW Geräte, ioBroker – RaspberryMatic GitHub Projekt / Twitter

Hackertomm
Beiträge: 495
Registriert: 18.04.2018, 12:32
System: Alternative CCU (auf Basis OCCU)
Wohnort: Neuhausen auf den Fildern
Hat sich bedankt: 15 Mal
Danksagung erhalten: 13 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von Hackertomm » 24.04.2021, 19:26

Danke für die Neue Version!
Ich bin gerade am runter laden, aber Installiere sie erst irgendwann später.
Ein Tipp zum Odroid:
Das Ding kann mit einem EMMC-Modul ausgerüstet werden.
Vermutlich kann man da auch davon Booten.
Zuletzt geändert von Hackertomm am 26.04.2021, 12:05, insgesamt 1-mal geändert.
Gruß
Hackertomm

Virtual Image auf einer Qnap TS-453pro, 2GHZ Celeron u. 8GB RAM, aktuell Raspberry X86, Vers. 3.59.6.20210703

MartinBr
Beiträge: 377
Registriert: 25.01.2017, 10:51
Wohnort: Bei Berlin
Hat sich bedankt: 3 Mal
Danksagung erhalten: 8 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von MartinBr » 24.04.2021, 19:36

Ich war mal so mutig und habe die neue Version installiert. System: X64 VM unter Proxmox mit HM_RF_ETH und EnOcean Gateway FAM300.
Das Update lieft komplett in weniger als 5 Minuten durch. Alle Geräte HM, HmIP und EnOcean sind da.
Vielen Dank Jens und den anderen "Contributors" an dieser Version.
Gruß
Martin
RaspberryMatic-3.57.5 auf Tinkerboard S, CUxD 2.6, XML-1.20, ioBroker (HM,HMIP, Zigbee, Zwave und Shelly) und Alexa in einer VM unter Proxmox, VitoComfort 200

Benutzeravatar
jmaus
Beiträge: 7422
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 212 Mal
Danksagung erhalten: 808 Mal
Kontaktdaten:

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von jmaus » 24.04.2021, 19:56

Hackertomm hat geschrieben:
24.04.2021, 19:26
Ein Tipp zum Ondroid:
Das Ding kann mit einem EMMC-Modul ausgerüstet werden.
Vermutlich kann man da auch davon Booten.
Natürlich kann man das :) Einziger Wehrmutstropfen bei Einsatz eines ODROID ist allerdings, das damit die LED des RPI-RF-MOD Funkmodules nicht gesteuert werden kann weil die Pins der GPIO Leistes wo die LEDs des RPI-RF-MOD anliegen vom ODROID anderweitig genutzt werden. Ansonsten geht das RPI-RF-MOD Funkmodul aber problemlos mit den ODROID SBCs.
RaspberryMatic 3.59.6.20210703 @ ESXi, ~190 Hm-RF/HmIP-RF/HmIPW Geräte, ioBroker – RaspberryMatic GitHub Projekt / Twitter

Benutzeravatar
cybermcm
Beiträge: 13
Registriert: 31.10.2019, 18:28
System: Alternative CCU (auf Basis OCCU)

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von cybermcm » 24.04.2021, 20:26

Vorweg, vielen Dank für RaspberryMatic, verwende die SW seit der ersten Minute und bin sehr zufrieden!
Bin heute von 3.57.4.20210320 auf die aktuelle 3.57.5.20210424 (RaspberryMatic-3.57.5.20210424-rpi3.zip) umgestiegen, leider sind jetzt ein paar Dinge "seltsam":
Der Status meiner HMIP-PS stimmt nach dem Reboot nicht mehr (werden OFF angezeigt, obwohl ON)
Mein HmIP-STHD meldet keine Daten mehr.
Die Steuerung mittels OpenHab ist ebenfalls buggy (meine HmIP-BDT lassen sich einschalten, aber nicht mehr ausschalten).

Alles seit der neuen Version gerade eben. Habe noch nie intensiv ins Log geschaut, da sind etliche Error MSG.
Hat jemand einen Ratschlag für mich? Reboot und Stromlos des Raspis habe ich schon versucht, hat nichts gebracht.

Code: Alles auswählen


***** messages *****
Apr 24 20:00:43 localhost syslog.info syslogd started: BusyBox v1.33.0
Apr 24 20:00:43 localhost user.notice kernel: klogd started: BusyBox v1.33.0 (2021-04-24 10:33:39 UTC)
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Apr 24 20:00:43 localhost user.notice kernel: [    0.000000] Linux version 5.10.17 (builder@aa5f58525287) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot -g4b6c93c) 9.3.0, GNU ld (GNU Binutils) 2.35.2) #1 SMP PREEMPT Sat Apr 24 11:10:41 UTC 2021
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] efi: UEFI not found.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Zone ranges:
Apr 24 20:00:43 localhost user.info kernel: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003dffffff]
Apr 24 20:00:43 localhost user.info kernel: [    0.000000]   DMA32    empty
Apr 24 20:00:43 localhost user.info kernel: [    0.000000]   Normal   empty
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Movable zone start for each node
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Early memory node ranges
Apr 24 20:00:43 localhost user.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000003dffffff]
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003dffffff]
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000] On node 0 totalpages: 253952
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000]   DMA zone: 3968 pages used for memmap
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000]   DMA zone: 0 pages reserved
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000]   DMA zone: 253952 pages, LIFO batch:63
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] percpu: Embedded 30 pages/cpu s83224 r8192 d31464 u122880
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000] pcpu-alloc: s83224 r8192 d31464 u122880 alloc=30*4096
Apr 24 20:00:43 localhost user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Detected VIPT I-cache on CPU0
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 845719
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 843419
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 249984
Apr 24 20:00:43 localhost user.notice kernel: [    0.000000] Kernel command line: dwc_otg.lpm_enable=0 sdhci_bcm2708.enable_llm=0 console=tty2 kgdboc=tty2 scandelay=5 root=PARTUUID=deedbeef-02 ro rootfstype=ext4 elevator=deadline fsck.repair=yes lapic rootwait rootdelay=5 consoleblank=120 logo.nologo quiet loglevel=0 net.ifnames=0 usb-storage.quirks=  coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  empty
Apr 24 20:00:43 localhost user.warn kernel: [    0.000000] Kernel parameter elevator= does not have any effect anymore.
Apr 24 20:00:43 localhost user.warn kernel: [    0.000000] Please use sysfs to set IO scheduler for individual devices.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] Memory: 909856K/1015808K available (9984K kernel code, 1688K rwdata, 3452K rodata, 3328K init, 1233K bss, 40416K reserved, 65536K cma-reserved)
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] ftrace: allocating 32429 entries in 127 pages
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] ftrace: allocated 127 pages with 7 groups
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] rcu: Preemptible hierarchical RCU implementation.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] rcu: 	RCU event tracing is enabled.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] 	Trampoline variant of Tasks RCU enabled.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] 	Rude variant of Tasks RCU enabled.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Apr 24 20:00:43 localhost user.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x3b8/0x574 with crng_init=0
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Apr 24 20:00:43 localhost user.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Apr 24 20:00:43 localhost user.info kernel: [    0.000009] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Apr 24 20:00:43 localhost user.info kernel: [    0.000306] Console: colour dummy device 80x25
Apr 24 20:00:43 localhost user.info kernel: [    0.000376] printk: console [tty2] enabled
Apr 24 20:00:43 localhost user.info kernel: [    0.000438] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Apr 24 20:00:43 localhost user.info kernel: [    0.000474] pid_max: default: 32768 minimum: 301
Apr 24 20:00:43 localhost user.info kernel: [    0.000688] LSM: Security Framework initializing
Apr 24 20:00:43 localhost user.info kernel: [    0.000721] Yama: becoming mindful.
Apr 24 20:00:43 localhost user.info kernel: [    0.001004] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    0.001043] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    0.002676] Disabling memory control group subsystem
Apr 24 20:00:43 localhost user.info kernel: [    0.005483] rcu: Hierarchical SRCU implementation.
Apr 24 20:00:43 localhost user.info kernel: [    0.006656] EFI services will not be available.
Apr 24 20:00:43 localhost user.info kernel: [    0.007338] smp: Bringing up secondary CPUs ...
Apr 24 20:00:43 localhost user.info kernel: [    0.008728] Detected VIPT I-cache on CPU1
Apr 24 20:00:43 localhost user.info kernel: [    0.008818] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Apr 24 20:00:43 localhost user.info kernel: [    0.010418] Detected VIPT I-cache on CPU2
Apr 24 20:00:43 localhost user.info kernel: [    0.010477] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Apr 24 20:00:43 localhost user.info kernel: [    0.012044] Detected VIPT I-cache on CPU3
Apr 24 20:00:43 localhost user.info kernel: [    0.012100] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Apr 24 20:00:43 localhost user.info kernel: [    0.012317] smp: Brought up 1 node, 4 CPUs
Apr 24 20:00:43 localhost user.info kernel: [    0.012340] SMP: Total of 4 processors activated.
Apr 24 20:00:43 localhost user.info kernel: [    0.012359] CPU features: detected: 32-bit EL0 Support
Apr 24 20:00:43 localhost user.info kernel: [    0.012376] CPU features: detected: CRC32 instructions
Apr 24 20:00:43 localhost user.info kernel: [    0.048121] CPU: All CPU(s) started at EL2
Apr 24 20:00:43 localhost user.info kernel: [    0.048210] alternatives: patching kernel code
Apr 24 20:00:43 localhost user.info kernel: [    0.049995] devtmpfs: initialized
Apr 24 20:00:43 localhost user.notice kernel: [    0.072051] Enabled cp15_barrier support
Apr 24 20:00:43 localhost user.notice kernel: [    0.072101] Enabled setend support
Apr 24 20:00:43 localhost user.info kernel: [    0.072456] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Apr 24 20:00:43 localhost user.info kernel: [    0.072494] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    0.075739] pinctrl core: initialized pinctrl subsystem
Apr 24 20:00:43 localhost user.info kernel: [    0.077012] DMI not present or invalid.
Apr 24 20:00:43 localhost user.info kernel: [    0.077551] NET: Registered protocol family 16
Apr 24 20:00:43 localhost user.info kernel: [    0.088881] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Apr 24 20:00:43 localhost user.info kernel: [    0.089385] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Apr 24 20:00:43 localhost user.info kernel: [    0.090938] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Apr 24 20:00:43 localhost user.info kernel: [    0.091753] thermal_sys: Registered thermal governor 'step_wise'
Apr 24 20:00:43 localhost user.info kernel: [    0.092093] cpuidle: using governor ladder
Apr 24 20:00:43 localhost user.info kernel: [    0.092171] cpuidle: using governor menu
Apr 24 20:00:43 localhost user.info kernel: [    0.093133] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Apr 24 20:00:43 localhost user.info kernel: [    0.093400] ASID allocator initialised with 65536 entries
Apr 24 20:00:43 localhost user.info kernel: [    0.121921] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Apr 24 20:00:43 localhost user.info kernel: [    0.128593] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-02-25T12:12:09, variant start
Apr 24 20:00:43 localhost user.info kernel: [    0.132608] raspberrypi-firmware soc:firmware: Firmware hash is 564e5f9b852b23a330b1764bcf0b2d022a20afd0
Apr 24 20:00:43 localhost user.info kernel: [    0.176953] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Apr 24 20:00:43 localhost user.notice kernel: [    0.180029] SCSI subsystem initialized
Apr 24 20:00:43 localhost user.debug kernel: [    0.180401] libata version 3.00 loaded.
Apr 24 20:00:43 localhost user.info kernel: [    0.180723] usbcore: registered new interface driver usbfs
Apr 24 20:00:43 localhost user.info kernel: [    0.180951] usbcore: registered new interface driver hub
Apr 24 20:00:43 localhost user.info kernel: [    0.181057] usbcore: registered new device driver usb
Apr 24 20:00:43 localhost user.info kernel: [    0.182263] NetLabel: Initializing
Apr 24 20:00:43 localhost user.info kernel: [    0.182281] NetLabel:  domain hash size = 128
Apr 24 20:00:43 localhost user.info kernel: [    0.182296] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
Apr 24 20:00:43 localhost user.info kernel: [    0.182424] NetLabel:  unlabeled traffic allowed by default
Apr 24 20:00:43 localhost user.info kernel: [    0.183670] clocksource: Switched to clocksource arch_sys_counter
Apr 24 20:00:43 localhost user.notice kernel: [    1.927599] VFS: Disk quotas dquot_6.6.0
Apr 24 20:00:43 localhost user.info kernel: [    1.927754] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Apr 24 20:00:43 localhost user.notice kernel: [    1.928005] FS-Cache: Loaded
Apr 24 20:00:43 localhost user.info kernel: [    1.928381] CacheFiles: Loaded
Apr 24 20:00:43 localhost user.info kernel: [    1.928659] simple-framebuffer 3eaa9000.framebuffer: framebuffer at 0x3eaa9000, 0x151800 bytes, mapped to 0x(____ptrval____)
Apr 24 20:00:43 localhost user.info kernel: [    1.928682] simple-framebuffer 3eaa9000.framebuffer: format=a8r8g8b8, mode=720x480x32, linelength=2880
Apr 24 20:00:43 localhost user.info kernel: [    1.929248] Console: switching to colour frame buffer device 90x30
Apr 24 20:00:43 localhost user.info kernel: [    1.935066] simple-framebuffer 3eaa9000.framebuffer: fb0: simplefb registered!
Apr 24 20:00:43 localhost user.info kernel: [    1.949780] NET: Registered protocol family 2
Apr 24 20:00:43 localhost user.info kernel: [    1.950961] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    1.951014] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    1.951300] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    1.951504] TCP: Hash tables configured (established 8192 bind 8192)
Apr 24 20:00:43 localhost user.info kernel: [    1.951869] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    1.951931] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Apr 24 20:00:43 localhost user.info kernel: [    1.952356] NET: Registered protocol family 1
Apr 24 20:00:43 localhost user.info kernel: [    1.953503] RPC: Registered named UNIX socket transport module.
Apr 24 20:00:43 localhost user.info kernel: [    1.953520] RPC: Registered udp transport module.
Apr 24 20:00:43 localhost user.info kernel: [    1.953534] RPC: Registered tcp transport module.
Apr 24 20:00:43 localhost user.info kernel: [    1.953549] RPC: Registered tcp NFSv4.1 backchannel transport module.
Apr 24 20:00:43 localhost user.info kernel: [    1.956381] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
Apr 24 20:00:43 localhost user.notice kernel: [    1.961692] Initialise system trusted keyrings
Apr 24 20:00:43 localhost user.info kernel: [    1.962122] workingset: timestamp_bits=46 max_order=18 bucket_order=0
Apr 24 20:00:43 localhost user.info kernel: [    1.971881] zbud: loaded
Apr 24 20:00:43 localhost user.notice kernel: [    1.974718] FS-Cache: Netfs 'nfs' registered for caching
Apr 24 20:00:43 localhost user.notice kernel: [    1.975715] NFS: Registering the id_resolver key type
Apr 24 20:00:43 localhost user.notice kernel: [    1.975787] Key type id_resolver registered
Apr 24 20:00:43 localhost user.notice kernel: [    1.975803] Key type id_legacy registered
Apr 24 20:00:43 localhost user.info kernel: [    1.975970] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Apr 24 20:00:43 localhost user.notice kernel: [    1.977594] Key type asymmetric registered
Apr 24 20:00:43 localhost user.notice kernel: [    1.977613] Asymmetric key parser 'x509' registered
Apr 24 20:00:43 localhost user.info kernel: [    1.977681] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Apr 24 20:00:43 localhost user.info kernel: [    1.978079] io scheduler mq-deadline registered
Apr 24 20:00:43 localhost user.info kernel: [    1.978098] io scheduler kyber registered
Apr 24 20:00:43 localhost user.info kernel: [    1.988229] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Apr 24 20:00:43 localhost user.info kernel: [    1.991609] bcm2835-rng 3f104000.rng: hwrng registered
Apr 24 20:00:43 localhost user.info kernel: [    1.992369] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Apr 24 20:00:43 localhost user.info kernel: [    1.993531] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Apr 24 20:00:43 localhost user.warn kernel: [    1.994044] cacheinfo: Unable to detect cache hierarchy for CPU 0
Apr 24 20:00:43 localhost user.info kernel: [    2.010471] brd: module loaded
Apr 24 20:00:43 localhost user.info kernel: [    2.028675] loop: module loaded
Apr 24 20:00:43 localhost user.info kernel: [    2.030250] Loading iSCSI transport class v2.0-870.
Apr 24 20:00:43 localhost user.info kernel: [    2.032409] libphy: Fixed MDIO Bus: probed
Apr 24 20:00:43 localhost user.info kernel: [    2.032698] tun: Universal TUN/TAP device driver, 1.6
Apr 24 20:00:43 localhost user.info kernel: [    2.033087] usbcore: registered new interface driver lan78xx
Apr 24 20:00:43 localhost user.info kernel: [    2.033170] usbcore: registered new interface driver smsc95xx
Apr 24 20:00:43 localhost user.info kernel: [    2.033198] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Apr 24 20:00:43 localhost user.warn kernel: [    2.234178] Core Release: 2.80a
Apr 24 20:00:43 localhost user.warn kernel: [    2.234199] Setting default values for core params
Apr 24 20:00:43 localhost user.warn kernel: [    2.234233] Finished setting default values for core params
Apr 24 20:00:43 localhost user.warn kernel: [    2.434704] Using Buffer DMA mode
Apr 24 20:00:43 localhost user.warn kernel: [    2.434721] Periodic Transfer Interrupt Enhancement - disabled
Apr 24 20:00:43 localhost user.warn kernel: [    2.434736] Multiprocessor Interrupt Enhancement - disabled
Apr 24 20:00:43 localhost user.warn kernel: [    2.434754] OTG VER PARAM: 0, OTG VER FLAG: 0
Apr 24 20:00:43 localhost user.warn kernel: [    2.434775] Dedicated Tx FIFOs mode
Apr 24 20:00:43 localhost user.warn kernel: [    2.439406] 
Apr 24 20:00:43 localhost user.warn kernel: [    2.439431] WARN::dwc_otg_hcd_init:1072: FIQ DMA bounce buffers: virt = ffffffc0117bb000 dma = 0x00000000fa400000 len=9024
Apr 24 20:00:43 localhost user.warn kernel: [    2.439469] FIQ FSM acceleration enabled for :
Apr 24 20:00:43 localhost user.warn kernel: [    2.439469] Non-periodic Split Transactions
Apr 24 20:00:43 localhost user.warn kernel: [    2.439469] Periodic Split Transactions
Apr 24 20:00:43 localhost user.warn kernel: [    2.439469] High-Speed Isochronous Endpoints
Apr 24 20:00:43 localhost user.warn kernel: [    2.439469] Interrupt/Control Split Transaction hack enabled
Apr 24 20:00:43 localhost user.debug kernel: [    2.439486] dwc_otg: Microframe scheduler enabled
Apr 24 20:00:43 localhost user.warn kernel: [    2.439548] 
Apr 24 20:00:43 localhost user.warn kernel: [    2.439566] WARN::hcd_init_fiq:496: MPHI regs_base at ffffffc0113c5000
Apr 24 20:00:43 localhost user.info kernel: [    2.439681] dwc_otg 3f980000.usb: DWC OTG Controller
Apr 24 20:00:43 localhost user.info kernel: [    2.439727] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Apr 24 20:00:43 localhost user.info kernel: [    2.439792] dwc_otg 3f980000.usb: irq 74, io mem 0x00000000
Apr 24 20:00:43 localhost user.warn kernel: [    2.439849] Init: Port Power? op_state=1
Apr 24 20:00:43 localhost user.warn kernel: [    2.439864] Init: Power Port (0)
Apr 24 20:00:43 localhost user.info kernel: [    2.440380] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Apr 24 20:00:43 localhost user.info kernel: [    2.440402] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Apr 24 20:00:43 localhost user.info kernel: [    2.440420] usb usb1: Product: DWC OTG Controller
Apr 24 20:00:43 localhost user.info kernel: [    2.440438] usb usb1: Manufacturer: Linux 5.10.17 dwc_otg_hcd
Apr 24 20:00:43 localhost user.info kernel: [    2.440456] usb usb1: SerialNumber: 3f980000.usb
Apr 24 20:00:43 localhost user.info kernel: [    2.441404] hub 1-0:1.0: USB hub found
Apr 24 20:00:43 localhost user.info kernel: [    2.441493] hub 1-0:1.0: 1 port detected
Apr 24 20:00:43 localhost user.debug kernel: [    2.442802] dwc_otg: FIQ enabled
Apr 24 20:00:43 localhost user.debug kernel: [    2.442818] dwc_otg: NAK holdoff enabled
Apr 24 20:00:43 localhost user.debug kernel: [    2.442833] dwc_otg: FIQ split-transaction FSM enabled
Apr 24 20:00:43 localhost user.debug kernel: [    2.442855] Module dwc_common_port init
Apr 24 20:00:43 localhost user.info kernel: [    2.444299] usbcore: registered new interface driver uas
Apr 24 20:00:43 localhost user.info kernel: [    2.444419] usbcore: registered new interface driver usb-storage
Apr 24 20:00:43 localhost user.info kernel: [    2.444886] mousedev: PS/2 mouse device common for all mice
Apr 24 20:00:43 localhost user.info kernel: [    2.446823] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Apr 24 20:00:43 localhost user.info kernel: [    2.451221] sdhci: Secure Digital Host Controller Interface driver
Apr 24 20:00:43 localhost user.info kernel: [    2.451240] sdhci: Copyright(c) Pierre Ossman
Apr 24 20:00:43 localhost user.info kernel: [    2.452403] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Apr 24 20:00:43 localhost user.info kernel: [    2.453304] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Apr 24 20:00:43 localhost user.info kernel: [    2.453601] sdhci-pltfm: SDHCI platform and OF driver helper
Apr 24 20:00:43 localhost user.info kernel: [    2.456725] ledtrig-cpu: registered to indicate activity on CPUs
Apr 24 20:00:43 localhost user.info kernel: [    2.456799] hid: raw HID events driver (C) Jiri Kosina
Apr 24 20:00:43 localhost user.info kernel: [    2.456941] usbcore: registered new interface driver usbhid
Apr 24 20:00:43 localhost user.info kernel: [    2.456948] usbhid: USB HID core driver
Apr 24 20:00:43 localhost user.info kernel: [    2.461384] NET: Registered protocol family 17
Apr 24 20:00:43 localhost user.notice kernel: [    2.461698] Key type dns_resolver registered
Apr 24 20:00:43 localhost user.info kernel: [    2.462525] registered taskstats version 1
Apr 24 20:00:43 localhost user.notice kernel: [    2.462542] Loading compiled-in X.509 certificates
Apr 24 20:00:43 localhost user.info kernel: [    2.475365] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 71, base_baud = 31250000) is a 16550
Apr 24 20:00:43 localhost user.info kernel: [    2.476172] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Apr 24 20:00:43 localhost user.info kernel: [    2.477439] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Apr 24 20:00:43 localhost user.info kernel: [    2.477450] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Apr 24 20:00:43 localhost user.info kernel: [    2.501847] sdhost: log_buf @ (____ptrval____) (c263d000)
Apr 24 20:00:43 localhost user.warn kernel: [    2.522052] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Apr 24 20:00:43 localhost user.warn kernel: [    2.523768] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Apr 24 20:00:43 localhost user.warn kernel: [    2.525492] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Apr 24 20:00:43 localhost user.warn kernel: [    2.528804] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Apr 24 20:00:43 localhost user.info kernel: [    2.553324] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Apr 24 20:00:43 localhost user.info kernel: [    2.558073] of_cfs_init
Apr 24 20:00:43 localhost user.info kernel: [    2.558131] of_cfs_init: OK
Apr 24 20:00:43 localhost user.info kernel: [    2.559764] Waiting 5 sec before mounting root device...
Apr 24 20:00:43 localhost user.notice kernel: [    2.594128] random: fast init done
Apr 24 20:00:43 localhost user.warn kernel: [    2.621670] mmc0: host does not support reading read-only switch, assuming write-enable
Apr 24 20:00:43 localhost user.info kernel: [    2.625306] mmc0: new high speed SDHC card at address 2127
Apr 24 20:00:43 localhost user.info kernel: [    2.626646] mmcblk0: mmc0:2127 APPSD 3.75 GiB
Apr 24 20:00:43 localhost user.info kernel: [    2.629354]  mmcblk0: p1 p2 p3
Apr 24 20:00:43 localhost user.warn kernel: [    2.648618] Indeed it is in host mode hprt0 = 00021501
Apr 24 20:00:43 localhost user.info kernel: [    2.652279] mmc1: new high speed SDIO card at address 0001
Apr 24 20:00:43 localhost user.info kernel: [    2.835782] usb 1-1: new high-speed USB device number 2 using dwc_otg
Apr 24 20:00:43 localhost user.warn kernel: [    2.836007] Indeed it is in host mode hprt0 = 00001101
Apr 24 20:00:43 localhost user.info kernel: [    3.044223] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
Apr 24 20:00:43 localhost user.info kernel: [    3.044272] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 24 20:00:43 localhost user.info kernel: [    3.045319] hub 1-1:1.0: USB hub found
Apr 24 20:00:43 localhost user.info kernel: [    3.045500] hub 1-1:1.0: 5 ports detected
Apr 24 20:00:43 localhost user.info kernel: [    3.331753] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Apr 24 20:00:43 localhost user.info kernel: [    3.432246] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
Apr 24 20:00:43 localhost user.info kernel: [    3.432269] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Apr 24 20:00:43 localhost user.info kernel: [    3.435229] smsc95xx v2.0.0
Apr 24 20:00:43 localhost user.info kernel: [    3.484157] libphy: smsc95xx-mdiobus: probed
Apr 24 20:00:43 localhost user.info kernel: [    3.485655] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:db:d9:08
Apr 24 20:00:43 localhost user.notice kernel: [    3.842287] random: crng init done
Apr 24 20:00:43 localhost user.info kernel: [    7.661115] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Apr 24 20:00:43 localhost user.info kernel: [    7.661226] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Apr 24 20:00:43 localhost user.info kernel: [    7.662106] devtmpfs: mounted
Apr 24 20:00:43 localhost user.info kernel: [    7.669075] Freeing unused kernel memory: 3328K
Apr 24 20:00:43 localhost user.info kernel: [    7.671868] Run /sbin/init as init process
Apr 24 20:00:43 localhost user.debug kernel: [    7.671880]   with arguments:
Apr 24 20:00:43 localhost user.debug kernel: [    7.671891]     /sbin/init
Apr 24 20:00:43 localhost user.debug kernel: [    7.671901]     lapic
Apr 24 20:00:43 localhost user.debug kernel: [    7.671911]     empty
Apr 24 20:00:43 localhost user.debug kernel: [    7.671923]   with environment:
Apr 24 20:00:43 localhost user.debug kernel: [    7.671933]     HOME=/
Apr 24 20:00:43 localhost user.debug kernel: [    7.671944]     TERM=linux
Apr 24 20:00:43 localhost user.debug kernel: [    7.671954]     kgdboc=tty2
Apr 24 20:00:43 localhost user.debug kernel: [    7.671964]     scandelay=5
Apr 24 20:00:43 localhost user.warn kernel: [    8.321776] EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
Apr 24 20:00:43 localhost user.info kernel: [    8.333486] EXT4-fs (mmcblk0p3): mounted filesystem with journalled data mode. Opts: data=journal
Apr 24 20:00:43 localhost user.info kernel: [   10.326804] zram: Added device: zram0
Apr 24 20:00:43 localhost user.info kernel: [   10.366410] zram0: detected capacity change from 0 to 1052319744
Apr 24 20:00:43 localhost user.info kernel: [   10.431738] Adding 1027652k swap on /dev/zram0.  Priority:75 extents:1 across:1027652k SSFS
Apr 24 20:00:43 localhost user.info kernel: [   10.498807] i2c /dev entries driver
Apr 24 20:00:43 localhost user.info kernel: [   10.528767] rtc-ds1307 1-0032: registered as rtc0
Apr 24 20:00:43 localhost user.warn kernel: [   10.544541] dummy_rx8130: loading out-of-tree module taints kernel.
Apr 24 20:00:43 localhost daemon.info kernel: [   10.991883] udevd[277]: starting version 3.2.9
Apr 24 20:00:43 localhost daemon.info kernel: [   11.038311] udevd[278]: starting eudev-3.2.9
Apr 24 20:00:43 localhost user.info kernel: [   11.216915] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Apr 24 20:00:43 localhost user.info kernel: [   11.217098] pl011_raw_uart 3f201000.serial: Detected RPI-RF-MOD, using alternative reset pin
Apr 24 20:00:43 localhost user.info kernel: [   11.395873] pl011_raw_uart 3f201000.serial: Initialized pl011 device; mapbase=0x3f201000; irq=99; clockrate=47999625
Apr 24 20:00:43 localhost user.notice kernel: [   11.459893] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Apr 24 20:00:43 localhost user.notice kernel: [   11.495284] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Apr 24 20:00:43 localhost user.warn kernel: [   11.496241] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Apr 24 20:00:43 localhost user.info kernel: [   11.496261] cfg80211: failed to load regulatory.db
Apr 24 20:00:43 localhost user.debug kernel: [   11.540888] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Apr 24 20:00:43 localhost user.err kernel: [   11.547839] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Apr 24 20:00:43 localhost user.info kernel: [   11.548090] usbcore: registered new interface driver brcmfmac
Apr 24 20:00:43 localhost user.warn kernel: [   11.569261] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Apr 24 20:00:44 localhost daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Apr 24 20:00:44 localhost user.err kernel: [   11.757917] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Apr 24 20:00:44 localhost user.err kernel: [   11.758030] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Apr 24 20:00:44 localhost user.err kernel: [   11.758883] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
Apr 24 20:00:44 localhost user.notice rfkill: block set for type bluetooth
Apr 24 20:00:44 localhost user.info kernel: [   12.109646] SMSC LAN8700 usb-001:003:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:003:01, irq=POLL)
Apr 24 20:00:44 localhost user.info kernel: [   12.110015] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 24 20:00:44 localhost user.info kernel: [   12.124748] smsc95xx 1-1.1:1.0 eth0: Link is Down
Apr 24 20:00:46 localhost user.info kernel: [   14.176750] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off
Apr 24 20:00:48 localhost syslog.info syslogd exiting
Apr 24 20:00:48 homematic syslog.info syslogd started: BusyBox v1.33.0
Apr 24 20:00:48 homematic user.notice kernel: klogd started: BusyBox v1.33.0 (2021-04-24 10:33:39 UTC)
Apr 24 20:00:48 homematic daemon.info udhcpc[396]: started, v1.33.0
Apr 24 20:00:48 homematic daemon.info udhcpc[396]: sending discover
Apr 24 20:00:48 homematic daemon.info udhcpc[396]: sending select for 192.168.10.4
Apr 24 20:00:48 homematic daemon.info udhcpc[396]: lease of 192.168.10.4 obtained, lease time 7200
Apr 24 20:00:49 homematic user.info kernel: [   16.669578] NET: Registered protocol family 10
Apr 24 20:00:49 homematic user.info kernel: [   16.673240] Segment Routing with IPv6
Apr 24 20:00:52 homematic user.info firewall: configuration set
Apr 24 20:00:53 homematic user.notice rfkill: block set for type wlan
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: ifplugd 0.28 initializing.
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: Using interface eth0/B8:27:EB:DB:D9:08 with driver <smsc95xx> (version: 5.10.17)
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: Using detection mode: SIOCETHTOOL
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: Initialization complete, link beat detected.
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Apr 24 20:00:53 homematic daemon.warn ifplugd(eth0)[546]: client: ifup: interface eth0 already configured
Apr 24 20:00:53 homematic daemon.info ifplugd(eth0)[546]: Program executed successfully.
Apr 24 20:00:53 homematic daemon.info ifplugd(wlan0)[551]: ifplugd 0.28 initializing.
Apr 24 20:00:53 homematic daemon.info ifplugd(wlan0)[551]: Using interface wlan0/B8:27:EB:8E:8C:5D with driver <brcmfmac> (version: 7.45.98.94)
Apr 24 20:00:53 homematic daemon.info ifplugd(wlan0)[551]: Using detection mode: IFF_RUNNING
Apr 24 20:00:53 homematic daemon.info ifplugd(wlan0)[551]: Initialization complete, link beat not detected.
Apr 24 20:01:01 homematic daemon.notice ntpdate[556]: step time server 217.196.145.42 offset +1.481599 sec
Apr 24 20:01:01 homematic daemon.info chronyd[560]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -NTS -SECHASH +IPV6 -DEBUG)
Apr 24 20:01:02 homematic user.info kernel: [   28.252143] raw-uart raw-uart: Reset radio module
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ 3f201000.serial(99) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Apr 24 20:01:05 homematic daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Apr 24 20:01:06 homematic daemon.err xinetd[651]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Apr 24 20:01:06 homematic daemon.crit xinetd[651]: 651 {init_services} no services. Exiting...
Apr 24 20:01:07 homematic auth.info sshd[682]: Server listening on 0.0.0.0 port 22.
Apr 24 20:01:07 homematic auth.info sshd[682]: Server listening on :: port 22.
Apr 24 20:01:07 homematic user.info root: Updating RF Lan Gateway Coprocessor Firmware
Apr 24 20:01:07 homematic user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Apr 24 20:01:07 homematic user.info root: Updating RF Lan Gateway Firmware
Apr 24 20:01:07 homematic user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Apr 24 20:01:07 homematic user.info kernel: [   33.670773] eq3loop: created slave mmd_hmip
Apr 24 20:01:07 homematic user.info kernel: [   33.671398] eq3loop: created slave mmd_bidcos
Apr 24 20:01:09 homematic user.info kernel: [   35.829635] eq3loop: eq3loop_open_slave() mmd_bidcos
Apr 24 20:01:30 homematic user.info kernel: [   57.073095] eq3loop: eq3loop_open_slave() mmd_hmip
Apr 24 20:01:30 homematic user.info kernel: [   57.073377] eq3loop: eq3loop_close_slave() mmd_hmip
Apr 24 20:01:31 homematic user.info kernel: [   57.110839] eq3loop: eq3loop_open_slave() mmd_hmip
Apr 24 18:01:48 homematic daemon.info : starting pid 1058, tty '/dev/null': '/usr/bin/monit -Ic /etc/monitrc'
Apr 24 20:01:48 homematic user.info monit[1058]: Starting Monit 5.27.2 daemon with http interface at /var/run/monit.sock
Apr 24 20:01:48 homematic user.info monit[1058]: 'homematic' Monit 5.27.2 started
Apr 24 20:02:00 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"001F58A9A70A22:0","CARRIER_SENSE_LEVEL"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: CARRIER_SENSE_LEVEL"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:00 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"001F58A9A70A22:0","CARRIER_SENSE_LEVEL"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:00 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D3C99C1FB8:6","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D3C99C1FB8:6","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAC0F:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D3C99C1FB8:6","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D3C99C1FB8:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAC0F:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DABA4:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DABA4:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAC0F:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAC0F:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAACC:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAACC:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DABA4:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DABA4:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA80A:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA80A:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAACC:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAACC:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA9DF:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA9DF:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA80A:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA80A:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000B9A4999FE7C:5","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000B9A4999FE7C:5","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA9DF:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA9DF:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA8E1:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA8E1:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000B9A4999FE7C:5","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000B9A4999FE7C:5","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA97B:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA97B:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA8E1:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA8E1:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA99E:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA99E:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA97B:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA97B:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA9BB:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA9BB:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA99E:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA99E:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAA50:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAA50:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DA9BB:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DA9BB:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:06 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085A498DAA50:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085A498DAA50:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:06 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:09 homematic user.err monit[1058]: 'hs485dEnabled' status failed (2) -- grep: /var/etc/hs485d.conf: No such file or directory
Apr 24 20:02:09 homematic user.err monit[1058]: 'hmlangwEnabled' status failed (1) -- no output
Apr 24 20:02:09 homematic user.warn monit[1058]: 'hasUSB' status failed (1) -- no output
Apr 24 20:02:09 homematic user.err monit[1058]: 'hb_rf_eth-CheckEnabled' status failed (1) -- no output
Apr 24 20:02:09 homematic user.warn monit[1058]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr 24 20:02:09 homematic user.err monit[1058]: Lookup for '/media/usb1' filesystem failed  -- not found in /proc/self/mounts
Apr 24 20:02:09 homematic user.err monit[1058]: Filesystem '/media/usb1' not mounted
Apr 24 20:02:09 homematic user.err monit[1058]: 'usb1' unable to read filesystem '/media/usb1' state
Apr 24 20:02:09 homematic user.info monit[1058]: 'usb1' trying to restart
Apr 24 20:02:09 homematic daemon.info chronyd[560]: Selected source 78.46.102.180 (europe.pool.ntp.org)
Apr 24 20:02:27 homematic user.warn monit[1058]: 'hasUSB' status failed (1) -- no output
Apr 24 20:02:27 homematic user.err monit[1058]: 'wlan0CheckEnabled' status failed (1) -- no output
Apr 24 20:02:27 homematic user.warn monit[1058]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr 24 20:02:27 homematic user.err monit[1058]: Filesystem '/media/usb1' not mounted
Apr 24 20:02:27 homematic user.err monit[1058]: 'usb1' unable to read filesystem '/media/usb1' state
Apr 24 20:02:27 homematic user.info monit[1058]: 'usb1' trying to restart
Apr 24 20:02:45 homematic user.warn monit[1058]: 'hasUSB' status failed (1) -- no output
Apr 24 20:02:45 homematic user.err monit[1058]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr 24 20:02:45 homematic user.err monit[1058]: Filesystem '/media/usb1' not mounted
Apr 24 20:02:45 homematic user.err monit[1058]: 'usb1' unable to read filesystem '/media/usb1' state
Apr 24 20:02:45 homematic user.info monit[1058]: 'usb1' trying to restart
Apr 24 20:02:47 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","SET_POINT_TEMPERATURE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SET_POINT_TEMPERATURE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","SET_POINT_TEMPERATURE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:47 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","ACTIVE_PROFILE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ACTIVE_PROFILE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","ACTIVE_PROFILE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:47 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","ACTUAL_TEMPERATURE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ACTUAL_TEMPERATURE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","ACTUAL_TEMPERATURE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:47 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","HUMIDITY"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: HUMIDITY"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","HUMIDITY"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","WINDOW_STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: WINDOW_STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","WINDOW_STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","SET_POINT_MODE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SET_POINT_MODE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","SET_POINT_MODE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","PARTY_TIME_START"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_START"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","PARTY_TIME_START"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal =  [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","PARTY_TIME_END"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_TIME_END"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","PARTY_TIME_END"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal =  [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","PARTY_SET_POINT_TEMPERATURE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_SET_POINT_TEMPERATURE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","PARTY_SET_POINT_TEMPERATURE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000E9A498DFC8C:1","PARTY_MODE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: PARTY_MODE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000E9A498DFC8C:1","PARTY_MODE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D3C99C1FB8:3","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D3C99C1FB8:3","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00199A4992F7C5:4","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00199A4992F7C5:4","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000B9A4999FE7C:2","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000B9A4999FE7C:2","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00021BE98EAF76:3","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00021BE98EAF76:3","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00021BE98EAF43:3","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00021BE98EAF43:3","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:02:48 homematic local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00021BE98EAF1A:3","STATE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: STATE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00021BE98EAF1A:3","STATE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr 24 20:02:48 homematic local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr 24 20:03:03 homematic user.warn monit[1058]: 'hasUSB' status failed (1) -- no output
Apr 24 20:03:03 homematic user.err monit[1058]: Filesystem '/media/usb1' not mounted
Apr 24 20:03:03 homematic user.err monit[1058]: 'usb1' unable to read filesystem '/media/usb1' state
Apr 24 20:03:03 homematic user.info monit[1058]: 'usb1' trying to restart
Apr 24 20:03:14 homematic daemon.info chronyd[560]: Selected source 192.168.1.254
Apr 24 20:03:15 homematic daemon.info chronyd[560]: Source 78.46.102.180 replaced with 212.51.144.44 (europe.pool.ntp.org)
Apr 24 20:03:21 homematic user.err monit[1058]: 'hasUSB' status failed (1) -- no output
Apr 24 20:06:28 homematic daemon.info chronyd[560]: Selected source 212.51.144.44 (europe.pool.ntp.org)
Apr 24 20:07:33 homematic daemon.info chronyd[560]: Selected source 192.168.1.254


***** hmserver.log *****
Apr 24 20:01:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Apr 24 20:01:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Apr 24 20:01:16 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Apr 24 20:01:26 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter LOCK_STATE_STATUS subtype=default 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RoutingNotificationHandler] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackboneWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouteManagementWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 25 classes to Vert.x 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 25 VertxDeployers initialized 
Apr 24 20:01:27 de.eq3.cbcs.server.core.vertx.CyclicSmokeDetectorAwakening INFO  [vert.x-eventloop-thread-1] SYSTEM: CyclicSmokeDetectorAwakening Verticle or Worker started 
Apr 24 20:01:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (9a144123-8b3a-49de-952d-fac6d4c2d411) 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler INFO  [vert.x-worker-thread-1] SYSTEM: TransactionSubsystemHandler Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of TransactionSubsystemHandler succeeded (f66606c2-9cc2-49b0-9d26-2305611bdd8e) 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.RoutingNotificationHandler INFO  [vert.x-eventloop-thread-7] SYSTEM: RoutingNotificationHandler Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBlindLevelCorrectionHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBlindLevelCorrectionHandler Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.CheckDeviceExistHandler INFO  [vert.x-eventloop-thread-5] SYSTEM: CheckDeviceExistHandler Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of RoutingNotificationHandler succeeded (dee226be-bc34-4261-8ce5-d293be34f5a1) 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of CheckDeviceExistHandler succeeded (a3d07b93-329d-488d-abdf-c7202cceffcc) 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.HMIPAbstractWriterWorker INFO  [vert.x-worker-thread-2] SYSTEM: HMIPTRXWriterWorker Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of HMIPTRXWriterWorker succeeded (5822d159-2b35-4b71-8256-e03484694ea1) 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (dd47697a-a891-46f4-8b66-50fc4c37b3a6) 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.DeviceInclusionDefaultConfigurationChanger INFO  [vert.x-eventloop-thread-6] SYSTEM: DeviceInclusionDefaultConfigurationChanger Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.server.core.vertx.KeyServerWorker INFO  [vert.x-worker-thread-0] SYSTEM: KeyServerWorker Verticle or Worker started 
Apr 24 20:01:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (bd0d1890-1a80-4e56-af6d-8d38e4e3af83) 
Apr 24 20:01:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of KryoPersistenceWorker succeeded (de863245-a6e3-4182-b4c7-a23b97e5f318) 
Apr 24 20:01:29 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentDataLoader INFO  [vert.x-eventloop-thread-3] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started 
Apr 24 20:01:29 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker started 
Apr 24 20:01:29 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worker started 
Apr 24 20:01:29 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started 
Apr 24 20:01:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (f7bfaf03-b5d9-4098-a558-4435070c1752) 
Apr 24 20:01:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (167bfc28-021c-4cb5-999e-1340f3a62570) 
Apr 24 20:01:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (9df54aa3-4b81-452d-8c25-a8b056d84823) 
Apr 24 20:01:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (5a639ac0-cfc7-4d94-be59-10e497171035) 
Apr 24 20:01:30 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 24 20:01:30 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker started 
Apr 24 20:01:30 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceInclusionAcceptHandler Verticle or Worker started 
Apr 24 20:01:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (265cff26-4bcf-4d81-a4d6-50018eb874a4) 
Apr 24 20:01:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (f56f94de-d33c-47ba-b53d-4a4965fe5a5f) 
Apr 24 20:01:30 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO  [vert.x-eventloop-thread-2] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker started 
Apr 24 20:01:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (32074a2e-9dae-4a7b-a26a-8f69378037f0) 
Apr 24 20:01:30 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle INFO  [vert.x-eventloop-thread-0] SYSTEM: TransactionManagementVerticle Verticle or Worker started 
Apr 24 20:01:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of TransactionManagementVerticle succeeded (1f2fb879-5413-4299-895b-37b20b5552b1) 
Apr 24 20:01:30 de.eq3.cbcs.server.core.vertx.BackendCommandHandler INFO  [vert.x-eventloop-thread-4] SYSTEM: BackendCommandHandler Verticle or Worker started 
Apr 24 20:01:30 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (e1d70cb1-4405-42ad-b69c-ea982e4e4b24) 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [vert.x-eventloop-thread-6] SYSTEM: LocalServerAdapterInitialization Verticle or Worker started 
Apr 24 20:01:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (26357cc0-9e15-48bf-953b-4db8f1923671) 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter state 1: HMIP_TRX_App 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter application is already running or started 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] No NWK, try to set address ... 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Try to set radio address 11801099... 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Set max send attempts for 3014F711A0001F58A9A70A22 to 3 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Try to get application version... 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Application version 4.2.14 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Bootloader version 1.0.1 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] hmos version 1.54.0 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] MCU type: CC1310 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Duty Cycle: 1.0 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] set DutyCycle limit to ffffffc8 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Set Duty Cycle Limit 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Current Security Counter: 717067522 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Update security counter to calculation: 717072306 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] TRX adapter has 2 link partners 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-7] Adapter with Access Point id 3014F711A0001F58A9A70A22 initialized 
Apr 24 20:01:31 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-7] HMIPTRXInitialResponseListener said that Adapter was initialized 
Apr 24 20:01:32 de.eq3.cbcs.server.local.base.internal.LocalServerFirmwareUpdateInitialization INFO  [vert.x-eventloop-thread-6] SYSTEM: LocalServerFirmwareUpdateInitialization Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (0ac891e1-4162-4c0b-8cf5-1e9671bb4201) 
Apr 24 20:01:32 de.eq3.cbcs.lib.backbone.lanrouting.RouteManagementWorker INFO  [vert.x-worker-thread-0] SYSTEM: RouteManagementWorker Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RouteManagementWorker succeeded (090854a7-a8cb-4707-8651-2769c662a24a) 
Apr 24 20:01:32 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-4] UDP Routing configuration: trying to bind port 43438 on eth0 0.0.0.0 -> 192.168.10.4 
Apr 24 20:01:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBackendNotificationHandler succeeded (9ecac9ba-8ddf-47d8-83ec-01fba5c411df) 
Apr 24 20:01:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyNotificationHandler INFO  [vert.x-worker-thread-2] SYSTEM: LegacyNotificationHandler Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LegacyNotificationHandler succeeded (d7af7e51-5c5f-4f61-a042-ce0ff3e621ba) 
Apr 24 20:01:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker INFO  [vert.x-worker-thread-1] SYSTEM: LegacyAPIWorker Verticle or Worker started 
Apr 24 20:01:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LegacyAPIWorker succeeded (711a6b43-d7f8-4b37-9e51-e31a218160cd) 
Apr 24 20:01:32 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates 
Apr 24 20:01:33 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Apr 24 20:01:33 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Apr 24 20:01:33 de.eq3.cbcs.lib.backbone.lanrouting.BackboneWorker INFO  [vert.x-worker-thread-4] SYSTEM: BackboneWorker Verticle or Worker started 
Apr 24 20:01:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of BackboneWorker succeeded (3188a8f6-e8ba-47a5-b287-ddfc34bfe901) 
Apr 24 20:01:33 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-2] UDP Routing established on network interface eth0 : 0.0.0.0 (192.168.10.4) 
Apr 24 20:01:33 de.eq3.cbcs.lib.backbone.lanrouting.UdpServer INFO  [vert.x-worker-thread-0] UDP Routing multi cast 'DEFAULT_MULTICAST_ADDRESS' established on network interface eth0 : 192.168.10.4 
Apr 24 20:01:33 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyInitializion INFO  [vert.x-eventloop-thread-5] SYSTEM: LegacyInitializion Verticle or Worker started 
Apr 24 20:01:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyInitializion succeeded (d6543d0f-d737-4fb7-8bb7-f3040d1fc154) 
Apr 24 20:01:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 24 20:01:35 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateServerWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 12 classes to Vert.x 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of BackendWorker succeeded (b6340aea-b9c8-498d-8632-775cedfc735a) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 12 VertxDeployers initialized 
Apr 24 20:01:36 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO  [vert.x-worker-thread-10] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of RegaClientWorker succeeded (52815e5e-4ef7-47c2-8691-a36d895552d4) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (f09fed06-7997-4f51-8a1e-2f91e4a4a2ce) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (5f21208e-8c6d-4e34-9e92-dd861c8b18f5) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of EnergyPriceRequestWorker succeeded (e24640fd-be01-488a-a64b-121f023f4e26) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CouplingRequestWorker succeeded (1f75ab2a-1187-40a3-b92c-e047e2abef77) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of StorageRequestWorker succeeded (d0414836-d4a8-4921-878b-2f2b1cae379d) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of AccessPointUpdateServerWorker succeeded (f155a9dd-d782-4b1e-a5be-132a40ffed05) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DiagramRequestWorker succeeded (11303fb5-0725-4bc7-8651-57aba42f9802) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupRequestWorker succeeded (f0c302e3-4834-458a-9e42-eb080af2ff54) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (431b59b2-011c-4c8a-bab2-72d2183a4c0d) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (b9250986-bb08-44aa-8444-97d487de0ddc) 
Apr 24 20:01:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Apr 24 20:01:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Apr 24 20:01:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Apr 24 20:01:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Apr 24 20:01:40 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Apr 24 20:01:41 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Apr 24 20:01:41 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Apr 24 20:01:41 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Apr 24 20:01:41 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Apr 24 20:01:41 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Apr 24 20:01:42 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Apr 24 20:01:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos 
Apr 24 20:01:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [HmIP-RF_java_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 24 20:01:42 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Apr 24 20:01:42 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: HmIP-RF_java 
Apr 24 20:01:43 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-3] updateDevicesForClient HmIP-RF_java -> 255 device addresses will be added 
Apr 24 20:01:43 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Checking all devices on all accesspoints for updates 
Apr 24 20:01:43 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Apr 24 20:01:43 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Apr 24 20:01:43 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Apr 24 20:02:06 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Apr 24 20:02:06 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-4] Added InterfaceId: 1008 
Apr 24 20:02:06 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-14] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Apr 24 20:02:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:31999 
Apr 24 20:02:16 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [1009_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 24 20:02:16 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Apr 24 20:02:16 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: 1009 
Apr 24 20:06:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: 0 Accesspoints in Queue 
Apr 24 20:06:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Apr 24 20:06:29 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-7] SYSTEM: Eventlistener Handler utilization: 0/50 used 
UPDATE: Ich war anscheinend zu ungeduldig und habe das System jetzt eine Weile "in Ruhe" gelassen und siehe da, scheint sich alles wieder zu normalisieren, die o.a. Fehler sind nicht mehr vorhanden...
Sorry für die Einmeldung, die Error MSG im Log haben mich wohl zu schnell dazu verleitet...

SteveDdorf
Beiträge: 9
Registriert: 16.05.2019, 19:10
Hat sich bedankt: 3 Mal
Danksagung erhalten: 1 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von SteveDdorf » 24.04.2021, 23:02

Hallo,

die neue RaspberryMatic Version 3.57.5.20210424 ( RaspberryMatic-3.57.5.20210424-rpi2.zip) läuft auf meinem Raspberry Pi2 Model B leider nicht. Das System bleibt in der boot Sequenz hängen.

Hat jemand ähnliche Probleme mit dem Raspberry Pi2 Model B?

Benutzeravatar
jmaus
Beiträge: 7422
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 212 Mal
Danksagung erhalten: 808 Mal
Kontaktdaten:

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von jmaus » 24.04.2021, 23:06

SteveDdorf hat geschrieben:
24.04.2021, 23:02
die neue RaspberryMatic Version 3.57.5.20210424 ( RaspberryMatic-3.57.5.20210424-rpi2.zip) läuft auf meinem Raspberry Pi2 Model B leider nicht. Das System bleibt in der boot Sequenz hängen.

Hat jemand ähnliche Probleme mit dem Raspberry Pi2 Model B?
Welche Version hattest du vorher auf diesem Pi laufen?
RaspberryMatic 3.59.6.20210703 @ ESXi, ~190 Hm-RF/HmIP-RF/HmIPW Geräte, ioBroker – RaspberryMatic GitHub Projekt / Twitter

karlo enzo
Beiträge: 42
Registriert: 15.08.2019, 18:37
Hat sich bedankt: 1 Mal
Danksagung erhalten: 2 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von karlo enzo » 24.04.2021, 23:09

die neue RaspberryMatic Version 3.57.5.20210424 läuft auf meiner Proxmox-VM ohne Auffälligkeiten.
Vielen Dank für die tolle Arbeit an alle Mitwirkenden.
Viele Grüße
Karl-Heinz

Benutzeravatar
Bernd-Joras
Beiträge: 540
Registriert: 26.03.2016, 09:33
Hat sich bedankt: 15 Mal
Danksagung erhalten: 19 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von Bernd-Joras » 24.04.2021, 23:31

Hallöle ....
von 0320 auf 0424 mittels Update in 12 Min bisher problemlos ... werde weiter beobachten und ggf. berichten ...
Danke vorab ... Bernd
RPi3B+ RaspberryMatic 3.59.6.20210703 / RPI-RF-MOD | Externe USB-Platinen Antenne | 2x LAN_RF_GW | 1x LAN_RS485_GW | ca. 100 Geräte davon 10x IP | ca. 180 Programme |>400 Kanäle | Addons: CUX-Daemon, XML-API, hm_pdetect, E-Mail, CCU-Historian, Philips Hue, HConnectVPN, Sonos Player

MathiasZ
Beiträge: 2412
Registriert: 29.03.2015, 09:54
Wohnort: München
Hat sich bedankt: 110 Mal
Danksagung erhalten: 70 Mal

Re: RaspberryMatic 3.57.5.20210424 – Neue Version

Beitrag von MathiasZ » 25.04.2021, 00:30

Mir sind zur Zeit leider die Hände gebunden! :evil:
Bin im Moment in einem 1-Zimmer Appartement, vermisse meine Freundin und warte, bis ich endlich ins Haus einziehen kann. Die Raspberries und der Proxmox liegen in einem der 60 Umzugskartons.
Ich mache deshalb eine schöpferische Pause und melde mich im Juli wieder. :cry:
Gruß,
Mathias
Das lesen vom WebUI Handbuch hilft bei Problemen ungemein!
Zum Download des Handbuchs:
https://www.eq-3.de/Downloads/eq3/downl ... h_eQ-3.pdf
Skript-Dokumentation 1. Teil v2.2:
https://www.eq-3.com/Downloads/eq3/down ... g_V2.2.pdf

Gesperrt

Zurück zu „RaspberryMatic“