MrBill

http 8080 is unencrypted network traffic and is great when you're using the connection on your local wifi network. https 8443 is encrypted network traffic is great for when you're accessing remotely. This method is slightly slower due encryption/decryption. It's more noticeable when using a 994 than a polisy. to use it remotely, it would also require a port forwarding rule on your router....that said, if you're accessing remotely the most secure method is via the portal.

it sounds like you need a rule for traffic in the opposite direction as well.

Help > Purchase Modules. It opens a browser window to the UDI website, but things can be un-intuitive once there. First login via the portal. Next find in the center left side and click "my products", assuming you have a portal account for your ISY you should find it listed on the next page. Click the Modules button on the right end of that line. The next page will show the X10 module which is $9. If your ISY isn't listed in the finder window one of several things could be the problem. The most common are, 1) the ISY obtained an IP address on a different logical network 2) the laptop finder is on has firewall rules blocking finder from finding the ISY 3) You have an advanced router with VLANs that isn't configured correctly. 4) your router doesn't support the method the ISY uses to autofind the ISY. and other less common.... If there is a network path, the ISY can manually be added to the finder window using the add button, the URL for a 994 is http://192.168.XXX.YYY/desc (of course the IP address must be fixed to equal that of the ISY.

while this is also true, what i really had in mind when i said... was FOLDER CONDITIONS. If the folder the program is in, or any folder above it has a negative condition "Run Then" and "Run Else" won't run the programs manually. Since "Run then" worked it doesn't appear to be a folder condition. This now sounds like an intermittent Noise issue.... How old are the devices? are they dual band or single band? There's a number of troubleshooting articles: https://wiki.universal-devices.com/index.php?title=Main_Page#INSTEON_2 the short story tho, is the ISY is doing what the ISY is supposed to be doing, but the signals aren't getting though to remote devices. I had a 2466 switch once get taken out by lightning. It produced constant noise that prevented anything Insteon from working until i figured it out and disconnected the switch. We also once had a countertop deep fryer in the kitchen, if it was plugged in, turned off or turned on, thermostat satisfied Insteon wouldn't work. We lived with that because it was only used for a short time once a week. Other's have reported various tool chargers, fluorescent lights, even some cheap LED bulbs that produce electrical noise. My troubleshooting method is to first suspect anything new. (this wouldn't apply in your case because you've had the problem for a long time. Next, I turn off half the breakers in the panel (ignoring the single circuit that has the ISY, network etc) if the problem goes away, I turn half of the off breakers back on and retest... if it didn't go away I turn that half back on and the other half off. Then retest. Gradually turning batches of breakers back on until i get it down to just one that causes the problem. Once i know that I go explore what's on that circuit... once found you either eliminate the problem or install a noise filter. Some other things to keep in mind about intermittent "noise" problems. think about "what's on" at the time things didn't work. For example, I remember someone that tracked it down to when a bathroom exhaust fan was on. If the front light (for example) always turn on, but never turn off... they themselves might be the problem. They turn on because there's no electrical noise present, but the low voltage transformer running the lights powers up, creating noise, and now the switch can't hear anymore. I've talked mostly about "Noise creators" but there's also "signal suckers".. devices that soak up insteon signals preventing them from reaching a device.

If you have these two buttons on the admin console ribbon then you have Pro: I don't specifically know if it's automatically included with IoP.

%1 should be getting replaced, it's a placeholder for a replacement. I'm not certain if it should be pointing to the full path of start.jnlp or more likely the full path to something else, such as a temporary file in the java cache. We need someone to come along that has Windows 11, to ensure that ISY Launcher works with Windows 11 (or perhaps @Michel Kohanim) In the meantime, you can use the old method to get an admin console running: https://192.168.XX.YY/admin.jnlp Fix the IP address to be the IP of your ISY. Ignore or bypass the browser security warning, download the file, move it to your desktop. (that file will work until the next time you do a firmware upgrade)

Are you double clicking start.jnlp or trying to run it some other way? The "%1" means that somehow the web launcher is not getting the path to start.jnlp the way it expects to. Discalaimer: I haven't yet installed windows 11, so I'm not sure if there's any window's 11 issues with ISY Launcher.

Most users will want the production store. There is a Non-production (or "test") store for developers to use before nodeservers are released.... "local store" and "install local nodeserver" would also be used primarily by developers. "Install local nodeserver" is about installing a nodeserver from local files. In all cases as a user, you will want to use the "production store" The ISY portal node is used with nodeservers. This cloud based node does still work, it's not part of PGC. ----------- to @Michel Kohanim and @bpwwer: Perhaps the interface should default to a "user mode" which steamlines the interface and hides all the features present for developers, then in the polyglot options a checkbox to select "developer mode" which then exposes.

You've correctly Surprised Replace Modem, you're also correct about not using Remove Modem and why to not. Caveat: it's a great solution for small systems. For those with large Insteon systems something somewhere will probably get a bad link along the way, to fix those click the device in the tree, right click it and select Restore Device-- the ISY will re-write that device only. For those with wireless devices, if you don't already have the "pro" version upgrade to pro before you start. (Pro is an instant upgrade, just buy the module then restart the admin console.) Anyone with wireless devices should use the toolbar button (only available with "pro") to turn off wireless device writes before using "Replace Modem", after Replace Modem is complete, put each wireless device into set up mode and then right click the device and pick "restore device", do this procedure one wireless device at a time-- leave wireless writes off until complete, Restore Device will work one by one.

@CPrince just re-read my reply above. I left something out... be sure when using the admin.jnlp method to also delete any copies of admin.jnlp anytime you're clearing the java cache. I think extra (outdated) copies are sometimes confused for the current version.

@sumguy I have a method that results in a few false notifications, but for the most part works, I started using this after the great iOS 15 breakage by apple. Either garage door closing starts a 1 minute wait. if someone opens the door going into the house the wait is canceled, if the wait finishes , it checks to see if away mode is set if it is, it exists silently, if away mode is not set I get a notification. For us this works better than trying to remember as we leave to make sure away made came on. Program garage_closed If garage 1 is switched off or garage 2 is switched off Then Wait 60 seconds run program check_away (if) Else (nothing) Program check_away (disabled) (note: disabled programs still run when called by another program.) If $sAway <= 0 then Send notification..... else (nothing) Program Stop_garage_timer If Garage2HouseDoor is switched to On then Stop Program garage_closed else (none) It does send false notifications when only one of us leaves, but for us that works out better than remembering to verify if the geofence worked. (there's actually a couple more inventive ways to cancel the wait, so a lot of times we use one of those too)

That provided the actual out loud laugh! I'm not certain why you're getting the certificate error that you're getting. It doesn't make sense, assuming that you are checking the box to "clear installed apps and applets" when the java cache is cleared. The procedure that you're following to download admin.jnlp seems to me to be correct. No it's not. the file named admin.jnlp is the specific admin console that works with the firmware that it was downloaded from. (which you appear to be following the correct rules to use). Many Mac users find that method still works best for them. The majority of windows users have better luck using the ISY Launcher which is newer method that has now been around for about 3.5 years. I linked a thread about it below. The major purpose behind the ISY Launcher is two-fold 1) eliminate browsers blocking java and associated browser security warnings. 2) ensure that the proper admin console version is launched each time (checking the firmware version and launching the admin version). To use, just clear the java cache including installed applications and applets, and delete any files you may have named start.jnlp or admin.jnlp . Then download and run https://isy.universal-devices.com/start.jnlp (note the name is start.jnlp, instead of admin.jnlp) The first time start.jnlp is run it will install an icon on your desktop named "ISY Launcher" which when clicked will run ISY finder and ultimately the correct admin console to match the ISY's firmware. In most cases once the ISY Launcher is installed, you'll no longer need to clear the java cache at firmware upgrades because the ISY Laucher is actually getting the correct admin console each time it's launched.

