apostolakisl

good to hear!

I am on 4.2.0 as well. It fixed the similar issue with Elk node not populating, but either created or didn't fix the GVx issue with programs. I don't often look at programs on UD mobile, so not sure when it started. @Javi

I already have the latest updates.

Really there are only two things. 1) The scene isn't being discovered by Alexa, or 2) the "spoken" isn't being understand by Alexa to refer to the scene. First off, from your phone Alexa app, see is the scene is even there. If not, then it isn't being discovered. If it is there, try creating a routine in Alexa to control the scene and see if that controls the scene. If so, then there is some issue with the "spoken" not lining up. If the routine works, you can make some spoken words for controlling the routine and leave it like that.

Is this a new development? Last I added stuff about 6 months ago, I had to do a discover. I was using the Alexa app to discover, so if something was going to pop up on its own, I would have seen it.

So you are saying that Alexa is doing some periodic discovery process all on its own? Every time I added a device, nothing popped up immediately. I always ran discovery process never waiting long, perhaps 15 minutes, probably less. Perhaps if I just waited a few hours or a day it would have done it anyway? Anyway, regarding @UD2)17rrh it certainly can't hurt to trigger Alexa into a discovery.

That is odd. The UD skill on Alexa is the only way to have ISY and Alexa sync at all as far as I know. Unless there is some other Alexa skill you are talking about, i am only aware of the single UD skill. When I search Alexa for Universal Devices only one shows up. And after I expose a scene or device or variable or whatever on the portal, I always have to tell Alexa to discover new devices. I always do it from my phone and then 10 seconds or so later whatever I "exposed" shows up in the list of new things discovered by Alexa and it asks me what I want to do with those things. Those things are not on my Alexa until I do this discovery. Maybe I am just not waiting long enough. I go to the 3 line setup menu icon at the bottom, then the "+" at the top right, then "device", then scroll down to the bottom and hit "other", then I select "can't match logo", then a few seconds later it tells me it discovered whatever I added.

After you add a device or scene on portal you need tell Alexa to discover new devices. It is the same as if you physically added a new device, the device is there, but Alexa still needs to recognize it's existence. The portal "exposes" the device to Alexa, but Alexa still has to be made aware of it by discovery.

I set it to run at startup and changed "is red" to "is not green". I have since reboot eisy twice and both times it connected, so I believe that solved the issue.

I put an Insteon filterlinc in my IT room and then I plugged my UPS into the filtered side of it and then everything in my IT closet is powered off of the UPS, except the PLM. I plugged the PLM into the passthrough plug on the filterlinc. This setup has worked perfectly for like a decade.

The above program isn't working for me. I just updated packages and I had the above program set to run at startup. It didn't run true because the server status was unpopulated, not red. I can probably fix the not running at startup by switching to "is not green" instead of "is red". Unfortunately I didn't remember to wait a whole minute for the re-discover to see if that worked. I ended up restarting the node manually.

Here is a forum describing it as well as an example of mine. I have only done this from routines.

If you activate the scene from the admin console, does it behave the same as with Alexa? Likely the answer is yes. Which means your scene links are corrupt. Try restoring all the devices in the scene. If that doesn't work, trying removing the device that isn't responding from the scene and then adding it back in. If that doesn't work, start deleting devices, factory resetting them, adding them back to ISY, then creating the scenes again.

There is only Google and Alexa that natively integrate with isy. For that matter, I am not aware of any cross platform voice system besides those two regardless. I use Alexa, and while I agree that it is a bit convoluted, it consistently works once you know what you are doing. I find that using Alexa routines is really the way to go. I prefer to expose my ISY devices to Alexa with the "spoken" purposefully not the logical name. I prefer to use routines to trigger things which opens up your phrase structure, not just "turn on x". You can also specify that only certain Alexa's respond to certain commands.