The one place that I rely on it is my "mailman audible annunciator".  When my mailbox is opened, the ISY turns on an LED on a Homeseer WD200+ and then turns on a Mimo relay driving a sonalert.  When my wife gets the mail she presses a button (connected to the Mimo Lite Input) that turns off the blinking LED.  I have attached a picture. 

This happens 6 times a week with no failures, so far....

Edited November 26, 20186 yr by KSchex
add last sentence

Cool.  Do you use some type of battery wireless sensor in the mailbox itself?

Good to see that others out there also have way too much time on their hands

2 hours ago, KSchex said:

The one place that I rely on it is my "mailman audible annunciator".  When my mailbox is opened, the ISY turns on an LED on a Homeseer WD200+ and then turns on a Mimo relay driving a sonalert.  When my wife gets the mail she presses a button (connected to the Mimo Lite Input) that turns off the blinking LED.  I have attached a picture. 

This happens 6 times a week with no failures, so far....

I am intrigued by the Practical Guide to Curl.....  (curling?).

1 hour ago, asbril said:

I am intrigued by the Practical Guide to Curl.....  (curling?).

I assume that it's the curl command, which basically lets you initiate lots of different network requests from the command line.

I use a MIMOLite for my garage door and it automatically reports status.  I do have some trouble getting the status to sync up after I reboot the ISY, but I suspect that's due to the query issue that I mentioned here, and earlier in one of the ISY 5.0.x release threads.

 

Edited November 26, 20186 yr by rccoleman

1 hour ago, rccoleman said:

I assume that it's the curl command, which basically lets you initiate lots of different network requests from the command line.

I use a MIMOLite for my garage door and it automatically reports status.  I do have some trouble getting the status to sync up after I reboot the ISY, but I suspect that's due to the query issue that I mentioned here, and earlier in one of the ISY 5.0.x release threads.

 

Should I change any of the Zwave parameters to get Status reporting ? I get an error message (see screenshot) when doing a Query. See attached event log.

ISY-Events-Log.v5.0.14__Mon 2018.11.26 05.40.08 PM.txt

Edited November 26, 20186 yr by asbril

That's the same error message that's in the second thread that I linked to.  It's been happening since I got the device, and definitely since 5.0.13 because I reported it here.  I don't recall if I had to do anything special to get instant status.  Here's a program that I use to tell me when my garage door is open:

Garage Door Open - [ID 004A][Parent 0051][Not Enabled]

If
        'Devices / Garage / Garage Door Sensor' Status is Off
 
Then
        Set Elk Speak Phrase 'Miscellaneous 1 '
        Set 'Devices / Garage / Garage Door Switch' On
 
Else
   - No Actions - (To add one, press 'Action')
 

Note that it's disabled, but it works fine when I run it as part of my "good night" routine, and I don't think it kicks off a query.  I also have Alexa routines that monitor the MIMOLite to tell me if my garage door opens or closes and a nearby Dot announces it.  No queries there that I'm aware of.

Here's a blurb from their FAQ:

Quote

I have your MIMOlite installed and working with my X controller so that the relay can be toggled to open and close my garage door. I have it setup as in the diagram on your website. I would like to get the wired sensor working so that I can tell whether the garage door is opened or closed. Could you tell me the Z-Wave command and what the payload would be for the contact sensor?

• Using your controller, you should be able to set up Association Group #4 in the MIMOlite (with the controller as an associated node).   This will cause Binary Sensor Reports to be automatically sent to the controller indicating the state of the changed input with the following payloads:

            0xFF = SIG1 contacts open
            0x00 = SIG1 contacts shorted

