kandlg

I had a similar issue when I migrated to eisy from ISY and filed a ticket. Here is the response I received, which I tried and it did work: To fix this for this particular lock, do the following on the lock node: 1) right+click Z-Wave | Compatability Mode ON 2) right+click Z-Wave | Validation | OFF 3) right+click Z-Wave | Rewrite All Device Links This will write the necessary associations to the BE469ZP and thus it should then automatically report the status of the lock to IoX. Note: For most devices you want to keep Validation ON and only turn it OFF as a last resort. I have since moved on to Home Assistant for all my Z-Wave devices and bridge with my eisy for the insteon devices. It works much better.

From the wiki: If you don't have Yellow/Red bands, then look for Zigbee and Z-Wave imprints (faint) at the base of the antenna. https://wiki.universal-devices.com/Eisy:User_Guide#Z-Wave_Support

I found an old IRLinc Transmitter 2411T and tried to link it to my Eisy for control of an A/C. It starts linking, but continues in a seemingly endless loop of adding nodes. After about 30 minutes and 7 nodes it was still going and I stopped it by rebooting the unit. Does this device still work with Eisy and if so anyone have experience with how to add it? Thanks

Thank you. I didn't notice the trash can up there.

Thanks for the feedback. I don't have an option for status for my WOL device, but thanks to your comment I set up a command type favorite using another device's status. This has fixed my initial issue. Now I have an issue with WOL node actually working. I've double checked the MAC and IP and all are correct. The devices are on the same network. From the log: ERROR wol:wakeOnLan: Failed to send WOL packet to Desktop: [Errno 8] Name does not resolve

I would like to add a WOL favorite in UD Mobile, but it appears that all the node types require a status, which WOL nodes do not have. Am I missing a node type which does not have a status or if not can this be supported? A dummy status could be added to the node server or the app could be modified, but the former seems easier.

If you are having an issue with a z-wave device, submit a ticket. They've helped me get some working after I converted to Eisy. I've got all the Z-Wave devices I had running with my ISY working again. I think the limitations are more Z-Wave than Eisy.

I agree Z-wave is harder to manage. There may be a better way to do it, but I use the buttons as toggle switches with two programs: one for on and the other for off. The below is an example: If a light is on, it turns the scene off. The wait at the end prevents a perpetual on/off loop. Not sure why it is required, but it works. I tried putting it in one program with then as "on" and else as "off", but that went into a loop also.

Yes. See this thread. The model number is actually MR40Z.

I had a similar experience. I had a bad POE camera on my network that would go off and back on periodically and take my Eisy down with it, requiring a reboot of the Eisy. Removed the camera and the Eisy is working OK now.

I was finally able to get this to work. Add it through the z-wave include process with security. All the correct nodes won't be installed at this point, but then turn on compatibility mode and synchronize - update with interview. Pressing button three 5 times on the remote will wake it up so the interview can complete. Once the interview is finished all four scene buttons will be available.

I suspect these are the same as the original ZEN 32s and if that is the case the smaller four buttons of the Zen 32 are scene controllers and only report an "on" command when pushed. This is normal behavior for the original ZEN 32 according to Zooz tech support. If you want to spend some time with programming, you can set up some logic and use advanced configuration commands to turn the LEDs on the small buttons on and off to reflect the status of what they are controlling. I purchased a couple of these as potential replacements for the 8 button insteon switches when insteon went out of business. I managed to get it to work like I wanted with the led on the small buttons reflecting status of the scene as a test, but never installed them permanently and don't think I will since the insteon devices are available again.

I'm having the same issue on the lack of status updates when the lock is manually operated. Interestingly, two of them migrated from ISY and work fine, but the one that does not work is one that I had to exclude/include to operate properly. I've filed a support ticket and will post back if I get any feedback. I've lost a lot of Z-wave functionality moving to Eisy/Z-Matter and am beginning to regret the decision to "upgrade". Can issues like these be fixed with firmware updates to Eisy/Z-matter?

I migrated from ISY994 w/500 z-wave and have several devices that wouldn't migrate so I'm trying to exclude some of them and then re-include. The first I tried was the Minoston MR40Z switch. I can't get it to add securely. Without security the buttons don't aren't mapped and it is unusable. Anyone had any luck with these switches? Eisy with Z-Matter on 5.7.1 and 21100 Z-Wave.

