Watchdog Alarm 'rfd restarted'

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

Moderatoren: jmaus, Co-Administratoren

scorpionking
Beiträge: 157
Registriert: 14.02.2016, 12:32

Re: Watchdog Alarm 'rfd restarted'

Beitrag von scorpionking » 30.04.2019, 11:02

Heute Nacht war's wieder soweit (ich habe den Monit für rfd wieder aktiviert, sonst bekomm ich das ja u.U. gar nicht mit).

Genaue Uhrzeit des Alarms: 2019-04-30 03:04:52

Log zu diesem Zeitpunkt:

Code: Alles auswählen

Apr 30 03:03:28 192.168.1.220 rfd: Event: NEQ0119269:1.BRIGHTNESS=7
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:28 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:34 192.168.1.220 multimac: C<: #116 TRX GetDutyCycle
Apr 30 03:03:34 192.168.1.220 multimac: C< @569846560: bin:FD 00 03 01 74 03 20 18
Apr 30 03:03:34 192.168.1.220 multimac: C> @569846661: #116 TRX Response Ack 02
Apr 30 03:03:34 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:03:44 192.168.1.220 multimac: C<: #117 TRX GetDutyCycle
Apr 30 03:03:44 192.168.1.220 multimac: C< @569856560: bin:FD 00 03 01 75 03 A6 1B
Apr 30 03:03:44 192.168.1.220 multimac: C> @569856662: #117 TRX Response Ack 02
Apr 30 03:03:44 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:03:46 192.168.1.220 multimac: C> @569858894: #254 LLMAC RX @28405ms -45dBm 27 86 53 40 42 C1 00 00 00 00 41 00 49 42 00 4D 43 FF FC 44 00 04
Apr 30 03:03:46 192.168.1.220 multimac: Bidcos RX: #27[BC|Ren|WMup] 4042C1->000000 MeasurementCyclic: 00 41 00 49 42 00 4D 43 FF FC 44 00 04
Apr 30 03:03:46 192.168.1.220 multimac: GetAckActionForIncomingTelegram() ackAction=AckAction_NotForUs, wakeup=None
Apr 30 03:03:46 192.168.1.220 multimac: A<: #238 HmBidcos RxTelegram AuthNone #27[BC|Ren|WMup] 4042C1->000000 MeasurementCyclic: 00 41 00 49 42 00 4D 43 FF FC 44 00 04
Apr 30 03:03:46 192.168.1.220 rfd: RX for MEQ1599449: @1808065728 RSSI=-45dB 0x4042C1 -> 0x000000 Generic [OEQ0306773]:
  CNT=39,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=1,BCAST=1,TYPE=0x53
  DATA = 00 41 00 49 42 00 4D 43 FF FC 44 00 04 
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:1.TEMPERATURE=7.300000
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:2.TEMPERATURE=7.700000
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:3.TEMPERATURE=-0.400000
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:4.TEMPERATURE=0.400000
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:0.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:1.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:2.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:3.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:4.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: Event: MEQ1599449:5.LOWBAT=false
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 10 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 9 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 10 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 9 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 9 events
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:46 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:03:54 192.168.1.220 multimac: C<: #118 TRX GetDutyCycle
Apr 30 03:03:54 192.168.1.220 multimac: C< @569866560: bin:FD 00 03 01 76 03 AC 1B
Apr 30 03:03:54 192.168.1.220 multimac: C> @569866662: #118 TRX Response Ack 02
Apr 30 03:03:54 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:03:54 192.168.1.220 multimac: C> @569866710: #255 LLMAC RX @ 3523ms -61dBm 9C 86 5A 64 60 A7 00 00 00 88 BC 30
Apr 30 03:03:54 192.168.1.220 multimac: Bidcos RX: #9C[BC|Ren|WMup] 6460A7->000000 HvacTemperatureInfo: 88 BC 30
Apr 30 03:03:54 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:03:54 192.168.1.220 multimac: A<: #241 HmBidcos RxTelegram AuthNone #9C[BC|Ren|WMup] 6460A7->000000 HvacTemperatureInfo: 88 BC 30
Apr 30 03:04:01 192.168.1.220 multimac: C> @569873723: #114 HMIP CMD=07  4C 12 00 83 62 D0 E4 F0 00 01 00 09 60 D6 AA EB 39 44 88 40
Apr 30 03:04:01 192.168.1.220 multimac: A<: #4 HMIP CMD=07  4C 12 00 83 62 D0 E4 F0 00 01 00 09 60 D6 AA EB 39 44 88 40
Apr 30 03:04:04 192.168.1.220 multimac: C<: #119 TRX GetDutyCycle
Apr 30 03:04:04 192.168.1.220 multimac: C< @569876560: bin:FD 00 03 01 77 03 2A 18
Apr 30 03:04:04 192.168.1.220 multimac: C> @569876661: #119 TRX Response Ack 02
Apr 30 03:04:04 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:04:07 192.168.1.220 root: check_mk_agent - connection accepted from 192.168.1.4:38984
Apr 30 03:04:07 192.168.1.220 multimac: A>: #217 HmSystem DutyCycleRequest 
Apr 30 03:04:07 192.168.1.220 multimac: A<: #217 HmSystem Response 02 02
Apr 30 03:04:10 192.168.1.220 cuxd[653]: sendbinrpc(192.168.0.:2067) error resolving hostname!
Apr 30 03:04:11 192.168.1.220 multimac: C> @569883367: #0 LLMAC RX @20320ms -76dBm CA A2 70 A5 A5 01 00 FF FF 00 41 27 ED 5E 00 00 00 00 00 0A E0
Apr 30 03:04:11 192.168.1.220 multimac: Bidcos RX: #CA[BiDi|Ren|WMup] A5A501->00FFFF WeatherData: 00 41 27 ED 5E 00 00 00 00 00 0A E0
Apr 30 03:04:11 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:11 192.168.1.220 multimac: A<: #244 HmBidcos RxTelegram AuthNone #CA[BiDi|Ren|WMup] A5A501->00FFFF WeatherData: 00 41 27 ED 5E 00 00 00 00 00 0A E0
Apr 30 03:04:11 192.168.1.220 multimac: C> @569883485: #1 LLMAC RX @20440ms -63dBm CA 80 02 00 FF FF A5 A5 01 00
Apr 30 03:04:11 192.168.1.220 multimac: Bidcos RX: #CA[Ren] 00FFFF->A5A501 Ack: 00
Apr 30 03:04:11 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:11 192.168.1.220 multimac: A<: #246 HmBidcos RxTelegram AuthNone #CA[Ren] 00FFFF->A5A501 Ack: 00
Apr 30 03:04:13 192.168.1.220 multimac: C> @569885935: #2 LLMAC RX @22909ms -71dBm 72 84 5E 37 05 D6 00 00 00 90 BD 53 00 00 02 00 00 09 25 FD
Apr 30 03:04:13 192.168.1.220 multimac: Bidcos RX: #72[BC|Ren] 3705D6->000000 EnergyCyclic: 90 BD 53 00 00 02 00 00 09 25 FD
Apr 30 03:04:13 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:13 192.168.1.220 multimac: A<: #248 HmBidcos RxTelegram AuthNone #72[BC|Ren] 3705D6->000000 EnergyCyclic: 90 BD 53 00 00 02 00 00 09 25 FD
Apr 30 03:04:13 192.168.1.220 rfd: RX for MEQ0273230: @1808092769 RSSI=-50dB 0x3705D6 -> 0x000000 Generic [NEQ0219037]:
  CNT=114,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x5E
  DATA = 90 BD 53 00 00 02 00 00 09 25 FD 
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.BOOT=true
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.ENERGY_COUNTER=109704.300000
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.POWER=0.020000
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.CURRENT=0.000000
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.VOLTAGE=234.100000
Apr 30 03:04:13 192.168.1.220 rfd: Event: MEQ0273230:2.FREQUENCY=49.970000
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:13 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:14 192.168.1.220 multimac: C<: #120 TRX GetDutyCycle
Apr 30 03:04:14 192.168.1.220 multimac: C< @569886560: bin:FD 00 03 01 78 03 08 18
Apr 30 03:04:14 192.168.1.220 multimac: C> @569886661: #120 TRX Response Ack 02
Apr 30 03:04:14 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:04:14 192.168.1.220 multimac: C> @569886710: #3 LLMAC RX @23692ms -52dBm 9C 84 70 64 60 A7 00 00 00 00 BC 30
Apr 30 03:04:14 192.168.1.220 multimac: Bidcos RX: #9C[BC|Ren] 6460A7->000000 WeatherData: 00 BC 30
Apr 30 03:04:14 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:14 192.168.1.220 multimac: A<: #251 HmBidcos RxTelegram AuthNone #9C[BC|Ren] 6460A7->000000 WeatherData: 00 BC 30
Apr 30 03:04:20 192.168.1.220 cuxd[653]: sendbinrpc(host1.mynet.local:2067) error resolving hostname!
Apr 30 03:04:20 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:21 192.168.1.220 multimac: UpstreamCharConnection slave device mmd_bidcos closed
Apr 30 03:04:21 192.168.1.220 kernel: [569893.682908] eq3loop: eq3loop_close_slave() mmd_bidcos
Apr 30 03:04:22 192.168.1.220 monit[1170]: 'rfd' process is not running
Apr 30 03:04:24 192.168.1.220 multimac: C<: #121 TRX GetDutyCycle
Apr 30 03:04:24 192.168.1.220 multimac: C< @569896560: bin:FD 00 03 01 79 03 8E 1B
Apr 30 03:04:24 192.168.1.220 multimac: C> @569896661: #121 TRX Response Ack 02
Apr 30 03:04:24 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:04:29 192.168.1.220 multimac: C> @569901852: #4 LLMAC RX @ 6194ms -86dBm 2D 86 10 36 F0 BD 00 00 00 0A F4 BC 0E 64 40
Apr 30 03:04:29 192.168.1.220 multimac: Bidcos RX: #2D[BC|Ren|WMup] 36F0BD->000000 Info: 0A F4 BC 0E 64 40
Apr 30 03:04:29 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:30 192.168.1.220 monit[1170]: 'rfd' process is not running
Apr 30 03:04:34 192.168.1.220 multimac: C<: #122 TRX GetDutyCycle
Apr 30 03:04:34 192.168.1.220 multimac: C< @569906561: bin:FD 00 03 01 7A 03 84 1B
Apr 30 03:04:34 192.168.1.220 multimac: C> @569906563: #122 TRX Response Ack 02
Apr 30 03:04:34 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:04:38 192.168.1.220 monit[1170]: 'rfd' process is not running
Apr 30 03:04:38 192.168.1.220 monit[1170]: 'rfd' trying to restart
Apr 30 03:04:38 192.168.1.220 monit[1170]: 'rfd' restart: '/etc/init.d/S61rfd restart'
Apr 30 03:04:38 192.168.1.220 rfd: BidCoS-Service started
Apr 30 03:04:38 192.168.1.220 rfd: XmlRpc Server is listening on TCP port 32001
Apr 30 03:04:38 192.168.1.220 multimac: UpstreamCharConnection slave device mmd_bidcos opened
Apr 30 03:04:38 192.168.1.220 multimac: A<: #0 HmSystem Identify Co_CPU_App
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::init() - Improved initialization.
Apr 30 03:04:38 192.168.1.220 multimac: A>: #0 HmSystem Identify 
Apr 30 03:04:38 192.168.1.220 multimac: A<: #0 HmSystem Response 02 43 6F 5F 43 50 55 5F 41 70 70
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::improvedInit() - Coprocessor is in application.
Apr 30 03:04:38 192.168.1.220 kernel: [569910.529565] eq3loop: eq3loop_open_slave() mmd_bidcos
Apr 30 03:04:38 192.168.1.220 multimac: A>: #1 HmSystem VersionRequest 
Apr 30 03:04:38 192.168.1.220 multimac: A<: #1 HmSystem Response 02 01 00 03 02 08 06
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.3
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 2.8.6
Apr 30 03:04:38 192.168.1.220 multimac: A>: #2 HmSystem CsmaCaControl 00
Apr 30 03:04:38 192.168.1.220 multimac: CSMA/CD off
Apr 30 03:04:38 192.168.1.220 multimac: A<: #2 HmSystem Response 01
Apr 30 03:04:38 192.168.1.220 rfd: () CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Apr 30 03:04:38 192.168.1.220 multimac: A>: #3 HmSystem GetSerialNumber 
Apr 30 03:04:38 192.168.1.220 multimac: A<: #3 HmSystem Response 02 4F 45 51 30 33 30 36 37 37 33
Apr 30 03:04:38 192.168.1.220 multimac: A>: #4 HmBidcos SetTime 5C C7 9F 26 04
Apr 30 03:04:38 192.168.1.220 multimac: Time 1556586278 +02:00
Apr 30 03:04:38 192.168.1.220 multimac: A<: #4 HmSystem Response 01
Apr 30 03:04:38 192.168.1.220 rfd: Default interface is now OEQ0306773
Apr 30 03:04:38 192.168.1.220 rfd: Lan Device Information:
Protocol-Version: 1
Product-ID: eQ3-HM-LGW
Firmware-Version: 1.1.5
Serial Number: NEQ0219037
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::init() - Improved initialization.
Apr 30 03:04:38 192.168.1.220 rfd: Lan Device Information:
Protocol-Version: 1
Product-ID: eQ3-HM-LGW
Firmware-Version: 1.1.5
Serial Number: NEQ0219037
Apr 30 03:04:38 192.168.1.220 rfd: CCU2CommController::improvedInit() - Coprocessor is in application.
Apr 30 03:04:38 192.168.1.220 rfd: Switching RF-LGW LED OFF
Apr 30 03:04:39 192.168.1.220 rfd: CCU2CommController::init(): Coprocessor Bootloader Version is: 1.0.4
Apr 30 03:04:39 192.168.1.220 rfd: CCU2CommController::init(): Coprocessor Firmware Version is: 1.4.1
Apr 30 03:04:39 192.168.1.220 rfd: (NEQ0219037) CCU2CommController::setCSMACAEnabled(): CSMA/CA disabled.
Apr 30 03:04:39 192.168.1.220 rfd: Current AES key=2, previous AES key=1
Apr 30 03:04:39 192.168.1.220 rfd: (NEQ0219037) Response status: OK.
Apr 30 03:04:39 192.168.1.220 rfd: (NEQ0219037) Response status: OK.
Apr 30 03:04:39 192.168.1.220 multimac: A>: #11 HmBidcos SetAesKey.cur (2) EF CC EF C9 74 39 A4 CB E8 62 73 E7 CF E8 FC 18
Apr 30 03:04:39 192.168.1.220 multimac: A<: #11 HmBidcos Response 01
Apr 30 03:04:39 192.168.1.220 rfd: (OEQ0306773) Response status: OK.
Apr 30 03:04:39 192.168.1.220 multimac: A>: #12 HmBidcos SetAesKey.prv (1) E2 2C 6C 95 B6 30 1E AF 34 95 A4 21 88 A7 8B 7A
Apr 30 03:04:39 192.168.1.220 multimac: A<: #12 HmBidcos Response 01
Apr 30 03:04:39 192.168.1.220 rfd: (OEQ0306773) Response status: OK.
Apr 30 03:04:39 192.168.1.220 rfd: CCU2BidcosRemoteInterface::StartInterface(): addr=21 61 be 
Apr 30 03:04:39 192.168.1.220 rfd: (NEQ0219037) Response status: OK.
Apr 30 03:04:39 192.168.1.220 rfd: CCU2BidcosRemoteInterface::StartInterface(): addr=21 61 be 
Apr 30 03:04:39 192.168.1.220 multimac: A>: #14 HmBidcos SetRfAddress 21 61 BE
Apr 30 03:04:39 192.168.1.220 multimac: A<: #14 HmBidcos Response 01
Apr 30 03:04:39 192.168.1.220 rfd: (OEQ0306773) Response status: OK.
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-senact-8-8-sc-bat.xml loaded (1)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_bl_conf_644_e_v2_0.xml loaded (2)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_pb-2-wm55_le_v1_3.xml loaded (3)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-ibut-8.xml loaded (4)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-lc-sw12-fm.xml loaded (5)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_1t_fm_lf.xml loaded (6)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_ks550.xml loaded (7)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s_1conf_644_le_v2_3.xml loaded (8)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_cfm_tw.xml loaded (9)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_bl_644.xml loaded (10)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sci_3.xml loaded (11)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sec_sd.xml loaded (12)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_es_tx_wm.xml loaded (13)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-sen-lev-tof.xml loaded (14)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rc_19.xml loaded (15)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-sen-wea_e_v13.xml loaded (16)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s_4_ba.xml loaded (17)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sen_db.xml loaded (18)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s_ba.xml loaded (19)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_2l_644.xml loaded (20)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_es_tx_wm_le_v1_0.xml loaded (21)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sc.xml loaded (22)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rc-4-2.xml loaded (23)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s_le_v1_5.xml loaded (24)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_bl.xml loaded (25)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_cc_rt_dn.xml loaded (26)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rc.xml loaded (27)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_d_le_v1_9.xml loaded (28)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-senact-8-8-rc.xml loaded (29)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sec_mdir.xml loaded (30)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_fs_ba.xml loaded (31)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_ws550.xml loaded (32)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_wds_v1_0.xml loaded (33)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s550ia.xml loaded (34)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_4dis.xml loaded (35)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_pb-2.xml loaded (36)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s_2conf_644.xml loaded (37)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sc_e_v1_7.xml loaded (38)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_1l_644_le_v2_4.xml loaded (39)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-sen-wea_ge_v14.xml loaded (40)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_oligo_smart_iq.xml loaded (41)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sen_wa_od.xml loaded (42)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-sen-wea_e_v12.xml loaded (43)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_wds_v1_1.xml loaded (44)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sen_mdir_wm55.xml loaded (45)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sec_mdir_v1_5.xml loaded (46)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_1tconf_644_le_v2_4.xml loaded (47)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_bl_conf_644_e_v2_1.xml loaded (48)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rhs_e_v1_7.xml loaded (49)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_cf.xml loaded (50)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_resc_win_pcb_sc.xml loaded (51)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rep.xml loaded (52)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dis_wm55.xml loaded (53)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_hm-wds100-c6-o-2.xml loaded (54)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-sen-cap-moist.xml loaded (55)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_wds30_ot2.xml loaded (56)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_s.xml loaded (57)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-uni-dmx-master_le_v10.xml loaded (58)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_cc_rt_dn_bom.xml loaded (59)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_1pwm_644_le_v2_4.xml loaded (60)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sen_mdir.xml loaded (61)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_rc_2_fm.xml loaded (62)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_t_le_v1_9.xml loaded (63)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_sec_sco.xml loaded (64)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_roto_wdf_solar.xml loaded (65)
Apr 30 03:04:39 192.168.1.220 rfd: Device description rf_dim_t.xml loaded (66)
Apr 30 03:04:39 192.168.1.220 rfd: Device description hb-dis-ep-42bw_e_v1_0.xml loaded (67)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-lc-bl1pbu-fm.xml loaded (68)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-dist-tof.xml loaded (69)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_pb-2-wm55_ge_v1_4.xml loaded (70)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_1t_dr.xml loaded (71)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rc-4-3_single_on.xml loaded (72)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-volt.xml loaded (73)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_swi.xml loaded (74)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dw.xml loaded (75)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rd_le_v1_3.xml loaded (76)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_1pwm_644.xml loaded (77)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_s_1conf_644.xml loaded (78)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_s_mega168.xml loaded (79)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_es_pmsw.xml loaded (80)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_tis.xml loaded (81)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rc_dis.xml loaded (82)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_ja_conf_644.xml loaded (83)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-8-8-rc-bat.xml loaded (84)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_2l_644_le_v2_4.xml loaded (85)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_central.xml loaded (86)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-temp.xml loaded (87)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-lev-us.xml loaded (88)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_s_644.xml loaded (89)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_winmatic.xml loaded (90)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_scd_v1_0.xml loaded (91)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-4-4-rc-bat.xml loaded (92)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dis_ep_wm55_le_v1_0.xml loaded (93)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_d.xml loaded (94)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-lc-sw1pbu-fm.xml loaded (95)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-8-8-sc.xml loaded (96)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rhs_le_v1_6.xml loaded (97)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_sec_sd_2.xml loaded (98)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_s_8_ba.xml loaded (99)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_sen_mdir_v1_5.xml loaded (100)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-4-4-rc.xml loaded (101)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_2t_644.xml loaded (102)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_bl_le_v2_3.xml loaded (103)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rd.xml loaded (104)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rc_single_on.xml loaded (105)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_1t_644.xml loaded (106)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_ddc.xml loaded (107)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rhs.xml loaded (108)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rgbw.xml loaded (109)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-press-sc.xml loaded (110)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_1tconf_644.xml loaded (111)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-wea_le_v10.xml loaded (112)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_cm.xml loaded (113)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_wds40_th_i_2.xml loaded (114)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_em_8.xml loaded (115)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_sec_sir_wm.xml loaded (116)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_ou_led16_le_v1_0.xml loaded (117)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_s_1conf_644_le_v2_1.xml loaded (118)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-rfid-rc.xml loaded (119)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_cc_tc.xml loaded (120)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_2t_644_le_v2_4.xml loaded (121)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_rc-sec4-2.xml loaded (122)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-4-4-sc.xml loaded (123)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_d_le_v1_7.xml loaded (124)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-weight.xml loaded (125)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_dim_2pwm.xml loaded (126)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_tis_le_v1_0.xml loaded (127)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_keymatic.xml loaded (128)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-sen-temp-ir.xml loaded (129)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_ao.xml loaded (130)
Apr 30 03:04:40 192.168.1.220 rfd: Device description hb-uni-senact-4-4-sc-bat.xml loaded (131)
Apr 30 03:04:40 192.168.1.220 rfd: Device description rf_sen_ep.xml loaded (132)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_bl_conf_644.xml loaded (133)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_sec_sd_schueco.xml loaded (134)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-sen-press.xml loaded (135)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_em_8_bit.xml loaded (136)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_sc_le_v1_6.xml loaded (137)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_tc_it_wm-w-eu.xml loaded (138)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_ou_led16_ge_v1_1.xml loaded (139)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-sen-iaq.xml loaded (140)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_ash550.xml loaded (141)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_es_pmsw_le_v2_4.xml loaded (142)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-lc-sw2-fm.xml loaded (143)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_rc_12.xml loaded (144)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-sen-dist-us.xml loaded (145)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_sec_sfa.xml loaded (146)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_cc_tc_le_v1_9.xml loaded (147)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-rgb-led-ctrl.xml loaded (148)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_st_6_sh.xml loaded (149)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_cmm.xml loaded (150)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_dis_ep_wm55.xml loaded (151)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_cc_vd.xml loaded (152)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_cfm.xml loaded (153)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-sen-dummy-beacon.xml loaded (154)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-uni-sen-wea.xml loaded (155)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_sen_li.xml loaded (156)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_dim_1l_644.xml loaded (157)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_s_le_v2_3.xml loaded (158)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_dim_1t_644_le_v2_4.xml loaded (159)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-lc-sw2pbu-fm.xml loaded (160)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_rc-key4-2.xml loaded (161)
Apr 30 03:04:41 192.168.1.220 rfd: Device description rf_pbi.xml loaded (162)
Apr 30 03:04:41 192.168.1.220 rfd: Device description hb-ou-mp3-led.xml loaded (163)
Apr 30 03:04:41 192.168.1.220 rfd: Team created: 0x44EC03
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0061432:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0061432
Apr 30 03:04:41 192.168.1.220 multimac: A>: #19 HmBidcos PeerAdd 6481D9 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #19 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #20 HmBidcos PeerAdd 6481D9 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #20 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #21 HmBidcos PeerAdd 6481D9 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #21 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: OEQ2081655:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #22 HmBidcos PeerAdd 6481D9 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #22 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: OEQ2081655
Apr 30 03:04:41 192.168.1.220 multimac: A>: #23 HmBidcos PeerAdd 1E3CF7 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #23 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #24 HmBidcos PeerAdd 1E3CF7 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #24 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #25 HmBidcos PeerAdd 1E3CF7 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #25 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: KEQ0038645:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #26 HmBidcos PeerAdd 1E3CF7 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #26 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: KEQ0038645
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: LEQ1321187:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: LEQ1321187
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0119269:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0119269
Apr 30 03:04:41 192.168.1.220 multimac: A>: #36 HmBidcos PeerAdd 44ECBB key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #36 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #37 HmBidcos PeerAdd 44ECBB key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #37 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #38 HmBidcos PeerAdd 44ECBB key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #38 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0059450:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #39 HmBidcos PeerAdd 44ECBB key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #39 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0059450
Apr 30 03:04:41 192.168.1.220 multimac: A>: #40 HmBidcos PeerAdd 482476 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #40 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #41 HmBidcos PeerAdd 482476 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #41 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #42 HmBidcos PeerAdd 482476 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #42 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0366214:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #43 HmBidcos PeerAdd 482476 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #43 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0366214
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0365480:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0365480
Apr 30 03:04:41 192.168.1.220 multimac: A>: #48 HmBidcos PeerAdd 1AE1D2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #48 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #49 HmBidcos PeerAdd 1AE1D2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #49 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #50 HmBidcos PeerAdd 1AE1D2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #50 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: JEQ0094972:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #51 HmBidcos PeerAdd 1AE1D2 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #51 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: JEQ0094972
Apr 30 03:04:41 192.168.1.220 multimac: A>: #52 HmBidcos PeerAdd 8141FF key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #52 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #53 HmBidcos PeerAdd 8141FF key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #53 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #54 HmBidcos PeerAdd 8141FF key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #54 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MKRGB99999:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #55 HmBidcos PeerAdd 8141FF key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #55 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MKRGB99999
Apr 30 03:04:41 192.168.1.220 multimac: A>: #56 HmBidcos PeerAdd 433D40 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #56 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #57 HmBidcos PeerAdd 433D40 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #57 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #58 HmBidcos PeerAdd 433D40 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #58 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MEQ0758883:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #59 HmBidcos PeerAdd 433D40 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #59 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MEQ0758883
Apr 30 03:04:41 192.168.1.220 multimac: A>: #60 HmBidcos PeerAdd 16B22A key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #60 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #61 HmBidcos PeerAdd 16B22A key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #61 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #62 HmBidcos PeerAdd 16B22A key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #62 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: IEQ0100612:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #63 HmBidcos PeerAdd 16B22A key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #63 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: IEQ0100612
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MKRGB00002:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MKRGB00002
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: LEQ0099162:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: LEQ0099162
Apr 30 03:04:41 192.168.1.220 multimac: A>: #73 HmBidcos PeerAdd 66AE66 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #73 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #74 HmBidcos PeerAdd 66AE66 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #74 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #75 HmBidcos PeerAdd 66AE66 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #75 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: PEQ0157347:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #76 HmBidcos PeerAdd 66AE66 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #76 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: PEQ0157347
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0256828:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0256828
Apr 30 03:04:41 192.168.1.220 multimac: A>: #81 HmBidcos PeerAdd 1532A2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #81 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #82 HmBidcos PeerAdd 1532A2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #82 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #83 HmBidcos PeerAdd 1532A2 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #83 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: IEQ0026468:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #84 HmBidcos PeerAdd 1532A2 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #84 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: IEQ0026468
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MEQ0276407:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MEQ0276407
Apr 30 03:04:41 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD-Team 
Apr 30 03:04:41 192.168.1.220 rfd: Serial Number *NEQ0059266 assigned to team 0x44EC03
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0059266:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0059266
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MEQ1006858:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MEQ1006858
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: NEQ0059474:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: NEQ0059474
Apr 30 03:04:41 192.168.1.220 multimac: A>: #101 HmBidcos PeerAdd 3E08C8 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #101 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #102 HmBidcos PeerAdd 3E08C8 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #102 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #103 HmBidcos PeerAdd 3E08C8 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #103 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MEQ0676758:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #104 HmBidcos PeerAdd 3E08C8 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #104 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MEQ0676758
Apr 30 03:04:41 192.168.1.220 multimac: A>: #105 HmBidcos PeerAdd 1B7827 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #105 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #106 HmBidcos PeerAdd 1B7827 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #106 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #107 HmBidcos PeerAdd 1B7827 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #107 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: JEQ0100142:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #108 HmBidcos PeerAdd 1B7827 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #108 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: JEQ0100142
Apr 30 03:04:41 192.168.1.220 multimac: A>: #109 HmBidcos PeerAdd 1B738B key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #109 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #110 HmBidcos PeerAdd 1B738B key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #110 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #111 HmBidcos PeerAdd 1B738B key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #111 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: JEQ0100807:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #112 HmBidcos PeerAdd 1B738B key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #112 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: JEQ0100807
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: KEQ0170511:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: KEQ0170511
Apr 30 03:04:41 192.168.1.220 multimac: A>: #117 HmBidcos PeerAdd 36DF20 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #117 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #118 HmBidcos PeerAdd 36DF20 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #118 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 multimac: A>: #119 HmBidcos PeerAdd 36DF20 key=0 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #119 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: MEQ0276674:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 multimac: A>: #120 HmBidcos PeerAdd 36DF20 key=2 
Apr 30 03:04:41 192.168.1.220 multimac: A<: #120 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:41 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: MEQ0276674
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Event: JEQ0088773:0.CONFIG_PENDING=false
Apr 30 03:04:41 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:41 192.168.1.220 rfd: Device created: JEQ0088773
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674857:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674857
Apr 30 03:04:42 192.168.1.220 multimac: A>: #129 HmBidcos PeerAdd 44EBD8 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #129 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #130 HmBidcos PeerAdd 44EBD8 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #130 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #131 HmBidcos PeerAdd 44EBD8 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #131 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0059223:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #132 HmBidcos PeerAdd 44EBD8 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #132 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0059223
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0236907:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0236907
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ1006797:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ1006797
Apr 30 03:04:42 192.168.1.220 multimac: A>: #141 HmBidcos PeerAdd 3DB4E2 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #141 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #142 HmBidcos PeerAdd 3DB4E2 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #142 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #143 HmBidcos PeerAdd 3DB4E2 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #143 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674925:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #144 HmBidcos PeerAdd 3DB4E2 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #144 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674925
Apr 30 03:04:42 192.168.1.220 multimac: A>: #145 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #145 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #146 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #146 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #147 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #147 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #148 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #148 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ1599449:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #149 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #149 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ1599449
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0038034:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0038034
Apr 30 03:04:42 192.168.1.220 multimac: A>: #154 HmBidcos PeerAdd 480A70 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #154 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #155 HmBidcos PeerAdd 480A70 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #155 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #156 HmBidcos PeerAdd 480A70 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #156 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0256753:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #157 HmBidcos PeerAdd 480A70 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #157 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0256753
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0269838:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0269838
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: OEQ0293535:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: OEQ0293535
Apr 30 03:04:42 192.168.1.220 multimac: A>: #166 HmBidcos PeerAdd 3E08D5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #166 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #167 HmBidcos PeerAdd 3E08D5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #167 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #168 HmBidcos PeerAdd 3E08D5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #168 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0676794:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #169 HmBidcos PeerAdd 3E08D5 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #169 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0676794
Apr 30 03:04:42 192.168.1.220 multimac: A>: #170 HmBidcos PeerAdd 451ECD key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #170 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #171 HmBidcos PeerAdd 451ECD key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #171 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #172 HmBidcos PeerAdd 451ECD key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #172 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0058354:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #173 HmBidcos PeerAdd 451ECD key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #173 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0058354
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: IEQ0048375:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: IEQ0048375
Apr 30 03:04:42 192.168.1.220 multimac: A>: #178 HmBidcos PeerAdd 1B7836 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #178 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #179 HmBidcos PeerAdd 1B7836 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #179 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #180 HmBidcos PeerAdd 1B7836 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #180 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0100155:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #181 HmBidcos PeerAdd 1B7836 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #181 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0100155
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ1844608:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ1844608
Apr 30 03:04:42 192.168.1.220 multimac: A>: #186 HmBidcos PeerAdd 1E3CF5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #186 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #187 HmBidcos PeerAdd 1E3CF5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #187 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #188 HmBidcos PeerAdd 1E3CF5 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #188 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0038647:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #189 HmBidcos PeerAdd 1E3CF5 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #189 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0038647
Apr 30 03:04:42 192.168.1.220 multimac: A>: #190 HmBidcos PeerAdd 4482C9 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #190 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #191 HmBidcos PeerAdd 4482C9 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #191 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #192 HmBidcos PeerAdd 4482C9 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #192 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #193 HmBidcos PeerAdd 4482C9 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #193 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0119355:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #194 HmBidcos PeerAdd 4482C9 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #194 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0119355
Apr 30 03:04:42 192.168.1.220 multimac: A>: #195 HmBidcos PeerAdd 226BEC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #195 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #196 HmBidcos PeerAdd 226BEC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #196 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #197 HmBidcos PeerAdd 226BEC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #197 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #198 HmBidcos PeerAdd 226BEC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #198 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0362130:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #199 HmBidcos PeerAdd 226BEC key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #199 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0362130
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MKRGB00001:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MKRGB00001
Apr 30 03:04:42 192.168.1.220 multimac: A>: #204 HmBidcos PeerAdd 225F5A key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #204 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #205 HmBidcos PeerAdd 225F5A key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #205 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #206 HmBidcos PeerAdd 225F5A key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #206 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0433332:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #207 HmBidcos PeerAdd 225F5A key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #207 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0433332
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674912:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674912
Apr 30 03:04:42 192.168.1.220 multimac: A>: #212 HmBidcos PeerAdd 1BEEEA key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #212 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #213 HmBidcos PeerAdd 1BEEEA key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #213 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #214 HmBidcos PeerAdd 1BEEEA key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #214 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0461906:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #215 HmBidcos PeerAdd 1BEEEA key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #215 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0461906
Apr 30 03:04:42 192.168.1.220 multimac: A>: #216 HmBidcos PeerAdd 1AE1B3 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #216 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #217 HmBidcos PeerAdd 1AE1B3 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #217 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #218 HmBidcos PeerAdd 1AE1B3 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #218 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0095004:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #219 HmBidcos PeerAdd 1AE1B3 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #219 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0095004
Apr 30 03:04:42 192.168.1.220 multimac: A>: #220 HmBidcos PeerAdd 1BE852 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #220 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #221 HmBidcos PeerAdd 1BE852 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #221 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #222 HmBidcos PeerAdd 1BE852 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #222 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0464840:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #223 HmBidcos PeerAdd 1BE852 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #223 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0464840
Apr 30 03:04:42 192.168.1.220 multimac: A>: #224 HmBidcos PeerAdd 482727 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #224 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #225 HmBidcos PeerAdd 482727 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #225 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #226 HmBidcos PeerAdd 482727 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #226 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0365516:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #227 HmBidcos PeerAdd 482727 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #227 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0365516
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: OEQ0293458:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: OEQ0293458
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: LEQ0099077:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: LEQ0099077
Apr 30 03:04:42 192.168.1.220 multimac: A>: #237 HmBidcos PeerAdd 1DDE35 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #237 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #238 HmBidcos PeerAdd 1DDE35 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #238 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #239 HmBidcos PeerAdd 1DDE35 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #239 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0653882:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #240 HmBidcos PeerAdd 1DDE35 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #240 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0653882
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: OEQ0293476:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: OEQ0293476
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0206014:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0206014
Apr 30 03:04:42 192.168.1.220 rfd: Device created: BidCoS-RF
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674909:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674909
Apr 30 03:04:42 192.168.1.220 multimac: A>: #254 HmBidcos PeerAdd 3DB4CC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #254 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #255 HmBidcos PeerAdd 3DB4CC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #255 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #0 HmBidcos PeerAdd 3DB4CC key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #0 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674907:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #1 HmBidcos PeerAdd 3DB4CC key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #1 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674907
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: OEQ0293451:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: OEQ0293451
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0674923:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0674923
Apr 30 03:04:42 192.168.1.220 multimac: A>: #10 HmBidcos PeerAdd 3F0D2C key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #10 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #11 HmBidcos PeerAdd 3F0D2C key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #11 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #12 HmBidcos PeerAdd 3F0D2C key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #12 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0819552:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #13 HmBidcos PeerAdd 3F0D2C key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #13 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0819552
Apr 30 03:04:42 192.168.1.220 multimac: A>: #14 HmBidcos PeerAdd 41CF77 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #14 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #15 HmBidcos PeerAdd 41CF77 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #15 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #16 HmBidcos PeerAdd 41CF77 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #16 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ1006589:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #17 HmBidcos PeerAdd 41CF77 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #17 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ1006589
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: KEQ0943754:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: KEQ0943754
Apr 30 03:04:42 192.168.1.220 multimac: A>: #22 HmBidcos PeerAdd 1B0278 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #22 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #23 HmBidcos PeerAdd 1B0278 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #23 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #24 HmBidcos PeerAdd 1B0278 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #24 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: JEQ0095864:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #25 HmBidcos PeerAdd 1B0278 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #25 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: JEQ0095864
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0675135:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0675135
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: MEQ0273230:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: MEQ0273230
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: LEQ1321553:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: LEQ1321553
Apr 30 03:04:42 192.168.1.220 multimac: A>: #38 HmBidcos PeerAdd 448239 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #38 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #39 HmBidcos PeerAdd 448239 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #39 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #40 HmBidcos PeerAdd 448239 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #40 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 multimac: A>: #41 HmBidcos PeerAdd 448239 key=0 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #41 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Event: NEQ0119495:0.CONFIG_PENDING=false
Apr 30 03:04:42 192.168.1.220 multimac: A>: #42 HmBidcos PeerAdd 448239 key=2 
Apr 30 03:04:42 192.168.1.220 multimac: A<: #42 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:42 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:42 192.168.1.220 rfd: Device created: NEQ0119495
Apr 30 03:04:42 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: Event: MEQ0674905:0.CONFIG_PENDING=false
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: Device created: MEQ0674905
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: Event: MEQ0269842:0.CONFIG_PENDING=false
Apr 30 03:04:43 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:43 192.168.1.220 rfd: Device created: MEQ0269842
Apr 30 03:04:43 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support system.methodHelp
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support system.multicall
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support updateDevice
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support deleteDevices
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support newDevices
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support firmwareUpdateStatusChanged
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support replaceDevice
Apr 30 03:04:43 192.168.1.220 rfd: yes support replace device
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support readdedDevice
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support system.listMethods
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support event
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF_java support listDevices
Apr 30 03:04:43 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support event
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support listDevices
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support newDevices
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support deleteDevices
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support updateDevice
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support system.multicall
Apr 30 03:04:43 192.168.1.220 rfd: BidCos-RF support system.listMethods
Apr 30 03:04:43 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support system.listMethods
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support setReadyConfig
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support updateDevice
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support replaceDevice
Apr 30 03:04:43 192.168.1.220 rfd: yes support replace device
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support readdedDevice
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support newDevices
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support deleteDevices
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support listDevices
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support event
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support eventSingle
Apr 30 03:04:43 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support system.multicall
Apr 30 03:04:43 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support deleteDevices
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support event
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support listDevices
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support newDevices
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support replaceDevice
Apr 30 03:04:43 192.168.1.220 rfd: yes support replace device
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support reportValueUsage
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support setReadyConfig
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support system.listMethods
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support system.methodHelp
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support updateDevice
Apr 30 03:04:43 192.168.1.220 rfd: 1007 support system.multicall
Apr 30 03:04:43 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:43 192.168.1.220 rfd: rcux support system.listMethods
Apr 30 03:04:43 192.168.1.220 rfd: rcux support system.methodHelp
Apr 30 03:04:43 192.168.1.220 rfd: rcux support system.multicall
Apr 30 03:04:43 192.168.1.220 rfd: rcux support init
Apr 30 03:04:43 192.168.1.220 rfd: rcux support listDevices
Apr 30 03:04:43 192.168.1.220 rfd: rcux support deleteDevice
Apr 30 03:04:43 192.168.1.220 rfd: rcux support getDeviceDescription
Apr 30 03:04:43 192.168.1.220 rfd: rcux support getParamsetDescription
Apr 30 03:04:43 192.168.1.220 rfd: rcux support getParamset
Apr 30 03:04:43 192.168.1.220 rfd: rcux support putParamset
Apr 30 03:04:43 192.168.1.220 rfd: rcux support getValue
Apr 30 03:04:43 192.168.1.220 rfd: rcux support setValue
Apr 30 03:04:43 192.168.1.220 rfd: rcux support reportValueUsage
Apr 30 03:04:43 192.168.1.220 rfd: rcux support listReplaceableDevices
Apr 30 03:04:43 192.168.1.220 rfd: rcux support ping
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0061432
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0059450
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0059266
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0059474
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0059223
Apr 30 03:04:43 192.168.1.220 rfd: Saving device NEQ0058354
Apr 30 03:04:44 192.168.1.220 multimac: C<: #123 TRX GetDutyCycle
Apr 30 03:04:44 192.168.1.220 multimac: C< @569916561: bin:FD 00 03 01 7B 03 02 18
Apr 30 03:04:44 192.168.1.220 multimac: C> @569916564: #123 TRX Response Ack 02
Apr 30 03:04:44 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 1.0 ) = 0
Apr 30 03:04:47 192.168.1.220 multimac: MacController::OnDownstreamFrame(#255 LLMAC TX @32768ms [10k,WOR,NoCCA] 42 94 3F 21 61 BE 00 00 00 02 04 24 5A 5B AF)
Apr 30 03:04:47 192.168.1.220 multimac: C<: #124 LLMAC TX @32768ms [10k,WOR,NoCCA] 42 94 3F 21 61 BE 00 00 00 02 04 24 5A 5B AF
Apr 30 03:04:47 192.168.1.220 multimac: C< @569919373: bin:FD 00 15 03 7C 06 80 00 90 42 94 3F 21 61 BE 00 00 00 02 04 24 5A 5B AF F3 6A
Apr 30 03:04:47 192.168.1.220 multimac: C> @569919758: #124 LLMAC Response ACK @23873: 5D 41
Apr 30 03:04:48 192.168.1.220 multimac: A>: #65 TRX GetDutyCycle
Apr 30 03:04:48 192.168.1.220 multimac: A<: #65 TRX Response Ack 02
Apr 30 03:04:52 192.168.1.220 monit[1170]: 'rfd' service restarted 1 times within 1 cycles(s) - exec
Apr 30 03:04:52 192.168.1.220 monit[1170]: 'rfd' exec: '/bin/triggerAlarm.tcl rfd restarted WatchDog-Alarm'
Apr 30 03:04:52 192.168.1.220 monit[1170]: 'rfd' process is running with pid 27577
Apr 30 03:04:52 192.168.1.220 monit[1170]: 'rfd' process is running after previous restart timeout (manually recovered?)
Apr 30 03:04:53 192.168.1.220 rfd: PlatformInit()
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support system.listMethods
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support setReadyConfig
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support updateDevice
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support replaceDevice
Apr 30 03:04:53 192.168.1.220 rfd: yes support replace device
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support readdedDevice
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support newDevices
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support deleteDevices
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support listDevices
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support event
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support eventSingle
Apr 30 03:04:53 192.168.1.220 rfd: nr_ChZJxC_BidCos-RF support system.multicall
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RCV-50 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw2-PB-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-SM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-PB-4Dis-WM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-19-B 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-4 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Ba-PCB 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-PB-2-WM55 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-WDS10-TH-O 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-WDS10-TH-O 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1T-Pl-3 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1T-Pl-3 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1T-Pl-3 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1T-Pl-3 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-WDS-2 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-ES-PMSw1-Pl 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-DR 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-DR 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-SM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-WDS30-OT2-SM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Sw1-Pl-CT-R1 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HB-UNI-RGB-LED-CTRL 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HB-UNI-RGB-LED-CTRL 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HB-UNI-RGB-LED-CTRL 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sen-MDIR-O 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sen-MDIR-O 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sen-MDIR-O 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-RC-2-PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Bl1PBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1PWM-CV 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1PWM-CV 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-LC-Dim1TPBU-FM 
Apr 30 03:04:53 192.168.1.220 rfd: GetAvailableFirmware for HM-Sec-SD-Team 
Apr 30 03:04:53 192.168.1.220 rfd: Switching RF-LGW LED ON (BLINK FAST)
Apr 30 03:04:53 192.168.1.220 multimac: A>: #51 HmBidcos PeerAdd 226BEC key=2 
Apr 30 03:04:53 192.168.1.220 multimac: A<: #51 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:53 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 multimac: A>: #52 HmBidcos PeerAdd 226BEC key=2 
Apr 30 03:04:53 192.168.1.220 multimac: A<: #52 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:53 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 multimac: A>: #56 HmBidcos PeerAdd 4042C1 key=0 
Apr 30 03:04:53 192.168.1.220 multimac: A<: #56 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:53 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 rfd: (NEQ0219037) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 multimac: A>: #58 HmBidcos PeerAdd 4482C9 key=2 
Apr 30 03:04:53 192.168.1.220 multimac: A<: #58 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:53 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:53 192.168.1.220 multimac: A>: #59 HmBidcos PeerAdd 448239 key=2 
Apr 30 03:04:53 192.168.1.220 multimac: A<: #59 HmBidcos Response 07 00 01 00 23 FF FF FF FF FF FF FF FF
Apr 30 03:04:53 192.168.1.220 rfd: (OEQ0306773) Response status: OK, Data.
Apr 30 03:04:54 192.168.1.220 multimac: C> @569926259: #115 HMIP CMD=07  35 10 00 8E 20 9A B3 B3 BA 13 00 07 63 29 73 91 D5 92 85 CF 00 3D 03 00 1D 06 00 00 0D 01 01 0F 01 00 00
Apr 30 03:04:54 192.168.1.220 multimac: A<: #10 HMIP CMD=07  35 10 00 8E 20 9A B3 B3 BA 13 00 07 63 29 73 91 D5 92 85 CF 00 3D 03 00 1D 06 00 00 0D 01 01 0F 01 00 00
Apr 30 03:04:54 192.168.1.220 multimac: A>: #4 HMIP CMD=03  00 10 00 8E 00 00 00 20 9A B3 02 CF 00
Apr 30 03:04:54 192.168.1.220 multimac: MacController::OnDownstreamFrame(#4 HMIP CMD=03  00 10 00 8E 00 00 00 20 9A B3 02 CF 00)
Apr 30 03:04:54 192.168.1.220 multimac: C<: #125 HMIP CMD=03  00 10 00 8E 00 00 00 20 9A B3 02 CF 00
Apr 30 03:04:54 192.168.1.220 multimac: C< @569926265: bin:FD 00 10 02 7D 03 00 10 00 8E 00 00 00 20 9A B3 02 CF 00 B7 6A
Apr 30 03:04:54 192.168.1.220 multimac: C> @569926444: #125 HMIP CMD=06  01
Apr 30 03:04:54 192.168.1.220 multimac: A<: #4 HMIP CMD=06  01
Apr 30 03:04:54 192.168.1.220 multimac: C<: #126 TRX GetDutyCycle
Apr 30 03:04:54 192.168.1.220 multimac: C< @569926561: bin:FD 00 03 01 7E 03 1C 18
Apr 30 03:04:54 192.168.1.220 multimac: C> @569926662: #126 TRX Response Ack 04
Apr 30 03:04:54 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 1.0, 2.0 ) = 0
Apr 30 03:04:59 192.168.1.220 multimac: C> @569931335: #116 HMIP CMD=07  4B 12 00 83 62 D0 E4 F0 00 01 00 09 60 D7 65 B1 50 76 86
Apr 30 03:04:59 192.168.1.220 multimac: A<: #12 HMIP CMD=07  4B 12 00 83 62 D0 E4 F0 00 01 00 09 60 D7 65 B1 50 76 86
Apr 30 03:04:59 192.168.1.220 multimac: C> @569931452: #5 LLMAC RX @ 3277ms -75dBm C1 84 5E 37 C4 6B 00 00 00 8D 49 BE 00 00 04 00 00 09 26 FD
Apr 30 03:04:59 192.168.1.220 multimac: Bidcos RX: #C1[BC|Ren] 37C46B->000000 EnergyCyclic: 8D 49 BE 00 00 04 00 00 09 26 FD
Apr 30 03:04:59 192.168.1.220 multimac: GetAckActionForIncomingTelegram(): Unknown peer, AckAction_NotForUs
Apr 30 03:04:59 192.168.1.220 multimac: A<: #4 HmBidcos RxTelegram AuthNone #C1[BC|Ren] 37C46B->000000 EnergyCyclic: 8D 49 BE 00 00 04 00 00 09 26 FD
Apr 30 03:04:59 192.168.1.220 rfd: RX for MEQ0269842: @1808138286 RSSI=-52dB 0x37C46B -> 0x000000 Generic [NEQ0219037]:
  CNT=65,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x5E
  DATA = 8D 49 BE 00 00 04 00 00 09 26 FD 
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.BOOT=true
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.ENERGY_COUNTER=87084.600000
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.POWER=0.040000
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.CURRENT=0.000000
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.VOLTAGE=234.200000
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:59 192.168.1.220 rfd: Event: MEQ0269842:2.FREQUENCY=49.970000
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send 5 events
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:04:59 192.168.1.220 rfd: HSSXmlRpcEventDispatcher::Handle send completed
Apr 30 03:05:04 192.168.1.220 multimac: C<: #127 TRX GetDutyCycle
Apr 30 03:05:04 192.168.1.220 multimac: C< @569936561: bin:FD 00 03 01 7F 03 9A 1B
Apr 30 03:05:04 192.168.1.220 multimac: C> @569936663: #127 TRX Response Ack 04
Apr 30 03:05:04 192.168.1.220 multimac: SubsystemBidcos::CheckDutyCycleEventThreshold( 2.0, 2.0 ) = 0
Apr 30 03:05:07 192.168.1.220 root: check_mk_agent - connection accepted from 192.168.1.4:39148
Apr 30 03:05:07 192.168.1.220 multimac: A>: #61 HmSystem DutyCycleRequest 
Apr 30 03:05:07 192.168.1.220 multimac: A<: #61 HmSystem Response 02 04
Kann da einer was rauslesen?
Für mich sieht das aus, als wenn da kurzzeitig in meinem Netz was nicht passt (wegen der cuxd-Meldung "error resolving hostname", die taucht nämlich sonst nicht auf), aber wenn das der grund ist, warum reißt mir das den RFD weg?

Danke schonmal für jeglichen Hinweis.

Benutzeravatar
jmaus
Beiträge: 4554
Registriert: 17.02.2015, 14:45
Wohnort: Dresden
Kontaktdaten:

Re: Watchdog Alarm 'rfd restarted'

Beitrag von jmaus » 30.04.2019, 12:09

scorpionking hat geschrieben:
30.04.2019, 11:02
Heute Nacht war's wieder soweit (ich habe den Monit für rfd wieder aktiviert, sonst bekomm ich das ja u.U. gar nicht mit).
[...]
Kann da einer was rauslesen?
Für mich sieht das aus, als wenn da kurzzeitig in meinem Netz was nicht passt (wegen der cuxd-Meldung "error resolving hostname", die taucht nämlich sonst nicht auf), aber wenn das der grund ist, warum reißt mir das den RFD weg?
Nun, wer soll denn "host1.mynet.local:2067" bitte sein? Das kannst aktuell nur du beantworten. Und da cuxd direkt mit dem rfd interagiert kann es mitunter schon sein das hier ggf. eine Aktion ausgeführt wird die zum Absturz des rfd führen könnte (auch wenn das nicht passieren sollte).
RaspberryMatic 3.45.7.20190511 @ TinkerS mit ~160 HomeMatic Geräten + ioBroker – GitHubPayPalTwitter

scorpionking
Beiträge: 157
Registriert: 14.02.2016, 12:32

Re: Watchdog Alarm 'rfd restarted'

Beitrag von scorpionking » 30.04.2019, 12:30

Auf dem läuft u.a. mein Syslog-Server sowie CCU-Historian und Node-RED mit ...contrib-ccu. Ist eine VM mit Debian.

Der Port müsste meines Wissens zum CCU-Historian gehören, der registriert sich ja bei allen CCU Services zum Abrufen der Werte, wenn ich es richtig weiß.

D.h. du siehst da in dem Log auch keine anderen Hiwneise, die mich der Ursache evtl. näher bringen?

Benutzeravatar
jmaus
Beiträge: 4554
Registriert: 17.02.2015, 14:45
Wohnort: Dresden
Kontaktdaten:

Re: Watchdog Alarm 'rfd restarted'

Beitrag von jmaus » 30.04.2019, 14:08

scorpionking hat geschrieben:
30.04.2019, 12:30
Auf dem läuft u.a. mein Syslog-Server sowie CCU-Historian und Node-RED mit ...contrib-ccu. Ist eine VM mit Debian.
Dann würde ich an der Stelle mal dafür sorgen das statt des Namens der VM die IP-Adresse in CUxD eingetragen ist da anscheinend aus irgendwelchen Gründen die Namensauflösung nicht immer zuverlässig zu funktionieren scheint.
scorpionking hat geschrieben:
30.04.2019, 12:30
D.h. du siehst da in dem Log auch keine anderen Hiwneise, die mich der Ursache evtl. näher bringen?
Nein, momentan sehe ich auf die schnelle keinerlei andere Dinge die mir auffallen würden.
RaspberryMatic 3.45.7.20190511 @ TinkerS mit ~160 HomeMatic Geräten + ioBroker – GitHubPayPalTwitter

deimos
Beiträge: 2626
Registriert: 20.06.2017, 10:38
Wohnort: Leimersheim
Kontaktdaten:

Re: Watchdog Alarm 'rfd restarted'

Beitrag von deimos » 30.04.2019, 14:12

Hi,

was kommt bei dmesg zu dem Zeitpunkt? Es würde mich nicht wundern, wenn da entweder irgendwelche Link-Down Nachrichten von der Netzwerkkarte und/oder Undervoltage Nachrichten sind.

Viele Grüße
Alex

Benutzeravatar
jmaus
Beiträge: 4554
Registriert: 17.02.2015, 14:45
Wohnort: Dresden
Kontaktdaten:

Re: Watchdog Alarm 'rfd restarted'

Beitrag von jmaus » 30.04.2019, 14:17

deimos hat geschrieben:
30.04.2019, 14:12
was kommt bei dmesg zu dem Zeitpunkt? Es würde mich nicht wundern, wenn da entweder irgendwelche Link-Down Nachrichten von der Netzwerkkarte und/oder Undervoltage Nachrichten sind.
Das ist ein guter Hinweis! Der Frage schliesse ich mich gleich an und frage noch dazu ob du nicht zufällig dein RaspberryMatic direkt an einen Router, FritzBox bzw. Switch angeschlossen hast der ggf. Neustarten kann und damit einen Link-Down provoziert? Auf der anderen Seite müsste aber in dem Falle der "monit" solch einen link-down ja mitbekommen und dann einen entsprechenden WatchDog Alarm raushauen das es zu einem LinkDown gekommen ist.
RaspberryMatic 3.45.7.20190511 @ TinkerS mit ~160 HomeMatic Geräten + ioBroker – GitHubPayPalTwitter

scorpionking
Beiträge: 157
Registriert: 14.02.2016, 12:32

Re: Watchdog Alarm 'rfd restarted'

Beitrag von scorpionking » 30.04.2019, 17:39

jmaus hat geschrieben:
30.04.2019, 14:08
Dann würde ich an der Stelle mal dafür sorgen das statt des Namens der VM die IP-Adresse in CUxD eingetragen ist da anscheinend aus irgendwelchen Gründen die Namensauflösung nicht immer zuverlässig zu funktionieren scheint.
Guter Hinweis, das war Node-RED, bei dem ich im CCU configuration node die Init address mit dem DNS-Namen statt IP-Adresse eingetragen hatte. Hab ich jetzt mal geändert.
Ist tatsächlich auch eine der neueren Geschichten, ich teste erst seit ca. 1-2 Monaten mit Node-RED.
deimos hat geschrieben:
30.04.2019, 14:12
was kommt bei dmesg zu dem Zeitpunkt? Es würde mich nicht wundern, wenn da entweder irgendwelche Link-Down Nachrichten von der Netzwerkkarte und/oder Undervoltage Nachrichten sind.
dmesg -T zeigt das hier als letzte Einträge:

Code: Alles auswählen

[Tue Apr 23 12:48:08 2019] raspberrypi-firmware soc:firmware: Request 0x00040002 returned status 0x80000001
[Tue Apr 23 12:48:08 2019] bcm2708_fb soc:fb: bcm2708_fb_blank(1) failed: -22
[Sat Apr 27 13:41:37 2019] smsc95xx 1-1.1:1.0 eth0: link down
[Sat Apr 27 13:41:38 2019] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[Tue Apr 30 03:04:20 2019] eq3loop: eq3loop_close_slave() mmd_bidcos
[Tue Apr 30 03:04:37 2019] eq3loop: eq3loop_open_slave() mmd_bidcos
[Tue Apr 30 11:17:01 2019] eq3loop: eq3loop_close_slave() mmd_bidcos
[Tue Apr 30 11:17:17 2019] eq3loop: eq3loop_open_slave() mmd_bidcos
Am 27.4. hatte ich aber keine Watchdog-Meldung oder sonstige offensichtliche Probleme.
jmaus hat geschrieben:
30.04.2019, 14:17
Das ist ein guter Hinweis! Der Frage schliesse ich mich gleich an und frage noch dazu ob du nicht zufällig dein RaspberryMatic direkt an einen Router, FritzBox bzw. Switch angeschlossen hast der ggf. Neustarten kann und damit einen Link-Down provoziert? Auf der anderen Seite müsste aber in dem Falle der "monit" solch einen link-down ja mitbekommen und dann einen entsprechenden WatchDog Alarm raushauen das es zu einem LinkDown gekommen ist.
Wäre der Switch weg gewesen, an dem die RM hängt, hätte ich das definitiv gemerkt, da da fast meine gesamte Infrastruktur dran hängt.

Mein Setup ist etwas komplexer (bin ein leicht verrückter Informatiker :D):
Die FritzBox gibt's zwar, aber nur als Client im Netz für die Telefonie. Gateway spielt eine Sophos UTM auf einen HP DL20 Gen9, zentrales Netzwerkelement ist ein ZyXEL 24-Port PoE+-Switch (GS1920-24HP). Die RM wird auch darüber versorgt über einen PoE-Splitter. Könnte also ggf. der der Übeltäter sein, wobei ja dmesg zum Zeitpunkt des Monit alert weder einen link down noch Spannungsprobleme meldet...

scorpionking
Beiträge: 157
Registriert: 14.02.2016, 12:32

Re: Watchdog Alarm 'rfd restarted'

Beitrag von scorpionking » 15.05.2019, 20:01

So, (hoffentlich) abschließende Rückmeldung meinerseits: Problem ist nicht wieder aufgetreten.

Was hab ich geändert? Eigentlich nur die Config des CCU-Node in Node-RED. Hier hatte ich als CCU address den internen DNS-Namen eingetragen, jetzt steht die IP der RaspberryMatic drin. Seither kein Alarm mehr.

Warum aber manchmal kurzzeitig keine DNS-Auflösung intern möglich war kann ich nicht nachvollziehen. Fällt sonst auch nirgends auf und auch mein Monitoring (check_mk) hat da noch nie angeschlagen, trotz Active Check auf DNS. Aber sei's drum, läuft ja jetzt alles... :D

Antworten

Zurück zu „RaspberryMatic“