[GELÖST] ständiges Initialized,CONNECTED,DISCONNECTED

Begonnen von NoxicTonic, 19 November 2017, 23:05:22

Vorheriges Thema - Nächstes Thema

NoxicTonic

Hallo,

seit dem update auf 5.8 hab ich ein seltsames Verhalten festgestellt.
Das Event Log sowie das fhem.log wird regelrecht zu gespammt mit diesen Meldungen.

Gefühlt funktioniert alles auch ein wenig träge im Vergleich zu vorher.

Hat das alles so seine Richtigkeit?

2017-11-19 22:55:17 ZWDongle ZWDongle_0 Initialized
2017-11-19 22:55:17 ZWDongle ZWDongle_0 CONNECTED
2017-11-19 22:55:18 ZWDongle ZWDongle_0 DISCONNECTED
2017-11-19 22:55:19 ZWDongle ZWDongle_0 Initialized
2017-11-19 22:55:19 ZWDongle ZWDongle_0 CONNECTED
2017-11-19 22:55:20 ZWDongle ZWAVE1 DISCONNECTED
2017-11-19 22:55:21 ZWDongle ZWAVE1 Initialized
2017-11-19 22:55:21 ZWDongle ZWAVE1 CONNECTED
2017-11-19 22:55:22 ZWDongle ZWAVE1 DISCONNECTED
2017-11-19 22:55:23 ZWDongle ZWAVE1 Initialized
2017-11-19 22:55:23 ZWDongle ZWAVE1 CONNECTED
2017-11-19 22:55:25 ZWDongle ZWAVE1 DISCONNECTED
2017-11-19 22:55:26 ZWDongle ZWAVE1 Initialized
2017-11-19 22:55:26 ZWDongle ZWAVE1 CONNECTED
2017-11-19 22:55:27 ZWDongle ZWAVE1 DISCONNECTED
2017-11-19 22:55:28 ZWDongle ZWAVE1 Initialized
2017-11-19 22:55:28 ZWDongle ZWAVE1 CONNECTED
2017-11-19 22:55:29 ZWDongle ZWDongle_0 DISCONNECTED
2017-11-19 22:55:30 ZWDongle ZWDongle_0 Initialized
2017-11-19 22:55:30 ZWDongle ZWDongle_0 CONNECTED
2017-11-19 22:55:31 ZWDongle ZWDongle_0 DISCONNECTED
2017-11-19 22:55:32 ZWDongle ZWDongle_0 Initialized
2017-11-19 22:55:32 ZWDongle ZWDongle_0 CONNECTED
2017-11-19 22:55:34 ZWDongle ZWDongle_0 DISCONNECTED
2017-11-19 22:55:35 ZWDongle ZWDongle_0 Initialized
2017-11-19 22:55:35 ZWDongle ZWDongle_0 CONNECTED
2017-11-19 22:55:36 ZWDongle ZWAVE1 DISCONNECTED


2017.11.19 22:55:17 5: ZWDongle_ReadAnswer: select timeout
2017.11.19 22:55:17 4: ZWDongle *** get ZWDongle_0 caps
2017.11.19 22:55:17 5: ZWDongle_Write 0007 ()
2017.11.19 22:55:17 5: SW: 01030007fb
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:caps regexp:^0107
2017.11.19 22:55:17 5: ACK received, removing 01030007fb from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 01070505011504000001fe83ff88cf1f0000fb9f7da067008080008086000000e87300000e0000401a00 (answer SERIAL_API_GET_CAPABILITIES), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for caps: 01070505011504000001fe83ff88cf1f0000fb9f7da067008080008086000000e87300000e0000401a00
2017.11.19 22:55:17 4: ZWDongle *** get ZWDongle_0 ctrlCaps
2017.11.19 22:55:17 5: ZWDongle_Write 0005 ()
2017.11.19 22:55:17 5: SW: 01030005f9
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:ctrlCaps regexp:^0105
2017.11.19 22:55:17 5: ACK received, removing 01030005f9 from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 010508 (answer ZW_GET_CONTROLLER_CAPABILITIES), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for ctrlCaps: 010508
2017.11.19 22:55:17 4: ZWDongle *** get ZWDongle_0 homeId
2017.11.19 22:55:17 5: ZWDongle_Write 0020 ()
2017.11.19 22:55:17 5: SW: 01030020dc
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:homeId regexp:^0120
2017.11.19 22:55:17 5: ACK received, removing 01030020dc from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 0120f183f75c01 (answer MEMORY_GET_ID), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for homeId: 0120f183f75c01
2017.11.19 22:55:17 4: ZWDongle *** get ZWDongle_0 sucNodeId
2017.11.19 22:55:17 5: ZWDongle_Write 0056 ()
2017.11.19 22:55:17 5: SW: 01030056aa
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:sucNodeId regexp:^0156
2017.11.19 22:55:17 5: ACK received, removing 01030056aa from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 015600 (answer ZW_GET_SUC_NODE_ID), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for sucNodeId: 015600
2017.11.19 22:55:17 4: ZWDongle *** get ZWDongle_0 random 32
2017.11.19 22:55:17 5: ZWDongle_Write 001c20 ()
2017.11.19 22:55:17 5: SW: 0104001c20c7
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:random regexp:^011c
2017.11.19 22:55:17 5: ACK received, removing 0104001c20c7 from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 011c01209a571b2d0fa969f618aa1d818dde33be44451da65efdd06cc916d1177a499116 (answer ZW_GET_RANDOM), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for random: 011c01209a571b2d0fa969f618aa1d818dde33be44451da65efdd06cc916d1177a499116
2017.11.19 22:55:17 4: ZWDongle *** set ZWDongle_0 timeouts 100 15
2017.11.19 22:55:17 5: ZWDongle_Write 0006640f ()
2017.11.19 22:55:17 5: SW: 01050006640f97
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer arg:timeouts regexp:^0106
2017.11.19 22:55:17 5: ACK received, removing 01050006640f97 from dongle sendstack
2017.11.19 22:55:17 4: ZWDongle_Read ZWDongle_0: rcvd 0106640f (answer SERIAL_API_SET_TIMEOUTS), sending ACK
2017.11.19 22:55:17 5: SW: 06
2017.11.19 22:55:17 4: ZWDongle_ReadAnswer for timeouts: 0106640f
2017.11.19 22:55:17 4: ZWDongle *** set ZWDongle_0 setNIF 1 2 1 0
2017.11.19 22:55:17 5: ZWDongle_Write 000301020100 ()
2017.11.19 22:55:17 5: SW: 0107000301020100f9
2017.11.19 22:55:17 5: Starting notify loop for ZWDongle_0, 1 event(s), first is Initialized
2017.11.19 22:55:17 5: createNotifyHash
2017.11.19 22:55:17 5: ZE.Batterie: not on any display, ignoring notify
2017.11.19 22:55:17 5: End notify loop for ZWDongle_0
2017.11.19 22:55:17 1: /dev/ttyACM0 reappeared (ZWDongle_0)
2017.11.19 22:55:17 5: Starting notify loop for ZWDongle_0, 1 event(s), first is CONNECTED
2017.11.19 22:55:17 5: ZE.Batterie: not on any display, ignoring notify
2017.11.19 22:55:17 5: End notify loop for ZWDongle_0

NoxicTonic

Ich glaube ich hab mal wieder das Problem bereits gefunden.
Interesanterweise hat Fhem den Dongle ein zweites mal in die fhem.cfg eingefügt...

[EDIT] Bitte closen o.ä. das Problem war wirklich ein 2. Eintrag in der fhem.cfg der automatisch hinzugefügt wurde.