To add to what @Geddy just said... the words "test build" were a bad choice for labeling the last couple of build (following 5.3.0), it really would have been better if they had simply been labeled "update 5.3.4". The specific problem with labeling of releases is that 5.3.0 (which is now 1.5 years old) is that it is the officially z-wave certified release. 5.3.1, 5.3.2. 5.3.3 and 5.3.4 are all minor relases that all only contain fixes for issues found in 5.3.0... Nothing more new. So why are the label test build? "Test" was a bad word choice, as mentioned above "update" might have been better. It's a sticky situation tho because 5.3.0 is the only officially certified version. So what doesn't UDI get these minor releases certified as well? Cost. UDI must make a significant cash payout for The Z-wave Alliance to test and certify a new version. As @Geddy mentioned 5.3.4 has been available for 8 months now... there are no known stability complaints or bugs.

Many users have successful exchanged the daughter board. That is removing the serial daughter board from a failed 2413s and installing it in place of the daughter board in a 2413u. Do you have Java 8, update 321 or later? Specifically Java 8, not java 11 or java 17 or anything other than Java 8? Are you using the ISY Launcher, or a copy of admin.jnlp to launch the admin console? are you using windows or a mac? When you can get the admin console open, if you go to the Help > About menu are the firmware and UI versions matched? With these answered we can probably get to the bottom of your java/admin console issue fairly quickly.