• This is assuming that the MIMOlite configuration parameter 8 is set to ‘digital’ (b0 = 1).  If your sensor does not open or short the contacts but instead supplies a voltage, the ‘analog’; configuration (Parameter 8, b0 = 0) may need to be set up.  The ‘digital’; configuration has a threshold around 1V while the ‘analog’; configuration can have a threshold and hysteresis within a wide range of voltages.  Refer to FortrezZ’s MIMOlite Configuration Utility for help in determining ‘analog’; thresholds and configuration settings. If you don’t want to use Association groups, you could set the controller to periodically poll the state of the input. You could use the Basic Command Class Get command or the Binary Sensor Get command to query the MIMOlite.  With either command the same payload considerations mentioned above apply. 

Edited November 26, 20186 yr by rccoleman

12 minutes ago, rccoleman said:

That's the same error message that's in the second thread that I linked to.  It's been happening since I got the device, and definitely since 5.0.13 because I reported it here.  I don't recall if I had to do anything special to get instant status.  Here's a program that I use to tell me when my garage door is open:

Garage Door Open - [ID 004A][Parent 0051][Not Enabled]

If
        'Devices / Garage / Garage Door Sensor' Status is Off
 
Then
        Set Elk Speak Phrase 'Miscellaneous 1 '
        Set 'Devices / Garage / Garage Door Switch' On
 
Else
   - No Actions - (To add one, press 'Action')
 

Note that it's disabled, but it works fine when I run it as part of my "good night" routine, and I don't think it kicks off a query.  I also have Alexa routines that monitor the MIMOLite to tell me if my garage door opens or closes and a nearby Dot announces it.  No queries there that I'm aware of.

Here's a blurb from their FAQ:

RColeman : I apologize for my ignorance, but how  do I " set up Association Group #4 in the MIMOlite (with the controller as an associated node). "  and/or "  the Basic Command Class Get command or the Binary Sensor Get command to query the MIMOlite.  ", knowing that I get an error message when doing a Query of my Mimo-Lites ?

I don't think I did anything special when I added it.  I might have done this:

This is assuming that the MIMOlite configuration parameter 8 is set to ‘digital’ (b0 = 1)

That's just setting a configuration parameter by right-clicking on the sensor node.

55 minutes ago, rccoleman said:

That's the same error message that's in the second thread that I linked to.  It's been happening since I got the device, and definitely since 5.0.13 because I reported it here.  I don't recall if I had to do anything special to get instant status.  Here's a program that I use to tell me when my garage door is open:

Garage Door Open - [ID 004A][Parent 0051][Not Enabled]

If
        'Devices / Garage / Garage Door Sensor' Status is Off
 
Then
        Set Elk Speak Phrase 'Miscellaneous 1 '
        Set 'Devices / Garage / Garage Door Switch' On
 
Else
   - No Actions - (To add one, press 'Action')
 

Note that it's disabled, but it works fine when I run it as part of my "good night" routine, and I don't think it kicks off a query.  I also have Alexa routines that monitor the MIMOLite to tell me if my garage door opens or closes and a nearby Dot announces it.  No queries there that I'm aware of.

Here's a blurb from their FAQ:

I could be a bit confused, but I do not see a reliable trigger condition in your "if" statement to actually run that program.

Shouldn't that be a "control" command "is switched Off"  instead of a "status" command "status is off" ?

You’re correct in that that program is disabled and won’t trigger automatically, but I can watch the status update in the admin console, and I don’t think the ‘status’ in the ‘if’ is sending a query. In part because queries don’t work, as we’ve been discussing. My Alexa routine also appears to work without any program at all. I just set up the sensor device in the portal and my Dot announces when the door opens and closes. I’ll do some more research, but I’m pretty sure that it’s reporting the status. 

Okay, this works fine for me.  I get an instant notification via a network resource when my garage door opens and when it closes.

New Program - [ID 00A1][Parent 0001]

If
        'Devices / Garage / Garage Door Sensor' is switched On
    And 'Devices / Garage / Garage Door Sensor' is not switched Off
 
Then
        Resource 'Garage Door Closed'
 
Else
        Resource 'Garage Door Open'

Here's a pic of the bottom of my MIMOLite and the wiring for my switch and sensor (from the outside, at least).

 

Here's the info from the sensor node:

