Z-Wave USB Stick (ZME_UZB1) - transmit NO_ACK

throbin · 29 März 2016, 22:07:20

Hi,

ich habe immer wieder ein seltsames Problem mit Pi3 und ZME_UZB1 Stick als ZWDongle. Ich setze einen FGS212 zum Testen ein. Damit schalte ich über das Webinterface den Switch auf ON und anschließend auf OFF. Der ON State wird sofort ausgelöst, beim OFF Befehl dauert es ca. 6 Sekunden, so dass nach 5s ein Timeout kommt. Während dieser Zeit leuchtet der Stick konstant.

Das komische daran ist, dass es sporadisch auftritt, d.h. es kann sein, dass wenn ich den Pi komplett neu starte (also Strom weg), dann läuft es wieder normal. Hat das jemand schon beobachtet?

Im Log vom ZWDongle sieht man das ganze:

Code Auswählen


2016.03.29 21:58:16 2: ZWave set ZWave_SWITCH_BINARY_2 on 
2016.03.29 21:58:16 5: ZWDongle_Write 001302032501FF2516 (d3142180)
2016.03.29 21:58:16 5: SW: 010a001302032501FF25160f
2016.03.29 21:58:16 5: ACK received, WaitForAck=>2 for 010a001302032501FF25160f
2016.03.29 21:58:16 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.03.29 21:58:16 5: SW: 06
2016.03.29 21:58:16 5: ZWDongle_0 dispatch 011301
2016.03.29 21:58:16 2: ZWave set ZWave_SWITCH_BINARY_2 off 
2016.03.29 21:58:18 4: no response from device, removing 010a001302032501FF25160f from dongle sendstack
2016.03.29 21:58:20 4: ZWDongle_Read ZWDongle_0: rcvd 00131601019b (request ZW_SEND_DATA), sending ACK
2016.03.29 21:58:20 5: SW: 06
2016.03.29 21:58:20 5: ZWDongle_0 dispatch 00131601019b
2016.03.29 21:58:20 4: CMD:ZW_SEND_DATA ID:01 ARG:019b CB:16
2016.03.29 21:58:20 2: ZWDongle_0 transmit NO_ACK for CB 16, target ZWave_SWITCH_BINARY_2
2016.03.29 21:58:21 2: ZWave: No ACK from ZWave_SWITCH_BINARY_2 after 5s for sentset:1302032501FF2516
2016.03.29 21:58:21 5: ZWDongle_Write 001302032501002517 (d3142180)
2016.03.29 21:58:21 5: SW: 010a001302032501002517f1
2016.03.29 21:58:21 5: ACK received, WaitForAck=>2 for 010a001302032501002517f1
2016.03.29 21:58:21 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.03.29 21:58:21 5: SW: 06
2016.03.29 21:58:21 5: ZWDongle_0 dispatch 011301

Listing vom FIBARO Switch

Code Auswählen


Internals: 
   DEF        d3142180 2 
   IODev      ZWDongle_0 
   LASTInputDev ZWDongle_0 
   MSGCNT     22 
   NAME       ZWave_SWITCH_BINARY_2 
   NR         21 
   STATE      TRANSMIT_NO_ACK 
   TYPE       ZWave 
   ZWDongle_0_MSGCNT 22 
   ZWDongle_0_RAWMSG 00131701019d 
   ZWDongle_0_TIME 2016-03-29 21:58:25 
   homeId     d3142180 
   isWakeUp 
   lastMsgSent 1459281501.07195 
   nodeIdHex  02 
   timeToAck  0.028 
   Readings: 
     2016-03-29 21:52:36   assocGroup_1    Max 5 Nodes ZWDongle_0 
     2016-03-29 21:52:36   assocGroup_2    Max 5 Nodes 
     2016-03-29 21:52:36   assocGroup_3    Max 5 Nodes 
     2016-03-29 21:52:36   assocGroups     3 
     2016-03-28 12:16:49   configActiveFlashingAlarmTime 600 
     2016-03-28 12:16:49   configAutoOff   0 
     2016-03-28 12:16:49   configAutoOffRelayAfterSpecifiedTime ManualOverrideDisabled 
     2016-03-28 12:16:49   configDimmerRollerShutterControl DisableDimmerRollerShutter0 
     2016-03-28 12:16:49   configEnableDisableALLONOFF ALLONActiveALLOFFActive 
     2016-03-28 12:16:49   configInputsBehaviour Toggle 
     2016-03-28 12:16:49   configInputsButtonSwitchConfiguration BiStableInputSwitch 
     2016-03-28 12:16:49   configRelayResponseToGeneralAlarm ALARMFLASHINGRelayWillTurnONAndO3 
     2016-03-28 12:16:49   configRelayResponseToSmokeCOCO2Alarm ALARMFLASHINGRelayWillTurnONAndO3 
     2016-03-28 12:16:49   configRelayResponseToTemperatureAlarm ALARMRELAYONRelayWillTurnONUpon1 
     2016-03-28 12:16:49   configRelayResponseToWaterFloodAlarm ALARMRELAYOFFRelayWillTurnOFF2 
     2016-03-28 12:16:49   configSavingStateBeforePowerFaillure StateSavedAtPowerFailureAll1 
     2016-03-28 12:16:49   configSeparationOfAssociationSending6 MapStatusToAllDevicesInGroup10 
     2016-03-24 20:59:36   mcCapability_01 SWITCH_BINARY 
     2016-03-24 20:59:36   mcCapability_02 SWITCH_BINARY 
     2016-03-24 20:59:36   mcEndpoints     total 2, identical 
     2016-03-24 20:59:35   model           FIBARO System FGS212 Switch 3kW 
     2016-03-24 20:59:35   modelConfig     fibaro/fgs212.xml 
     2016-03-24 20:59:35   modelId         010f-0402-1002 
     2016-03-24 21:52:34   neighborList    ZWDongle_0 
     2016-03-24 21:52:15   powerlvl        current 0 remain 0 
     2016-03-29 21:58:25   state           TRANSMIT_NO_ACK 
     2016-03-29 21:58:25   transmit        NO_ACK 
     2016-03-24 21:52:24   version         Lib 3 Prot 3.52 App 2.2 
Attributes: 
   IODev      ZWDongle_0 
   classes    MANUFACTURER_SPECIFIC VERSION CONFIGURATION ASSOCIATION MULTI_CHANNEL_ASSOCIATION MULTI_CHANNEL SWITCH_BINARY SWITCH_ALL FIRMWARE_UPDATE_MD POWERLEVEL MARK SWITCH_BINARY MULTI_CHANNEL 
   room       ZWave 
   vclasses   ASSOCIATION:2 CONFIGURATION:1 FIRMWARE_UPDATE_MD:1 MANUFACTURER_SPECIFIC:1 MULTI_CHANNEL:2 MULTI_CHANNEL_ASSOCIATION:1 POWERLEVEL:1 SWITCH_ALL:1 SWITCH_BINARY:1 VERSION:1

Listing vom ZWDongle:

Code Auswählen


