MrBill

Again I don't have that plugin, but open the Home app and click the + in the top right, then select Add Accessory, then click the more options link and I think they will be found.

It's weird that the insteon device is effecting z-wave devices. If any have red X's in the admin console, right click the device and select query.

@jkraus I'm not sure that PG3 and IoP are communicating. I think you could have a setting wrong, but I don't have PG3 pointing to IoP yet, so i'm not sure what to suggest to fix it. It sounds like Kasa is working but PG3 isn't talking to the IoP process.

Yes you can. Use multiple scenes. I'm using 4 not 3 but it can actually be done in 3. Alexa will keep the keypad button in sync with this method.

do you have other working node servers or is this the first?

You can do this with 3 scene's and No programs. 3 scenes" High Med Low Set all the 3 buttons for High, Med, Low to Non-Toggle ON Set the off button to Non_toggle OFF make each button a controller for the respective scene. Make the off button a second controller for any of the scenes. Make sure to add the other buttons as a responder (if it's not the controller) Make the appropriate Fan node a responder for scenes. You can use Multiple keypads for the fan or fan group. You can use Multiple IOlincs (fan groups). No programs needed. Have alexa turn on the appropriate scene. Pick any scene to use for off.

do you have a Kasa controller in your device tree? you may need to right click it and group the devices. otherwise restart the Node server, make sure there's no errors in the Node server log then restart the admin console.

No internet Enabled is out of date... it actually enables UPnP... which shouldn't be enabled. It fails because your router rejects UPnP for security reasons. I can't tell you anything about the homebridge plugin but this should work "[isy-nodejs] Connecting to: ws://192.168.1.103/rest/subscribe" assuming that is the correct IP address for your ISY, and the two devices are on the same subnet and can talk to each other.

The version to use is right here: https://java.com/en/ No account required.

@FloridaGary You can do it two ways, @Geddy shows you one. You don't want to use any of the instructions you quoted in your initial post above, thats for setting up the FROM address. The Groups window below that one is the TO: Addresses and you can in fact configure a "group" to send the same email to multiple addresses. here's an example: test 1 send the email to 2 text message addresses, Bill sends a text message and a copy to my email address. You achieve this by adding multiple T0: addresses in the Add/Edit/Remove receipts popup for each row in the groups window. Again, don't change anything in the SMTP section of that page, that's the FROM portion of the email configuration. --- That said.... discover using Pushover via network resources (or the Notification node server) instead. It's definitely faster and more reliable for notifications.

@shergenr cache.insteon.com is still available. Just google insteon 2443-222 manual (for example) and you'll get PDF results https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiQ15687r73AhXoAZ0JHRSIAQUQFnoECA8QAQ&url=http%3A%2F%2Fcache.insteon.com%2Fdocumentation%2F2443-x22-en.pdf&usg=AOvVaw0EZD09LxxXXojPC3kI-Cie

I only purchase Phillips Warm Glow now. I have some older bulbs in use still tho.