Mon 11/26/2018 04:39:47 PM : [UZW-CMD 51      ] [ZWCMD cmd.51]
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] ----------------------------------------------
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] Garage Door Sensor
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] ZW016_104 uid=16 type=4.16.0 mid=132 tid=1107 pid=273 model=11
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] ZW016_1 - Primary Isy Node
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x72  V1   MANUFACTURER_SPECIFIC
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x86  V1   VERSION
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x71  V1   NOTIFICATION
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x30  V1   SENSOR_BINARY
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x31  V1   SENSOR_MULTILEVEL
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x35  V1   METER_PULSE
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x70  V1   CONFIGURATION
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x85  V1   ASSOCIATION
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ]    -  x25  V1   SWITCH_BINARY
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] - Secure
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] 
Mon 11/26/2018 04:39:55 PM : [ZW-SHOW         ] ----------------------------------------------
Mon 11/26/2018 04:39:55 PM : [UZW-CMD 37      ] Show All Node Details : ZW016_104

Parameter 8 is set to "3", which means that both bits 0 and 1 are 1.  Both bits are described here, but basically they both need to be 1 for the sensor to report digital values (0/1), rather than analog.

https://www.cd-jackson.com/zwave_device_uploads/219/tech-appendix-mimolite-05may2015.pdf

I was also getting unsolicited reports from the multi-level sensor, so I disabled those via parameter 9 (set to 0).

Edited November 27, 20186 yr by rccoleman

On ‎11‎/‎26‎/‎2018 at 3:23 PM, rccoleman said:

I assume that it's the curl command, which basically lets you initiate lots of different network requests from the command line.

I use a MIMOLite for my garage door and it automatically reports status.  I do have some trouble getting the status to sync up after I reboot the ISY, but I suspect that's due to the query issue that I mentioned here, and earlier in one of the ISY 5.0.x release threads.

 

In a working world my forte' was hardware design, C and assembly programming.  Now I need to learn internet & web related programming (cURL, JavaScript, PHP, Python...) for retirement!

Sorry I can't add much assistance to the garage problem.  For what it's worth, I have Mimos set for latching and momentary.  The diagram I posted is just a switch that I read with a program.  I did have problems with the input when the switch was in an open position.  The Mimos kept sending analog reports to the ISY as the numbers bobbled a couple of digits.  I had to tweak some of the parameters to get it to stop. 

 

On 11/17/2018 at 6:44 AM, dcard said:

A bit confused on what is, and is not working for the MIMO2+ as of Nov 2018.

Has anybody verified proper operation of BOTH relays with v.5.0.14 software?

Thx in advance

1

I updated to v.5.0.14 software yesterday (Dec 8, 2018) and BOTH relays were working flawlessly as momentary NO contacts. I didn't test the other options on the MIMO2+, as the motorized curtains that I was trying to control wanted two pulse inputs, one to open the drapes and one to close them. 

Now on a separate topic, a simple Modbus TCP stack in the ISY would rock. It breaks my heart to pay almost as much for a cheaply built 2-relay I/O block as I would for industrially hardened PLC with 16 I/O. In a previous life, I was responsible for creating a very in-depth Modbus/TCP DPI firewall (www.tofinosecurity.com) and I'd be happy to support developing a Modbus/TCP module. It would only need to support the two Class 0 Function Codes, namely FC 3 - Read Multiple Registers and FC 15 - Write Multiple Registers. Anything more would be pure luxury.

And if there was a module in existence, I'd be happy to pay $49 for it. As well as solving the I/O problem (especially stable Analog I/O), most modern PLCs support full floating point math with functions like SqRt, Sine and Cosine. Modbus would allow me to get the math out of the ISY and into a robust PLC that will probably still be running long after I am not.

44 minutes ago, PLCGuy said:

I updated to v.5.0.14 software yesterday (Dec 8, 2018) and BOTH relays were working flawlessly as momentary NO contacts. I didn't test the other options on the MIMO2+, as the motorized curtains that I was trying to control wanted two pulse inputs, one to open the drapes and one to close them. 

