I've seen a number of posts of people having trouble with using a Mimolite as a momentary switch but most of those issues seem like they didn't read the manual where it says that "Momentary vs Latched relay operation is selected by jumper P5 on the circuit board. The Momentary / Latched jumper is read only at power on when the MIMOlite is not in a ZWave network. "
I'm seeing a more basic problem which is possibly adding to that confusion and is my specific problem.
When you trigger it to "on" (from the dashboard or the device properties) part of the time it works correctly and part of the time HE will leave it showing the state of the switch as "on". The switch isn't on as you can stand next the Mimolite and you hear the relay close contact and then immediately open contact. The device properties correctly show that the contact is "open". When HE is incorrectly showing the switch state rarely will update the state after a while but usually you have to specifically trigger "off" (which doesn't do anything to the relay that is already off) to get HE to correctly report the switch state as "off".
Basically there should never be a time where the contact is "open" and the switch shows as "on". Something is broken here.
Also shouldn't any z-wave device report it's state at some point to update the hub? At worst I'd expect it to update in a minute or so.
These always worked flawlessly in Wink (Yes... There was stuff that worked in WINK!) and it worked pretty smoothly in Vera except sometimes it took 5 or 6 seconds to correctly update the state to "off".
Background info. The Mimolite is about 12 feet from the C8 hub so communication shouldn't be an issue. I've tried configuring the dashboard tile as a relay or a switch with no difference. The state can "stick wrong" from the device properties page or the dashboard. Sometimes I can trigger it 10 times in a row with no error and then sometimes it will screw up more than 50% of the time.
Lutron’s instant status patent meant that Zwave devices either had to rely on mesh-intensive methods like HAIL to get the zwave controller to poll them for status, or for a periodic polling process to run on the controller, which is also mesh-intensive. The Fortrezz Mimolite doesn't support HAIL, so it requires the latter.
From my perspective, it is befuddling that someone would want to use a 300-series device, like the Mimolite, with a 800-series controller.
The 300 series choice is pretty clear. I have four of them already in place already mounted and wired into the grounds access gate and the three garage doors. And they have been working perfectly for over 5 years. Plus they are already paid for. No reason to create more work for more money.
Also when I got them the Mimolite was the only momentary switch available. I'm not aware of another z-wave momentary switch that is available but I haven't been looking for one as I don't need any more.
Is there a way to get the source code for the Mimolite driver in some form because it seems apparent that they messed something up in the logic. Or maybe it just needs a version that is specific to a Mimolite that is set to momentary.
Noob to direct z-wave commands and can't find a command reference for z-wave so don't know the connect syntax. I wish I had a test environment. I'll probably need to get one with some of the things I want to do.
Wayne's computing commandment #1:"Never do anything you can't undo!"
Headed out of the country today so I threw a bandaid on the problem and setup a virtual switch to trigger it. (but my OCD will grind its teeth on something "working at random"...)
) and it worked pretty smoothly in Vera except sometimes it took 5 or 6 seconds to correctly update the state to "off".
