Guy Lavoie

Assuming you'll get a eISY (the only controller model currently sold by UDI), you can either get a Zooz 700 series USB dongle if you only need Zwave, or the ZMatter dongle if you also want Zigbee and Matter functionality. Matter connectivity is not released yet.

It's a conceptual idea, that I haven't tested. But I can picture that kind of thing possibly working. Devices can both be controllers and responders (like we do with virtual 3 way circuits) or not, like in many scene applications. That's the big advantage with Insteon: the multiple linking concept. You'd be testing for the virtual light getting turned off, during the nighttime, which shouldn't occur according to your description of the way it's supposed to work. I'd test it with a couple of switches.

It depends on what you mean by if they're turned off "by themselves". By someone manually turning one off? One way might be to use the "Virtual" plugin to create a virtual light that gets turned on at the beginning of the night, and then make all these night lights controllers for a scene that turns that virtual light on or off. That way if one of them is turned off, the virtual light also turns off, and you could have a single IF statement looking for the status change to off for that virtual light, during the night time. Just an idea that I haven't tested.

You could possibly add actual repeats of the command if they're being initiated by a program. Such as send the command, wait a few seconds, and then send it again.

Try encoding it in this order: https://admin:admin@my.isy.io:8443/rest/nodes Replace admin:admin with your own username and password, but in plain text, not base 64 encoded. The base 64 encoding works with a multiline http request. I just tested this successfully on my own eisy, from a chrome browser on Windows 10 to turn on an Insteon switch: http://admin:admin@192.168.0.145:8080/rest/nodes/20 88 BE 1/cmd/DON

Well, the "open" and "close" buttons (at the top right) are normally open momentary contact buttons. Are you looking to just control opening and closing, or more than that (like monitoring status, etc)?

Yes, that's the trick. I migrated from X10 to Insteon that way, doing 3 or 4 devices, then programming them the way I wanted them to work together, to learn the programming at the same. Then a few more. As usual, the first time can be daunting. Yes, there is a learning curve. Not being in a hurry is the best approach.

I had that happen to me 2 days ago. It had been running fine for weeks, then suddenly both my eisy and polisy wouldn't show up. Did the clear cache, full resintall of java, reinstall of launcher...no go. I ended up having to use the "add" button on the launcher to manually tell it where the devices were. Like this: https://192.168.0.145:8443/desc Just write in your own ip address. It worked for both devices. I then did a "save" to make it easier next time. No idea why this suddenly happens.

You need to go into Configuration -> Emails/Notifications. Configure the email server (try it with just the default box checked first), then in Settings/groups, define a recipient group (even if it's just yourself) and then add recipient(s) to the group in the second field. Test...and save. Then you go into Customizations to define a notification type that you'll want to send, and in the second field (content) you compose the actual email with subject and body. Save. Finally, in your programs you can now choose "notify" as an action. You then define the two fields from the select lists. The group you defined earlier as the "to" destination, and the email you defined as "content".

There you go, thanks. Just something to file under "good to know".

I have no idea, but that's what I also understand to be the case.

No urgent need for an answer, just would be nice to know, if anyone already has an answer. I prefer tickets for actual time sensitive issues and problems... It's because as it stands, I first acquired a used ISY994i a few months ago for cheap and got into this world (I was an ADI Ocelot user for the past 25 years), then lucked out on a slightly used eisy, to which I added a Zooz dongle and have since implemented lots of Insteon devices and zwave locks into my home setup. It's my in-use home system. Now just a few days ago, I got a nice used polisy that has the Zmatter board in it. I want to use it as my development and test system. I've already begun plugin development testing. It will also be handy to test any zigbee or matter devices when the support is finally released. I know zigbee is already possible, and will try it when I come across anything zigbee (can it drive Hue bulbs directly?) So at some point in the future, if I ever end up with actual installed zigbee or matter devices, I'll probably want to move the Zmatter board to the eisy. It would be nice to be able to put it back temporarily on the polisy if needed for any testing.

My eisy is running 5.8.4 with the 700 series Zooz stick just fine. I do remember seeing a post saying that if you went from the Zooz stick to the Zmatter board and then try to put the Zooz stick back in, it won't work unless you run a command in unix to undo the upgrade. Look at the highlighted solution here:

My Zmatter equipped Polisy does have it. It might depend on if you started out with the Zmatter board, vs if you upgraded from the Zooz stick to Zmatter.

As the instructions clearly indicate, if someone has a Zmatter board in his polisy and wants to transfer it to a eisy, you take it out, install it the USB enclosure, and then plug into your eisy. My question is this: with the Zmatter board now USB, can it plugged into a polisy as a USB device and work? Or does it have to be reinstalled internally?

Maybe you got that bad 5.8.4_1 update the came out just about a week ago. Tried the rollback? Read this thread:

I've been taking the periodic glance at the discussions about Matter, which often include inquiries about where it's at with UDI. From reading up on it, it's mostly attractive as an interoperability standard, and won't really be offering any functionality that you didn't have before. I compare it to the Cirrus or Plus ATM networks, which allow you to do basic banking at a member bank that's not your own, but not the more detailed stuff that requires you to go to your own bank. For Matter, this might mean on/off and dim commands, but not status tracking or scenes. Controllers like the eisy are how we've been doing this already, using if/then programming to look for commands from one controller type to then issue a command to another platform. The Matter standard (dare I call it a standard...) might make that more transparent to the casual user who prefers to buy a shrink wrapped product (think Apple). Send a Homekit "On" command and the hub will issue the equivalent generic Zigbee "On" command agreed upon in the standard, etc. If this is what it is, then UDI is indeed in a good position to add simplified functionality to an already capable controller. It already does some of that in scene support, allowing you to include a zwave device as a responder to an Insteon scene for example, without writing any programs. Matter does appear to be closely related to Zigbee and Wifi devices. Those two (especially Wifi) data layers have a multitude of incompatible devices all using a common transport layer, but proprietary protocols. The companies that make them know that most people have Wifi at home, so they use that as the mode of transmission, but then write their own protocol and issue their own phone app and a "skill" for Alexa and Google home to make them compatible to those devices so they can put "Works with Alexa/Google home" on the package, but little else. This is where Matter might help make them finally interoperate, and then let them compete on price and features.

Looks like you'll need to get direct support from UDI.

What if you add it manually in the IoX finder? Like this: https://polisy:8443/desc If that doesn't work, enter the IP address you know it obtained (ex) https://192.168.0.100:8443/desc

If you did that on Saturday, before the rollback was issued sometime late Saturday night, then that would not have helped as it would have after the fix was made available.

You'd have to ask that one directly to UD support.

I asked UD about how that worked. It turns out that when you restart your eisy this way, it connects over the web to look for updates or anything that is ideally performed from a cold start (kind of like looking in AUTOEXEC.BAT in good ole DOS). This capability was used by UD to roll back the update.

The fix was probably more related to something else you did, like restart the eisy. The problematic update has been rolled back.

Worked for me too.

A fix has been issued. try the following procedure to install it: Please reboot using the following method: 1. Press/hold power button -> red 2. Click again -> blue Everything working again.