Guy Lavoie

I'm still rather new at this (a year and a half) but the things that work for me: Put all programs related to a common function or area in distinct folders. So I have a folder for all shade related programs, another folder for water leak detection, another one for locks, etc. For device naming, I'll tend to name devices with a prefix for the type of device it is, so Leak_<name> for leak detectors, Motion_<name> for motion sensors, etc. IoX tends to do that by default too for devices like ZWave (ZW_<name>) Matter (ZM<name>. Of course you can rename them anything you want, but I like to keep that prefix. For light switches, well as an X10 user for the previous 25 years, I knew the rooms by their house/unit codes by heart, so I kept the naming scheme as a prefix: eg C4_living_room, B2_office, etc. They did have a natural progression throughout the house and each house code grouped something or a floor, so that remained meaningful. For variables, status variables get name s_<name> and integer variables as i_<name>. For Alexa, I keep the spokens to single words, for reliability ("living", not "living room"). Sounds a bit awkward sometimes.

You'll need to have it appear on your local network before thinking about seeing it in IoX finder or the portal. The first thing to try would be powering it off and then back on. Try that a couple of times, giving it a couple of minutes to reconnect. If that doesn't solve it, you might need to open a ticket, and be ready to have a hdmi moniter and keyboard attached.

I don't know how "scenes" work in Zwave, but with Insteon, you set up scenes that make the switches communicate directly with each other, so the eisy isn't involved in the actual communication between them, making for very fast response.

Does it appear in your router's connected devices table? If so, have you tried a ssh connection to it from your PC?

You could create a "all off" scene with everything you want turned off as responders.

There are both "All Units Off" and "All Lights Off" commands, depending on if you want to turn off all devices or just lights, on a given house code.

Well it sounds like he wants to run a Hue emulator on the eisy (there is a plugin called Hue Emulator). So access to the eisy and the Hue emulator would both be at the same IP address. If the IoX port could be changed to something else than 8080 then this could be a solution, but the ports number isn't currently editable in Configuration. So that's a good question.

I did experiment with triggering Alexa routines with a variable change in isy. It worked but indeed, there was a variable delay that would occur, sometimes 10 seconds or more.

Could something generating electrical noise be jamming the signals? Anything new added to the household?

I've kept all the spokens to single word names. That can get challenging when you're up to 50 devices but it seems to make things more reliable.

Speaking of backups, I also do the one I describe here:

Not all LED lights work well with dimmers, even if you don't dim them. Is the fixture itself rated as dimmable? Many aren't.

Did you ever figure out how to get the temperature device to be recognized as such by Alexa? Just wondering. Thanks.

The same thing happened with one of my Polisys, updating from 6.0.0 to 6.0.4, upon a reboot (which came after powering it up after I flashed it's SSD with a 6.0.0 image I had made in September). Looks like they're taking a page from Microsoft's playbook, doing upgrades on the fly upon a reboot. I'm guessing that they figured 6.0.0 wasn't stable enough to leave as-is on a running system.

It could just be going bad, such as a bad capacitor.

Can you see your eisy among your router's device table?

The usual advice is to go into java and clear the cache (all 3 clear options). My personal approach is to click on "Add" in IoX finder and manually enter the url. For example if the IP address of your eisy is 192.168.0.123 then enter: https://192.168.0.123:8443/desc Then click on the new entry. If that works out, saving it to a file (click on "Save") is handy, so you can load it from a file the next time this happens.

I had a similar experience with one of my two Polisys. It took a long time to update, though I left for lunch while it was still going so I can't say how long it all took. I was monitoring the log file with a tail -f so I know it was busy doing it.

My understanding of the wall mounted panels on the old Chamberlain openers (which is what I have) is that they have only two wires but have three buttons: open/close, light, and lock. The open/close button shorts the two wires together, which what we do when we use a IO Linc to operate the door. The other two buttons would put capacitors across the wires, altering an oscillator circuit that the main controller board in the opener could distinguish to know which button was pressed. With the newer openers, the wall mounted panel only receives power, and the buttons make the panel transmit rf commands, just like a remote. This would mean that you need to open up the panel and wire the IO Linc across the contacts of the open/close button itself, instead of the external wires supplying power to the panel.

Can you ssh into it? If you're not in a position to wait for UDI support in 2 days, you can try this: ssh admin@eisy (or ssh admin@<ipaddress>) Then try: sudo pkg install -f isy sudo pkg install -f udx If it asks you to allow reinstalling packages, respond with yes. If it completes ok, then wait at least 10 minutes, and then reboot: sudo shutdown -r now See if that brings you back up.

Fresh batteries would be step#1

Motion sensors can certainly add to irregular triggering. Adding cats to the mix steps that up another few notches!

I've always saved the device list whenever the list changes, and I've never needed to do the clear java cache thing. It would be handy if we could add a link to eisy-ui among the entries. A one stop shop for whatever access method we want.

The nodes in folders I'm seeing aren't ones I created. In fact I've never tried that myself in admin console. The ones I see are those created by plugins, such as the Hue plugin.

This morning I can confirm that it's now working for me, which is the first time I'm trying this plugin.