This is a motion/temp sensor - Seems that rebooting my PC has made the message go away.
Motion Sensor error
- 74 Views
- Last Post 12 September 2014
jschiesser
posted this
11 September 2014
jschiesser
posted this
12 September 2014
This is a motion/temp sensor - Seems that rebooting my PC has made the message go away.
Ryan-Scott
posted this
12 September 2014
What is causing this? How/do I need to fix it?
9/11/2014 4:26:25 PM: SceneTrigger Alarm - Motion: Device Motion:Bsmt & Temp changed to 255. Running script activateScene.cs.
9/11/2014 4:26:25 PM: SceneTrigger Alarm - Motion: Script aborted because conditions were not met. Condition type StateOfDevice did not pass. Extra Info: |47e2890b-8e32-471c-a6d9-60a7363de7fb| level is |=| |255|
9/11/2014 4:26:25 PM: Unprocessed parameter ZensorNetSourceNodeID, value=0 from node 22 alarmreport
9/11/2014 4:26:25 PM: Unprocessed parameter ZWaveAlarmStatus, value=255 from node 22 alarmreport
9/11/2014 4:26:25 PM: parameter ZWaveAlarmType, value=7 from node 22 alarmreport
9/11/2014 4:26:25 PM: zwavealarmtype set with value of 7 from value 7
9/11/2014 4:26:25 PM: parameter ZWaveAlarmEvent, value=2 from node 22 alarmreport
9/11/2014 4:26:25 PM: Unprocessed parameter NumberofEventParameters, value=0 from node 22 alarmreport
9/11/2014 4:26:25 PM: NOTIFICATIONREPORT unprocessed!
9/11/2014 4:26:25 PM: NOTIFICATIONREPORT unprocessed!
9/11/2014 4:29:31 PM: Unprocessed parameter ZensorNetSourceNodeID, value=0 from node 22 alarmreport
9/11/2014 4:29:31 PM: Unprocessed parameter ZWaveAlarmStatus, value=255 from node 22 alarmreport
9/11/2014 4:29:31 PM: parameter ZWaveAlarmType, value=7 from node 22 alarmreport
9/11/2014 4:29:31 PM: zwavealarmtype set with value of 7 from value 7
9/11/2014 4:29:31 PM: parameter ZWaveAlarmEvent, value=2 from node 22 alarmreport
9/11/2014 4:29:31 PM: Unprocessed parameter NumberofEventParameters, value=0 from node 22 alarmreport
9/11/2014 4:29:31 PM: NOTIFICATION_REPORT unprocessed!
Are you talking about the unprocessed messages? What type of device is it and do you know what "alarm" the device is trying to report?
