Guy Lavoie

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:

Would you be willing to ship to Canada, by US mail?

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.

Yup, count me among the healed! A big thanks to Michel for such a quick fix, and over a weekend too.

The rising body count indicates that this is a pretty fundamental issue, and should (I said should...) bring a quick fix.

Was an IoX update installed a few days ago? Look at these forum threads:

Looks like our exclusive 5.8.4_1 club is growing.

Given that you upgraded on Oct 3rd, I'm just wondering if you're getting the same problem I'm having, after an update notification appeared and I installed it, at around noon on Oct 3rd. Run this command: https://eisy.local:8443/WEB/sysconfig.txt And scroll down to the isy version. Are you seeing 5.8.4 or 5.8.4_1 ? I had it go from 5.8.4 to 5.8.4_1 and have been having several problems since.

Ok just tried all that. Cleared java cache, reinstalled launcher. Same problem. If I try to turn on a X10 device, I get a window that says: Socket Open Failed java.net.ConnectException: Connection refused: no further information Then about a minute later, another window pops up asking me to log into admin again, asking for user id and password. Looks like I'm really stuck. The origin of that 5.8.4_1 update is really mysterious. It popped up as a "needed update" when I launched UD mobile on Thursday, at the time you see the update. I'm guessing that this is the probable source of my problems, and I wonder why I'm the only one who got this update. Is there a provision to roll back updates? I haven't found anything.

If you can construct multiline URLs, the better way is to encode the username and password as a base 64 value, and include it as a parameter. Browsers do this internally. It looks like this: GET /rest/programs/0009/runThen HTTP/1.0 Host: 192.168.160.31:8080 Authorization: YWRtaW46YWRtaW4= That authorization value is the result of encoding "admin:admin" You can encode your own userid:password here https://www.base64encode.net/

You can encode the username and password into the http GET string, like this: http://admin:<password>@192.168.160.31:8080/rest/programs/0009/runThen replace <password> with the actual password

Thanks guys. I'm getting these numbers: UDX 3.5.8 Version : 5.8.4_1 Installed on : Thu Oct 3 12:52:59 2024 EDT (it's the "_1" that caught my eye when the upgrade notification appeared, glad it wasn't just my imagination...) Pg3X 3.2.27 If I just leave the admin console running and go away, it's frozen when I return an hour later. I have to kill it using the windows task manager.