Guy Lavoie

I've been messing with Matter (and it's been messing with me). I've had some success, and some frustrations. You need to keep in mind that this is still very much beta for UDI. I suspect that until now, support will mostly be for output devices like bulbs and plug in modules. I'm not sure if sensors are supported yet. I did try a Kajplats bulb in March, which worked well. You can read up on some of my experiments and discussions about Matter devices here:

So when you click on the Zigbee menu at the top, you get the various options (Add a Zigbee device, etc) right? That means that it's seeing the dongle. The next thing to try would be to try and factory reset the device you want to add, and then try adding it back. This usually involves something like holding down a button on it while powering it up, or some similar procedure. See the instructions that come with the device.

Have you tried a reboot that includes actuallypowering off your eisy?

If ELSE works by executing the command only the first time the statement becomes false, that might work too.

I think the keypadlinc really exists for this kind of thing. The ability to set a button's backlight on or off remotely (and set it's next sent command as on or off based on this, when set to toggle mode) provides the versatility you're looking for. I have one keypadlinc near my exit door with one button indicating whether any basement light is on. And that includes Hue bulbs in lamps, etc. That's the nice thing about using a program. So if anything;s status is On, the button gets lit by the program. That's a whole bunch of Or statements. Conversely, if everything is Off, the button backlight gets turned off. That's a whole bunch of And statements. These are two programs that are just left to run continuously, not triggered to run by any switch actions. There is always a short (about 2 second) delay between a status condition that warrants turning the key backlight on or off, but it's been very reliable.

Not that I know of. I'd look for control on and control off events (with Or statements).

Yes that's what I did, which includes then pressing and holding it in until it beeps continuously and then stops. That did clear it, but restoring the switch had brought back the beep. That's why I then deleted it from IoX, followed by another factory reset.

I tried writing that very setting to the switch (with a value of 0) but that wouldn't disable the beep.

I just came across an interesting twist with a used 2477D that I just acquired locally (as a spare). I hooked up power to it, and it worked normally, but it would do a short beep every time that I turned it on or off manually. Then I linked it to a test Polisy and that went fine, but still did the beep thing when operated manually. It wouldn't do that when controlled by the Polisy. So I though I'd factory reset it (airgap) and the beep thing stopped. But surprise: doing a "restore device" from the Polisy restored the beep. As if it was part of the configuration information that it obtained from the switch when I first linked it. Ok, so now I deleted it from the Polisy, and factory reset it again, and relinked it again as a new switch. Now the beep is gone, just like a 2477D usually works. There is no settable feature in IoX for beep on touch, but it looks like the switch can be set to do that. It had been used with an Insteon hub. Interesting.

When you use IoX finder, select loading the admin console from cloud. This will download and update the version on your eisy. Updating from eisy to eisy r2 would be a marginal improvement. The r2 is a bit faster and produces less heat.

Have you then tried exiting admin console and then logging back in, and try it again? Node discovery (or rediscovery) often need you to restart your console session.

0.1.11 is the origianl one, probably what you've been using up until now. I have that one too. The newer one uses the V2 Hue API and is meant to also support the new Hub Pro, which only supports V2.

Are you using the Hue plugin? Have you tried rediscovering the Hue bridge (re-discover bulbs button in the main node) to have it learn the new bridge IP address?

It doesn't work even with the port number (8443) in the url? Have tried using your actual IP address instead of eisy.local? eg: http://192.168.0.123:8443/desc

Did you first add it to another platform, then use a share pin or QR code to add it to your eisy?

I just stumbled across the announcement for the eisy lite. The cost of RAM has pushed up the price of the eisy r2 again, and UDI wanted to offer a lower cost alternative. The interesting thing is that the eisy lite has 4 GB of RAM instead of 8, and is a bit slower. That kind of vindicates the viability of the Polisy, which also has 4 GB. Just a thought. The r2 price hasn't increased at the Canadian ditributor yet. If you're in Canada and want one, don't wait!

Yes, that backup you have is the key. Set up your eisy and restore the backup on it. Look here, scroll down to "Migration" https://wiki.universal-devices.com/Eisy:User_Guide

No, scene commands are broadcasts from a controller to all devices, and all responders recognizing the scene number then do their thing. That the beauty of Insteon, it's peer to peer. The eisy always includes itself (ie: it's PLM) in scenes so it can see Insteon status and control changes, so it can track them and optionally trigger programs.

I agree. I've had a similar issue once about a year ago. Not fun. Let us know how it turns out.

I'd also open a ticket, if you want to get your eisy properly upgraded. 5.8.4 is getting rather old.

Given that the current version is meant to be upgraded from 5.9.1 or later, it is best that this upgrade didn't happen. But getting launched automatically isn't something that should have happened. You say that the dirst hint was a message saying that it was already in progress?

In principle, you don't need to do anything if you're keeping your existing router. If you're getting a new router, then if you have your eisy communicating with other devices that talk to it over IP on your local network, then you might need to make IP address reservations that correspond to any current ones configured in your existing router.

You need to encode the login name and password into the http GET statement, like this: GET /rest/vars/set/2/2/78 HTTP/1.0 Host: 192.168.0.123 Authorization: admin:admin

If you mean directly by the motion sensor (ie: not using a program) then no, that won't be possible. You'll have to use a program, and tolerate the slight delay.

I think he simply wants to keep his established direct, device to device setup working as it does, without needing to recreate all the original scenes in the isy994i.