Multi Sensor 6 stopped monitoring motion detection

I have ~23 hardwirded Aeon multi sensor 6 (ZW100) installed throughout my house and although they are sometime slow to respond to motion and trigger events, they have all worked fine for the last five years, until just recently. I'm now finding that all 23 sensors have simutaniously stopped responding to any motion ie. turn on lights when detecting motion.

I thought this might be a device issue, but for all devices to fail at the same time seems to point to something else.

Before I start to unpair and repair each device, and run the risk that the system may start to literually go on the blink (# of devices starts to repeatly turn on & off simultaneously when trying to pair this type of device, does not happen with any other devices), can someone help me to determine what may be causing this issue and the best cause of action?

I use these throughout my home and can't say I've run across this behavior. I don't have as many as you have, probably only 10 or so, but I doubt the sheer number of devices would be relevant to this problem.

Have you recently done a Z-wave optimization?

[jay (support)]

If you send a status request to those sensors, do you get any errors in the Event Log window?

Last update for each device is showing current date & time, yet the "Send Status Request" button is greyed out on all devices (See screen shot below). I have just taken a screen shot of Motion, Temperature, Humidity, Illuminance & Ultraviolet status for all devices, as I suspect that none of the values are being updated, except maybe motion sensors. This would explain why lights are not turning on as each trigger condition is reliant on illuminance level.

I have performed a network optimization with no change.

Chiming in here:

I have had a bunch of the previous motion sensor versions fail - almost all at once. The issue seemed to be they had suddenly failed to find any neighbours at all, and hence all but those very close failed to work.. Nothing, including firmware updates and resetting fixed. Something had gone

Maybe print the device info to log (right click) and post here to see..

Haven’t seen it for this version of multisensor… but ….


Sent from my iPad using Tapatalk

Interesting,thanks Glenn, please see sensor information below as requested.

Embedded script executor host2 started
Script address : 62
allowOnStateChange : True
allowSensorValueChange : False
batteryLevel : None
buttonGroupCount : 0
configured : True
description : Kitchen
deviceTypeId : zwOnOffSensorType
displayStateId : onOffState
displayStateImageSel : SensorOff
displayStateValRaw : False
displayStateValUi : off
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 621032056
globalProps : MetaProps : (dict)
com.perceptiveautomation.indigoplugin.zwave : (dict)
AllowOnStateChange : true (bool)
SupportsOnState : true (bool)
SupportsSensorValue : false (bool)
SupportsStatusRequest : false (bool)
address : 62 (integer)
indigoObjVersion : 10 (integer)
userEnergyPollingEnabled : false (bool)
version : 1.14 (string)
zwClassCmdBase : 49 (integer)
zwDevSubIndex : 1 (integer)
zwManufactureId : 134 (integer)
zwManufactureName : Aeon Labs (string)
zwModelId : 33685604 (integer)
zwModelName : Multi Sensor 6 (ZW100) (string)
zwShowDumpDevToLog : false (bool)
zwShowEnergyPollingUI : false (bool)
zwShowMainUI : false (bool)
zwShowManualModifyConfigParmUI : false (bool)
zwShowPollingUI : false (bool)
zwShowSubmitModelInfoUI : false (bool)
zwShowWakeIntervalUI : false (bool)
id : 1837948810
lastChanged : 2024-04-27 22:25:42
lastSuccessfulComm : 2024-04-27 22:25:42
model : Multi Sensor 6 (ZW100)
name : Kitchen - Tamper
onState : False
ownerProps : com.perceptiveautomation.indigoplugin.zwave : (dict)
AllowOnStateChange : true (bool)
SupportsOnState : true (bool)
SupportsSensorValue : false (bool)
SupportsStatusRequest : false (bool)
address : 62 (integer)
indigoObjVersion : 10 (integer)
userEnergyPollingEnabled : false (bool)
version : 1.14 (string)
zwClassCmdBase : 49 (integer)
zwDevSubIndex : 1 (integer)
zwManufactureId : 134 (integer)
zwManufactureName : Aeon Labs (string)
zwModelId : 33685604 (integer)
zwModelName : Multi Sensor 6 (ZW100) (string)
zwShowDumpDevToLog : false (bool)
zwShowEnergyPollingUI : false (bool)
zwShowMainUI : false (bool)
zwShowManualModifyConfigParmUI : false (bool)
zwShowPollingUI : false (bool)
zwShowSubmitModelInfoUI : false (bool)
zwShowWakeIntervalUI : false (bool)
pluginId : com.perceptiveautomation.indigoplugin.zwave
pluginProps : emptyDict : (dict)
protocol : ZWave
remoteDisplay : True
sensorValue : None
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
onOffState : off (on/off bool)
subModel : Tamper,ui=Tamper
subType : Tamper
supportsAllLightsOnOff : False
supportsAllOff : False
supportsOnState : True
supportsSensorValue : False
supportsStatusRequest : False
version : 1.14

Just a shot in the dark, but have you verified that the motion sensor device has "Com Enabled" checked when you look at the my house window?

Sorry might need the Z wave logging info - I’m away at moment - but think it is there for all devices (not just those not paired)

Glenn


Sent from my iPhone using Tapatalk

I seem to have resolved this issue, it appears that the z-stick had hung itself.

I tried to re optimize the all devices last night, only to find that move devices had become unresponsive (No acknowledgement) this morning, which resulted in a number of failed triggers & schedules. I removed the -stick from my mini mac and reinserted it after a brief pause, which seemed to correct everything, unresponsive devices are now responding and al the Multi sensor 6's are updating the various fields (temperature, humidity, illuminance), which is great.

On reflection, I recently had a switch device that was not communicate status to Indigo when manually operated (turned on the switch in the room, but it remained "off" in Indigo). I removed the Z-stick from the mini mac to exclude the device using the button on the Z-stick, I then reinserted the z-stick in the mini mac to re-include the device. This was successful after a number of attempts. I suspect that the removal of the z-stick may have interfered with the connection with Indigo to caused device drop-outs.

I would be interested to hear if there is a safer way to exclude and include devices to the network. I find it extremely time consuming when trying to exclude a device from the network which is located some distance from the server (Start controller exclusion mode in Indigo, go to the device and press the relevant button to commence the exclusion process, go back to the server only to find that nothing happen, then go back to the device and start the process all over again). I find it easier to just remove the z-stick, to the device, press hold the button on the z-stick until it flashes yellow, then press the button on the device until the light on the z-stick turns blue.

* only to find that more devices

I use the Jump app on my iPad or iPhone to remotely connect to my Mac mini running Indigo. I can then be at the device and see/control my Mac mini.


Sent from my iPhone using Tapatalk