larryllix

Since you never disclosed what "device A" is/was it is hard to know how it could work.

Actually we would need both so we can poke holes in it and help fix it. Sent using Tapatalk

You are looking at two different light switches. One is a program and the other is a scene profile. They are not related except they are controlling the same device. A scene is a preset inside the device. When ISY or any other Insteon device calls out that scene on command the device just does it Insteon devices can hold about 250 scenes each. Sent using Tapatalk

If the device is Insteon then querying it is unnecessary unless you have bad comms and events are missed. On power up ISYwill query all devices to resynch again. Sent using Tapatalk

Not quite. Read the program more carefully. The posted program has an additional trigger that was mentioned @kclenden addresses this in his final paragraph. @lilyoyo1 did not discuss the program. @lhranchBTW: You have to select the attention getting @ technique from the pulldown search resultant or it doesn't function just typing the name. Look for the reverse video difference.

I believe that condition is only known from the last query ISY did on that device (3:00 AM?) , or from the last ACK response ISY got from sending a commend to the device. A cyclic query may need to be set up, if the device or NS does not send a heartbeat.

Copy and paste your program here and people can take a look at it. ISY time triggers can be complex as they can act as filters to screen blocks of time and also as trigger themselves. Eg: If any trigger AND From 8:00 PM To 4:00 AM (next day) Then runs at 8:00 PM each day and also any trigger between 8:00 PM and 4:00 AM Else runs at 4:00 AM each day and also any trigger between 4:00 AM and 8:00PM each day

Yeah, The twenty minutes likely knocks this program out of the troubleshooting. OP should use the search function in the admin console to find any other reference to these devices.

Perhaps he has defective Zwave KeyPadLincs then.

If your scenes contain button LED controls and your program duplicates what your Insteon Scenes do, you may have caused yourself an ALL ON phenomenon. All the devices inside the KPL are on the same address and this type of signal bombardment, is suspected of causing enough signal collision to cause a bad Insteon code, that other Insteon devices can amplify as an ALL ON or a Scene control command. Take the duplicate actions out of your program, or remove the scenes from the devices and just rely on scenes for the on. If you need the response speed, I would isolate the KPL LEDs into separate scenes, allow the lights scene to work directly, and with a 1-2 delay make the program operate the LEDs only. Actually with any human keypress a 1-2 second delay for feedback, or any lights is not that noticeable. Bedtime Prg - [ID 000D][Parent 0001] If 'BedLR1' is switched On Or 'BedLR2' is switched On Then Wait 2 seconds Set 'BedLED' On Run Program 'Lock Doors' (Then Path) Set 'Front Porch Light Dev' Off ... (removed) Wait 2 minutes Set 'Front Hall Light Dev' Off ... (removed) Wait 10 minutes Set 'BedLED' Off Else - No Actions - (To add one, press 'Action')

We use "Alexa...what time is it?" to establish it has disconnected from WiFi. I have jumped up to a mesh network WiFi router and I think with all the automatic amplitude adjusting they do it makes Alexa boxes switch routers occasionally and gives a lot of dead times, we aren't supposed to notice.

@bmercier A further update: Something at amazon definitely was changed as any of my devices with multiple vocals containing the same words get asked about to reaffirm which device I want, now. eg: For alarm system i use two (or more) different vocals. ie: "alarm" and "alarm system". If I ask.... "Alexa... turn on alarm" Alexa will respond with "You said alarm, right?" This was not happening before this week. Either vocal syntax could be used without further query back. I have many vocal using multiple length options like this and the change has caused me lots of maintenance now. Most of these are due to being new,, and the familiar syntax (by humans) was not established until a few usages.

@bmercier I attempted the repeat discover again and no components from ISY Portal were duplicated this time. I conclude that I must have caught amazon in some transitional stage when I did a discover and it duplicated everything I had. IIRC some devices were duplicated 3-4 times while others were not duplicated at all. My attention was attracted when alexa repeatedly advised there were multiple devices with the same names and wouldn't operate certain devices/programs. All good now. Thanks.

I cleared out all devices via the windows browser and did a new discover. That only created one device for each spoken phrase. However, I did not try to repeat discover again as previously it would create another copy of every device, so I left it alone. I may try this tomorrow to test this again, as now I know how to recover from it. I had 3 to 5 copies of almost every pseudo device (spoken phrase) in my alexa app before. Since the amazon app offers no way to delete all devices, I suspect this must have been some amazon failure of their automatic clean-up for redundant devices during discovery.

There is no "Delete all devices" in the android app any more. It was eliminated a few years ago. However I found one in the amazon browser webpage still. That doesn't solve the duplication of every device each "Discover"

Wondering why alexa began complaining of duplicate names on items yesterday I tried to change some offending names that have been working for years now. In particular I had two items named "T V" and "T V lights" that alexa started complaining of having two names the same. Entering the app on my cell phone I found multiple devices using the name "T V". I did another discover and alexa reported no new devices. Another instance of "T V" appeared in the app. Now I had four instances of the same name as well as several instances of every device now. I manually deleted all but one "T V" and did another discover. Another instance of "T V" device appeared. Back to the drawing board I disabled my ISY Portal account from the alexa account app, and then installed it again. More of the same with duplicates. Then I disabled the ISY account again, did a discover which found all the devices exactly the same again but none of them work because the device or account was not ready. Exiting and killing the app from running in the background each time I repeated the process with discovery and app kill between every stage. Alexa just remembers every device and will not forget anything. So it looks like between the ISY Portal skill, and Amazon accounts, something is a real mess. Somebody has eliminated the "delete devices" feature a long time back, and yet any automatic cleanup of unrecognised, or defunct devices, is not functioning anymore. Each time a Alexa discovery is done, every device is duplicated one more time. Alexa never forgets (They think they are gaggle home)

If you can write python3 code about 20 lines of code could receive a URL sequence and reboot the RPi from a NR command. I do it in python3 by running a system command "sudo reboot" in python3 code.

Green means running Then. Red means running Else White means..hasn't run anything since boot up. Hollow/partial colour means last ran Then/Else

Yeah. I don't trust anything that comes off of the MS II units except for motion sensing. They appear to do this quite reliably but the rest is just nonsense, so far. When queried they can go into oscillation and cripple your whole ISY system. UDI wanted to dump this unit for ISY development, until Insteon produces an API spec or some documentation.. What we have so far is only a hack from UDI efforts.

Yellow means something wrong Solid Green means running Then now Hollow green means ran Then last Solid Red means running Else now Hollow Red means ran Else last Green arrow means updating is waiting 1011 means binary is writing to device or failed last attempt depending on colour.

Been a very long term problem with java. It is getting more frequent lately.

What are you using to lock down your ISY's IP address?

ISY Launcher is a strictly cloud service but the java app admin.jnlp should work without it. Maybe make sure your ISY had permission under the java security tab.

I am surprised the water would chase the deer away but maybe the change in motion does it? Last time I drove through the western states we noticed...man you guys have deer problems!

The Polisy beeping was addressed in a thread a few months ago but sorry, I can't remember what it means. IIRC it means it cannot connect to ISY, or other Ethernet problem. I think I found it but it doesn't offer a lot of help except to open a ticket with UDI. They will fix you up. Here, I will also ping @Michel Kohanimabout his. He is the chief cook and bottle washer. Have you opened up the polisy to see if your Ethernet card inside hasn't fallen out?