apostolakisl

@Guy Lavoie As mentioned. Uncheck daily and then you pick specific dates. But the issue with that is you would need to go through and set every Christmas (or whatever) for every year going forward. Using the plugin for dates let you use wildcards. In other words, you can set it for every December 25 and the year can be wildcard. Or you can do every other day, or every just about anything you can think of, perhaps requiring some thinking to convert it to what you want, but really nothing can't be done. Many years ago, prior to plugins existing, I wrote a whole series of programs that does the same thing. In fact, I continue to use those programs because they work and why would I go through and re-write a bunch of programs that aren't broken that use the series of date programs. But if I were starting over, I would just use the plugin.

What is it you are trying to do? One button seems to cover it. Not sure what you mean by "lock down programs". No programs need to be locked down or I guess disabled if that is what you mean.

I still say the easiest way to handle this is a "run then" of the program when using the admin console or mobile linc to set the variable to 0 . Again, I assume that mobile linc lets you execute programs from a favorites folder. If you want to simultaneously shut the lights off when setting the value to 0, then add "off" commands to your then clause for the lights. If the light is already off it won't matter, it will just stay off as if nothing happened. I don't really know how you are handling this since obviously at least one of the lights will shut off if you do a fast off from one of the switches, seems like if you want one of them off you might want all of them off? I don't know what you are going for here. In UD mobile you can create a favorite and set the favorite icon to execute a "run then" upon tapping it. And it lets you name it separately from the program as well. I suspect mobile linc lets you do something similar. And if you are in the admin console, you might also just directly set the value to 0.

The language "switched" means you physically pushed the button, or at least that is the case with a switchlinc or KPL. Other devices it means that the command initiated at THAT device. If the device responded to a command issued elsewhere, it won't trigger the program. You would need to add to your program triggers that you can initiate from your phone. The easiest way I would say is to create a favorite in UD mobile that is the actual program. Add to your program to shut the devices off as well. If you actually click the switch itself and do the "fast off", it won't matter that the program shuts it off as well, it will already be off, no harm done. EDIT: I see you are using mobile linc and not UD mobile. I assume Mobile linc also lets you create favorites that might include programs where you can execute a "run then" by hitting the favorite button.

You can try using ssh to log into the eisy and reboot it from there. I use putty. You enter the ip address of eisy and it should give you a login screen. The login should be admin/admin. If eisy has been told to update and hours have gone by, it is not going to succeed. Eisy can take many minutes to update, but not hours. This command will reboot. sudo shutdown -r now

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.

@DennisC Thanks for the info. I can confirm that it is fixed. i did the update and all is well again on that front. I did not have any of the other issues you refer to. My IOX launcher still works like normal. EDIT: I don't seem to be able to login into PG3x. I tried admin/my not portal password, admin/admin, and email/portal password. I also can't login into eisy-ui. Won't accept the portal username/password. I can login into portal using portal user/pass and I can login into admin console using both the local port 8080 user/password and the portal user/password @Javi

I have had this same problem after adding a device. It did add the device, and the device worked properly, but the popup just keeps happening every time I opened a new admin console session. After rebooting eisy it stopped. I feel like it is a firmware bug. I have added multiple devices and it didn't happen every time. I never saw this problem in the 15 plus years I have had an ISY until just a few months ago. Regarding the OP's issue. I think the scene is corrupted. I would delete the device completely from ISY, factory reset it, add the device back into ISY, and then put it back into the various scenes. Hopefully it isn't a super complicated set of scenes/programs.

So the problem is with ISY, not Alexa. If the light doesn't turn on when you turn the scene on from the ISY admin console it isn't going to turn on when Alexa triggers it either. I have also had this (edit, by this I mean it keeps doing the pop up) happen after adding a device and ended up having to power cycle ISY. A bug in one of the more recent firmwares I guess. I have now seen at least a couple other people report this. I would start with rebooting your ISY (eisy/polisy/whatever model). Then see if the scene works. My bet, however, is it will not. Perhaps the "replace with" command did not function correctly. You can always try a "restore device", but I usually just completely delete the device, add it back, and configure it back into all the scenes.

If Alexa is controlling the scene, then Alexa won't know if you swapped out a device in the scene. Alexa doesn't see the individual devices in a scene. Alexa triggers ISY to issue a "scene on" and from there it is all Insteon configuration as to what responds to the scene. What happens if you trigger the scene from the ISY admin console? If that works, then I can't understand how Alexa isn't unless Alexa isn't triggering a scene but rather a device. When you open the ISY portal and go to Amazon echo: Is the "ISY category" for whatever it is listed as a "scene" or "device"?

I'm going to assume that you have a scene and that in the portal you set the scene to be controlled by Alexa (not individual devices). Since Alexa still is controlling the scene, it sounds to me like the new switch isn't in the scene. If you did a "replace with", then it should be in the same scenes as before. If you deleted the old device and added the new switch, then perhaps you never put it into the scene.