Geddy

Like this: https://forum.universal-devices.com/forum/432-tasmota/

@KHouse for future reference it's easier to post a program to the forums as text. To do so: Right click on the program Select "Copy to Clipboard" Paste as text. This does 2 things. 1) makes the program searchable in case it's a program that others are attempting in the future. 2) allows anybody helping you make the modification(s) to help explain how to fix the program. In addition to what @Techman suggested is the switch you're checking for "on" a dimmer? If that's the case maybe make it "Status NOT off". That way if it's at 50% the status would be "not off" and at 9pm would turn it off. This is a test program I just made and confirm it worked and looks like what you're attempting: Office_test If Time is 8:43:00PM And 'Office' Status is not Off Then Set 'Office' Off Else - No Actions - (To add one, press 'Action')

Try accessing Polyglot from a different browser. If that doesn't work, I recall another user recently that had a similar problem. If I recall they did the following: login to https://eisy.local:3000 go to System | Switch Portal Profile then login (to the portal) Screen will refresh back to Polyglot click the Logout button (polyglot web access - top right) Log back in

Just made a program like this on my eisy. Test-PaulBates If Time is Sunset - 30 minutes Then Set 'Backdoor' On Else - No Actions - (To add one, press 'Action') isy-5.7.0_5 Name : isy Version : 5.7.0_5 I even closed admin console and re-launched to be sure display wasn't frozen and it still shows as expected to run 5:07:08 with sunset at 5:37:08.

@DSwallow why not just use HTTP? It won’t warn you that way. I use: http://eisy.local:3000 And never get a warning. Only if you’re using https would you. Since you’re internally accessing a device on the same network do you really need https? It’s just that browsers “default” to the https. If you would like to pose this question directly to UDI it’s best to use the “Contact Us” method on their site.

@Eric just so everybody knows what you're working with please let us know: Device Firmware While the answer normally wouldn't change all that much there appear to be a lot of long-time ISY994 users still on a 4.x firmware. There were big changes when going to 5.x. Also, nice to know if using a current model device (eisy or Polisy). Now, you might want to look at what you have setup for the controller for the scenes. Remember if you control the scene from the admin console that is a controller and it might not have the same settings as a button or switch setup as a controller. If you expand the scene compare the settings of the red devices in the scene with the settings (actions) of the root. The ISY service (i.e. admin console and possibly the Alexa) would act as the root to control the scene.

Did you do something recently to the network configuration that would make you think it would be messed up now? Otherwise, does kind of look like somebody might be running port scanning on you, but that's just a guess. I think @Techman is right the only "real" way to know is to open a support ticket and include the log (as a zip file) for them to review. https://www.universal-devices.com/my-tickets If you did make changes to the network settings please explain further. Have you added port forwarding on your router so that you can access the ISY while remote? If so, that's risky. The best way to securely access the ISY994 from a remote location would be through the UD Portal connection (make sure you have a strong password for the portal account!). Lastly, once you hear back from UDI on the support ticket please post the findings here so it might help others if they run into this issue they can learn what it was.

@eataft answer given by @tlightne is correct. From the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device Right click the device you need to replace. If it's in a folder the option you want is "Remove from Folder" Then you can right click on it once it's in the root and will have "Replace {device name} with >".

@Palmer marketing I think you're mistaking about the admin console, it's Java based. But I get your point(s). However, if you want to contact UDI directly the best method is using their "Contact Us" portion of their website. Their time is not spent monitoring every thread of the forums. Also note that while the Mobilinc app will work with the eisy just as it does with the ISY994 it will not incorporate plugins added to the system (and some have mentioned that Z-Wave and Zigbee devices are limited). Many have moved to the UD Mobile app that is being developed by UDI.

@bgrubb1 probably hard for some to really know what version they're on. It depends on when they upgraded to 5.7.0. Since the _5 came out several days after the initial release and there wasn't a "new" post made and since it didn't impact the actual release number not many would know what build release(?) they were on unless they went to the info page that Michel had posted earlier in the support thread. To find what version is installed go here: eisy: https://eisy.local:8443/WEB/sysconfig.txt Polisy: https://polisy.local:8443/WEB/sysconfig.txt (or replace the *.local with the device IP)

@ctviggen1 yes, the program issue was an "old" bug issue with IoX 5.7.0 and you need to run upgrade packages again to get an updated version of IoX. Please go to this link when you're local to your device: https://eisy.local:8443/WEB/sysconfig.txt (If you have a Polisy replace eisy.local with polisy.local or use the IP address instead) You are looking for: isy-5.7.0_5 Name : isy Version : 5.7.0_5 You can see issues that happened after time change starting with this post in the IoX support thread:

@GSpitale01 This is a known issue. Been posted about in other threads. It's only a UI issue. It appears to have been corrected this morning based on some posts. Looking at my own eisy admin console it does appear to be correct for display. Based on your screen shots your highlighted program was next set to run at 6:00pm even though the displayed sunset time is 4:52. so that would mean the time displayed was incorrect, but the program should fire about the time of sunset. Depending on your location setting. Closing this thread as there are already other posts about it and issue seems resolved as of this time. If you still have issues please comment in thread linked below.