I think this is what you are looking for. They used to sell it by itself, but it looks like it's only available as a garage door kit. Maybe it's hidden somewhere else in the store. I/O Module - Owner's Manual — Insteon I/O Module - Garage Door Control & Status Kit – Insteon

I am using a ZEN17 as a garage door controller/sensor. The status sensor on the ZEN17 is connected to a magnetic door sensor and reports changes in status very quickly and is very reliable. I am using an ISY 994 FW 5.3.4 and the ZEN17 is about 40 feet and several walls from the ISY and is relaying through other powered nodes. These are the settings I have changed from default: Set all relays to off after power fail: Parameter 1 set to 0. Set relay 1 to garage door with independent trigger: Parameter 2 set to 11. Set relay 1 to independent from switch: Parameter 10 set to 0 In my ISY the door status shows as "Barrier 1" and reports as "Open" or "Closed". I know the configuration is different from yours, but I have it working reliably with ISY which was one of your original questions.

With the demise of Insteon I've been looking for replacement devices and buying a few to test out. I liked Insteon's remote switches, but the batteries on a couple of mine are dying and one is acting flaky so I thought I would try the Zooz ZEN34. I saw a couple of threads here saying the ZEN34 worked with ISY, but I didn't see an explanation and I didn't understand what all the nodes were for and I started playing around with it. I have pretty limited Z-wave and programming skills so I thought I would post what I found and maybe someone can comment if there is a better way to do the advanced things. A couple of very obvious points: The Wall Controller shows the battery level. The Basic Control 2 includes the status of the switch with 0 as Off and 255 as On. I thought maybe pressing and holding could get it to a point somewhere in between for dimming, but no luck. Scene button 1 is the top part of the switch and Scene button 2 is the bottom part of the switch and can trigger programs. I was unable to determine a purpose for the multilevel switch 3. I've been able to include the Basic Control 2 device in a scene as a controller and it will turn Insteon devices on and off, though there is a bit of a delay. There were no options/dropdowns for the device within the scene. Scene Button 1 and 2: I could set up programs using the two Scene Buttons. On= single press; Fast On = double press; triple, 4x and 5x respond as expected. To make use of them you need to set up separate programs for Buttons 1 and 2: one for the on function and one for the off function. Pressing and holding the button does support dimming with the use of a program (I couldn't get it to work when put in a scene with insteon devices): Fade up and Fade stop can be used to brighten / dim a dimmer device using separate programs: One program to start the brighten action when the button is pressed and held (Fade Up) and one program to stop the brighten action when the button is released (Fade Stop). Buttons 1 and 2 have to be set up separately for brighten and dim, requiring four programs total. I was concerned this wouldn't work well due to the system lag with Z-wave, but it worked fine. It seems to have a lot of capability, but a bit difficult to implement in ISY.

I gave one of these a try and I’ve been talking to Zooz customer support. They say this behavior only occurs on the ISY and that it is how the ISY sets up the associations, “probably in an outdated manner.” Not sure if that is right or they are passing the buck. They said they were going to reach out to see if ISY would update it on their side.

I figured it out. I right clicked on the node and added a button press node for both devices. After adding these to the scene as controllers with the regular device as a responder it works properly as a three-way switch. This custom button press item can then be used to detect on and off button presses and run programs. I am not sure why this item is not added by default when you add a device and it is a separate step. I am on 5.3.0 and I think I have a 500 series since I bought it last year.

Thank you for the suggestions. Yes I tried adding them both as controllers. Nothing happens. If I use status instead of control I end up with an endless loop of them switching on and off until I disable one of the programs.

I am new to using z-wave with the ISY and am having trouble creating a scene in which two switches with independent lines and loads to essentially become a three-way switch without the wiring connection. I tried to add them both as controllers to a scene like I have before with insteon devices but that doesn't work. The switches are Honeywell Ultrapro 39348. There are a number of "child" devices (as shown below for one of them) - should I be including a certain combination of those? Another issue - I also tried to include the switch in a program based on switching on or off. The only one that allows me to build a condition for status control doesn't have an "Off" control, only an "On". Is this a limitation of the specific switches or issues in general with ISY or, more likely, user error? Any help would be appreciated.