Now on a separate topic, a simple Modbus TCP stack in the ISY would rock. It breaks my heart to pay almost as much for a cheaply built 2-relay I/O block as I would for industrially hardened PLC with 16 I/O. In a previous life, I was responsible for creating a very in-depth Modbus/TCP DPI firewall (www.tofinosecurity.com) and I'd be happy to support developing a Modbus/TCP module. It would only need to support the two Class 0 Function Codes, namely FC 3 - Read Multiple Registers and FC 15 - Write Multiple Registers. Anything more would be pure luxury.

And if there was a module in existence, I'd be happy to pay $49 for it. As well as solving the I/O problem (especially stable Analog I/O), most modern PLCs support full floating point math with functions like SqRt, Sine and Cosine. Modbus would allow me to get the math out of the ISY and into a robust PLC that will probably still be running long after I am not.

Thanks for the update on the MIMO2+.  I have been waiting for this for quite a while so I can press the buy button on Amazon.

Having spent a lifetime in industrial and military electronics I believe more could be done to hardware, software, and especially communications to make ZWave  more reliable and robust.  It would also be nice to be able to interface to some multiple digital input and 12 bit analog input Modbus modules.  The unfortunate thing about any HA protocol is it is adapted with time and is never really hardened.  Let's also not forget quality, or lack of.  Manufacturers are competing with one another for the most cost effective product and trying to keep up with new features at the same time.  Just my 2 cents!

1 hour ago, PLCGuy said:

Now on a separate topic, a simple Modbus TCP stack in the ISY would rock. It breaks my heart to pay almost as much for a cheaply built 2-relay I/O block as I would for industrially hardened PLC with 16 I/O. In a previous life, I was responsible for creating a very in-depth Modbus/TCP DPI firewall (www.tofinosecurity.com) and I'd be happy to support developing a Modbus/TCP module. It would only need to support the two Class 0 Function Codes, namely FC 3 - Read Multiple Registers and FC 15 - Write Multiple Registers. Anything more would be pure luxury.

And if there was a module in existence, I'd be happy to pay $49 for it. As well as solving the I/O problem (especially stable Analog I/O), most modern PLCs support full floating point math with functions like SqRt, Sine and Cosine. Modbus would allow me to get the math out of the ISY and into a robust PLC that will probably still be running long after I am not.

Doubt you'll see UDI support Modbus, they've gone the way of using Node Servers for extra support.

If you're on V5 and don't mind running a Pi, NodeLink has a ModbusTCP device.  I use it for DI/DO into industrial bus couplers such as a Beckhoff BK9000.

13 hours ago, io_guy said:

Doubt you'll see UDI support Modbus, they've gone the way of using Node Servers for extra support.

If you're on V5 and don't mind running a Pi, NodeLink has a ModbusTCP device.  I use it for DI/DO into industrial bus couplers such as a Beckhoff BK9000.

The trouble is, I do mind running a Pi for I/O management in a home automation system. IMHO, while Pi are fun for hobbyist projects (I have several), they aren't built for long-term 7x24x365 operation. The power supplies for the Pi get quoted with an MTBF of about 50,000 (which isn't very good), and MTBF data for the Pi itself is non-existent. Neither gives me warm fuzzy feelings.

Now to be honest, my use case is a little harsher than most. We use home automation supporting the neighbour's water cistern systems. We also use it in our vacation rental properties to make our renter's experience more fun (and to stop people from trying to air condition the desert). But when core components fail, neighbours and renters are never happy and I'm 3000 miles away and can't help them. And the local electrician can't help at all.

In fact, the whole reason I decided to try the MIMO2+ was because I was sick of replacing over-priced IOLincs that fail regularly. But adding a nodeserver to do basic I/O handling just adds another failure mode in an already fragile system. IMHO it defeats the vision for robust home automation. On the other hand, I've never seen an ISY fail (kudos to Michael and Team) and most low-cost PLCs come with MTBFs of 100,000 or better. So a combination of PLCs and ISY with no Pi would be a perfect solution for our use case.