@oberkc if you've run the "upgrade packages" process and there was no change in the version in the information link supplied above then a power cycle would be best step to force everything to start correctly and implement the changes. Somewhere from 5.6 to 5.7 the system triggered all programs to go disabled. Once UDI released 5.7.0_5 that would restore programs as expected. Otherwise, restoring from a recent backup would be an option, but any reboot might trigger all programs to disable again. If you get upgraded to 5.7.0_5 (or later) and the programs still disable on reboot (or randomly otherwise) please open a ticket with UDI for them to help troubleshoot and resolve directly.

Glad you got it working. By chance on the computer you were using originally were you running any firewall or VPN services? One of the links @paulbates posted suggested the Proxy error was related to lost network connection. Usually that could be the case if running a firewall, antivirus, or VPN like program that would suddenly drop the connection to the ISY. Once you have the eisy up and running try going back to the original computer, clear the Java Cache (checking all three boxes), make sure you turn off any 3rd party programs that might impact your network and see if you can access the admin console from that computer.

@johnnyt oh, I believed you all along (I even said "I've suffered similar issues"). I just don't have anything so major that depends on time to do stuff. My HVAC works independent of eisy, but does report state and status, but I don't rely on the eisy to control it. I don't have eisy handle alarm clocks (that's just crazy to consider (IMO)...I use my phone for that or an actual alarm clock - I must be "old school"). This time I just have the UI issue showing the sunset/sunrise time off by an hour, but no programs had issues running and nothing went too crazy on my system so it was basically a non-event for me. It wasn't until others were posting that they noticed the times were displayed wrong that I went to see and experienced the same issue. Hope your system survived whatever you attempted!

@AnthemAVM split this out since the other thread seemed to have run it's course and you have NEW request for specific use case. This way people might see your post and help rather than skipping a post that seemed to have been resolved. What was wrong with the suggestion that @Techman offered in the other thread? Sound like you just need to get a sensor then learn how to program it correctly to correctly handle your situation.

Closing this thread as this is also being discussed in the IoX 5.7.0 support thread. It appears to only be a UI issue (meaning the programs run at the time they are expected to run with relation to the actual sunrise/sunset time. Only the time being displayed in the admin console is incorrect.

@madmartian I'm not the strongest users for Z-Wave so only going off what I've read on the forums. I think this is a warning that the ISY should be removed as the controller for the Z-Wave network before you proceed. From what I hear others reply with is when adding Z-Wave devices you have to do an exclude process then include process. I think it's similar to factory resetting Insteon devices before adding them in to clear out prior programming. Since you will remove the primary controller from the ISY system the devices would still be looking for the ZMatter controller. (I assume you're using the Z-Matter, but please correct if that is a wrong assumption). You're right, I don't see any documentation anywhere. So if you're worried about the process please open a ticket with UDI Support to get the answer you're looking for as most here have not (recently) attempted to rebuild an entire Z-Wave install. https://www.universal-devices.com/my-tickets/ As an additional comment, I might suggest you make a text copy/backup of your programs so you can recreate any Z-Wave related programs once you have the devices added back to your system. The programs should stay in place, but have broken links to the missing devices, but text file might also be something to assist you in the process of repairing those programs. Right click on the root of the programs tree (mine is "My Programs") then select "Copy Folder to Clipboard", then paste that to a text editor (i.e. Notepad for Windows).

FYI it's this area: https://forum.universal-devices.com/forum/339-current-release-announcements/ All "current release" announcements are made there. I haven't attempted to update through UD Mobile in a very long time so I'm not sure what's the issue with that. The "Upgrade Packages" in admin console should work. Don't click any of the alerts after you start the upgrade process and you should get another alert that it has completed and needs to reboot. Follow the steps above again to power cycle the system. After any IoX update you will need to clear the java cache (selecting all three boxes) and get a new start.jnlp file to put the icon back on the desktop. This way the "local" option of connecting through the IoX Launcher won't complain about the UI/Firmware mismatch. The "cloud" option should download the proper UI, but I've found that the local still needs a fresh start. I'm not sure what you mean by "transferred all the licenses". What licenses and how did you do that? Do you just mean portal account migration? How is your UD Mobile setup to connect to the eisy? If only through portal then you need the portal credentials. If you have a local network setup that would be the same that you use when connecting through admin console locally. I think you've attempted a lot of troubleshooting on your own that might have put the device into a point that it isn't an "easy" fix with forums posts. Your best bet would be to open a support ticket and have UDI help troubleshoot and fix directly. https://www.universal-devices.com/my-tickets/

