Mimo2+ trigger issue

Ok, it's possible I don't understand how the Mimo2+ is supposed to work but I'm scratching my head on this.
I'm converting from an Insteon I/O Linc to z-wave Mimo2+. I'm using Seco-Larm magnetic contact switches for my two garage doors. I've wired them into the analog ports of the Mimo2+. When I separate the magnetic contacts the Sig1 and Sig2 lights on the Mimo2+ come on so that tells me it's wired properly.
If I understand correctly, I'm not going to receive an on/off or open/close notification in Indigo. I guess I'm going to receive an electrical current signal. Zero or near zero appears to be closed and around 3800 appears to be open. I set the range notification to be less than 100 or more than 2000 for the appropriate triggers. My problem is that Indigo doesn't notice when the contacts separate for an automated trigger. If I do a manual device status then the expected device status is received and the trigger fires.
What am I missing?

david

[matt (support)]

Hi David,

Are the Indigo devices "Binary Input 1" and "Binary Input 2" states being updated when you open/close the contact switches? You won't be using the Analog devices at all since you are interested in the binary input on/off (open/close) states. Copy/paste the contents of the Event Log window after you trip the switches a few times. If it isn't showing anything, then re-sync the device in Indigo and copy/paste the results of that into a forum reply for me.

The binary/analog 1 and binary/analog 2 devices reflect the state change but only when I query the devices. There is no automatic Indigo notification of state change. When I query the binary or analog device, I only get a response for the analog.


Mar 18, 2019 at 10:08:37 AM
Z-Wave sent "026 - Binary Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 0
Z-Wave sent "026 - Binary Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 1
Z-Wave sent "026 - Analog Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 0
Z-Wave sent "026 - Analog Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 1

Mar 18, 2019 at 10:09:30 AM
Z-Wave sent "026 - Binary Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 3097
Z-Wave sent "026 - Binary Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 3085
Z-Wave sent "026 - Analog Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 3097
Z-Wave sent "026 - Analog Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 3084

Also -

I've now deleted and re-added the device multiple times. Sometimes it cleanly deletes and sometimes not. I now have a couple of zombie entries that I can't get rid of.
I've noticed on the recent adds, that I get this "failed to assign return route" error, perhaps this has been my problem all along. During the troubleshooting process I've moved the Mimo2+ and door contacts into my office where it's about 4 feet form the Indigo server. Neighbor list 4,7,12 are devices in my office so it seems to correctly know where it is.

Mar 17, 2019 at 6:31:40 PM
Z-Wave Syncing - started for "026 - Multilevel Sensor"
Z-Wave Syncing - retrieved module neighbors list: 4, 7, 12
Z-Wave Syncing - assigning return route to "026 - Multilevel Sensor"
Z-Wave Error Syncing - failed to assign return route
Z-Wave Syncing - retrieved manufacture and model names: FortrezZ - 0084, I/O Module (MIMO2+) - 04630208
Z-Wave Syncing - retrieved protocol version 4.34, app version 2.08
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Multilevel Sensor : -- (04 : 21 : 00, base 31)
Z-Wave Syncing - retrieved command classes: 20v1 85v1 86v1 8Ev1 98v1 59v1 5Av1 5Ev1 60v4 25v1 71v1 70v1 31v9 72v1 73v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
Z-Wave Syncing - retrieved multi-endpoint types: 1:(21 : 00), 2:(21 : 00), 3:(10 : 01), 4:(10 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[31 59 85 8E], 2:[31 59 85 8E], 3:[25 20 59], 4:[25 20 59]
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 "Relay 1 mode" is 5 "Momentary (0.5 Second)"
Z-Wave Syncing - retrieved parameter 3 "Input 1 mode" is 168 "Trigger Between Thresholds - Report Analog Every 20 Minutes"
Z-Wave Syncing - retrieved parameter 4 "Input 1 OFF threshold HIGH" is 2304
Z-Wave Syncing - retrieved parameter 5 "Input 1 OFF threshold LOW" is 2048
Z-Wave Syncing - retrieved parameter 6 "Input 1 ON threshold HIGH" is 4080
Z-Wave Syncing - retrieved parameter 7 "Input 1 ON threshold LOW" is 4064
Z-Wave Syncing - retrieved parameter 2 "Relay 2 mode" is 5 "Momentary (0.5 Second)"
Z-Wave Syncing - retrieved parameter 9 "Input 2 mode" is 168 "Trigger Between Thresholds - Report Analog Every 20 Minutes"
Z-Wave Syncing - retrieved parameter 10 "Input 2 OFF threshold HIGH" is 2304
Z-Wave Syncing - retrieved parameter 11 "Input 2 OFF threshold LOW" is 2048
Z-Wave Syncing - retrieved parameter 12 "Input 2 ON threshold HIGH" is 4080
Z-Wave Syncing - retrieved parameter 13 "Input 2 ON threshold LOW" is 4064
Z-Wave Syncing - created device "026 - Binary Input 1"
Z-Wave Syncing - created device "026 - Analog Input 1"
Z-Wave Syncing - created device "026 - Binary Input 2"
Z-Wave Syncing - created device "026 - Analog Input 2"
Z-Wave Syncing - created device "026 - Relay 1"
Z-Wave Syncing - created device "026 - Relay 2"
Z-Wave Syncing - complete
Z-Wave sent "026 - Binary Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 0
Z-Wave received "026 - Analog Input 1" units changed
Z-Wave sent "026 - Analog Input 1" status request
Z-Wave received "026 - Analog Input 1" sensor update to 0
Z-Wave sent "026 - Binary Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 1
Z-Wave received "026 - Analog Input 2" units changed
Z-Wave sent "026 - Analog Input 2" status request
Z-Wave received "026 - Analog Input 2" sensor update to 1
Z-Wave sent "026 - Relay 1" status request
Z-Wave sent "026 - Relay 2" status request

Matt - Any thoughts on the "Z-Wave Error Syncing - failed to assign return route" message? Could that be the cause of my problem? Any tips on deleting the zombie entries?

david

After trying to add the mimo2+ a hundred times I decided that maybe it's a flaky device so I sent it back and got another one...same exact problems.

[matt (support)]

I think there are a couple of different issues here. The first one (binary devices only updating if you query them) I think is because the MIMO2 is behaving differently than the MIMO Lite. I believe we need to send a different type of association command to it in order for it to send out the state changes to Indigo as they occur. I can give you some raw commands to have Indigo to send to see if that gets it working.

But the other problem ("failed to assign return route") that is causing the syncing to fail is different. So previously you had it syncing and working (minus the updating problem), but now you cannot get Indigo to sync the device even after trying multiple times? This includes first excluding the device, then re-including and re-syncing it (after selecting the new node ID if needed)?

To remove the failed nodes choose the Interfaces->Z-Wave->Remove Failed Modules from Controller... menu item. That might help, but I'm not sure. If it doesn't then I'm afraid your Z-Stick may have gotten into a bad state. I wonder if you can add any new modules at all now. That is, the problem may not be specific to the MIMO's.

I may have had a bad repeater so I replaced it. I also got a new mimo2+ because things just seemed flaky. When I would add the device, sometimes it would recognize it as the appropriate device type (but still not function) and sometimes it would think it was a different type of sensor. I added and deleted it dozens of times. I got frustrated with it and left it for a couple of weeks. A couple of days ago I did the 7.3 update. Yesterday I thought I would give it another try. I guess there's something in the update because now it works.