Now I've ranted about this in the past, so feel free to just press delete on this post   I just keep hoping that reliable I/O for home automation won't stay a dream forever.

 

Hi PLCGuy,

I totally understand. Unfortunately the current ISY does not have enough GPIO pins to allow for more analog input. Our next gen hardware will definitely have more onboard GPIO pins.

With kind regards,
Michel

PLCGuy,

Fair enough and good points.  I use an industrial PS to feed my Pi.  Phoenix also offers a kit:

https://blog.phoenixcontact.com/marketing-gb/raspberry-pi-gets-a-new-home/

Can't say I've heard of a Pi failing. SD cards fail all the time, but the ISY has one as well.  

You could always buy an embedded industrial PC and install linux on it. 

The Phoenix Contact Pi enclosure is super cool. That is almost enough to convince me to try a Pi for industrial applications.

On 12/9/2018 at 7:24 PM, PLCGuy said:

I updated to v.5.0.14 software yesterday (Dec 8, 2018) and BOTH relays were working flawlessly as momentary NO contacts. I didn't test the other options on the MIMO2+, as the motorized curtains that I was trying to control wanted two pulse inputs, one to open the drapes and one to close them. 

Now on a separate topic, a simple Modbus TCP stack in the ISY would rock. It breaks my heart to pay almost as much for a cheaply built 2-relay I/O block as I would for industrially hardened PLC with 16 I/O. In a previous life, I was responsible for creating a very in-depth Modbus/TCP DPI firewall (www.tofinosecurity.com) and I'd be happy to support developing a Modbus/TCP module. It would only need to support the two Class 0 Function Codes, namely FC 3 - Read Multiple Registers and FC 15 - Write Multiple Registers. Anything more would be pure luxury.

And if there was a module in existence, I'd be happy to pay $49 for it. As well as solving the I/O problem (especially stable Analog I/O), most modern PLCs support full floating point math with functions like SqRt, Sine and Cosine. Modbus would allow me to get the math out of the ISY and into a robust PLC that will probably still be running long after I am not.

Thx PLCGuy!

I guess using as momentary outputs, you really cannot see if the status gets updated automatically.  Wondering if that is working.

Also, are you using the newer 500 series Z-Wave hardware on your ISY?  Any idea if this is required, in general, when Z-wave+ is released?

*********

Agree 1000 percent on the Modbus TCP function, and FC 3 and FC 16 may be all you need, but some PLC's will far prefer coil commands too.  even better is FC 23 if the device supports it.

But that Modbus TCP stack is very easy to implement, and in pretty much any language that supports TCP/UDP calls (even native in Java).

 

Edited December 11, 20186 yr by dcard

On 12/10/2018 at 12:01 PM, PLCGuy said:

The trouble is, I do mind running a Pi for I/O management in a home automation system. IMHO, while Pi are fun for hobbyist projects (I have several), they aren't built for long-term 7x24x365 operation. The power supplies for the Pi get quoted with an MTBF of about 50,000 (which isn't very good), and MTBF data for the Pi itself is non-existent. Neither gives me warm fuzzy feelings.

Now to be honest, my use case is a little harsher than most. We use home automation supporting the neighbour's water cistern systems. We also use it in our vacation rental properties to make our renter's experience more fun (and to stop people from trying to air condition the desert). But when core components fail, neighbours and renters are never happy and I'm 3000 miles away and can't help them. And the local electrician can't help at all.

In fact, the whole reason I decided to try the MIMO2+ was because I was sick of replacing over-priced IOLincs that fail regularly. But adding a nodeserver to do basic I/O handling just adds another failure mode in an already fragile system. IMHO it defeats the vision for robust home automation. On the other hand, I've never seen an ISY fail (kudos to Michael and Team) and most low-cost PLCs come with MTBFs of 100,000 or better. So a combination of PLCs and ISY with no Pi would be a perfect solution for our use case.

