Guy Lavoie

The other hidden benefit of looking for control events (instead of status change) is that it allows you to separate the status display from triggering action. In other words, you can have a program update the status of that device, which will show in UD Mobile, without triggering the control event that you would get by pressing a button on it. Updating the status triggers a status change, but not a control event. This is the same benefit that you get with Keypadlincs.

What you've discovered is that at this point, eisy isn't very good at configuring (commissioning) a new Matter device, but it's becoming better at accepting a shared Matter device from another platform, like Alexa or Google home. That's how we mainly do it at this time. It's still in Alpha testing on the eisy.

The first step might be to try a "restore device" (right click on the switch in Admin Console to see that option). That should rewrite the links between it and the PLM. If that doesn't work, then the next step might be a factory reset of the switch and then relinking it to the controller.

Well that's what forum buddies are for! Seriously though, this wasn't very well explained in the release announcement. It took a bit of figuring out to get things working the "old" way. Changing the default login method automatically to the new one wasn't the best thing, and has caused lots of grief. A good idea, badly implemented. A pop up box offering the new method (with an option to choose it) would have been better.

There is no harm in having both eisy login methods listed if you plan on using eisy-ui and/or polyglot and/or the portal every now and then. Using the portal login makes going from one to the other seamless.

Try adding a new entry to IoX finder, to log in the old way (admin...). Click on Add, then enter the URL as (for example): https://192.168.0.123:8443/desc The port number 8443 will have it request your IoX login name (usually admin, admin) and password.

Have you tried going into your phone's settings screen -> Apps, then finding the UD Mobile app, and clearing cache?

I had been holding off on upgrading my in-service eisy, which was still on 5.9.1. After testing 6.0.0. and 6.0.3 on a test Polisy, and seeing that the release notes in the sysconfig.txt file indicated only minor fixes for 6.0.4, I concluded that the new version must be stable enough to give it a go. So with lots of trepidation (and a couple of prayers) I went ahead and launched the upgrade. Of course, doing this on a day like Christmas would usually be quite foolhardy, with no UDI support readily available. But I have a eisy recovery image on a USB all set, and a screen and keyboard at the ready. So I started by doing a full cpio backup of my entire eisy to a USB drive first. In a nutshell, it worked out ok. I had to manually add the eisy back to IoX finder before I could see it. I added both lines for the IoX and portal logins. Then I took a quick tour of my system. Insteon was Insteoning, Zwave was Zwaving. Plugins seemed to be up and running ok. The only thing not quite working is eisy-ui, which isn't critical for me at this time. I indicated that in the appropriate forum section. I guess getting an updated recovery image would be a good next step, to keep my first aid kit up to date.

I just updated to IoX 6.0.4 and I did get the blank page in eisy-ui. Now I'm getting some things displaying but with errors. For example the Nodes page shows the nodes for about 2 seconds, then goes blank and shows an error 404. It displays the program list ok but if I click on any program, I get "error loading profiles" where the program listing should be. The System -> Upgrade page is showing all the latest versions ok.

What's not working is...my brain! Hehe, I just retested this and yes, it does generate control events. I've only been into the eisy for just over a year, so I'm still learning. That excuse will thus be expiring sooner than later 😀. I think that what threw me off was that initially I was testing it from admin console, before I got more into UD Mobile, where it really becomes more useful. It would be handy if UD Mobile allowed you to optionally display a switch as two little on/off buttons instead of default toggle, without needing to go into the switch's detailed menu. So Virtual just keeps getting better. Even more when you understand how it works! 😄

Yup, my mistake, Virtual does send control events too. I just retested it to my satisfaction. Sorry about the misdirection.

The fact that virtual devices don't generate control events can be worked around, by having the status change trigger a program that then resets the status after a short wait. It just makes things a bit more cumbersome.

Yup, that plus a few more Matter related fixes and improvements:

I guess triggering device changes from UD Mobile is indistinguishable from doing the same thing from Admin Console, right? It would have been nice if turning a virtual switch on or off from UD Mobile could generate Control events as well as Status change events, just like a physical switch. Wishful thinking?

One thing: the Virtual plugin doesn't generate Switched events, only Status changes. It would be handy if it could create Switched events too, but there is no physical device involved.

You install it by going into "plugins" and selecting PG3. This will allow you to log into PG3 then select and install the plugin from the production list. The more information button will let you see the instructions on how to define virtual devices by entering custom parameters.

Click on Link management at the top, then Start Linking You will get a pop up window telling you to put the device in linking mode. Do that, and it will find the device, and show you the device ID too.

Two useful things to know as you open a ticket: Can you see it in your router'sdevice table? If so, can you ping it? Be prepared to hook up a keyboard and a hdmi screen if asked to do so.

Controllers like Google home and eisy don't necessarily "see" each other like that, unless some utility provides that. Instead, you share devices. In Google home (since this is what you have) look for a function to share that device, which will offer you either a pin code or a qr code, that will be valid for a limited time (often a few minutes) that you can then use in UD mobile to add the device to the eisy. Pin codes are easier because you can write them down, while a qr code is an image, which you have to scan ( awkward when you are running both Google home and UD Mobile on the same phone). In testing, I'd save a phone screen shot, email it to myself, open it on my pc, and scan it off the screen with UD Mobile. Hardly user friendly. Now UD Mobile supports entering a Matter pin, much better.

I'm still running 5.9.1 on my eisy, but I did get a message in UD Mobile telling me to synchronize. Until I did that, my custom icons weren't displaying, I was seeing all light bulbs. Now back to normal after doing a sync

Here is the thread I think you're looking for, as per your first post. I used that as a basis for my own monitoring of my triggerlincs and leak sensors:

Yes, that's the usual way to install updates.

Do you also have Insteon devices anywhere? If so, is the PLM able to control those?

What made you determine that the Polisy was overworked?

It would really help if UDI came up with a way of indicating the progress of an update. The uncertainty and varying update speed isn't very helpful at seeing if things are proceeding properly.