Geddy

@Michaelco one thing I just thought of...looks like you're on an iOS device. You could use Apple Shortcuts to trigger the variable. In Shortcuts there is a way to trigger if you're in a geofence area or connected to a specific SSID (can choose multiple). You'd then need to know how to send the command to the eisy to set the variable. I'm sure that's with a rest or some other URL based command (I don't do that kind of coding so I'm not entirely sure how that's setup, but I know many here seem to be able to do that or the info might be in the UD Wiki). I just checked about the connecting to an SSID and it has an option not to run again if it reconnects within 3 minutes. That part gets too complicated for me to sort out, but it's another option. I'm not sure if Apple's geofence option would work as good or better than the UD option. But the Apple Shortcut does give you an option to select which SSID you connect to and then trigger a shortcut that could be programmed to update the variable. I'd probably go on the side of over notification at that point. Just get an alert every time the gate opens. Kind of like MyQ with the garage door it will always alert open/close no matter who does it.

https://wiki.universal-devices.com/ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration While this might not be "fool proof" it's something that UD released after a lengthy discussion in another post (probably one that you've read and got confused by). I think @jkmcfadden is right that everybody has their own way to setup a fanlinc. There's not really a "wrong" way to do it as long as the way you do it works for you. But what might work for you might not work for others. I found where things get messy is trying to keep buttons in sync if/when you use Alexa or even a mobile app to change the fan speed. This is where programs are often used to adjust the button being light to match the actual speed of the fan. I set my Fanlinc and Keypads up in 4.x and didn't have to make any changes in 5.x because I have programs in place to keep things in sync. Also, I really don't care what button is light up if/when the fan is on as if the button wasn't pressed to set the speed then Alexa was and it will be at whatever speed it is until it gets adjusted or turned off. I'm just not finicky enough (aka OCD) to care about lights on a keypad on the wall compared to the speed of a fan in the middle of the room. To me...if the fan is on some light on the keypad might be on. I don't care which.

@lgilsenberg no, I use Alexa. I haven't "updated" to Alexa+ since there were a lot of known issues with that system not working well with home automation systems (not just UD). You're doing more advanced integration with UD and Alexa that I don't use so not sure why it would break. I just have it for the family to turn lights on/off when needed if our daily schedule alters from what we usually have automated. The trick is to keep the voice prompts unique and simple. Make sure devices don't sound like other devices: Hall/fall/wall Keep simple one or two word device (not long names): Living Fan or Livingroom Fan NOT Living Room Ceiling Fan I think scenes and routines are the most common complaints of things getting broken in the UD/Echo skill link. It's not clear if it's because the scene can get very complicated and Echo is trying to be "smart" by looking for a device rather than a scene and just control the device when really you want to control something in IoX that's a scene. It's as though the Echo system is trying to be the primary controller (especially with Alexa+) rather than using the skill link to send a command back to IoX.

