ZWave No ACK

[Ralf.E]

Moin,

ich beobachte bei mir seit einiger Zeit, dass relativ häufig die Kommunikation zwischen ZWave-Dongle und Devices im Log mit einem NoACK gelistet werden und habe nicht wirklich eine Idee wo ich ansetzen kann. Im Großen und Ganzen läuft alles und ich merke die Aussetzer primär daran, dass Wakeups von Wakeup-Devices nicht immer ankommen oder Aktionen wie ein neighborUpdate nicht zu funktionieren scheinen - ein kurzer Auszug des Logs (hier jetzt nur always-on Devices):

Code Auswählen Erweitern

2018.04.05 21:12:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 21:27:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 21:27:53 2: ZWAVE1 transmit NO_ACK for CB 53, target cp_MotionSensor
2018.04.05 21:29:53 3: ZWave set ku_PlugTablet on
2018.04.05 21:41:51 2: ZWAVE1 transmit NO_ACK for CB 55, target ku_MotionSensor
2018.04.05 21:42:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 21:42:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d000225022556
2018.04.05 21:42:53 2: ZWAVE1 transmit NO_ACK for CB 56, target cp_MotionSensor
2018.04.05 21:57:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 21:57:53 2: ZWAVE1 transmit NO_ACK for CB 58, target cp_MotionSensor
2018.04.05 21:57:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d000225022558
2018.04.05 22:12:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 22:12:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d000225022559
2018.04.05 22:12:54 2: ZWAVE1 transmit NO_ACK for CB 59, target cp_MotionSensor
2018.04.05 22:27:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 22:27:53 2: ZWAVE1 transmit NO_ACK for CB 5c, target cp_MotionSensor
2018.04.05 22:41:29 2: ZWAVE1 transmit NO_ACK for CB 5d, target ku_MotionSensor
2018.04.05 22:42:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 22:42:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d00022502255e
2018.04.05 22:42:53 2: ZWAVE1 transmit NO_ACK for CB 5e, target cp_MotionSensor
2018.04.05 22:57:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 22:57:53 2: ZWAVE1 transmit NO_ACK for CB 5f, target cp_MotionSensor
2018.04.05 22:57:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d00022502255f
2018.04.05 23:12:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 23:12:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d000225022560
2018.04.05 23:12:53 2: ZWAVE1 transmit NO_ACK for CB 60, target cp_MotionSensor
2018.04.05 23:27:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 23:27:53 2: ZWave: No ACK from cp_MotionSensor after 5s for sentget:130f06600d000225022563
2018.04.05 23:27:53 2: ZWAVE1 transmit NO_ACK for CB 63, target cp_MotionSensor
2018.04.05 23:42:48 3: ZWave get cp_DayLightSensor swbStatus
2018.04.05 23:42:54 2: ZWAVE1 transmit NO_ACK for CB 67, target cp_MotionSensor


List vom Device cp_DayLightSensor und dem Parent:

Code Auswählen Erweitern


Internals:
   DEF        deefb60e 3842
   IODev      ZWAVE1
   NAME       cp_DayLightSensor
   NR         34
   STATE      off
   TYPE       ZWave
   ZWaveSubDevice yes
   endpointParent cp_MotionSensor
   homeId     deefb60e
   nodeIdHex  0f02
   READINGS:
     2018-02-28 01:25:54   UNPARSED        METER_PULSE 033503ff
     2018-04-06 06:42:53   reportedState   off
     2018-04-06 06:42:53   state           off
Attributes:
   IODev      ZWAVE1
   classes    SWITCH_BINARY
   event-on-change-reading reportedState,state
   room       Carport,ZWave