correct. The 4 scene method (shown in the wiki as the method for V4 firmware works without variables. To have alexa be able to control to specific speeds tho, you need the 4 scene method. Not sure how you are using variables in conjunction with this.

If you're using an ISY don't set options at the switch, because the ISY doesn't know about the change made at the switch. Instead change the setting via the ISY. If you have on-level set to 60% in the admin console using the dialog shown in the screenshot above, and you have written the change to the device using the button to the left of the dialog box then turning the switch on manually at the switch, or using the on button in the ISY on the device node should turn the device on to 60%.

You cant pick your own colors, only choose between a few theme's under File > Theme's the pink/purple color is complained about a lot, but sadly it's still used. On thing that Improves it's readability greatly is to increase the font size, but don't use font size 14... it doesn't format drop-downs in Programs correctly (the others work tho).

Java 8 is the only supported java. However, it updates every month(ish) like everything else. Current is Java 8, Update 331... sometime or another that will advance beyond update 331...

Do the scenes always work if controlled manually from the ISY? for testing purposes add Wait 15 seconds between each of the Set statements. Is the PLM plugged in where it always has been? Have you plugged anything new recently? Like a charger for a new gadget? or even changed an LED bulb.... What I'm getting at is the sounds like a garden variety Insteon noise or signal sucker issue. The ISY is doing what it's supposed to but the message is not received. ALso Open Event Viewer Level 3 and watch to see if the ISY is generting Insteon traffic.

@kzboray the linked wiki has actually been updated to use a single scene with controllers set differently. I use 4 different scenes for the fan and then have Alexa setup to turn on or off the correct scene. It's expensive to eat 4 scenes per fan or fan group, and if all my fans had fanlincs i would feel that pain but reality is I don't have fanlincs everywhere, nor do I need them.

originally, when firmware was updated the user would go to http://ip.of.the.isy/admin.jnlp and download the new version of the admin console directly from the ISY. Eventually browsers started liking that method less, throwing security warnings about using unsafe java... etc etc. Users also seems to have great difficulty clearing the cache and deleting old copies of admin.jnlp when they obtained a new one. So in 2018 The ISY Launcher was born to solve both of those issues. Launcher (start.jnlp) is downloaded from https://isy.universal-devices.com/start.jnlp and since it's an https site (rather than http from the ISY itself) browsers are a little bit happier about downloading it. The first time you run start.jnlp it will install an icon named ISY Launcher on the desktop. That's what you should use to run the Launcher going forward. Launcher when launched immediately runs ISY Finder, and as such the two are often confused Launcher is not Finder and Finder is not Launcher. Depending on the type of record in Finder you'll get various choices of things that can be started using finder, an example this one for the ISY994, allows us to start The admin console either from LAN or from Cloud. In this case cloud is faster because it's fetching the file from UD's cloud server which runs from AWS... the LAN alternative is slower because the ISY has to serve it up encrypted for transport... a job that the ISY994 is very slow at preforming. The above described all works great on Windows, and most MAC users don't complain, but some do... and I've never figured out why. for those users it's best to simply use admin.jnlp that they download from the ISY. When using the ISY Launcher icon, it's really not, in theory, necessary to go thru the hoops of deleting the java cache and re-installing etc as often as most people seem to. Personally I vary rarely clear my java cache and re-install. My local network can have up to 4 ISY's running on it (only 1 is actually production but I have a second 994, and 2 Polisy's) and at any given time there might be 4 different firmware version loaded, needing 4 different admin console versions... Launcher manages all that. The only time I really clear my java cache is when a java update installs. So the best advice is download and run start.jnlp which installs ISY Launcher on the desktop. Use that going forward. When you're forced to re-install due to java updates, download a fresh copy of start.jnlp instead of using the one you might have laying around from last time because UD does at times revise that file. .... and if that procedure doesn't work because you're using a Mac, then use the http://IP.of.the.ISY/admin.jnlp and store the file on the desktop. Just remember that when firmware is upgraded you must manually clear the java cache, delete the current admin.jnlp and download the new one.

Scenes: https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

Someone else had this problem too. Open a ticket support@universal-devices.com (they do answer on weekends but more slowly than weekdays)

THIS IS NOT COVERED WELL ANYWHERE, NOR IS IT INTUITIVE... after you set the dropdown, press the button to the LEFT of the dropdown. IN this case "On Level" I'm not sure why its so hard to make this either more intuitive, or add a line of on-screen instruction.

What your reading on the label IS a "D" not an "O" If you look really closely the left corners are square, the right corners are rounded: so you have the device correctly added to the ISY at this point. Edit to add: It will never be the letter O the characters are hexadecimel so they stop at F in the alphabet

You're missing a step or 2.... after 5 and before 6 you need to load the firmware. the bootloader firmware that comes up in in step 5 isn't compete. You should install the same firmware the backup was made with, which will reboot again. THEN restore the backup.

What you're describing sounds like mismatched firmware and admin console... so I'm suprised they match. the issue @Techman refers to is about the use of "adjust scene" use in a program. that particular program statement won't update automatically and requires manual intervention. 4.9 is in this thread, if you want to try to go back. I'm curious tho what's going on with your programs.