Internals: 
   CallbackNr 0 
   Clients    :ZWave: 
   DEF        /dev/ttyACM0@115200 
   DeviceName /dev/ttyACM0@115200 
   FD         11 
   MaxSendRetries 3 
   NAME       ZWDongle_0 
   NR         20 
   PARTIAL 
   RAWMSG     00131701019d 
   ReadTime   1459281505.20395 
   STATE      Initialized 
   SendRetries 0 
   SendTime   1459281501.07263 
   TYPE       ZWDongle 
   WaitForAck 0 
   ZWDongle_0_MSGCNT 56 
   ZWDongle_0_TIME 2016-03-29 21:58:25 
   homeId     d3142180 
   nodeIdHex  01 
   nrNAck     0 
   Matchlist: 
     1:ZWave    .* 
   Readings: 
     2016-03-29 21:17:06   caps            Vers:5 Rev:2 ManufID:0115 ProductType:0400 ProductID:0001 SERIAL_API_GET_INIT_DATA SERIAL_API_APPL_NODE_INFORMATION APPLICATION_COMMAND_HANDLER ZW_GET_CONTROLLER_CAPABILITIES SERIAL_API_SET_TIMEOUTS SERIAL_API_GET_CAPABILITIES SERIAL_API_SOFT_RESET UNKNOWN_09 UNKNOWN_0a ZW_SET_R_F_RECEIVE_MODE ZW_SET_SLEEP_MODE ZW_SEND_NODE_INFORMATION ZW_SEND_DATA ZW_SEND_DATA_MULTI ZW_GET_VERSION ZW_SEND_DATA_ABORT ZW_R_F_POWER_LEVEL_SET ZW_SEND_DATA_META ZW_GET_RANDOM MEMORY_GET_ID MEMORY_GET_BYTE MEMORY_PUT_BYTE MEMORY_GET_BUFFER MEMORY_PUT_BUFFER FLASH_AUTO_PROG_SET UNKNOWN_28 NVM_GET_ID NVM_EXT_READ_LONG_BUFFER NVM_EXT_WRITE_LONG_BUFFER NVM_EXT_READ_LONG_BYTE NVM_EXT_WRITE_LONG_BYTE ZW_GET_NODE_PROTOCOL_INFO ZW_SET_DEFAULT ZW_REPLICATION_COMMAND_COMPLETE ZW_REPLICATION_SEND_DATA ZW_ASSIGN_RETURN_ROUTE ZW_DELETE_RETURN_ROUTE ZW_REQUEST_NODE_NEIGHBOR_UPDATE ZW_APPLICATION_UPDATE ZW_ADD_NODE_TO_NETWORK ZW_REMOVE_NODE_FROM_NETWORK ZW_CREATE_NEW_PRIMARY ZW_CONTROLLER_CHANGE ZW_SET_LEARN_MODE ZW_ASSIGN_SUC_RETURN_ROUTE ZW_REQUEST_NETWORK_UPDATE ZW_SET_SUC_NODE_ID ZW_DELETE_SUC_RETURN_ROUTE ZW_GET_SUC_NODE_ID ZW_SEND_SUC_ID ZW_EXPLORE_REQUEST_INCLUSION ZW_REQUEST_NODE_INFO ZW_REMOVE_FAILED_NODE_ID ZW_IS_FAILED_NODE ZW_REPLACE_FAILED_NODE UNKNOWN_66 UNKNOWN_67 UNKNOWN_78 GET_ROUTING_TABLE_LINE LOCK_ROUTE_RESPONSE UNKNOWN_92 UNKNOWN_93 UNKNOWN_98 ZW_SET_WUT_TIMEOUT ZW_WATCHDOG_ENABLE ZW_WATCHDOG_DISABLE ZW_WATCHDOG_CHECK ZW_SET_EXT_INT_LEVEL ZW_RF_POWERLEVEL_GET ZW_TYPE_LIBRARY ZW_SEND_TEST_FRAME ZW_GET_PROTOCOL_STATUS WATCHDOG_START WATCHDOG_STOP UNKNOWN_d4 UNKNOWN_ef ZME_FREQ_CHANGE ZME_BOOTLOADER_FLASH UNKNOWN_f5 
     2016-03-29 21:17:07   homeId          HomeId:d3142180 CtrlNodeIdHex:01 
     2016-03-24 23:01:19   nodeInfo_1      STATIC_CONTROLLER listening frequentListening:0 beaming:16 40kBaud Vers:4 Security:0 
     2016-03-24 20:39:49   nodeInfo_2      ROUTING_SLAVE listening frequentListening:0 beaming:16 routing 40kBaud Vers:4 Security:0 
     2016-03-24 21:47:01   nodeList        ZWDongle_0 ZWave_SWITCH_BINARY_2 
     2016-03-29 21:17:07   random          5704e948ec04b0c5aa30e5c1aad3edd6ebd6fa154c84d2227e95a1ef27e36210 
     2016-03-29 21:17:07   state           Initialized 
     2016-03-24 21:51:18   version         Z-Wave 3.99 STATIC_CONTROLLER 
   SendStack: 
Attributes: 
   verbose    5

rudolfkoenig · 29 März 2016, 22:34:33

Steht eigentlich da:

Zitat2016.03.29 21:58:18 4: no response from device, removing 010a001302032501FF25160f from dongle sendstack

Der Stick hat den ACK nicht gehoert, und FHEM hat sich nicht getraut, noch ein Befehl hinterherzuschicken.

throbin · 29 März 2016, 23:16:45

Das habe ich auch gesehen

Aber ich begreife es nicht, warum es dazu kommt... Teilweise lässt sich der Pi auch nicht neu starten (reboot). Ich beobachte es weiter, vielleicht finde ich es heraus $:-\$

Jackson · 21 Oktober 2016, 19:15:41

Aus aktuellen Anlass hole ich den Thread mal aus der Versenkung.

Ich teste gerade einen Wall Plug. Das Schalten läuft problemlos. Nur das Auslesen der Readings nicht immer...

Ich Plug habe ich auch schon komplett zurücksetzt und wieder neu eingebunden, als auch meinen PI2 mal rebootet. An der Reichweite kann es eigentlich nicht liegen, denn der Plug leuchtet grün, wenn man ihn kurz rein und raus steckt.

Hat einer eine Idee? Kann man das Timeout evtl. hoch setzen?

Log:

Code Auswählen



