MrBill

@CJVann Your PLM also needs a factory reset.

300 series z-wave boards need 5.0.16C. 500 series (which is the only thing that would be shipping in a new ISY994) is fine with the latest firmware. If 'new' quoted means used, the fastest way to check which z-wave board is installed is to look at the back of the 994, adjacent to port A, if there is a Blue LED that's a 300 series z-wave board. (You might need your phones flashlight shining on it to realize it's a Blue LED). For the rest of your issues... I'd just open a ticket. UDI's support dept (aka Michel) will have you up and running in a flash.... support@universal-devices.com

seems to be back now...

I noticed that a little while ago to. @Michel Kohanim are you aware?

My Polisy's in an inconvenient place for beeps and lights, and even if I was there I can't physically hear the beeps anyway. I use http://IP.ADDR.of.Polisy:8080/WEB/udajax.htm to determine when the upgrade is complete... if that page loads and requests credentials then IoP is back and I can open the admin console. I wish we could just get a simple status page on some arcane port that could be opened in a web browser, nothing fancy just text.

Sounds like you were using Polyglot cloud to get OpenWeatherMap data. As @Geddy mentioned it was shut down 6 months ago due to security vulnerabilities. Also Polisy's also became unavailable earlier this summer due to the global chip shortage. UDI is working on a replacement that's due to be available in the coming weeks. There were at one time some heavy hardware discounts for those that were using Polyglot cloud, you'll have to check with sales@universal-devices.com to find out what's available now.

admin console or web interface (i.e. /WEB/udajax.htm)? Not Found sounds like a DNS error. have you made any changes to your network? or do you have blockers/filters for ads?

I have the same issue. I wish we had a better workflow for upgrades.

I doubt that was your only solution. OP also seems to think that the interface changed dramatically... which it hasn't... we need to explore this part: Even with the jump from v4 to v5.. the interface didn't really change alot...

@koko Please give us your details: model number, and firmware and UI versions. Approx how old is the equipment? The design of the admin console hasn't changed much..... We need to get the bottom of the issues you are having and better understand what changes to the interface you are speaking of.

my money's on the first scene actually, because it has All in the spoken.

Include both the laundry room switch and the KPL button in a scene and make them both controllers. Both links in the scene should be Red. That creates the same links that you made manually in the switches, but it also creates that link in the PLM-- by doing that the ISY is also a controller for the scene, and the ISY can follow along when the scene is turned on or off from either the switch or the keypad button.

I don't have an opinion on this anymore. If I tell Alexa to turn all lights off she doesn't do anything although she does say OK. mostly mine are Variables or programs she controlling as a scene. I did make sure to turn on one of each type before telling her to turn All lights off.

Manual linking shouldn't happen. You use the ISY to create all links, whether KPL or not. That way the link is included in the PLMs link table. If the ISY doesn't create the link it doesn't follow what's happening. Making scene's IS linking, its the same thing for basic scenes, but you can make more complex scene's as well using the ISY. Another way of saying is that all switching programming and linking should be done via the ISY, don't manually do config modifications or links at the switch.

You can't do it that way. Creating Scene's in the ISY is how you create links between devices. If you manually link devices they don't include the PLM in the linkages. The ISY MUST CREATE ALL DEVICE LINKS.

@Schlyguy Do you have an Insteon hub also configured with these devices?

That's interesting if you didn't configure something in the portal. I can't duplicate it, but I only have a limited number of devices integrated thru the portal, and most of those set a variable instead. There doesn't seem to be a documented "All lights" command in ISY Portal Amazon Echo Integration V3.

In another thread you wanted the light behind that button to stay off, so I showed you how to configure it as Non-toggle off. I can't tell by your current question for sure, but it doesn't seem like you're building off that. A "scene" can be considered "preset" when the "on" is sent everything in that scene is set according to the instructions in the scene. When an "off" is sent to the scene however everything in the scene is set to off. Here's an example of a scene that turns some things on and somethings off. Note when you include other scene's within a scene, what you actually do is include ALL the members of that other scene, including it's button and set everything as it should be have in THIS scene. For example all the entries that start with {hide} are keypad buttons on the same keypad. (all 4 of these scene's actually have all the same members... The 4 scenes are Day, Evening, Late night, and bright. The ISY normally cycles those scene's (except Bright) but they can be manually overridden using buttons on the keypad.)

Alexa is turning off every device she knows about individually, not as part of a scene. You say turn "all" off and she run thru the device list and turns each node off. Alexa believes that she's the controller. She's not used to telling a smarter controller what to do, so she breaks it down into the smallest steps and converts the word "all" to turn off the kitchen light, turn off the hall light, turn off the bedroom light, turn off the lamp.... etc

Tell us more about the scene and the testing procedure. Obviously the two outdoor switches are part of the scene, are there any other members of the scene? Is the ISY the only controller? When you "tested' did you mean press scene on/off from the admin console? When you went to use the the scene, how were you controlling it. The questions are so we can begin to figure out whether it's a scene setup error (multiple controllers require setting up each controller) or a classic case of line noise or signal problems? do you know what model number the outdoor switches are? Looking to figure out if it's a dual band or single band device.

I've been trying to get that point across for years.

I think you're crossing 994 instructions and trying to use it on a Polisy... not the same thing. For your issue I would recommend that that you open a ticket.. email support@universal-devices.com (they do answer on weekends although not as fast on Saturday as any other day.) UDI has amazing support!

that's subjective.... 🤣 The scene method is faster however.

The reason I made the suggestion to switch to control instead of status is because there is a wait in the program. if the program triggers via "control" it will for sure complete the THEN block, if it trips by "status" it can end prematurely if the status changes back before the THEN block is complete due to a wait.

If "control" is available so that this can say "Bedroom / Smoke Bridge-Smoke' is switched On" will probably solve it. Test that and tell me if it works, I'd try it but I don't have a smoke bridge. Also when you test, have the event viewer open on level 3.