Mimolite - Garage Door

[Charles3]

I recently purchased a z-wave mimolite device. I want to use this device to open my garage door.

I have added the mimolite to my device list in isy. However when I attempt to turn it on it appears that it sends a signal to the mimolite 3 times. All 3 times the mimolite lite responds and I can hear the relay clicking. After 3 times I get a response back in ISY it cant communicate and then it has ! listed next to the device.

I have removed the jumper on the mimolite to set it in momentary switch mode.

How do I get ISY to send 1 command to enable the mimolite and then stop?

I've tried adding and removing the device.

When I add the device I get the errors in the image below.

[Charles3]

So I have been trying to do some more research. I have just recently added the zwave module to my isy994i.

I added tilt sensor with no issue. The one issue I did have is the distance. The distance between the isy and sensor has to be less than 40'. Tonight as I stated above I attempted to add a mimolite device. I was able to add it and it showed 4 different devices in isy994i. When I try to active the binary switch device my mimolite clicks 3 times with about 2 second pause between each click. Then the ISY console reports a communication error and disables the device.

So I read some more that I should do a factory reset on the zwave module when I get it installed. So I did that and there were no errors. Then I reset the isy by unplugging it.

Then I looked at the zwave module firmware. Currently it is showing Bootloader 0.0

I tried to run the upgrade z-wave firmware option.

A few seconds into it says: Now Updating - do not turn off isy
Then at 10% it say Cannot Enter into Programming Mode

I am not sure what to do from here...

[oberkc]

I hope you get an answer to this.  I am having zwave issues and similar failed communications.  Interestingly, my zwave devices appear to respond reliably, but the comminication errors seem to be based upon lack of comms back from the device.  Also in my case, some zwave devices seem to work ok, with no error messages or red exclamation points, si I assume that the zwave module and software are fine.

I have a single zwave repeater, and my perception is that moving this device around can affect which devices fail, so I am treating this problem as devices beong out of optimal range and have ordered som additinal repeaters.  I will try to remember to report back if this solves the problem.

Is this mimolite device your home only zwave unit?  I cannot help but wonder if you, simply, dont have enough zwave devices to forum a robust network.

[Charles3]

I only have one other tilt sensor that is zwave. As long as its in close proximity of the isy hub then it works flawlessly. The mimolite is the new device I am trying to setup. Currently it is sitting next to the isy, so hopefully proximity is not an issue. It adds 4 devices to the isy. But when I try to activate the mimolite Binary Switch node it acts as if its not receiving a response from the mimolite, however the mimolite activates 3 times everytime I send the turn on command from isy.

I imagine once I get it working I will have to buy a zwave repeater. However my garage motor where the mimolite will be sitting is about 40' away. So Ill have to wait and see.

[Charles3]

So has anyone else had an issue like mine with the mimolite? I am at a loss here on how to set this up. Can anyone confirm if I need to download some firmware update?

Is it normal for the Z-Wave Version boot loaded to show 0.00?

Attached is my current ISY Version

[mwester]

Try the most recent 5.0.x version -- it's still beta, but it's working very well for most users that try it -- and it has far better z-wave support.

[Charles3]

Where do I find the beta version?

[dbuss]

3 minutes ago, Charles3 said:

Where do I find the beta version?

 

[Charles3]

Thanks I got my ISY updated to the latest version. 

I am not sure if my Z-wave firmware is most up to date. When I try to run the update I get the error below.

[Charles3]

So now I have tried adding my mimolite back in.

I excluded it, and then added it. Once it was added it showed the 4 devices below.

But my biggest problem is trying to control it. When I try to turn the binary switch on I get the error in the second pic.

Anyone have any idea what is causing this?

[dbuss]

@Charles3 , unless you have the new Z-wave dongle, you don't need the latest Z-Wave upgrade. Z-Wave firmware version 4.55 is what you should be using.

[rccoleman]

Based on his screenshot, he has the latest series 500 dongle and the right firmware version (6.81.00).

[Charles3]

I assume I have the latest dongle, but not sure. I bought it recently and installed the board inside my isy994i unit.

I just wish I could figure out why it wont communicate.

Currently I cant get the mimolite unit to respond at all. Prior to the update the mimolite responded 3 times and the Isy controller timed out, I assume because it was not receiving a response from the mimolite.

This is the error I get when I try to turn the mimolite binary switch on.
Currently on the mimolite unit I removed the jumper to set it to momentary mode. Would this affect it?

[rccoleman]

34 minutes ago, Charles3 said:

I assume I have the latest dongle, but not sure. I bought it recently and installed the board inside my isy994i unit.

I just wish I could figure out why it wont communicate.

Currently I cant get the mimolite unit to respond at all. Prior to the update the mimolite responded 3 times and the Isy controller timed out, I assume because it was not receiving a response from the mimolite.

This is the error I get when I try to turn the mimolite binary switch on.
Currently on the mimolite unit I removed the jumper to set it to momentary mode. Would this affect it?

I get a similar error when I query my MIMOLite that I use with my garage door, but I can trigger the relay and the status does update. It has some trouble getting synced up after an ISY reboot and I have to manually trigger the door to get it to start working. I reported this back in the early 5.0.13 days with the old dongle, so it’s not a new issue.