2016.10.21 19:01:59.822 3: ZWave got config for fibaro/fgwpe.xml from ./FHEM/lib/openzwave_deviceconfig.xml.gz
2016.10.21 19:02:11.520 3: ZWave get ZWave_SWITCH_BINARY_8 version 
2016.10.21 19:02:11.521 5: ZWDongle_Write 0013080286112501 (c698b541)
2016.10.21 19:02:11.522 5: SW: 010900130802861125015c
2016.10.21 19:02:11.526 5: ACK received, WaitForAck=>2 for 010900130802861125015c
2016.10.21 19:02:11.533 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:02:11.533 5: SW: 06
2016.10.21 19:02:11.535 5: ZWDongle_0 dispatch 011301
2016.10.21 19:02:13.588 4: no response from device, removing 010900130802861125015c from dongle sendstack
2016.10.21 19:02:16.522 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080286112501
2016.10.21 19:02:21.364 4: ZWDongle_Read ZWDongle_0: rcvd 0013010103d8 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:02:21.365 5: SW: 06
2016.10.21 19:02:21.367 5: ZWDongle_0 dispatch 0013010103d8
2016.10.21 19:02:21.367 4: CMD:ZW_SEND_DATA ID:01 ARG:03d8 CB:01
2016.10.21 19:02:21.368 2: ZWDongle_0 transmit NO_ACK for CB 01, target ZWave_SWITCH_BINARY_8
2016.10.21 19:02:44.877 3: ZWave get ZWave_SWITCH_BINARY_8 version 
2016.10.21 19:02:44.878 5: ZWDongle_Write 0013080286112502 (c698b541)
2016.10.21 19:02:44.879 5: SW: 010900130802861125025f
2016.10.21 19:02:44.883 5: ACK received, WaitForAck=>2 for 010900130802861125025f
2016.10.21 19:02:44.891 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:02:44.892 5: SW: 06
2016.10.21 19:02:44.893 5: ZWDongle_0 dispatch 011301
2016.10.21 19:02:46.897 4: no response from device, removing 010900130802861125025f from dongle sendstack
2016.10.21 19:02:49.880 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080286112502
2016.10.21 19:02:54.720 4: ZWDongle_Read ZWDongle_0: rcvd 0013020103d7 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:02:54.721 5: SW: 06
2016.10.21 19:02:54.722 5: ZWDongle_0 dispatch 0013020103d7
2016.10.21 19:02:54.723 4: CMD:ZW_SEND_DATA ID:01 ARG:03d7 CB:02
2016.10.21 19:02:54.724 2: ZWDongle_0 transmit NO_ACK for CB 02, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:07.821 3: ZWave get ZWave_SWITCH_BINARY_8 configActionInCaseOfExceedingDefined52 
2016.10.21 19:03:07.822 5: ZWDongle_Write 001308037005342503 (c698b541)
2016.10.21 19:03:07.823 5: SW: 010a0013080370053425038a
2016.10.21 19:03:07.827 3: ZWave get ZWave_SWITCH_BINARY_8 configAlarmDuration 
2016.10.21 19:03:07.829 3: ZWave get ZWave_SWITCH_BINARY_8 configAlwaysOnFunction 
2016.10.21 19:03:07.832 3: ZWave get ZWave_SWITCH_BINARY_8 configDOWNValue 
2016.10.21 19:03:07.835 3: ZWave get ZWave_SWITCH_BINARY_8 configImmediatePowerReport 
2016.10.21 19:03:07.838 3: ZWave get ZWave_SWITCH_BINARY_8 configLEDRingIlluminationColourAtTheZ63 
2016.10.21 19:03:07.841 3: ZWave get ZWave_SWITCH_BINARY_8 configLEDRingIlluminationColourWhen61 
2016.10.21 19:03:07.844 3: ZWave get ZWave_SWITCH_BINARY_8 configLEDRingIlluminationColourWhen62 
2016.10.21 19:03:07.846 3: ZWave get ZWave_SWITCH_BINARY_8 configMeteringEnergyConsumedByTheWall49 
2016.10.21 19:03:07.849 3: ZWave get ZWave_SWITCH_BINARY_8 configOveloadSafetySwitch 
2016.10.21 19:03:07.852 3: ZWave get ZWave_SWITCH_BINARY_8 configPowerLoadWhichWhenExceededMakes60 
2016.10.21 19:03:07.855 3: ZWave get ZWave_SWITCH_BINARY_8 configPowerReportingFrequency 
2016.10.21 19:03:07.858 3: ZWave get ZWave_SWITCH_BINARY_8 configReactionToAlarms 
2016.10.21 19:03:07.861 3: ZWave get ZWave_SWITCH_BINARY_8 configRememberDeviceStatusAfterPower16 
2016.10.21 19:03:07.863 3: ZWave get ZWave_SWITCH_BINARY_8 configReportingChangesInEnergyConsumed45 
2016.10.21 19:03:07.866 3: ZWave get ZWave_SWITCH_BINARY_8 configStandardPowerLoadReporting 
2016.10.21 19:03:07.869 3: ZWave get ZWave_SWITCH_BINARY_8 configTimePeriodBetweenReportsOnPower47 
2016.10.21 19:03:07.872 3: ZWave get ZWave_SWITCH_BINARY_8 configUPValue 
2016.10.21 19:03:07.875 3: ZWave get ZWave_SWITCH_BINARY_8 configWallPlugSResponseToAlarmFrames 
2016.10.21 19:03:07.878 5: ACK received, WaitForAck=>2 for 010a0013080370053425038a
2016.10.21 19:03:07.878 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:07.879 5: SW: 06
2016.10.21 19:03:07.881 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:09.884 4: no response from device, removing 010a0013080370053425038a from dongle sendstack
2016.10.21 19:03:12.824 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005342503
2016.10.21 19:03:12.830 5: ZWDongle_Write 001308037005272504 (c698b541)
2016.10.21 19:03:12.831 5: SW: 010a0013080370052725049e
2016.10.21 19:03:13.504 5: ACK received, WaitForAck=>2 for 010a0013080370052725049e
2016.10.21 19:03:13.515 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:13.516 5: SW: 06
2016.10.21 19:03:13.518 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:15.522 4: no response from device, removing 010a0013080370052725049e from dongle sendstack
2016.10.21 19:03:17.833 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005272504
2016.10.21 19:03:17.840 5: ZWDongle_Write 001308037005012505 (c698b541)
2016.10.21 19:03:17.841 5: SW: 010a001308037005012505b9
2016.10.21 19:03:18.843 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a001308037005012505b9
2016.10.21 19:03:18.844 5: SW: 010a001308037005012505b9
2016.10.21 19:03:19.383 5: ACK received, WaitForAck=>2 for 010a001308037005012505b9
2016.10.21 19:03:19.394 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:19.394 5: SW: 06
2016.10.21 19:03:19.396 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:19.398 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:21.402 4: no response from device, removing 010a001308037005012505b9 from dongle sendstack
2016.10.21 19:03:22.842 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005012505
2016.10.21 19:03:22.848 5: ZWDongle_Write 001308037005322506 (c698b541)
2016.10.21 19:03:22.849 5: SW: 010a00130803700532250689
2016.10.21 19:03:23.851 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700532250689
2016.10.21 19:03:23.851 5: SW: 010a00130803700532250689
2016.10.21 19:03:24.853 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700532250689
2016.10.21 19:03:24.853 5: SW: 010a00130803700532250689
2016.10.21 19:03:25.095 5: ACK received, WaitForAck=>2 for 010a00130803700532250689
2016.10.21 19:03:25.097 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:25.098 5: SW: 06
2016.10.21 19:03:25.100 5: ZWDongle_0 dispatch 011300
2016.10.21 19:03:25.102 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:03:25.104 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:25.105 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:25.320 4: ZWDongle_Read ZWDongle_0: rcvd 001306010016 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:25.321 5: SW: 06
2016.10.21 19:03:25.322 5: device ack reveived, removing 010a00130803700532250689 from dongle sendstack
2016.10.21 19:03:25.323 5: ZWDongle_0 dispatch 001306010016
2016.10.21 19:03:25.324 4: CMD:ZW_SEND_DATA ID:01 ARG:0016 CB:06
2016.10.21 19:03:25.325 2: ZWDongle_0 transmit NO_ACK for CB 06, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:27.850 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:1308037005322506
2016.10.21 19:03:27.856 5: ZWDongle_Write 001308037005322506 (c698b541)
2016.10.21 19:03:27.858 5: SW: 010a00130803700532250689
2016.10.21 19:03:27.861 5: ACK received, WaitForAck=>2 for 010a00130803700532250689
2016.10.21 19:03:27.870 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:27.871 5: SW: 06
2016.10.21 19:03:27.873 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:27.880 4: ZWDongle_Read ZWDongle_0: rcvd 001306010002 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:27.881 5: SW: 06
2016.10.21 19:03:27.883 5: device ack reveived, removing 010a00130803700532250689 from dongle sendstack
2016.10.21 19:03:27.884 5: ZWDongle_0 dispatch 001306010002
2016.10.21 19:03:27.885 4: CMD:ZW_SEND_DATA ID:01 ARG:0002 CB:06
2016.10.21 19:03:27.885 2: ZWDongle_0 transmit NO_ACK for CB 06, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:32.861 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005322506
2016.10.21 19:03:32.867 5: ZWDongle_Write 001308037005282507 (c698b541)
2016.10.21 19:03:32.869 5: SW: 010a00130803700528250792
2016.10.21 19:03:33.570 5: ACK received, WaitForAck=>2 for 010a00130803700528250792
2016.10.21 19:03:33.580 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:33.581 5: SW: 06
2016.10.21 19:03:33.583 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:35.587 4: no response from device, removing 010a00130803700528250792 from dongle sendstack
2016.10.21 19:03:37.870 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005282507
2016.10.21 19:03:37.877 5: ZWDongle_Write 0013080370053f2508 (c698b541)
2016.10.21 19:03:37.878 5: SW: 010a0013080370053f25088a
2016.10.21 19:03:38.880 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370053f25088a
2016.10.21 19:03:38.881 5: SW: 010a0013080370053f25088a
2016.10.21 19:03:39.421 5: ACK received, WaitForAck=>2 for 010a0013080370053f25088a
2016.10.21 19:03:39.431 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:39.432 5: SW: 06
2016.10.21 19:03:39.434 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:39.436 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:39.452 4: ZWDongle_Read ZWDongle_0: rcvd 001308010003 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:39.452 5: SW: 06
2016.10.21 19:03:39.454 5: device ack reveived, removing 010a0013080370053f25088a from dongle sendstack
2016.10.21 19:03:39.455 5: ZWDongle_0 dispatch 001308010003
2016.10.21 19:03:39.456 4: CMD:ZW_SEND_DATA ID:01 ARG:0003 CB:08
2016.10.21 19:03:39.457 2: ZWDongle_0 transmit NO_ACK for CB 08, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:42.880 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370053f2508
2016.10.21 19:03:42.887 5: ZWDongle_Write 0013080370053d2509 (c698b541)
2016.10.21 19:03:42.888 5: SW: 010a0013080370053d250989
2016.10.21 19:03:43.890 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370053d250989
2016.10.21 19:03:43.891 5: SW: 010a0013080370053d250989
2016.10.21 19:03:44.891 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370053d250989
2016.10.21 19:03:44.892 5: SW: 010a0013080370053d250989
2016.10.21 19:03:45.147 5: ACK received, WaitForAck=>2 for 010a0013080370053d250989
2016.10.21 19:03:45.150 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:45.151 5: SW: 06
2016.10.21 19:03:45.153 5: ZWDongle_0 dispatch 011300
2016.10.21 19:03:45.154 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:03:45.156 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:45.157 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:45.388 4: ZWDongle_Read ZWDongle_0: rcvd 001309010018 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:45.389 5: SW: 06
2016.10.21 19:03:45.391 5: device ack reveived, removing 010a0013080370053d250989 from dongle sendstack
2016.10.21 19:03:45.392 5: ZWDongle_0 dispatch 001309010018
2016.10.21 19:03:45.393 4: CMD:ZW_SEND_DATA ID:01 ARG:0018 CB:09
2016.10.21 19:03:45.393 2: ZWDongle_0 transmit NO_ACK for CB 09, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:47.889 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:13080370053d2509
2016.10.21 19:03:47.895 5: ZWDongle_Write 0013080370053d2509 (c698b541)
2016.10.21 19:03:47.896 5: SW: 010a0013080370053d250989
2016.10.21 19:03:47.900 5: ACK received, WaitForAck=>2 for 010a0013080370053d250989
2016.10.21 19:03:47.909 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:47.909 5: SW: 06
2016.10.21 19:03:47.912 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:47.948 4: ZWDongle_Read ZWDongle_0: rcvd 001309010005 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:47.949 5: SW: 06
2016.10.21 19:03:47.951 5: device ack reveived, removing 010a0013080370053d250989 from dongle sendstack
2016.10.21 19:03:47.951 5: ZWDongle_0 dispatch 001309010005
2016.10.21 19:03:47.952 4: CMD:ZW_SEND_DATA ID:01 ARG:0005 CB:09
2016.10.21 19:03:47.953 2: ZWDongle_0 transmit NO_ACK for CB 09, target ZWave_SWITCH_BINARY_8
2016.10.21 19:03:52.900 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370053d2509
2016.10.21 19:03:52.907 5: ZWDongle_Write 0013080370053e250a (c698b541)
2016.10.21 19:03:52.908 5: SW: 010a0013080370053e250a89
2016.10.21 19:03:53.579 5: ACK received, WaitForAck=>2 for 010a0013080370053e250a89
2016.10.21 19:03:53.589 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:53.590 5: SW: 06
2016.10.21 19:03:53.592 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:55.596 4: no response from device, removing 010a0013080370053e250a89 from dongle sendstack
2016.10.21 19:03:57.910 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370053e250a
2016.10.21 19:03:57.917 5: ZWDongle_Write 00130803700531250b (c698b541)
2016.10.21 19:03:57.918 5: SW: 010a00130803700531250b87
2016.10.21 19:03:58.920 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700531250b87
2016.10.21 19:03:58.921 5: SW: 010a00130803700531250b87
2016.10.21 19:03:59.397 5: ACK received, WaitForAck=>2 for 010a00130803700531250b87
2016.10.21 19:03:59.409 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:03:59.409 5: SW: 06
2016.10.21 19:03:59.411 5: ZWDongle_0 dispatch 011301
2016.10.21 19:03:59.413 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:03:59.552 4: ZWDongle_Read ZWDongle_0: rcvd 00130b010010 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:03:59.552 5: SW: 06
2016.10.21 19:03:59.554 5: device ack reveived, removing 010a00130803700531250b87 from dongle sendstack
2016.10.21 19:03:59.555 5: ZWDongle_0 dispatch 00130b010010
2016.10.21 19:03:59.556 4: CMD:ZW_SEND_DATA ID:01 ARG:0010 CB:0b
2016.10.21 19:03:59.557 2: ZWDongle_0 transmit NO_ACK for CB 0b, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:02.920 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:130803700531250b
2016.10.21 19:04:02.927 5: ZWDongle_Write 00130803700546250c (c698b541)
2016.10.21 19:04:02.928 5: SW: 010a00130803700546250cf7
2016.10.21 19:04:03.930 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700546250cf7
2016.10.21 19:04:03.931 5: SW: 010a00130803700546250cf7
2016.10.21 19:04:04.932 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700546250cf7
2016.10.21 19:04:04.933 5: SW: 010a00130803700546250cf7
2016.10.21 19:04:05.185 5: ACK received, WaitForAck=>2 for 010a00130803700546250cf7
2016.10.21 19:04:05.187 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:05.188 5: SW: 06
2016.10.21 19:04:05.190 5: ZWDongle_0 dispatch 011300
2016.10.21 19:04:05.192 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:04:05.193 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:05.194 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:05.381 4: ZWDongle_Read ZWDongle_0: rcvd 00130c010013 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:05.382 5: SW: 06
2016.10.21 19:04:05.383 5: device ack reveived, removing 010a00130803700546250cf7 from dongle sendstack
2016.10.21 19:04:05.384 5: ZWDongle_0 dispatch 00130c010013
2016.10.21 19:04:05.385 4: CMD:ZW_SEND_DATA ID:01 ARG:0013 CB:0c
2016.10.21 19:04:05.386 2: ZWDongle_0 transmit NO_ACK for CB 0c, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:07.929 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:130803700546250c
2016.10.21 19:04:07.936 5: ZWDongle_Write 00130803700546250c (c698b541)
2016.10.21 19:04:07.937 5: SW: 010a00130803700546250cf7
2016.10.21 19:04:07.940 5: ACK received, WaitForAck=>2 for 010a00130803700546250cf7
2016.10.21 19:04:07.949 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:07.950 5: SW: 06
2016.10.21 19:04:07.952 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:07.970 4: ZWDongle_Read ZWDongle_0: rcvd 00130c010002 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:07.971 5: SW: 06
2016.10.21 19:04:07.973 5: device ack reveived, removing 010a00130803700546250cf7 from dongle sendstack
2016.10.21 19:04:07.974 5: ZWDongle_0 dispatch 00130c010002
2016.10.21 19:04:07.975 4: CMD:ZW_SEND_DATA ID:01 ARG:0002 CB:0c
2016.10.21 19:04:07.975 2: ZWDongle_0 transmit NO_ACK for CB 0c, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:12.938 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:130803700546250c
2016.10.21 19:04:12.945 5: ZWDongle_Write 0013080370053c250d (c698b541)
2016.10.21 19:04:12.947 5: SW: 010a0013080370053c250d8c
2016.10.21 19:04:13.620 5: ACK received, WaitForAck=>2 for 010a0013080370053c250d8c
2016.10.21 19:04:13.630 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:13.631 5: SW: 06
2016.10.21 19:04:13.633 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:15.637 4: no response from device, removing 010a0013080370053c250d8c from dongle sendstack
2016.10.21 19:04:17.948 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370053c250d
2016.10.21 19:04:17.954 5: ZWDongle_Write 0013080370052b250e (c698b541)
2016.10.21 19:04:17.955 5: SW: 010a0013080370052b250e98
2016.10.21 19:04:18.957 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052b250e98
2016.10.21 19:04:18.958 5: SW: 010a0013080370052b250e98
2016.10.21 19:04:19.440 5: ACK received, WaitForAck=>2 for 010a0013080370052b250e98
2016.10.21 19:04:19.451 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:19.452 5: SW: 06
2016.10.21 19:04:19.454 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:19.456 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:19.514 4: ZWDongle_Read ZWDongle_0: rcvd 00130e010007 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:19.515 5: SW: 06
2016.10.21 19:04:19.516 5: device ack reveived, removing 010a0013080370052b250e98 from dongle sendstack
2016.10.21 19:04:19.517 5: ZWDongle_0 dispatch 00130e010007
2016.10.21 19:04:19.518 4: CMD:ZW_SEND_DATA ID:01 ARG:0007 CB:0e
2016.10.21 19:04:19.519 2: ZWDongle_0 transmit NO_ACK for CB 0e, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:22.958 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370052b250e
2016.10.21 19:04:22.964 5: ZWDongle_Write 00130803700522250f (c698b541)
2016.10.21 19:04:22.965 5: SW: 010a00130803700522250f90
2016.10.21 19:04:23.967 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700522250f90
2016.10.21 19:04:23.968 5: SW: 010a00130803700522250f90
2016.10.21 19:04:24.969 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a00130803700522250f90
2016.10.21 19:04:24.970 5: SW: 010a00130803700522250f90
2016.10.21 19:04:25.242 5: ACK received, WaitForAck=>2 for 010a00130803700522250f90
2016.10.21 19:04:25.244 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:25.245 5: SW: 06
2016.10.21 19:04:25.247 5: ZWDongle_0 dispatch 011300
2016.10.21 19:04:25.248 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:04:25.250 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:25.251 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:25.408 4: ZWDongle_Read ZWDongle_0: rcvd 00130f010010 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:25.409 5: SW: 06
2016.10.21 19:04:25.411 5: device ack reveived, removing 010a00130803700522250f90 from dongle sendstack
2016.10.21 19:04:25.412 5: ZWDongle_0 dispatch 00130f010010
2016.10.21 19:04:25.413 4: CMD:ZW_SEND_DATA ID:01 ARG:0010 CB:0f
2016.10.21 19:04:25.413 2: ZWDongle_0 transmit NO_ACK for CB 0f, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:27.966 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:130803700522250f
2016.10.21 19:04:27.974 5: ZWDongle_Write 00130803700522250f (c698b541)
2016.10.21 19:04:27.975 5: SW: 010a00130803700522250f90
2016.10.21 19:04:27.978 5: ACK received, WaitForAck=>2 for 010a00130803700522250f90
2016.10.21 19:04:27.987 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:27.988 5: SW: 06
2016.10.21 19:04:27.990 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:27.999 4: ZWDongle_Read ZWDongle_0: rcvd 00130f010002 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:27.999 5: SW: 06
2016.10.21 19:04:28.001 5: device ack reveived, removing 010a00130803700522250f90 from dongle sendstack
2016.10.21 19:04:28.002 5: ZWDongle_0 dispatch 00130f010002
2016.10.21 19:04:28.003 4: CMD:ZW_SEND_DATA ID:01 ARG:0002 CB:0f
2016.10.21 19:04:28.003 2: ZWDongle_0 transmit NO_ACK for CB 0f, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:32.978 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:130803700522250f
2016.10.21 19:04:32.985 5: ZWDongle_Write 001308037005102510 (c698b541)
2016.10.21 19:04:32.986 5: SW: 010a001308037005102510bd
2016.10.21 19:04:33.702 5: ACK received, WaitForAck=>2 for 010a001308037005102510bd
2016.10.21 19:04:33.713 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:33.714 5: SW: 06
2016.10.21 19:04:33.716 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:35.721 4: no response from device, removing 010a001308037005102510bd from dongle sendstack
2016.10.21 19:04:37.988 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005102510
2016.10.21 19:04:37.994 5: ZWDongle_Write 0013080370052d2511 (c698b541)
2016.10.21 19:04:37.995 5: SW: 010a0013080370052d251181
2016.10.21 19:04:38.997 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052d251181
2016.10.21 19:04:38.998 5: SW: 010a0013080370052d251181
2016.10.21 19:04:39.505 5: ACK received, WaitForAck=>2 for 010a0013080370052d251181
2016.10.21 19:04:39.515 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:39.516 5: SW: 06
2016.10.21 19:04:39.518 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:39.520 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:39.586 4: ZWDongle_Read ZWDongle_0: rcvd 001311010008 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:39.587 5: SW: 06
2016.10.21 19:04:39.588 5: device ack reveived, removing 010a0013080370052d251181 from dongle sendstack
2016.10.21 19:04:39.590 5: ZWDongle_0 dispatch 001311010008
2016.10.21 19:04:39.590 4: CMD:ZW_SEND_DATA ID:01 ARG:0008 CB:11
2016.10.21 19:04:39.591 2: ZWDongle_0 transmit NO_ACK for CB 11, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:42.997 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370052d2511
2016.10.21 19:04:43.004 5: ZWDongle_Write 0013080370052a2512 (c698b541)
2016.10.21 19:04:43.005 5: SW: 010a0013080370052a251285
2016.10.21 19:04:44.007 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052a251285
2016.10.21 19:04:44.008 5: SW: 010a0013080370052a251285
2016.10.21 19:04:45.009 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052a251285
2016.10.21 19:04:45.010 5: SW: 010a0013080370052a251285
2016.10.21 19:04:45.277 5: ACK received, WaitForAck=>2 for 010a0013080370052a251285
2016.10.21 19:04:45.279 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:45.280 5: SW: 06
2016.10.21 19:04:45.282 5: ZWDongle_0 dispatch 011300
2016.10.21 19:04:45.283 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:04:45.285 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:45.286 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:45.457 4: ZWDongle_Read ZWDongle_0: rcvd 001312010012 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:45.458 5: SW: 06
2016.10.21 19:04:45.460 5: device ack reveived, removing 010a0013080370052a251285 from dongle sendstack
2016.10.21 19:04:45.461 5: ZWDongle_0 dispatch 001312010012
2016.10.21 19:04:45.462 4: CMD:ZW_SEND_DATA ID:01 ARG:0012 CB:12
2016.10.21 19:04:45.462 2: ZWDongle_0 transmit NO_ACK for CB 12, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:48.007 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:13080370052a2512
2016.10.21 19:04:48.013 5: ZWDongle_Write 0013080370052a2512 (c698b541)
2016.10.21 19:04:48.015 5: SW: 010a0013080370052a251285
2016.10.21 19:04:48.018 5: ACK received, WaitForAck=>2 for 010a0013080370052a251285
2016.10.21 19:04:48.026 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:48.027 5: SW: 06
2016.10.21 19:04:48.029 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:48.062 4: ZWDongle_Read ZWDongle_0: rcvd 001312010005 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:48.062 5: SW: 06
2016.10.21 19:04:48.064 5: device ack reveived, removing 010a0013080370052a251285 from dongle sendstack
2016.10.21 19:04:48.065 5: ZWDongle_0 dispatch 001312010005
2016.10.21 19:04:48.066 4: CMD:ZW_SEND_DATA ID:01 ARG:0005 CB:12
2016.10.21 19:04:48.067 2: ZWDongle_0 transmit NO_ACK for CB 12, target ZWave_SWITCH_BINARY_8
2016.10.21 19:04:53.018 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370052a2512
2016.10.21 19:04:53.025 5: ZWDongle_Write 0013080370052f2513 (c698b541)
2016.10.21 19:04:53.026 5: SW: 010a0013080370052f251381
2016.10.21 19:04:53.726 5: ACK received, WaitForAck=>2 for 010a0013080370052f251381
2016.10.21 19:04:53.738 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:53.739 5: SW: 06
2016.10.21 19:04:53.741 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:55.745 4: no response from device, removing 010a0013080370052f251381 from dongle sendstack
2016.10.21 19:04:58.027 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080370052f2513
2016.10.21 19:04:58.034 5: ZWDongle_Write 001308037005332514 (c698b541)
2016.10.21 19:04:58.035 5: SW: 010a0013080370053325149a
2016.10.21 19:04:59.037 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370053325149a
2016.10.21 19:04:59.038 5: SW: 010a0013080370053325149a
2016.10.21 19:04:59.530 5: ACK received, WaitForAck=>2 for 010a0013080370053325149a
2016.10.21 19:04:59.541 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:04:59.542 5: SW: 06
2016.10.21 19:04:59.544 5: ZWDongle_0 dispatch 011301
2016.10.21 19:04:59.546 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:04:59.634 4: ZWDongle_Read ZWDongle_0: rcvd 00131401000a (request ZW_SEND_DATA), sending ACK
2016.10.21 19:04:59.635 5: SW: 06
2016.10.21 19:04:59.637 5: device ack reveived, removing 010a0013080370053325149a from dongle sendstack
2016.10.21 19:04:59.637 5: ZWDongle_0 dispatch 00131401000a
2016.10.21 19:04:59.638 4: CMD:ZW_SEND_DATA ID:01 ARG:000a CB:14
2016.10.21 19:04:59.639 2: ZWDongle_0 transmit NO_ACK for CB 14, target ZWave_SWITCH_BINARY_8
2016.10.21 19:05:03.037 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005332514
2016.10.21 19:05:03.044 5: ZWDongle_Write 001308037005232515 (c698b541)
2016.10.21 19:05:03.045 5: SW: 010a0013080370052325158b
2016.10.21 19:05:04.047 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052325158b
2016.10.21 19:05:04.048 5: SW: 010a0013080370052325158b
2016.10.21 19:05:05.049 2: ZWDongle_ProcessSendStack: no ACK, resending message 010a0013080370052325158b
2016.10.21 19:05:05.050 5: SW: 010a0013080370052325158b
2016.10.21 19:05:05.272 5: ACK received, WaitForAck=>2 for 010a0013080370052325158b
2016.10.21 19:05:05.274 4: ZWDongle_Read ZWDongle_0: rcvd 011300 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:05:05.275 5: SW: 06
2016.10.21 19:05:05.277 5: ZWDongle_0 dispatch 011300
2016.10.21 19:05:05.278 2: ERROR: cannot SEND_DATA to ZWave_SWITCH_BINARY_8: transmit queue overflow
2016.10.21 19:05:05.280 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:05:05.281 4: ZWDongle_Read ZWDongle_0: CAN received
2016.10.21 19:05:05.473 4: ZWDongle_Read ZWDongle_0: rcvd 001315010014 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:05:05.474 5: SW: 06
2016.10.21 19:05:05.475 5: device ack reveived, removing 010a0013080370052325158b from dongle sendstack
2016.10.21 19:05:05.476 5: ZWDongle_0 dispatch 001315010014
2016.10.21 19:05:05.477 4: CMD:ZW_SEND_DATA ID:01 ARG:0014 CB:15
2016.10.21 19:05:05.478 2: ZWDongle_0 transmit NO_ACK for CB 15, target ZWave_SWITCH_BINARY_8
2016.10.21 19:05:08.046 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for get:1308037005232515
2016.10.21 19:05:08.052 5: ZWDongle_Write 001308037005232515 (c698b541)
2016.10.21 19:05:08.053 5: SW: 010a0013080370052325158b
2016.10.21 19:05:08.056 5: ACK received, WaitForAck=>2 for 010a0013080370052325158b
2016.10.21 19:05:08.065 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:05:08.065 5: SW: 06
2016.10.21 19:05:08.067 5: ZWDongle_0 dispatch 011301
2016.10.21 19:05:08.088 4: ZWDongle_Read ZWDongle_0: rcvd 001315010003 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:05:08.089 5: SW: 06
2016.10.21 19:05:08.091 5: device ack reveived, removing 010a0013080370052325158b from dongle sendstack
2016.10.21 19:05:08.092 5: ZWDongle_0 dispatch 001315010003
2016.10.21 19:05:08.093 4: CMD:ZW_SEND_DATA ID:01 ARG:0003 CB:15
2016.10.21 19:05:08.093 2: ZWDongle_0 transmit NO_ACK for CB 15, target ZWave_SWITCH_BINARY_8
2016.10.21 19:05:13.055 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:1308037005232515
2016.10.21 19:05:14.496 4: ZWDongle_Read ZWDongle_0: rcvd 001315010284 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:05:14.497 5: SW: 06
2016.10.21 19:05:14.499 5: ZWDongle_0 dispatch 001315010284
2016.10.21 19:05:14.500 4: CMD:ZW_SEND_DATA ID:01 ARG:0284 CB:15
2016.10.21 19:05:14.501 2: ZWDongle_0 transmit NO_ACK for CB 15, target ZWave_SWITCH_BINARY_8
2016.10.21 19:05:17.928 4: ZWDongle_Read ZWDongle_0: rcvd 0013150103db (request ZW_SEND_DATA), sending ACK
2016.10.21 19:05:17.929 5: SW: 06
2016.10.21 19:05:17.931 5: ZWDongle_0 dispatch 0013150103db
2016.10.21 19:05:17.932 4: CMD:ZW_SEND_DATA ID:01 ARG:03db CB:15
2016.10.21 19:05:17.933 2: ZWDongle_0 transmit NO_ACK for CB 15, target ZWave_SWITCH_BINARY_8
2016.10.21 19:06:09.580 3: ZWave get ZWave_SWITCH_BINARY_8 version 
2016.10.21 19:06:09.581 5: ZWDongle_Write 0013080286112516 (c698b541)
2016.10.21 19:06:09.581 5: SW: 010900130802861125164b
2016.10.21 19:06:09.584 5: ACK received, WaitForAck=>2 for 010900130802861125164b
2016.10.21 19:06:09.592 4: ZWDongle_Read ZWDongle_0: rcvd 011301 (answer ZW_SEND_DATA), sending ACK
2016.10.21 19:06:09.593 5: SW: 06
2016.10.21 19:06:09.594 5: ZWDongle_0 dispatch 011301
2016.10.21 19:06:11.596 4: no response from device, removing 010900130802861125164b from dongle sendstack
2016.10.21 19:06:14.582 2: ZWave: No ACK from ZWave_SWITCH_BINARY_8 after 5s for sentget:13080286112516
2016.10.21 19:06:19.394 4: ZWDongle_Read ZWDongle_0: rcvd 0013160103d5 (request ZW_SEND_DATA), sending ACK
2016.10.21 19:06:19.395 5: SW: 06
2016.10.21 19:06:19.397 5: ZWDongle_0 dispatch 0013160103d5
2016.10.21 19:06:19.398 4: CMD:ZW_SEND_DATA ID:01 ARG:03d5 CB:16
2016.10.21 19:06:19.399 2: ZWDongle_0 transmit NO_ACK for CB 16, target ZWave_SWITCH_BINARY_8

