larryllix

@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?

I think you need to open a ticket with UDI. They know things about the inside of your ISY that we don't. I would hate to see you rebuild all this only to find out there is another problem with your ISY OS. Maybe your old PLM is overloaded with too many links? Of course that would be right after factory resetting my ISY, reloading the OS image and restoring my programs.

Think you might have blown your UDI assist when you saved all those messed up programs. Now you need to edit every program looking for commented out lines that ISY could not convert correctly. Some will be correct already and some may have comment lines substituted. When they were not absolutely sure, they left it for the user to examine and correct as needed. They may still have yellow icons in the admin console program tree yet.

If I would have gone with GH rooms idea it may have worked better but it would have required renaming all my device vocals, once I figure out what was likely to be happening. Eleven years now and we are thinking of taking off the switchplate labels for lights but I don;t know how to label the vocal commands now. Alexa....give me a list of the closest light control commands

That was my problem. I started out with only devices in my Gathering Room and didn't use any prefixes. I have most of my devices with no room prefix like blue lights, red lights, TV, etc,. When I started adding things like bedroom TV, blue bedroom lights etc... Google got confused a lot, and with it's additional attempt at grouping devices, it didn't work well at all. With Alexa, these combinations of prefixes and no prefixes, are not a problem, and I still have use them all except for All lights, which I changed for GH when I used it. When I would use All lights before bed, GH would shut my whole house off, including the heat, making it's AI attempt assumptions. ISY Portal doesn't send your ISY names for devices to GH/Alexa.

I drink and eat different things each day. I might have to change the vocals each day then.

You are missing the fact that the ISY Portal is a conversion table from ISY elements (programs,scenes, variables, devices, etc..) to vocal device names. It doesn't matter what your elements in ISY are named, you must supply independent name, or up to five different vocal names for each element you want to control. eg. My Ceiling pot lights over my kitchen eating bar are named. Kitchen Lights, Kitchen bar lights, bar lights, counter lights, and kitchen counter lights. You have to remember one of them. With Google I found you have to watch the multiple usage of any device name. IOW: If you have red bedroom lights, and bedroom lights it will often confuse the two names. If you have 8 different colours for a light strip eg. Red Bedroom lights, Blue Bedroom Lights, Orange Bedroom lights, etc... when you say Hey Google...turn off the bedroom lights. It would respond with OK...turning off eight devices, and send every one of the codes out flooding the comm channels. After Google constantly changing their security systems and having to restart or create a new account, about three times now, I stopped using my four GH devices. Now I found out when my router would get a power blink, and they couldn't connect right away (competing with about 70 other devices), my GH devices would all start sending out their own SSID WiFi beacons on the last known WiFi channel and flooding my router's WiFi system, causing comm problems on my LAN. Now my sit in my junk box doing nothing and I rely on my 10 Alexa devices only.

But with Zwave sensors you don't have the problem of the Insteon direct link scene turning the lights off again. All control logic goes through the ISY programs right?

First...you can right click on your programs, copy to clipboard, paste into forum post. I would try something like this. If elk is armed Then Wait 30 seconds Enable program2 <--------------- or set $variable = 1, also init to 1 Else Wait 5 seconds Disable program 2 <------------- set $variable = 0, also init to 0 Program2 If MS is switched On Then do whatever Else ---- Of course, you could use a state variable also and make a folder conditional upon that variable being 1 and not 0 Put all your related programs into that folder. Be aware that turning the folder off will stop your programs dead and anything that requires finishing will need to be handled separately. OR... Use an Integer variable (not State) and Include that variable in all your program conditions If MS is switched On AND $Variable is 1 Then MS actions Else ------

Ohhh..not sure what MSes you are using. If you cannot turn off the Off signal from the MSes, it will not work very well. I have some Insteon MS IIs that have this problem and they are a PITA having to flounder in the middle of the night in the dark. I have found that a cure should be to set the On duration to a long time inside the MS but these POSs will not send another On signal until the On duration x2. (The internal circuitry needs to be off as long as it was on).

Have a look at this I believe the top two programs do what you want. Yours look very similar.

Add ISY to the java permissions table under the "security" tab.

Oh Yeah. You may need to go to the java console and enable access to your ISY in the permissions table....about third tab IIRC. ooops fourth Tab in the picture above. "Security"