WHen you clear your cache you also need to get rid of any files named start.jnlp or admin.jnlp. Download new ones fresh. and just to make certain when you clear the java cache are you manually checking the box to remove "Installed Applications and Applets" --- the box is not checked by default, but must be checked by you as you clear the cache.

@JAboud Tell me what happans when you click the name of the program, then right click and choose "Run Then" or "Run Else"? Are the Then and Else bodies running when manually executed via that method? There is something very specific that I'm using that test to fish for...

let's see the thermostat program.... Best method to post a program is to click the program name and then right click it and pick copy to clipboard. then paste into a forum post.

to add to what @oberkc said.... It's a maze to find how to buy the optional module, and the screenshots are likely out of date for that too (I didn't look). To purchase the optional $9 module choose help, purchase modules, which will open a browser window... Once you're logged in, click the My Products tab in the LEFT Center of the window Then click "modules" next to the ISY that you want to add it to. (this assumes that your product is already in UDI's database, if it's not you need to add the ISY as well).

To add to that it's imperative to do the link count when there is NO traffic if you want a valid link count. Any traffic while the link count is running will throw the results off. This can be a problem for those of us with wireless devices that generate heartbeats, because a single heartbeat will through the link count off... (and not by 1, depending on the address of the device it can be alot). When i want an accurate link count it usually takes 4-5 tries to confirm I've got a good count. I also only do it when I'm the only one home.. basically run multiple link counts until you get the same answer two or three times. It's much easier in small systems where the link count runs quickly.

this sounds like the typical case of noise. I assume when it was turned on/off you meant at the switch itself? can it be controlled via the admin console? both on and off? Typically when a switch works for "on" and doesn't work for "off" consistently the problem is with the load that that switch itself is controlling. i.e. no noise the switch turns on, but turning on the switch turns on the electronic noise source.. therefor "off" won't work. Sounds like you've been down the noise path before because you know to say you haven't added anything, and have noise filters... however keep in mind something that was not a noise producer in the past may have become one. I had an electronic transformer for an accent light that had been around for many years... one day after a lighting storm it became a noise producer that prevented Insteon from working when it was powered.

It's unclear if your speaking of the status in the admin console or via mobilinc connect. If the admin console (connected on your local network) is not updating the status when you open a close the door. then we need to troubleshoot a set of possibilities that include bad PLM or Noise preventing communication. If on the otherhand the problem is the devices are not updating via mobilinc connect then you need to open a support ticket with mobilinc.

Looks like he was migrating from V2 of the skill to V3... but he's really late to the party as V3 has been around at least 5 years from my memory. Was the new voice entry made after the devices appeared in the app? if so you need to tell her again "Alexa, Discover Devices" to have the new entry discovered. But if the error is the title, then it's something else. In the portal click "my profile" in the top right corner and make certain the correct ISY is selected in the dropdown, and that the UUID entry for preferred is correct.

It's also important to remember that scenes can be programmed differently based on the controller used. In this scene: There are 3 Controllers: The root level (i.e. Christmas-All) and the two RED nodes. The root level determines what happens with the ISY itself (admin console control, app control, program control, Alexa, Google Home, etc) controls the scene. Clicking each of the Red links determines what happens when those nodes are used to control the scene. Repeating for clarity... this scene can have 3 different behaviors based on which controller controlled it.

heartbeats are unknown until the first heartbeat after a restart. Wireless devices will be unknown until they report once. (some people have success with a program that does a query on when heartbeat received, but it still requires waiting for the heartbeat). As for wired switches, you need to have "Query at restart" checked on the Configuration tab for their status to be known. (this screenshot is from V5 firmware, yours may look slightly different. ) If mobilinc connect is not connecting you might want to check with @InsteonNut by opening a ticket with support@mobilinc.com perhaps there is a problem with mobilinc's cloud services.

I also tend to make loops like this occur at odd times, so that there is a less likely chance be data collisions. That is, instead of happening every 30 minutes exactly on the half and and hour, I'll mix it up: DoorOpenLight.Query - [ID 014C][Parent 0034] If From 5:28:28AM To 11:59:59PM (same day) Then Repeat Every 33 minutes and 33 seconds Set 'Garage Entryway+# / Door Open' Query Else - No Actions - (To add one, press 'Action')