List Wall Plug

Code Auswählen


Internals: 
   DEF        c698b541 8 
   IODev      ZWDongle_0 
   LASTInputDev ZWDongle_0 
   MSGCNT     22 
   NAME       ZWave_SWITCH_BINARY_8 
   NR         69 
   STATE      on 
   TYPE       ZWave 
   ZWDongle_0_MSGCNT 22 
   ZWDongle_0_RAWMSG 0013160103d5 
   ZWDongle_0_TIME 2016-10-21 19:06:19 
   ZWaveSubDevice no 
   homeId     c698b541 
   isWakeUp 
   lastMsgSent 1477069569.58113 
   nodeIdHex  08 
   Readings: 
     2016-10-21 19:05:05   SEND_DATA       failed:00 
     2016-10-21 18:36:50   UNPARSED        BASIC 052006380110 
     2016-10-21 18:40:13   assocGroup_1    Max 5 Nodes ZWDongle_0 
     2016-10-21 18:40:19   assocGroup_2    Max 5 Nodes 
     2016-10-21 18:40:19   assocGroup_3    Max 1 Nodes ZWDongle_0 
     2016-10-21 18:40:12   assocGroups     3 
     2016-10-21 18:36:44   configActionInCaseOfExceedingDefined52 2And3Combined 
     2016-10-21 18:36:50   configAlwaysOnFunction functionInactive 
     2016-10-21 18:36:55   configLEDRingIlluminationColourAtTheZ63 LEDRingFlashesRedBlueWhite 
     2016-10-21 18:36:55   configLEDRingIlluminationColourWhen61 UsingFullSpectrumOfAvailable1 
     2016-10-21 18:37:01   configLEDRingIlluminationColourWhen62 illuminationTurnedOffCompletely 
     2016-10-21 18:37:19   configMeteringEnergyConsumedByTheWall49 functionInactive 
     2016-10-21 18:37:01   configOveloadSafetySwitch 65535 
     2016-10-21 18:37:01   configPowerLoadWhichWhenExceededMakes60 25000 
     2016-10-21 18:37:07   configPowerReportingFrequency 30 
     2016-10-21 18:37:07   configRememberDeviceStatusAfterPower16 WallPlugMemorizesItsStateAfterA1 
     2016-10-21 18:37:08   configReportingChangesInEnergyConsumed45 10 
     2016-10-21 18:37:14   configStandardPowerLoadReporting 15 
     2016-10-21 18:37:19   configUPValue   500 
     2016-10-20 22:14:51   energy          0 kWh 
     2016-10-20 22:13:34   model           FIBARO System FGWPE Wall Plug 
     2016-10-20 22:13:34   modelConfig     fibaro/fgwpe.xml 
     2016-10-20 22:13:34   modelId         010f-0600-1000 
     2016-10-21 18:55:35   neighborList    ZWDongle_0 UNKNOWN_5 
     2016-10-21 18:57:52   power           0.0 W 
     2016-10-20 22:14:52   reportedState   off 
     2016-10-21 18:58:11   state           on 
     2016-10-21 18:55:16   timeToAck       0.086 
     2016-10-21 19:06:19   transmit        NO_ACK 
     2016-10-21 18:39:57   version         Lib 3 Prot 3.52 App 25.25 