Internals:
   DEF        deefb60e 15
   IODev      ZWAVE1
   NAME       cp_MotionSensor
   NR         32
   STATE      off
   TYPE       ZWave
   ZWaveSubDevice no
   endpointChildren cp_Light_e1,cp_DayLightSensor,ZWave_Node_15.3
   homeId     deefb60e
   nodeIdHex  0f
   READINGS:
     2018-02-11 20:40:25   SEND_DATA       failed:00
     2018-04-05 22:27:50   UNPARSED        ZIP_PORTAL 07610c02002503ff
     2017-08-06 17:56:31   assocGroup_1    Max 5 Nodes
     2017-05-03 19:37:28   assocGroup_2    Max 5 Nodes
     2017-05-03 19:37:28   assocGroup_3    Max 1 Nodes ZWAVE1
     2017-08-06 17:56:30   assocGroups     3
     2017-08-06 17:56:04   configALARMFLASHINGAlarmTime 600
     2017-08-06 17:56:04   configAutoOffForRelay1 0
     2017-05-03 19:19:33   configAutoOffForRelay2 0
     2017-08-06 17:56:10   configAutoOffRelayAfterSpecifiedTime ManualOverrideDisabled
     2017-08-06 17:56:10   configControlKey2Behaviour DeviceStatusIsChecked
     2017-08-06 17:56:10   configDimmerRollerShutterControl EnableDimmerRollerShutterControl
     2017-08-06 17:56:11   configEnableDisableALLONOFF ALLONActiveALLOFFActive
     2017-08-06 17:56:11   configInputsBehaviour FollowSwitchContactClosedONOpenO1
     2017-08-06 17:56:11   configInputsButtonSwitchConfiguration BiStableInputSwitch
     2016-12-04 12:39:56   configManagingTheTransmissionOfControl6 TheControlCommandsAreSentWhenThe0
     2016-12-04 12:39:56   configManagingTheTransmissionOfControl7 TheControlCommandsAreSentWhenThe1
     2017-08-06 17:56:12   configRelay1ResponseToGeneralAlarm ALARMFLASHINGRelayWillTurnONAndO3
     2017-08-06 17:56:12   configRelay1ResponseToSmokeCOCO2Alarm ALARMFLASHINGRelayWillTurnONAndO3
     2017-08-06 17:56:12   configRelay1ResponseToTemperatureAlarm ALARMRELAYONRelayWillTurnONUpon1
     2017-08-06 17:56:12   configRelay1ResponseToWaterFloodAlarm ALARMRELAYOFFRelayWillTurnOFF2
     2017-08-06 17:56:13   configRelay2ResponseToGeneralAlarm ALARMFLASHINGRelayWillTurnONAndO3
     2017-08-06 17:56:14   configRelay2ResponseToSmokeCOCO2Alarm ALARMFLASHINGRelayWillTurnONAndO3
     2017-08-06 17:56:14   configRelay2ResponseToTemperatureAlarm ALARMRELAYONRelayWillTurnONUpon1
     2017-05-03 19:19:35   configRelay2ResponseToWaterFloodAlarm ALARMRELAYOFFRelayWillTurnOFF2
     2017-05-03 19:19:35   configSavingStateBeforePowerFailure StateSavedAtPowerFailureAll1
     2017-05-03 19:19:35   configSeparationOfAssociationSending6 MapStatusToAllDevicesInGroup10
     2017-09-30 03:21:57   config_2        0
     2017-05-03 19:35:50   mcCapability_01 SWITCH_BINARY
     2017-05-03 19:35:51   mcCapability_02 SWITCH_BINARY
     2017-05-03 19:30:26   mcEndpoints     total 2, identical
     2017-08-07 18:10:15   mcaGroups       2
     2016-04-27 20:18:05   mcaSupportedGroupings 2
     2017-05-03 22:44:08   mca_0           Max 0
     2017-08-07 18:10:16   mca_1           Max 5 Nodes ZWAVE1:1
     2017-05-03 22:44:14   mca_2           Max 5 Nodes ZWAVE1:2
     2017-05-03 22:44:48   mca_3           Max 0
     2017-05-03 19:30:16   model           FIBARO System FGS222 Double Relay Switch 2x1.5kW
     2017-05-03 19:30:16   modelConfig     fibaro/fgs222.xml
     2017-05-03 19:30:16   modelId         010f-0202-1002
     2016-12-04 12:41:19   neighborList    tr_MotionSensor wz_JalousieFenster wz_JalousieTuer ku_MotionTablet ku_PlugTablet
     2016-12-04 12:41:34   neighborUpdate  done
     2017-05-03 19:22:59   powerlvl        current 0 remain 0
     2018-04-04 20:29:32   reportedState   off
     2018-04-04 20:29:32   state           off
     2018-03-04 22:14:31   swa             on off
     2018-04-06 03:12:51   timeToAck       1.966
     2018-04-06 06:42:56   transmit        NO_ACK
     2017-05-03 19:37:02   version         Lib 3 Prot 3.52 App 2.2
Attributes:
   IODev      ZWAVE1
   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       Carport,Terasse,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


Bei einem weiteren Device (Fibaro WallPlug) wird zum Beispiel ein 'set ku_PlugTablet neighborUpdate' mit einem 'neighborUpdate failed' vermerkt:

Code Auswählen Erweitern