Now I've ranted about this in the past, so feel free to just press delete on this post   I just keep hoping that reliable I/O for home automation won't stay a dream forever.

 

Hear you about looking for robust solutions, but just don't think new products from tiny new companies have any track record to judge reliability  (MIMO2+)

On computer boards, SBC's and the like, failures usually fall to power supply capacitors, and overall thermals.  Keep the temperature down on that board, and give it a quality power supply, and I think you will get the MTBF you are looking for.  High volume manufacturers that have been in business awhile usually get it right, or they die with downstream failures pissing their customers off.

However, I do agree with you about adding another component into the mix.  But my issue is not necessarily decreased MTBF.  My issue is long term support.  Six years flies by quickly, and if you are not constantly dinking with your system, when it does fail, it can become a real pain in the *** getting replacement parts with life-cycle issues, and the re-learning on how to load and setup your system.

Every new programmed part you add into the system, with its own learning curve, special tools to configure/program adds tremendous downstream support issues and complexity.

I tend to want ONE PROGRAMMED PART, and everything else dumb, perhaps configured VERY easily with dipswitches, or from that ONE PROGRAMMED PART that remotely configures it.

So even if I was using MODBUS I/O, I would likely NOT use the PLC programming available in that module.  Most of these products default to MODBUS slave support out of the box with no programming.  And if you pick a Beckoff, Wago, or even an Advantech, their volumes are so high that you stand a good chance of getting replacements in the 5-10 year time frame.

Certainly, having a stronger programming environment like a PLC could be a real plus.  But having done a lot of work with real-time automation systems using high level (and 40 years ago low level) languages, even PLC are maddeningly inflexible too (but keep you out of trouble). 

If I wanted to step-up in programming capability from the ISY, I would probably add the Pi, linux, and a basic I/O controller module (software) in a high level language.  At that point, I also have the Nodeserver thanks to that io dude!

 

Edited December 11, 20186 yr by dcard

On 12/10/2018 at 3:33 PM, Michel Kohanim said:

Hi PLCGuy,

I totally understand. Unfortunately the current ISY does not have enough GPIO pins to allow for more analog input. Our next gen hardware will definitely have more onboard GPIO pins.

With kind regards,
Michel

A bit confused, Michel.  A MODBUS TCP implementation is just a simple network protocol that uses the existing Ethernet port...no GPIO needed.

It is a pretty trivial protocol, small code, available in many programming languages, Java, etc.

One easy way to implement would be for the user to just create a new variable with the name the actual "Device-modbus address" (i.e. MB-DEV01-00005). 

The underlying (new) firmware sees that it is a Modbus address and cyclically reads that Modbus address, setting "Status," and triggering "Command" on change.   Any program that makes an assignment of a new value to that Modbus variable automatically does an immediate one- time Modbus send.   If sequential DEV-MB names exist, it just makes one multi-register read. 

Of course, that would also require configuration with a simple "Device-IPaddress table" with perhaps cyclic update rate field and debounce window to detect change. (probably on the Config Network tab.)  It could be really simple.  This would be for a Modbus MASTER.  Modbus SLAVE would be even easier, but not as useful for dumb I/O.

p.s. even simpler is to just provide the raw Modbus read and write commands in the programming environment, and let the user set up cyclic reads and wirtes based on trigger from change of state variables. Still would probably want  a DeviceName-IPaddress table on the config-network tab.

 

Edited December 14, 20186 yr by dcard

Re: use of the Rasberry Pi for Industrial Control:

https://info.opto22.com/raspberry-pi-io

Of course, you pay for it -- at $120 list price for JUST the power supply, it had better be good!