I might suggest you open a support ticket with UD (https://www.universal-devices.com/my-tickets) and get their help. Your system is out of date and needs to update. There was a warning about running below 5.9.1 to update to 6.0.5, but could also be less significant issue going to 6.0.5 from what you're running if you're having linking issues already. Typically a hung system means something isn't right. You're just looking to reboot the system. I'm not sure what you mean by "shutting down the console". If you're in admin console and the link status is still constantly restarting or hung then the system is frozen. If you're able to get into admin console without a status bar running all the time click on the configuration tab then click on "reboot" and that should restart the eisy enough that it might not freeze. Allow a few minutes (maybe 5) for the system to fully restart/reboot. If you're using UD Mobile you should get a few alerts that PG3 is stopping then another message saying it is starting. If you don't get those messages then the reboot might not have been successful. Be sure to close/exit admin console and then push the power button until it turns red. Pull the plug for ~20 seconds. Plug the unit back in, wait 5 seconds, then (if the button is red) press power briefly and it should turn blue. You should get alerts that PG3 is starting (if you're using UD Mobile). After about 3-5 minutes try logging back into the admin console. MAKE A BACKUP OF IoX! Before you try to link anything again make a backup NOW. If you're running z-wave (with zmatter dongle) make a z-wave backup and THEN backup IoX. Usually you would want to select the option of "removing existing links". Now you mentioned something about this being previously linked directly with a remote. You might want to preserve those, but typically this option could be what is causing you issues. It's usually better to remove previous links when adding to the IoX system and then re-linking any devices directly once the unit is added and programmed correctly in IoX. Lastly, you should update the system to 6.0.5 simply to keep it current. Usually step # 1 in trouble shooting is "are you on the current release for firmware?". You are not. Many things could be working against you that might have been fixed in an update. Not likely in this case, but still would be the first issue is you're on an older firmware that could have an unknown bug/issue that is causing you to have this issue.

What are you trying to paste that keeps the indents? You posted a program. That's just fine and readable by many/most here. But for the specific to keep the indenting you would want to click the "+" icon in the format portion of the post block. Click the down arrow next to that and you'll have an option for "editor_tool--codebox". (I really don't like how the forum developer has so messed up some of the options. It's beyond our control as they're a separate company, but it's not quite as intuitive as it once was - IMO) That should get what you might be looking for, but don't sweat it...what you posted originally works perfectly. FYI the current version is 6.0.5. While I'm not sure if you're having problems or not it's advisable to update to fix any little bugs that might be lingering in the older system firmware. You can find info about this version in the "Current Release" portion of the forums. It also indicates best method to update.

looks like both virtual button plugins are free. Not sure what you're thinking costs anything. As for the Alexa problem -- yeah, that probably an Alexa issue as they (Amazon/Alexa/Echo team) really like to change code and ends up breaking things without letting people know. It's been a recurring theme here that things connected to/through the UD Portal to Alexa will randomly break then randomly work and it's nothing done by UD to disrupt the process...it's 100% random code changes via Amazon. I'm surprised people have been able to get support from Amazon to get things to work again. If I had anything that depended on Amazon's service it would have been removed long time ago.

@HBoley welcome to the UD Forums. For this issue you'll need to clear your Java cache and download a new start.jnlp from the UD site (near the top of the site click on "My ISY" and save the start.jnlp file). Otherwise you can also download the admin.jnlp file directly from the ISY994 device (http://<ISY-IP-ADDRESS>/admin.jnlp - remove the <> and use the IP of your device). When you clear the java cache be sure you select all 3 boxes! What computer OS are you using?

Sad that I keep little tidbits like that in my memory at times. I couldn't put my finger on the post if I tried, but I know there was something about it being very faded or small. This screen shot does show how faded it is. I guess if it were a different theme then it might show better, but can't say for sure. Glad it worked out easy for just being a UI anomaly.

@ferventgeek what computer OS are you running? I think I've seen people talk about this on macOS in the past. Looks like it's just a UI issue. Are you sure there are things in those scenes? Maybe add something to one to test and see if it adds a plus. Empty scenes will show up without anything to expand. If you select the scene try pressing the plus sign on your keyboard (if you have a separate number pad on the keyboard). Or try using the right arrow to get the scene to expand. While I doubt this was a "bug" in 6.0.4 there is an update to 6.0.5 that I would probably suggest updating to first just to be sure that's not an issue. Next be sure to clear java cache (checking all 3 boxes) then downloading a new start.jnlp from UD's site (on their home page click "My ISY" and save start.jnlp). I would be sure you're using the local sign on just in case there is a ui bug when using the cloud or portal login. Although I tried all options of mine (while local) and the scenes always appear with a plus (if there is something in them). One other thing I might suggest is looking for the UD State files in the temp directory (Reference: https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored). It doesn't hurt anything to remove them all, but specifically remove the udi_tree.state file for this issue. Make sure admin console is closed when you remove these files. Then clear the Java cache and download a fresh start.jnlp file again. (It's a good idea to remove any old admin.jnlp and start.jnlp files after they are used in case UD makes modifications to the files in the future you always want to get a fresh file from their site.)

Wouldn't you need to put an IP reservation in the router for the phone then? Also, most phones (at least I know the iOS) now uses random MAC address to limit tracking. Of course those that remember to might disable this and set it to fixed for known networks, but just how many really remember/know to do that? Then the issue becomes needing to remember to update the router/program/plugin to ping a new phone. Too many moving parts to remember.

I would say no. This isn't possible with UD Mobile. As @dbwarner5 points out looks like the main point of ONLY using wifi is not supported with UD Mobile. At least not in the geofence method. I don't see a way to make wifi connection change a variable. Geofence only uses location inside or outside an area. Not only relative to if you're connected to a certain SSID/Wi-Fi. @Michaelco the thing that I see suggested a lot of times is to set multiple geofence areas. If you have spotty service near the house a larger geofence could also be set that might have better cell coverage and set a variable when that is crossed. I do agree with @Javi in the point that if something did only use wifi that it could erroneously trigger just by having a router go offline or a device rebooting. Ultimately, the question needs to be what are you trying to accomplish? Perhaps use case of what you are trying to accomplish we could give suggestions of alternative methods of making something like this "work".

Not saying this is your issue, but the instructions to get 6.0.5 clearly said the update should be run through Admin Console. Glad you got it squared away though. I would suggest opening support tickets before randomly running SSH commands so that UD can learn what failed and fix/repair in the future. Plus they can instruct on the proper commands to run depending on what they see in your logs. But again, glad you got it cleared up.

@iglon do you have z-wave in your ISY994? If not then you can upgrade to the version @Brian H mentioned above (5.3.4). If you have and are using z-wave then which board do you have? See this post from @lilyoyo1 from a few years ago: https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/ Specifically: You don't need to have the ISY994 connected to the internet to update, but it does need to be connected to your network. If you want to update to 5.3.4 (and you don't have z-wave or have the 500 series board) you can get the update from the current release section of the forums: https://forum.universal-devices.com/topic/33287-534-isy994-last-release-for-isy994/ Be sure that you read the post and take precautions to make the backup before you attempt to update. My question would be that since you had updated to incremental point in the 5.x line for the ISY994 more than likely you didn't update again after because you might have a series 300 z-wave board and thus cannot update further. Since there is no support offered by UD and very limited support on the forums related to updates of unsupported hardware you would risk being on your own for any issues you stumble into if you do update. You might be at the point of it it isn't broke don't fix it. Are you having issues that you think an update would resolve issues?

@NewB welcome to the UD Forums. A couple of questions just for further information so we might have others chime in to help. What device are you using? You've posted in the ISY994 area so we will assume this is the device, but please confirm. What firmware are you running? Make sure that UI and Firmware match on admin console Help -> About screen. (Please post actual number showing on help/about screen) Have you tried any other troubleshooting other than just replacing the PLM? It sounds like you've done this before so you should be familiar with the process. Are any of the devices battery operated? I would strongly suggest making a backup of your current programs in case you have to start again. On the Programs / Details tab right click on the root folder (probably "My Programs"). Then select the last option "Copy Folder to Clipboard". Make sure you use "COPY". Then paste this as text in a text editor (i.e. Notepad on WindowsPC - DO NOT use a word processing document as you don't want it to auto format any text/code you might paste). Save this text file locally in case you do have to start over you have a text representation of all your programs and if they are enabled or disabled or not. This way you don't have to recreate them or fix them from memory. After you've made a copy of your programs I might suggest making a new scene (similar, but different) to an existing scene. See if those work as expected. If a new scene works with the new PLM then it's possible something is corrupt in the existing scenes with the new PLM. I'm not a big user of scenes so can't tell you other things to check. For other reference and troubleshooting though please open Event Viewer (Tools / Diagnostics / Event Viewer). Then set the level to level 3. Then manually operate a controller for the scene. Then try to change the scene from admin console. Save the log and post here. It might help narrow down devices that aren't responding.

Take a look at this thread: https://forum.universal-devices.com/topic/44344-issues-after-installing-tesla-powerwall-3/ Not sure why your house would be impacted by a neighbor doing something, but it might be a similar situation.

Thanks @bmercier for the release. This worked great while away from home! Seemed to work really quick on my testing. Now, just need to get web access to be as good as the Java interface! 😉 What I still don't understand is why doesn't the system page so true "upgrade to" versions? It didn't say there was an update needed to get this function. I saw you posted this and slid the comment to upgrade to 1.0.1. Making progress...nice! Baby steps.

@pjjameso what do you see if you go to the PG dashboard via eisy_ui? https://eisy.local then click the top left and seelct "dashboard". The best way to get to the PG3 dashboard now is considered via eisy_ui. There have been some changes with how plugins are connecting and using eisy_ui keeps things connecting "correctly" for some plugins. If you're going to the PG3 via the port 3000 connection it could show some plugins disconnected or stopped when viewing. Have you forced a refresh on the web page? Could be a cache value being displayed.

I seem to remember those settings always going away on Java update. If you have a lot of items and programs it should help if you add them again, but many systems have more memory these days so don’t think it is as big an issue as it was many years ago. Remember admin console is not designed to be left open. Many seem to leave it open and end up with issues if on a wireless network or a computer that goes into sleep mode. Be sure you exit admin console when not actively using it.

@mmb is there a typical time this is happening? On startup, on program save, if admin console left open? I think there was a thread about this a few months ago on an older firmware (early 6.x) and it was resolved in an update. If happening again you might want to open a support ticket to get it looked into for your specific situation/reason for this to be happening. Make sure that you don't have any 3rd party firewall or anti-virus software running and no VPN running. Open a support ticket here: https://www.universal-devices.com/my-tickets

@walkman9999 what z-wave controller are you using?

Read his earlier reply. Perhaps some changes have finally broken the last ISY994 firmware settings. I recall that there was a time that 4.x and early 5.x wouldn't work with the default due to the changes.

@GreyFox because this program is set to "run at startup" if you reboot your eisy then log into admin console this program will probably usually show the red line. Here is the reference in the wiki just as information: https://wiki.universal-devices.com/index.php?title=ISY_Programs:Icon_Colors The only time your icon would be fully green is while it was running the "THEN" portion. After the 15 minuets it should show half green. If you're rebooting your system and looking at admin console before the program triggers at 10:30:00pm then it will be partially red. That doesn't mean it isn't running. It's just the last time the program triggered it was false (and since you have something in the else section it would have run that portion). So that it doesn't catch your attention you might want to disable the "Run at startup" by right clicking on the program in the summary tab and select "Disable Run at Startup". You should look at the other programs that show half red in the summary tab to see if the "Run At Startup" column shows "ON" or a dash (-). If you want to see if the program works then right click the program and select "Run Then". It should turn on your light. But because the "IF" wasn't run it won't turn off in 15 minutes. If you're still worried that your programs are not running in the Summary tab look at the "Last Run Time" column and see if it's recent. If you just rebooted the device and all your programs are set to run at startup then most all of them should have a recent time run. I should also caution you that if you have a lot of programs set to run at startup you could run a big risk of too much Insteon traffic and create issues for your system. I would suggest limiting only major necessary programs to run at startup and others just allow to run at their regularly scheduled time. You could set the catch up grace period to a longer time if you have a lot of power issues. As @hart2hart suggests you should review the "Query All" program. Since in the ISY994 that might have been referencing the ISY994 or the name of the ISY994 you had. The Query All program is no longer default on Polisy or eisy systems. You will probably need to update that to point to your new device. The object will be in the "Your Devices" list. Sometimes it is near the bottom as a scene and will have an icon like a computer monitor. Then be sure you save the programs once you make the edit.

Try to reboot your device. Then also only access dashboard through eisy_ui and see if the versions are updated. Also, try the sysconfig.txt link above to see if the versions are updated. Lastly, relaunch the browser and refresh the page. Could be a browser cache display issue.

@hart2hart https://forum.universal-devices.com/topic/46475-updated-software-available/ I too seemed to be able to update without issue...maybe. Took less than 5 minutes. I think about 7 minutes including the reboot based on notifications from UD Mobile. Two issues I experienced: eisy_ui had issues logging in giving this error: "Timeout waiting for PG3 UI Session" (using Chrome) Plugin dashboard did not load (just showed blank page) (using Chrome) Just closing chrome and re-opening it seemed resolve the problems. The unit seemed to be okay to login so not sure why the errors were being given, but seemed to load fine on Firefox so restarted Chrome and things worked as expected. I confirmed with https://eisy.local:8443/WEB/sysconfig.txt that all systems updated to versions that @Michel Kohanim posted in link above. Nice work UD! PS: If you are using the java admin console and using the device credentials (i.e. https://eisy.local:8443/desc w/ local user/pass) you will need to clear java cache if using IoX Launcher/Finder (be sure you check all three boxes!). If you use the admin.jnlp direct download from the unit you'll also need to clear the java cache and download a fresh admin.jnlp so that UI and Firmware match.

@aLf too many uncertainties to say. I'd say no on an initial simple answer. Only because the ISY994 is no longer supported by UD and it's been so long for many of us on the forums since the update to 5.x to try to help resolve any issues that might happen in the update. If you need to spend a lot of time fixing things now then making the mover to eisy you might become frustrated and have issues that carry into the eisy system. One thing to look for in your current system is any programs that use "adjust scene". I recall that those will probably 100% break in the update from 4.x to 5.x. You'll need to recreate the program and possibly the scene. So if you have a lot of complicated scenes and even more complicated programs then I wouldn't spend the time to go to 5.x on the ISY994. It's just personal preference at this point and knowing that you won't have support from UD for the changes and have limited user help here because of time it's been since many updated to 5.x can't remember the little tips/tricks that fixed things along the development of 5.x.