MrBill

the only things not in the v5 upgrade instructions that I think should be: 1) in addition to a regular ISY backup before you start, Also make a text backup of your programs. Open the programs tab and click the top folder usally name "My programs" right click and pick "copy folder to clipboard", then open any basic text editor, windows Notepad is a perfecft choice. paste the clipboard and save the file. 2) After upgrade, the first place you should check when you get logged back into the admin console is "Help > About" to ensure you are running the firmware version you expect AND that the UI version matches. If the UI version doesn't match, solve that problem before you do anything else. 3) next stop... Programs > Summary tab... look for the color YELLOW... if you have any you either ignored step 2 above and have mismatched firmware and UI... OR... the program had "adjust scene" in it and needs manual help.

Yes it's from version 5, I'm guessing you're running v4 then? (you need to upgrade seriously... upgrade from v4 to v5.3.4 is fairly simple... they only real caveat is if you have programs that use "adjust scene", if so, each of those programs will require a manual fix.) It's been a ;long time since i've seen a version 4 screen but if I recall there is a button near the bottom of the screen labels "options" that may have a beep setting. You can still try the factory reset followed by "restore device" that procedure didn't change.

I believe your premise above is correct: Yes.

which java do you have installed? The basic Java 8 installation downloaded here: https://java.com/en/ is what all the instructions on this forum are written for. If you install even the Java 8 SDK it changes things... If you install Java 11 or Java 17 which I believe are open source versions those aren't supported.

No it does not. The screenshots just above your latest 3 posts show how to set it up via Network Resources. It can also be done via a portal nodeserver named "Push". it can also be done via a Polisy nodesever named "Notification". But again those are 3 options the first option does NOT require polisy or polyglot.