(I've got a few of the opto 22 mounting racks, and a whole bunch of the opt 22 I/O modules, so I'll be buying the Raspberry Pi adapter ("Carrier" they call it)... but I think I'll use one of my existing power supplies, thank you! )

I like the Opto 22 modules, using the quad IO modules.  There are several different clones also.  Usually I can pick them up along with a 4-slot backplane on Ebay cheap.  I have used them with my aircondition monitor system along with a Beaglebone Black.  Even though I build my own interface, I use only UL and CE approved  devices for interface to my home.  Best regards..

Just as a follow up, I did get the MIMO2+ unit some time back, and it works great. (HVAC air handler blower speed control)

Out of the box, the relays are set to momentary.  Using the "Binary Switch" device, set the ZWave parameters 1 and 2 both to "0" instead of the default "5" for latched operation.  Start by selecting the Parameter number you want to change, and hit "Query" to grab the current value.  Then change it, hit "Set," wait, then "Query" again to make sure it took.

Played a bit with the two analog inputs.  I set up both inputs to update as fast as possible (Parameter 3 (for Sig1) and Parameter 9 (for Sig2) each set to -127.  This gives updates that vary between 12 and 20 seconds.  They have a downloadable application helper that guides you to the proper parameter values to use.

The input is not clearly defined in the literature.  You will measure 2.725 volts between sig and common with nothing connected.You better have a low/zero impedance voltage source capable of both sourcing and sinking current (as signals below 2.725 volts will want your source to sink current (yeach).

I characterized both inputs and was disappointed not so much by the nonlinearity, but by the garbage at the bottom end:

Essentially, below 0.6 volts, it is very funky.  In general, it doesn't seem to be filtered internally, as successive readings (12-20 seconds) change 10's of counts (with a very stable signal source).  Given the instability of the signal (no internal filtering), the non-linearity (difficult to linearize in ISY), and the garbage relationship below 0.6 volts input (unusable), I give it a "fail" for my application (cheap SCT current transformer conditioned with AD8436 RMS converter). 

 

2 hours ago, dcard said:

Just as a follow up, I did get the MIMO2+ unit some time back, and it works great. (HVAC air handler blower speed control)

Out of the box, the relays are set to momentary.  Using the "Binary Switch" device, set the ZWave parameters 1 and 2 both to "0" instead of the default "5" for latched operation.  Start by selecting the Parameter number you want to change, and hit "Query" to grab the current value.  Then change it, hit "Set," wait, then "Query" again to make sure it took.

Played a bit with the two analog inputs.  I set up both inputs to update as fast as possible (Parameter 3 (for Sig1) and Parameter 9 (for Sig2) each set to -127.  This gives updates that vary between 12 and 20 seconds.  They have a downloadable application helper that guides you to the proper parameter values to use.

The input is not clearly defined in the literature.  You will measure 2.725 volts between sig and common with nothing connected.You better have a low/zero impedance voltage source capable of both sourcing and sinking current (as signals below 2.725 volts will want your source to sink current (yeach).

I characterized both inputs and was disappointed not so much by the nonlinearity, but by the garbage at the bottom end:

Essentially, below 0.6 volts, it is very funky.  In general, it doesn't seem to be filtered internally, as successive readings (12-20 seconds) change 10's of counts (with a very stable signal source).  Given the instability of the signal (no internal filtering), the non-linearity (difficult to linearize in ISY), and the garbage relationship below 0.6 volts input (unusable), I give it a "fail" for my application (cheap SCT current transformer conditioned with AD8436 RMS converter). 

 

Yes it does not match the Fortrezz spec sheet.  I found that I had to use  .8V to 2 volts input,  This seemed to be the closest reasonably linear segment,  not enough range.  I considered doing curve segment breakpoints with a look up table or a curve fit but that was beyond the ISY.  My solution was to use the MIMO2+ inputs  for contact inputs from switches.  I wound up with a Beaglebone black, and an 12-bit A/d to measure my house current.  It sends Rest commands to the ISY setting the appropriate variables with the current (amps).  Good luck..

Edited January 27, 20196 yr by KSchex
first sentance