Guy Lavoie

Well that would be whatever the actual command you are using would be. I was assuming that you had this set up already and that you had noticed that the door would activate no matter if you asked it to open or close.
If you haven't really set anything up yet, I would suggest that you set up the garage door device in the portal to set a variable, to make it single triggering. It would be something like this: Make the Alexa Open command set (let's call it the Door_command_variable) to 1, and the Alexa Close command set it to 2. Now the program logic would go like this:
If Door_command_variable = 1
    And Tilt sensor variable = "closed"
      Then Open door
      Then Door_command_variable = 0
 
If Door_command_variable = 2
    And Tilt sensor variable = "open"
        Then Close door
        Then Door_command_variable = 0
 
Setting the variable back to 0 makes sure that nothing will happen until a new, valid command is issued. 

1- you can usually choose the backup file by browsing your computer
2- Could you see the status changes in the admin console when operating the switches manually?
3- If the switches are already listed in the admin console, did you delete them first?

No. the Virtual plugin creates a virtual device (switch, etc) in the eisy, mainly for the purpose of acting as a flag in scenes, so that you can do things like trigger program actions on the status of the virtual switch being on or off, having been turned on or off by a scene command. IoX doesn't have an instruction to trigger on a scene command (eg: if Scene kitchen is turned on). Since individual switches can usually be turned on or off by themselves as well as through scene commands, the trick is to add a virtual switch to it, which cannot be turned on other than by the scene command. Monitoring the status of that switch can thus be your indication of a change due to a scene command.
The plugin also has other virtual device types than switches (dimmer, generic, temperature) which might also be useful for other types of situations. I have not used those.
If you know the protocol and communication type (wifi, zigbee, etc) then you could potentially control them directly with the eisy, or by using the network module.

Well you'll need to wait until UDI releases the update that supports Matter. That should be very soon according to the latest announcement:
https://www.universal-devices.com/2025-liftoff/

The currently installed firmware version will remain. I've factory reset a ISY994i with a 300 series Zwave card and it didn't cause any issues.

That goes for most plugins where you configure it by making parameter changes or doing some type of discovery. You need to exit the admin console and log back in to see the results.

Well you can't really have two physical switches controlling the same light (unless you wired two relay switches in parallel or something...). Sounds like you have one switch, the one that works, actually controlling the light. The second one would probably be set up as a virtual 3 way switch, controlling the first one. If that's the case, then it probably doesn't have any load connected to it. Thus turning that switch on or off remotely, such as through the admin console, wouldn't do anything. It won't receive the command and then retransmit it as if it had been manually activated. 
So that sounds normal.

Well try clicking on them to send your changes after choosing your values. That's how I do it, as indicated in my first post.

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.

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/

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.

This has a happy ending! From reading and searching, I discovered the plugin called "Virtual" which seems to be exactly there for this purpose. This forum reply will also help anyone looking for this functionality in the future. Virtual allows you to create virtual switches (and other devices) which can then be added as responders to scenes. Turn on a scene and the virtual switch turns on too, and same for off. Then you can use the virtual device in a IF statement just like an actual device. Because the device only exists as a responder for the scene, no need to "guess" the status of several devices as suggested earlier.
Having this capability helps maintain the optimum failure mode for an Insteon setup, since Insteon is peer to peer. So if the eisy/PLM/whatever ever fails, the generic scene will still function, and only the additional functionality provided by the eisy will be lost. This is different than relying on eisy to launch the scene just because you also want added functionality in a program.