Attributes: 
   IODev      ZWDongle_0 
   classes    MANUFACTURER_SPECIFIC VERSION CONFIGURATION ASSOCIATION MULTI_CHANNEL_ASSOCIATION SWITCH_BINARY POWERLEVEL METER SENSOR_MULTILEVEL FIRMWARE_UPDATE_MD MARK SWITCH_BINARY METER SENSOR_MULTILEVEL 
   room       ZWave

List USB_Dongle:

Code Auswählen


Internals: 
   CallbackNr 0 
   Clients    :ZWave: 
   DEF        /dev/ttyACM0@115200 
   DeviceName /dev/ttyACM0@115200 
   FD         19 
   MaxSendRetries 3 
   NAME       ZWDongle_0 
   NR         65 
   PARTIAL 
   RAWMSG     0013160103d5 
   ReadTime   1477069579.39443 
   STATE      Initialized 
   SendRetries 0 
   SendTime   1477069569.58175 
   TYPE       ZWDongle 
   WaitForAck 0 
   ZWDongle_0_MSGCNT 50 
   ZWDongle_0_TIME 2016-10-21 19:06:19 
   homeId     c698b541 
   nodeIdHex  01 
   nrNAck     0 
   Matchlist: 
     1:ZWave    .* 
   Readings: 
     2016-10-21 19:01:13   caps            Vers:5 Rev:5 ManufID:0115 ProductType:0400 ProductID:0001 SERIAL_API_GET_INIT_DATA SERIAL_API_APPL_NODE_INFORMATION APPLICATION_COMMAND_HANDLER ZW_GET_CONTROLLER_CAPABILITIES SERIAL_API_SET_TIMEOUTS SERIAL_API_GET_CAPABILITIES SERIAL_API_SOFT_RESET UNKNOWN_09 UNKNOWN_0a ZW_SET_R_F_RECEIVE_MODE ZW_SET_SLEEP_MODE ZW_SEND_NODE_INFORMATION ZW_SEND_DATA ZW_SEND_DATA_MULTI ZW_GET_VERSION ZW_SEND_DATA_ABORT ZW_R_F_POWER_LEVEL_SET ZW_SEND_DATA_META ZW_GET_RANDOM MEMORY_GET_ID MEMORY_GET_BYTE MEMORY_PUT_BYTE MEMORY_GET_BUFFER MEMORY_PUT_BUFFER FLASH_AUTO_PROG_SET UNKNOWN_28 NVM_GET_ID NVM_EXT_READ_LONG_BUFFER NVM_EXT_WRITE_LONG_BUFFER NVM_EXT_READ_LONG_BYTE NVM_EXT_WRITE_LONG_BYTE ZW_GET_NODE_PROTOCOL_INFO ZW_SET_DEFAULT ZW_REPLICATION_COMMAND_COMPLETE ZW_REPLICATION_SEND_DATA ZW_ASSIGN_RETURN_ROUTE ZW_DELETE_RETURN_ROUTE ZW_REQUEST_NODE_NEIGHBOR_UPDATE ZW_APPLICATION_UPDATE ZW_ADD_NODE_TO_NETWORK ZW_REMOVE_NODE_FROM_NETWORK ZW_CREATE_NEW_PRIMARY ZW_CONTROLLER_CHANGE ZW_SET_LEARN_MODE ZW_ASSIGN_SUC_RETURN_ROUTE ZW_REQUEST_NETWORK_UPDATE ZW_SET_SUC_NODE_ID ZW_DELETE_SUC_RETURN_ROUTE ZW_GET_SUC_NODE_ID ZW_SEND_SUC_ID ZW_EXPLORE_REQUEST_INCLUSION ZW_REQUEST_NODE_INFO ZW_REMOVE_FAILED_NODE_ID ZW_IS_FAILED_NODE ZW_REPLACE_FAILED_NODE UNKNOWN_66 UNKNOWN_67 UNKNOWN_78 GET_ROUTING_TABLE_LINE LOCK_ROUTE_RESPONSE UNKNOWN_92 UNKNOWN_93 UNKNOWN_98 ZW_SET_WUT_TIMEOUT ZW_WATCHDOG_ENABLE ZW_WATCHDOG_DISABLE ZW_WATCHDOG_CHECK ZW_SET_EXT_INT_LEVEL ZW_RF_POWERLEVEL_GET ZW_TYPE_LIBRARY ZW_SEND_TEST_FRAME ZW_GET_PROTOCOL_STATUS WATCHDOG_START WATCHDOG_STOP UNKNOWN_d4 UNKNOWN_ef ZME_FREQ_CHANGE ZME_BOOTLOADER_FLASH UNKNOWN_f5 
     2016-10-21 19:01:13   ctrlCaps        PRIMARY 
     2016-10-21 19:01:13   homeId          HomeId:c698b541 CtrlNodeIdHex:01 
     2016-10-20 22:31:52   nodeList        ZWDongle_0 UNKNOWN_3 UNKNOWN_4 UNKNOWN_5 UNKNOWN_6 UNKNOWN_7 ZWave_SWITCH_BINARY_8 
     2016-10-21 19:01:13   random          97d8c72eb052c977bd122a43c02440d03bdb216335aa738a97b6e9947551a156 
     2016-10-21 19:01:13   state           Initialized 
     2016-10-21 19:01:13   sucNodeId       no 
     2016-10-20 22:58:09   timeouts        01060803 
     2016-10-20 22:30:45   version         Z-Wave 4.05 STATIC_CONTROLLER 
   SendStack: 
