Probleme beim Unpairing von Aeotec Door/Window Sensor 6

Begonnen von Mellomania, 09 April 2018, 17:35:54

Vorheriges Thema - Nächstes Thema

Mellomania

Beim Unpairing von Aeotec Door/Window Sensor 6 tritt folgendes Problem auf:
Dem eventlog zufolge wurde das device ungepaired:
2018-04-09 17:23:38 ZWDongle ZWDongle_1 removeNode on
2018-04-09 17:23:38 ZWDongle ZWDongle_1 ZW_REMOVE_NODE_FROM_NETWORK learnReady
2018-04-09 17:23:45 ZWave ZWave_SENSOR_NOTIFICATION_105 basicSet: 255
2018-04-09 17:23:45 ZWDongle ZWDongle_1 ZW_REMOVE_NODE_FROM_NETWORK nodeFound
2018-04-09 17:23:46 ZWDongle ZWDongle_1 ZW_REMOVE_NODE_FROM_NETWORK slave
2018-04-09 17:23:46 ZWDongle ZWDongle_1 ZW_REMOVE_NODE_FROM_NETWORK done

trotzdem kommen die events danach noch an (siehe Zeitstempel):
2018-04-09 17:23:56 ZWave ZWave_SENSOR_NOTIFICATION_105 basicSet: 0
2018-04-09 17:23:56 ZWave ZWave_SENSOR_NOTIFICATION_105 basicSet: 255


Der Aeotec Sensor hat folgende Definition:
defmod ZWave_SENSOR_NOTIFICATION_105 ZWave ca89f3b0 105
attr ZWave_SENSOR_NOTIFICATION_105 IODev ZWDongle_1
attr ZWave_SENSOR_NOTIFICATION_105 classes ZWAVEPLUS_INFO SENSOR_BINARY BATTERY WAKE_UP CONFIGURATION ASSOCIATION ASSOCIATION_GRP_INFO ALARM VERSION MANUFACTURER_SPECIFIC POWERLEVEL FIRMWARE_UPDATE_MD DEVICE_RESET_LOCALLY MARK
attr ZWave_SENSOR_NOTIFICATION_105 room ZWave
attr ZWave_SENSOR_NOTIFICATION_105 vclasses ALARM:4 ASSOCIATION:2 ASSOCIATION_GRP_INFO:1 BATTERY:1 CONFIGURATION:1 DEVICE_RESET_LOCALLY:1 FIRMWARE_UPDATE_MD:2 MANUFACTURER_SPECIFIC:2 POWERLEVEL:1 SENSOR_BINARY:1 VERSION:2 WAKE_UP:2 ZWAVEPLUS_INFO:2

setstate ZWave_SENSOR_NOTIFICATION_105 wakeupInterval 86400 1
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:23:01 CMD ZW_APPLICATION_UPDATE
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:26:12 basicSet 255
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:19:34 config_9 256
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:19:30 model Aeotec ZW112 Door Window Sensor 6
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:19:30 modelConfig aeotec/zw112.xml
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:19:30 modelId 0086-0002-0070
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:19:27 state wakeupInterval 86400 1
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:23:02 timeToAck 1.713
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:23:07 transmit NO_ACK
setstate ZWave_SENSOR_NOTIFICATION_105 2018-04-09 17:23:01 wakeup notification

und das Gateway/Dongle sieht folgendermassend aus:
defmod ZWDongle_1 ZWDongle /dev/ttyACM0@115200
attr ZWDongle_1 homeId ca89f3b0
attr ZWDongle_1 networkKey 5967ec272d6bbc210235961a767215ba
attr ZWDongle_1 room ZWave

setstate ZWDongle_1 2018-04-09 17:10:23 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 ZW_GET_PRIORITY_ROUTE ZW_SET_PRIORITY_ROUTE 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 ZME_CAPABILITIES
setstate ZWDongle_1 2018-04-09 17:10:23 ctrlCaps PRIMARY
setstate ZWDongle_1 2018-04-09 17:10:23 homeId HomeId:ca89f3b0 CtrlNodeIdHex:01
setstate ZWDongle_1 2018-04-05 09:13:53 nodeList ZWDongle_1 ZWave_SWITCH_MULTILEVEL_13 ZWave_SENSOR_NOTIFICATION_92 ZWave_SENSOR_NOTIFICATION_96
setstate ZWDongle_1 2018-04-09 17:10:24 random 16fc60917b990e4e0a395c2f6feebd58cbe821c4778175fde450aef417a62785
setstate ZWDongle_1 2018-04-09 17:10:24 state Initialized
setstate ZWDongle_1 2018-04-09 17:10:23 sucNodeId no
setstate ZWDongle_1 2017-12-01 16:18:55 version Z-Wave 4.05 STATIC_CONTROLLER


Das Problem tritt sporadisch auf, d.h. mehrere Male hat es funktioniert, nur ab und an ist er weiterhin gepaired. Zu erkennen ist das nur an der Farbe der LED des Sensors.
Die benutzte Fhem-Version ist:
Latest Revision: 16574