KSchex

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.

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....

Nothing against any of the manufacturers, but this is why I have begun using Beaglebone Blacks with HTTP Get / Post and my own optically isolated IO. With this I have over come the single point problem. I still believe Z-Wave and most of the controllers were meant to be a consumer product, designed and manufactured in China with the attitude of sell a bunch and move on, as I have "moved on" through many trash devices. We as serious ISY users have taken this a step further; relying on this for daily performance of home automation. In my case I am disable and rely on it to do it's thing when I press the button, as advertised. As for MIMO, I have several Lites in my system but rely on them to report their status change and do not query them. In all cases I use the input to send me the status of the controlled device. The lack of support for the 2+ and long software lead time is what drove me to the Beaglebone solution as I could not wait any longer. It is unfortunate because they are well built little devices that I have found are easy to deal with and don't get confused with power failures. It has been quite a project. Thanks all for airing your views and findings as well as Michel for his undying support and assistance.

Hi Asbril….I don't know if this will help you but...I have found on some devices if I wait a second or two before asking for status or ask twice with a wait in between that 99% gets a lot better. Not sure if it is the device or the ISY being busy, or a little of both. Perhaps you have already tried this. I have found there are occasional times when the ISY is busy and misses messages. Especially in V5. I stripped my system down to one device and one simple program and the Event Viewer to verify this. With a sensor you tend not to notice it as much (even though it is there), but with a Wallmote keypad commanding a light through the ISY and a program it is very apparent when the ISY does not service the incoming message. As a side note, the first thing I did was verify good RF signal strength and no external interference with a spectrum analyzer. I realize this is above and beyond for some users but I was determined to know where my problem lies.

I too am still waiting on MIMO+2. I am holding back on two automation projects for the +2 compatibility. Because of the lack of multi input support I have used WIFI and Beaglebones in some key home areas. It would be nice to keep everything ZWave within the ISY and have a nice clean system.

Also impatiently awaiting MIMO 2+ complete ISY support. Thanks Michael for putting it in the que. Keith.

Would like to know what Insteon says the problem is. My guess is the output circuit driving the light is of a poor design. It probably uses a triac device or similar that is being turned on an off (modulated if you will) by the line noise. My guess is that later manufactured devices have a more stable circuit with some minimal filtering. Getting rid of the noise makers (switching power supplies, etc.) or adding filters in your home is a solution but in todays digital age this may be impossible. Nobody uses good old fashion analog power supplies any more or worries about harmonic distortion of your home power. Cost effective designs that are quick to market is whats important. It blows me away how a company can sell a device on such a grand scale that is so susceptible to power line noise, hampering the output and/or communication. Sorry, just had to add my 2 cents to a problem I have spent days working on. One reason I switched to Z Wave.

Just out of curiosity why could you not put pgm2 in the then of pgm1? It always calls it when the conditions are met. Thanks..

Hi mikek, I am currently using 3 MimoLites in my system; 1 drives an audible annunciator and 2 drive latching relays for light control. Both are set for momentary and use the output (for control) and input (for status). I added them like any other Z Wave device; exclude then include. I did not need to change any of the parameters. Good luck..

Hi Teken, I would really like to know what UDI has to say. Every computer has it's Achilles' heal. In this case it maybe the inability to handle the added successive Ethernet interrupts in a short time period. Just a guess.

I am not sure this is what you are looking for but …. Over the last year I created my own web user interface using the Home Automation Dashboard software in the UDI Forum as a base. Not having web programming experience I literally took the software apart to learn how it worked. From there I stripped out and saved all the AJAX and communication related code, starting simple. I prefer to stay away from “plugins” like JQUERYUI, etc. although I have used them in places. My UI is hosted on my NAS running Apache. As a personal rule, all logic is done in the ISY. My UI is only for viewing status, commanding devices, and setting user options. It will flag and alert me of status changes in specific alarm devices showing the date and time as well as flagging disabled devices. It is still a work in progress and is a subset of my system. I would recommend you look at the HAD Forum and Wiki along with the REST documentation, on the UDI web site. Also look at the SDK that is available. Best of luck…

Thanks Paul. I learned something new.

I saw the original post here and it got me thinking. Why would you want to query for status. The devices should send the status back automatically on a transition and the ISY should have that data. Am I missing something?

I am considering a zWave "stick" to interface to the Plus devices. I will need to write software to make this work with my graphic interface.

Thanks all....I was hoping I maybe missed something that would make passing and testing parameters simpler.

Has anybody figured a way to call a program with an attached parameter such as like a function call; function(parameter)? This would make annunciating various situations a lot cleaner with a lot less If than elses. Thanks....

Could not resist the comment....As we all know, Mimo2+ full functionality does not work in the current 4 or 5 Beta. Once again, I am patiently awaiting the released version 5 in hopes of full support for Mimo2+ (hint hint). Multi input/output device support would really be nice, two ins and two outs.

When I added it to the ISY the following popped up: binary sensor, binary switch, multilevel sensor, power management, and pulse meter. I tested them all and they work. All I am using is the sensor and switch.

Yes...MimoLite worked first try for me. I just need an additional in and out.

So since Mimo2+ is not fully supported and may never be, does anyone have any ideas for a multi input/output Z-Wave device that is compatible with the ISY994?

Using 4.5.4, MimoLite works flawlessly. Fortrezz has solid products as is the ISY994. The ISY994 sees the MimoLite binary sensor, binary switch, multilevel sensor, power management, and pulse meter. I am patiently awaiting V5 in hopes of full support for Mimo2+ (hint hint). Multi input/output device support would really help. Two ins and two outs like the Mimo2+ would go a long way.

I must have missed something, if you do a Z-Wave backup where is it saved? If you do an ISY backup does it automatically include a fresh Z-Wave backup? I also find that the Z-Wave backup is slow on my system, taking about 15 minutes. All I have is one Z-Wave device, Mimo Lite. It spends a lot of time with the display saying "ZWAVE WAKUP 3)Put back to sleep ZW003_1" which is the Mimo Binary Switch. Is this normal?

I am OK with time slice, interrupts, polling flags, whatever. It just makes a difference to me in how I code certain devices and alarms. Sometimes, depending on the process, you can get carried away with features slowing down the system, especially on an "embedded" device even though you try to make it as tight as possible..As long as the processor is fast enough it should not matter. What bothers me is these "IF" statements can multiply quickly if you have 20 or more devices along with automatic enables and disables together with driving visual and audible annunciation...I guess I don't have a good feel for it yet and am trying to predict performance. Thanks again..

Thanks all...I think I have an idea now.

Hello All, So that I can more effeciently program my ISY, I need to better understand the architecture of the internal system. I have the following questions: 1-Is the ISY continusouly evaluating the IF statement in each program one after the other, in a round-robin fassion? 2-Once an IF/THEN is executing can it be interrupted by another "program"; ie: time, wait, etc? 3-If a device is commanded does it wait for return status before moving to the next program or the next THEN/ELSE statment within the program? 4-Assuming the ISY executes one program then the next then the next....On an average, how many miliseconds does it take for one loop iteration assuming one simple program commanding one device? I realize there are a lot of variables that would effect this. Thanks very much....