Attributes: 
   verbose    5

jeep · 21 Oktober 2016, 20:11:22

ZitatAn der Reichweite kann es eigentlich nicht liegen, denn der Plug leuchtet grün, wenn man ihn kurz rein und raus steckt.

Das hat damit nichts zu tun, selbst wenn er nicht inkludiert ist zeigt er dieses Verhalten.
Sieht für mich doch nach Reichweiten Problem aus. Vor allem da dass das einzige Gerät im Netz ist.

rudolfkoenig · 21 Oktober 2016, 20:16:03

ZitatKann man das Timeout evtl. hoch setzen?

Nicht ohne weiteres. Und ein Timeout von 10s waere auch nicht gesund. 10ms sind normal.
Da muss nach was anderes kaputt sein, die vielen CANs sind auch nicht normal.

Jackson · 21 Oktober 2016, 21:06:54

Zitat von: rudolfkoenig am 21 Oktober 2016, 20:16:03
Nicht ohne weiteres. Und ein Timeout von 10s waere auch nicht gesund. 10ms sind normal.
Da muss nach was anderes kaputt sein, die vielen CANs sind auch nicht normal.

Kaput klingt so böse...

Hab's frisch bestellt zum Testen

Zitat von: jeep am 21 Oktober 2016, 20:11:22
Das hat damit nichts zu tun, selbst wenn er nicht inkludiert ist zeigt er dieses Verhalten.
Sieht für mich doch nach Reichweiten Problem aus. Vor allem da dass das einzige Gerät im Netz ist.