@timlacey first try a full power cycle of the device. I will assume you have the eisy (even though you don’t specifically say) based on the versions shown. press the power button 6 times Blue light should turn red if bot after about 60 seconds pull the power supply Pull power supply wait 20-30 seconds plug back in wait 2-3 minutes for the device to boot up completely attempt to access the web interface directly http://your.eisy.IP.address:3000 Check what version is now shown at the bottom of the web interface. It appears your system was stuck in an update somewhere. Thus the “restart required” comment you see in your screenshot. Check the current versions area to see what version you should be on. If you’re not on the current builds you need to either run the update packages process in admin console or read the wiki for the button presses to initiate an update. As for the device not being found in the IoX Finder window that can depend on your router and network. Best option to troubleshoot that is to clear Java cache (checking all 3 boxes to clear internet files), delete any “start.jnlp” and “admin.jnlp” files you might have on your system, download a new IoX Launcher (start.jnlp) from either UDI website (clicking on “My ISY” on the top right) or from the wiki. NOTE: if you had node servers (now “plugins) installed previously you need tun click on “system” then “reinstall all plugins” once your device is on the current version.

@TheA2Z you could also review this post if it gives any tips/tricks. Seems to be similar to what you're wanting to do and how @tazman describes involving Routines. I've never explored this path so don't know if this post is still relevant or not, but know many referenced it in the past.

@UD2)17rrh did you update the eisy recently? If so, have you performed a full power cycle? (not just pressing the reboot button in Admin Console.) It sounds like some processes are not running correctly and the device needs to be power cycled for things to get back in sync. Best practice would be: Pressing the power button 6 times (that's the multi-function button on the eisy) Blue light should turn red (might take some time - if longer than 5 minutes something is probably "stuck") Pull power cord Wait 30-60 seconds Plug device in Wait 3-5 minutes for it to fully boot before attempting to access the web interface or admin console. The credentials for the web access are the same you use to log into the Admin Console locally. Rather than trying to access the web portion from the admin console open a web browser and go to: http://eisy.local:3000/ - See if that gets you to the login screen. If you still don't get logged in try that on a different browser (cache could be stopping you if you've tried multiple times on your current browser).

The only path to migrate to the eisy is with firmware version 5.3.4 on the ISY994. Therefore, you'd have to go through the (possibly painful) path of updating the current system (if you're not running Z-wave you could go all the way to 5.3.4) then making a backup to import to the eisy. Please review the wiki for migration steps: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994 For the backup of programs you could copy all programs to a text document and recreate them manually. It's time consuming, but might be "easier" to do that than updating the firmware to a version that would migrate and run the risk of issues in that firmware update and then more/different issues in the migration. Right click on the root program folder ("My Programs"?). The last item should be "Copy folder to Clipboard". (note: be sure you COPY, you do NOT want export) Then open Notepad (or other text editor - NOT a word processing program because you do not want the text manipulated). Paste in the text file and save as plain text document. This will be all your current programs.

@gschoffstall what does the node server look like on the PG3x dashboard? Does it show nodes? If not then the hub hasn’t linked. If you reinstalled the plugin you might have to link the hub again. Restart the plugin then press the hub button again. If you have nodes being displayed on the web dashboard for Polyglot they should push to IoX when admin console is reloaded. You have been doing a lot of different settings changes…please make sure you haven’t altered the IoX configuration in Polyglot. Click on “IoX Configuration” then “Edit Current IoX” and make sure the IP is 127.0.0.1 (or maybe localhost). Beyond this point it might be best to get help directly from UDI. I’ve got you this far along. I’m not sure why it’s not working and they can diagnose with you to get you running. See link in a post above to start a ticket.

@gschoffstall Have you closed/restarted Admin Console? You should NEVER have to setup anything in Admin Console as you're suggesting. If you have it could have overwritten something the node server was pushing there. Did you see my comment above about not having Admin Console open when you add plugins? Nodes are only added to Admin Console on launch. So if you added Hue and AC was open then you have to close and restart it. The nodes should be pushed into the primary tree of devices. It's been so long since I added mine I forget how they were entered. But you shouldn't have to do anything in Admin Console to make the lights appear in the device list. I put all devices that use a plugin (formerly Node Server) in a "NodeServer" folder. Just easier for my preference. Once the node server finds the lights they should be nodes in the plugin screen. From the dashboard you should now have this: (disregard the number on my Nodes and your screen will say "Hue (1)") Your dashboard (assuming you got the hub to connect to the plugin) should display the node count for your system and should be for all lights and rooms you might have setup previously in the Hue app. You can click on "Nodes" or "Details" (they take you to the same place). Then click on "Nodes" again and it should take you to a list of items it found when it synched with the hub. Look in the "Address" area. That should now correspond to a device in the IoX Admin Console with a "n001_" prefix. That means it is a node from node server (now plugin) in slot 1 and the address is the identifier for that device. In the Admin Console you should see it by a common name seen in "Node Name 1". If you click on that device on the right side of the screen under that name you should see the "n001_#######" information. Now...since you said you did something in Admin Console to make Hue node server 1 it might be okay just to re-launcher admin console. Or you might need to delete what you did there by clicking on that listing and clicking "Delete" at the bottom of that window. Do THAT as last resort! Just close and re-launch admin console to see if it fills in nodes/items in your device list.