in the admin console does Beep show zero? Also after making a change to any of these dropdowns you must push the button to the LEFT of the drop-down (such as "Beep" to cause the change to be sent to the device.... (yea it's not intuitive to do that). the second thing you can try is to to factory reset the device... Pull the air gap set button out, wait 30 seconds, press the set button all the way in an hold it in until the long beep STOPS. (other switches may have different factory reset instructions when in doubt google up the insteon pdf for the device). After the factory reset go back to the switch in the admin console, right click it and pick "restore device" which will cause the ISY to re-write the options and links to the switch.

Correct, ISY program If statements are event based. Anytime a value changes the IF is re-evaluated. The reason "Control" works where "Status" doesn't is Status is reporting On/off/dim level/etc, whereas "control" is just looking for the action "switched on". The other method that you might use when "control" isn't a choice is to link two programs: Program 1: If $state_variable = 1 then run program 'Program 2' (then) ----- Program 2: if (none) then disable Program 1 turn something on wait 1 hour turn something off enable program 1 --------- but if we do that we likely also need a program to make certain Program 2 wasn't running when the ISY restarted--- or in other words to get us to a known state: Program 3: [disabled][run at startup] if $state_variable = 1 then Run program "Program 2" (then) else turn something off enable Program 1 --- program 3 is always disabled but will run at startup if the run at startup flag is set. Disabled means specifically that the IF won't be evaluated, the program does run if called by another program or called by run at startup.

I don't own one so I can't say for sure, but someone in another thread recently pointed out that the 2448A7 has smaller memory and as I recall a limit ~500 links... Can't seem to find the post found it:

FYI, these links are pointing to wirelesstags instead of flume...

The instructions are in the wiki link above, but to re-paste here: Pushover Apps IOS - https://itunes.apple.com/us/app/pushover-notifications/id506088175 Android - https://play.google.com/store/apps/details?id=net.superblock.pushover Instructions Sign up at https://pushover.net/login Make a note of your user key Create an application at https://pushover.net/apps Make a note of your application key Enter same credentials into 'Pushover' app on device For each message you wish to send, create a network resource as follows 'https' 'post' host is 'api.pushover.net' port is 443 path is '/1/messages.json' timeout at least 2000ms (SSL takes a while to become established - can be lower if you change method to 'http' though mode is 'C Escaped' body to 'token=#Application Token#&user=#User Key#&message=Test Notification' full API documentation is at https://pushover.net/api ---- to add to that if you want a newline in the message use \n here's a screenshot: the "body string" here is: token=[redacted]&user=[redacted]&message=ISY Rebooted ${sys.date} ${sys.time}\nUptime before reboot: ${var.1.42} \nSaved Value: ${var.1.43}\n\nSent direct from ISY. which produces this notification:

Which brings up a new question.... that link is the PG2 store... is there an equivalent link for the PG3 store? I'll bet that @bpwwer knows...

That's exciting news... I'm curious to see if others experience good geofence experiences once updated to iOS 15.

I've not used the t-mobile text gateway, but I have used At&T and Verizon's and had sporadic results with both. Currently we have AT&T and the gateway is hit and miss.. somedays they come thru fast and somedays they take hours... and then there was a batch that were delivered 8 months later (thank goodness I add timestamps to the message body!) (I have a few messages that i still send via 3 services, although I'm now confident that Pushover always works) as @KeviNH mentions there are alternatives. He choose one that works well for him, my pick is Pushover. Pushover is a free to try, then one time 4.99 fee. Messages volume is almost unlimited. (10,000 per month which equates to about about 13.8 messages per hour 24 hours per day...lol.. no one needs that many!) Pushover can be used with Network Resources, see the link above, Or via a cloud Nodeserver Called Push, or via a polisy nodeserver called Notification. I started with network resources and converted over to the Notification Nodeserver because it has the added benefit of "retries" when there is an internet failure between Polisy and the pushover server. Pushover notifications arrive instantly.

You need to use "control" instead of "status" in the if statement. With "Status" when the motion detector itself turns off the status is no longer "on" so the "Then" body is abandoned and "else" (which is empty) immediately runs. The then body with "Control" will read "...is switched On" After you've made that change, a second trigger of the motion will start the time over again, once there's no motion for 5 minutes the light will turn off.

@matt.york You may want to just open a ticket for that issue, email support@universal-devices.com Climate is deprecated, they may need to delete it from your account. Include your portal login name and your ISY's UUID in the email.

Except your second screenshot suggests that's not the only problem you're chasing. If the ISY is not "Online" in the portal, you're likely never going to connect to it via the admin console. This is why I asked the questions about re-booting the ISY and what the front lights do when you do that.

@X-10 Your first screenshot shows irrelevant information about the security certificate of www.isy.com which is an Italian electronics retailer. Your second screenshot shows that the portal doesn't think your ISY is online. I assume you've tried rebooting it but plugging and unplugging it. What happens with the lights on the front of the device when you do that? If you only see the blue power light come on and don't see any of the other lights flash over the next couple of minutes, then I suspect that you have a bad ISY power supply (the black wallwart that plug into the outlet). UDI did have a batch of those that fail after a long time. Unfortunity the way they fail, coupled with the way the blue "power" LED connects to the circuit board means that the blue power light can come on, but there's not enough power to actually power up the ISY. This is easy to test because the ISY accepts a wide variety of replacements. from the wiki: Not sure what you're doing in the 3rd screenshot. ISY Launcher.app may not start from safari if that's a valid method.... I'm not a Mac guy, but browsers tend to block java.

If your notifications are email to text messages, that is likely the issue. The notifications are actually going out at the correct time, but they get hung up in the email to text gateway at your carrier. You can thank spammers that are using the gateway for spam for creating the problem. there are several solutions, the best of which is using pushover.net with a nodeserver. If you have Polisy I'd suggest @Jimbo's nodeserver called Notification, If you don't have a Polisy but do have a paid Portal account there is a cloud nodeserver called Push that will also work with pushover.net. Essentially to use pushover you buy the app once for as I recall 4.99 and there is no monthly charge. Pushover notifications are instant.

@walkman9999 to add a detail... ${sys.time12} contains the time the ISY sent the message. email to text on all the carriers is terrible. If you'd like a faster more reliable method investigate using pushover.net There are multiple methods. Network Resources alone can be used. There is also a nodeserver called Notification that has many robust features if you have a local polyglot instance, or if you have portal there is a different nodeserver without as many features called Push that also uses pushover.net infrastructure.

Attempt to send an email via the ISY, then check the ISY error log via the tools menu in the admin console, there should be a corresponding error if the server rejected the email.

to reiterate what @Geddy already said... Files named admin.jnlp (such as the file retrieved from http://isy.universal-devices.com/994i/5.3.3/admin.jnlp ) are a specific version of the admin console. admin.jnlp can also be downloaded from the ISY994 using the url http://<IP.OF.THE.ISY>/admin.jnlp. Each version of the ISY firmware has a matching admin.jnlp that is only designed to work with that firmware. start.jnlp (as downloaded from https://isy.universal-devices.com/start.jnlp ) is the ISY Launcher. The first time it is run it will install a Launcher Icon on the desktop. This is different than admin.jnlp When the launcher is used to correct version of the admin console is determinded and downloaded each time the admin console is opened either from a cloud source (udi server) or from the isy itself. Both of these methods rely on ISY Finder, however ISY Finders behavior is slightly different depending whether its being launched by admin.jnlp or ISY Laucher (which was installed on the desktop via start.jnlp) The Launcher is a newer method which was created to solve two problems: 1) browsers that block java due to security concerns 2) users mixing up versions of admin.jnlp and running the wrong version. If using Windows, ISY Launcher is definitely the best method. Some Mac users report issues when using ISY Launcher and report that continuing to use admin.jnlp works better for them. When using ISY Launcher on Windows it's really not even required to jump through the java cache clearing hoops with upgrading firmware because a fresh copy of the admin console is downloaded each time ISY Launcher is clicked from the desktop. It should be noted that "ISY Launcher" that appears on the desktop is not simply the file start.jnlp saved to the desktop, it was installed by start.jnlp but its not start.jnlp anymore.

Removing the variable from the ISY and re-adding it won't solve the problem. Early On I deleted the geofence from the locative app, and re-added it. I can't remember for certain if I also deleted the app from the phone. For the most part, my wife and mines phone via the locative app does enter and exit the geofence correctly, but not 100%... I still have extra notification programs enabled to manually supervise... which is a PITA...

While most of us have an expectation of what a nodeserver that we might be adding to make the switch from PG2 to PG3 does... I'm surprised that there appears to be no "Try Before You Buy" provision. What if it doesn't do what the user needs it to do? Is there a refund provision? I won't be just buying nodeservers to try them out. If they fill a need that's one thing, if they don't work that's another.

Login via SSH and type passwd at the prompt, and follow the prompts.

@SESamuels the short answer is you need more RED links. Any button in the scene that you want to be able to push and have it update anything (loads or other buttons) needs to be a RED link. Red links are controllers, the blue (or not red) links are responders. Responders only respond they don't control. When adding buttons after one button from the device is already a controller there is a trick question asked. It says something like "XXX is already a controller would you like to add this as a responder" answer NO... you want all of those links to be red. Once they are, then you will need to configure each device in each of the red links. (PS--it's time consuming, but once it's done you won't have to do it again).