kandlg

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.