Internals:
   DEF        deefb60e 21
   IODev      ZWAVE1
   LASTInputDev ZWAVE1
   MSGCNT     17
   NAME       ku_PlugTablet
   NR         115
   STATE      neighborUpdate
   TYPE       ZWave
   ZWAVE1_MSGCNT 17
   ZWAVE1_RAWMSG 000400150a32022144000005280000
   ZWAVE1_TIME 2018-04-06 10:13:18
   ZWaveSubDevice no
   cmdsPending 0
   homeId     deefb60e
   isWakeUp   
   lastMsgSent 1523002193.67343
   nodeIdHex  15
   Helper:
     DBLOG:
       energy:
         db_DataLog:
           TIME       1523002398.50042
           VALUE      13.2
   READINGS:
     2016-03-15 17:21:10   SECURITY        DISABLED (SECURITY not supported by device)
     2016-04-26 05:35:04   UNKNOWN         multilevel type  00 fl: 22 arg: 002b
     2018-02-28 03:25:38   UNPARSED        CONTROLLER_REPLICATION 06211504220000
     2017-08-21 17:52:39   assocGroup_1    Max 5 Nodes
     2017-08-21 17:52:39   assocGroup_2    Max 5 Nodes
     2017-08-21 17:52:39   assocGroup_3    Max 1 Nodes ZWAVE1
     2017-08-21 17:52:38   assocGroups     3
     2017-05-30 12:10:00   basicSet        0
     2017-10-29 14:41:34   configActionInCaseOfExceedingDefined52 2And3Combined
     2018-04-06 10:07:48   configAlarmDuration 600
     2017-10-29 14:41:34   configAlwaysOnFunction functionInactive
     2018-04-05 20:37:39   configDOWNValue 300
     2018-04-06 10:07:58   configImmediatePowerReport 80
     2018-04-06 10:07:58   configLEDRingIlluminationColourAtTheZ63 LEDRingFlashesRedBlueWhite
     2018-04-06 10:07:58   configLEDRingIlluminationColourWhen61 UsingFullSpectrumOfAvailable1
     2018-04-06 10:07:59   configLEDRingIlluminationColourWhen62 illuminationTurnedOffCompletely
     2018-04-06 10:07:59   configMeteringEnergyConsumedByTheWall49 functionInactive
     2018-04-06 10:08:00   configOveloadSafetySwitch 65535
     2018-04-06 10:08:00   configPowerLoadWhichWhenExceededMakes60 25000
     2018-04-06 10:08:00   configPowerReportingFrequency 30
     2018-04-06 10:08:00   configReactionToAlarms ALARMALL
     2018-04-06 10:08:01   configRememberDeviceStatusAfterPower16 WallPlugMemorizesItsStateAfterA1
     2018-04-06 10:08:01   configReportingChangesInEnergyConsumed45 10
     2018-04-06 10:08:01   configStandardPowerLoadReporting 15
     2017-10-29 14:41:34   configTimePeriodBetweenReportsOnPower47 3600
     2018-04-05 20:38:00   configUPValue   500
     2018-04-06 10:08:12   configWallPlugSResponseToAlarmFrames NoReaction
     2017-01-05 09:19:36   config_11       62
     2018-04-06 10:13:18   energy           13.2 kWh
     2017-06-21 10:21:51   luminance       1648 Lux
     2017-01-14 13:44:04   mcaGroups       2
     2017-01-14 13:44:05   mca_1           Max 5 Nodes ZWAVE1
     2017-01-14 13:44:05   mca_2           Max 5
     2017-04-08 12:29:42   model           FIBARO System FGWPE/F Wall Plug
     2017-04-08 12:29:42   modelConfig     fibaro/fgwpe.xml
     2017-04-08 12:29:42   modelId         010f-0600-1000
     2018-04-05 20:47:40   neighborList    ZWAVE1 tr_MotionSensor tr_Device_FGS222 cp_MotionSensor wz_JalousieFenster wz_JalousieTuer ku_MotionSensor dg_FlutSensor
     2018-04-06 10:09:59   neighborUpdate  failed
     2018-04-06 08:50:56   power           0.0 W
     2016-03-15 19:23:02   powerLevel      0
     2017-10-29 14:42:15   powerlvl        current 0 remain 0
     2018-04-05 20:47:18   reportedState   on
     2018-04-06 10:09:53   state           neighborUpdate
     2018-04-06 10:08:11   timeToAck       0.335
     2018-04-06 10:08:11   transmit        OK
     2018-03-21 20:03:45   undef           12.89 undef
     2017-10-29 14:43:03   version         Lib 3 Prot 3.52 App 25.25
     2018-02-28 13:04:22   voltage         340.17 V
Attributes:
   DbLogInclude power,energy,state
   IODev      ZWAVE1
   classes    MANUFACTURER_SPECIFIC VERSION CONFIGURATION ASSOCIATION MULTI_CHANNEL_ASSOCIATION SWITCH_BINARY POWERLEVEL METER SENSOR_MULTILEVEL FIRMWARE_UPDATE_MD MARK SWITCH_BINARY METER SENSOR_MULTILEVEL
   event-on-change-reading .*
   room       Küche,System,ZWave
   vclasses   ASSOCIATION:2 CONFIGURATION:1 FIRMWARE_UPDATE_MD:1 MANUFACTURER_SPECIFIC:1 METER:2 MULTI_CHANNEL_ASSOCIATION:2 POWERLEVEL:1 SENSOR_MULTILEVEL:2 SWITCH_BINARY:1 VERSION:1

Neustart und Power-Toggle des Raspi habe ich bereits probiert - hat jemand eine Idee wo ich ansetzen kann?

Gruß Ralf

[rudolfkoenig]

NoACK ist ein Zeichen dafuer, dass die Funk-Uebertragung nicht funktioniert, genauer: der Controller bekommt keine Bestaetigung vom Geraet.

Es gibt (gefuehlt) tausende Themen hier im Forum, die mit diesem Thema beschaeftigen, sowohl fuer andere Protokolle wie FS20/HomeMatic/EnOcean, wie auch speziell fuer ZWave, bitte da nachlesen. Kurz:
- Geraeteposition verschieben, Antennen passend ausrichten
- bessere Antennen besorgen
- Funk-Reapeater strategisch platzieren. Bei ZWave sind alle "nicht batteriebetriebene" Geraete Repeater.