OK... wohl doch die Reichweite. Ich habe den Wall Plug nun mal in dem gleichen Raum gesteckt und es funktioniert.

Gibs da Erfahrungen mit anderen ZWave-Sticks, zwecks der Reichweite?

throbin · 21 Oktober 2016, 21:32:38

Hi,

ich betreibe seit Monaten mein Netz mit dem Stick und bisher keine Reichweitenprobleme. Der Stick hängt mit dem Pi3 an der Wand in der Küche und sendet bis über 2 Betondecken unters Dach hoch. Vielleicht muss die Position geändert werden, meiner zeigt nach oben.

LG

jeep · 21 Oktober 2016, 21:38:13

Zitat von: Jackson am 21 Oktober 2016, 21:06:54
Kaput klingt so böse... Hab's frisch bestellt zum Testen

OK... wohl doch die Reichweite. Ich habe den Wall Plug nun mal in dem gleichen Raum gesteckt und es funktioniert.

Gibs da Erfahrungen mit anderen ZWave-Sticks, zwecks der Reichweite?

Je mehr devices sich in Deinem Zwave Netz befinden desto kleiner werden Deine Reichweitenprobleme. Hängt natürlich alles von der Gebäudeinfrastruktur ab. Betonwände mit starker Stahlarmierung können das Signal stark dämpfen. Da kann nach 5 -10 Meter dahinter Schluß sein.

Aber alles kein Problem wenn andere (netzversorgte) Geräte dazukommen. Die Devices routen dann untereinander bis zum Controller. Standard im Gebäude sollten 30 Meter sein, Freifeld über 100. Wird aber erst mit ZWave plus devices besser.
Nur nicht zu schnell aufgeben.

rudolfkoenig · 21 Oktober 2016, 21:51:58

Und da die Hersteller das natuerlich wissen, bauen sie miserable Antennen in den Geraeten ein.

Jackson · 23 Oktober 2016, 19:57:14

Zitat von: throbin am 21 Oktober 2016, 21:32:38
Hi,

ich betreibe seit Monaten mein Netz mit dem Stick und bisher keine Reichweitenprobleme. Der Stick hängt mit dem Pi3 an der Wand in der Küche und sendet bis über 2 Betondecken unters Dach hoch. Vielleicht muss die Position geändert werden, meiner zeigt nach oben.

LG

OK.. ich hab den PI jetzt mal auf meinen Küchenschrank gelegt. Es sieht erstmal gut aus. Ich werd's mal beobachten...