Zooz ZEN25 error

The ZEN25 is always listed as a "failed" device. When synching, getting:

Z-Wave Error device "multiPlug (USB Sensor)" does not support status request command

Any way to address this error to stop the device from being listed as "failed"

Thank you!

JP

[matt (support)]

Re-sync it again and copy/paste the Event Log results showing the entire sync.

Z-Wave received "Master-Motion Sensor" status update is off
Z-Wave received "Hallway 2nd Floor-Master-Motion Sensor" status update is off
Z-Wave Syncing - started for "Master-multiPlug Behind Dresser (Master Control)"
Z-Wave Syncing - retrieved module neighbors list: 9, 15, 18, 20, 24, 26, 27, 28, 32, 92, 126, 127, 131, 140, 141, 153, 157, 162, 181, 182, 195, 196, 197, 217
Z-Wave Syncing - assigning return route to "099 - Master-multiPlug Behind Dresser (Master Control)"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Zooz - 027A, Double Plug (ZEN25) - A000A003
Z-Wave Syncing - retrieved protocol version 5.03, app version 1.00
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : Relay Power Switch (04 : 10 : 01, base 25)
Z-Wave Syncing - retrieved command classes: 20v1 25v1 27v1 5Ev1 85v1 8Ev1 59v1 55v1 86v1 72v1 5Av1 73v1 70v1 71v1 32v4 9Fv1 60v4 6Cv1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved multi-endpoint types: 1:(10 : 01), 2:(10 : 01), 3:(10 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 85 59 8E 25 32 6C 9F], 2:[5E 85 59 8E 25 32 6C 9F], 3:[5E 85 59 8E 25 32 6C 9F]
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - added group 1 association to interface
Z-Wave Syncing - retrieved parameter 1 "Power up state" is 0 "Last State"
Z-Wave Syncing - retrieved parameter 2 "Report threshold watts" is 0 watts
Z-Wave Syncing - retrieved parameter 3 "Periodic power reports" is 3600 seconds
Z-Wave Syncing - retrieved parameter 4 "Periodic energy reports" is 3600 seconds
Z-Wave Syncing - retrieved parameter 16 "Enable manual control via button" is true
Z-Wave Syncing - retrieved parameter 17 "LED behavior" is 3 "Always OFF"
Z-Wave Syncing - complete
Z-Wave sent "Master-multiPlug Behind Dresser (Master Control)" status request
Z-Wave sent "Master-multiPlug Behind Dresser (Master Control)" power status request
Z-Wave sent "Master-multiPlug Behind Dresser (Master Control)" energy status request
Z-Wave sent "Master-multiPlug Behind Dresser (Molecule Filter)" status request
Z-Wave sent "Master-multiPlug Behind Dresser (Molecule Filter)" power status request
Z-Wave sent "Master-multiPlug Behind Dresser (Molecule Filter)" energy status request
Z-Wave sent "Master-multiPlug Behind Dresser (Alexa Echo)" status request
Z-Wave sent "Master-multiPlug Behind Dresser (Alexa Echo)" power status request
Z-Wave sent "Master-multiPlug Behind Dresser (Alexa Echo)" energy status request
Z-Wave Error device "Master-multiPlug Behind Dresser (USB Sensor)" does not support status request command

[matt (support)]

Does selecting your Master-multiPlug Behind Dresser (USB Sensor) device and pressing the Turn On or Turn Off button (just to reset the state UI) change the error state?

What about plugging something drawing current from the USB port in for a few seconds and then removing it? Normally the error state will get reset whenever Indigo receives a valid command from the device for that endpoint, so that might get it out of the error state.

I'll look at modifying the definition so Indigo doesn't try to send it a status request to avoid the problem altogether.

Thanks Matt. All my ZEN25 double plug-ins throw the error for the USB port saying that the USB Port device “does not support status request command.” I just ignore the errors in the log.


Sent from my iPhone using Tapatalk

[matt (support)]

I'm tweaking the device definition for the next release which will hopefully fix the problem (after a re-sync).

[matt (support)]

This should now be fixed in Indigo 2022.2.0 which is now available.