Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

JimTurner

Members
  • Joined

  • Last visited

Everything posted by JimTurner

  1. UPDATE: it seems that an "Run at Startup" selection messes with the next scheduled run. Example: I have outside lights that are supposed to come on at sunset. Here is the sequence: Saturday - Last Run Time is Saturday 8:06PM, Next Scheduled Run is Sunday @ 8:05 PM <-- THIS IS CORRECT Sunday - System auto power cycles @ 12:05 AM which now reports the next line: Last Run Time is Sunday @ 12:06 AM, Next Scheduled Run is Monday @ 8:04 PM <-- THIS IS INCORRECT I would NOT expect running a program between scheduled times would affect the schedule... I turned off the "Run at Startup" and tested again. The schedules now report correctly.
  2. The "turn on" is actually 2 programs: the second is run with no conditions but executed from the "Run Then" in the first (which is scheduled). I used a "Repeat 3 times" in the second as some of my devices didn't respond correctly / consistently. That solved it. (may be overkill, but it worked). There are no other folder conditions. The governing triggers are the generator switch and the sunset time - 20 minutes. It's the first program that shows the messed up times in the screen snippet above (new snippet attached showing complete line...). I would have expected that the next run should have been Sunset on SUNDAY not Sunset on MONDAY... First Program (controlling): NighttimeLightsOnAtSunset - [ID 0054][Parent 0026] If $GeneratorInUse is 0 And Time is Sunset - 20 minutes Then Run Program 'NighttimeLightsOn' (Then Path) Else - No Actions - (To add one, press 'Action') Second Program (does the work): NighttimeLightsOn - [ID 0053][Parent 0026] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 3 times Set 'ButterflyLamp' On Wait 2 seconds Set 'Dining Room Chandelier' On 35% Wait 2 seconds Set 'Front Porch' On Wait 2 seconds Set 'Front Porch Plug Top' On Wait 2 seconds Set 'Front Up Lights' On Wait 2 seconds Set 'Garage Outside Lights' On Wait 2 seconds Set 'Kitchen Und Cab Fridge' On Wait 2 seconds Set 'Kitchen Und Cab Stove' On Wait 2 seconds Set 'Living Room Floor Lamp' On 50% Wait 2 seconds Set 'Media Room inner wall' On 50% Wait 2 seconds Set 'Media Room outer wall' On 50% Wait 2 seconds Set 'Shop Front Lights' On Wait 2 seconds Set 'Shop Side Lights' On Wait 2 seconds Set 'Virtual Device Controller / GoodNightControl' On Else - No Actions - (To add one, press 'Action') Uploading Attachment...
  3. Hi - Dug through the forum posts and did not find my issue. I have an EISY with a device that cycles the power 1/week on Sunday at 12:05 AM - off, and 12:10 - on (currently - can be scheduled). I have a program that turns lights on at Sundown - 20 minutes The program was set to run at startup, so it ran at at 12:12 AM,, then set the next run time at Monday at 8:05 PM. This SKIPPED the Sunday 8:5-ish run and my lights didn't turn on. Call me puzzled. Thoughts from the experts?
  4. Ticket submitted...
  5. Hi all. This has happened more than once. UD Mobile won't read status of any nodes - even though it says connected from the admin section a. It cycles on the "home screen" saying disconnected - attempting to reconnect b. Testing the local connection reports "Cached firmware version may be incorrect *6.0.4), try pressing the search icon next to the Local IP..." Doing that changes the IP to EISY.LOCAL but the issue remains... (The "Cached firmware... " message remains even after clearing the main problem for nodes) c. Testing the remote connection works fine e. Same behavior on 2 different IOS devices (iPhone and iPad) Admin Console works fine eisy.local web access works fine I've tried rebooting from eisy.local, Admin Console, UD Mobile, Pulling the plug and waiting for 2 minutes seems the only way to clear this. HELP! ~jimt
  6. I have a ZOOZ Range Extender https://www.thesmartesthouse.com/collections/zooz/products/zooz-800-series-z-wave-plus-range-extender-zac38 that reports power loss. It connects via z-wave and has a battery backup. Maybe something like that connected to the grid side of your power?
  7. Not sure if this is intended behavior, but version 1.4.7 of the app only opens favorites on App Launch. It USED to go back to favorites when you toggled back to the app from somewhere else. Restarting phone does not help. Running this on an iPhone.
  8. Success! One thing to note: when you add the original eisy URL (with port 8443) to the ISY Finder, you will use that one to sign on with the original credentials. Hitting the same URL WITHOUT the port will require you to use your Portal credentials.
  9. JimTurner replied to JimTurner's topic in eisy
    Holy CRAP! Looking this up, it's a known issue for Spectrum DNS servers... Geesh. Time to change to a public DNS.
  10. JimTurner posted a topic in eisy
    Was setting myself up for the upgrade to the latest on my eisy and issued an ssh tail to /var/log/messages and saw this: Sep 23 12:37:04 eisy ntpd[1545]: error resolving pool pool.ntp.org: Name does not resolve (8) If I hit the pool.ntp.org directly, it resolves to some luggage website. Is there a place to change the URL for updating the time? This seems to be buried somewhere that is not evident.
  11. Update on this issue for those who may be looking for this later: I THINK I found the issue. In the old Insteon Hub days and before I ended up with as many Insteon devices as I have now, I used a Range Extender 2992-222. It is supposed to just relay Insteon traffic, but after I unplugged this device my random ons have disappeared. (Watch, within 24 hours of this post something will turn on again... )
  12. Thanks. I'll see what happens when I try this.
  13. I had to add the 8080 port number (configured in the AC) to get this to work.
  14. I had an ISY994 and was able to trigger programs with this URL: http://<UserID>:<Password>@192.168.x.x/rest/programs/<ProgramID>/runThen The program ID is what is listed in the program summary tab in the Admin Console ("0001" or "000A", etc.) First time trying to test this with the EISY and it fails. My use case: I trap my UPS events in Windows (Power Restore, Dirty Power, etc.), hit a URL in the ISY that would shut off some sensitive equipment before the surges killed them - gotta love Central Texas power grid... Possible? Edit: Figured it out - but can't delete my post! :(
  15. Wondering how many have gone through the upgrade process. I am on FreeBSD 14.1 p6, and IOX 5.9.1. To get me to this point, I needed assistance from UD ticket meisters, so I am a little leery of hitting the "go" button. Let me know your experiences... ~jim
  16. Thanks. I found the files and cleared them (actually just renamed them in case...).
  17. Anybody know where these values that show in the IOX finder are cached?
  18. So, I had 2 issues - the second one was self induced trying to solve the first. My PG3 was totally MIA, and in attempting to do a simple reboot, I started the upgrade unknowingly, and then the entire EISY was MIA from my network. ugh. Submitted a ticket and Michel assisted in getting me network access. I attached a monitor, keyboard and mouse directly to the EISY to do this. Once network connectivity was restored I was able to SSH into it. Lastly, Michel did a screen share and cleaned up the mess. Amongst other things, looks like I had logs that chewed up storage - not sure, as Michel was moving very fast. EISY is up, Zwave is up, PG3 is up, and all good. ~jim
  19. Hello: I have an EISY but have not done the latest massive upgrade just yet. My Polyglot installation seems to have disappeared, and 4 plugins that I am using no longer work. I get "Connection Refused" when I try to launch the PG3 webservice from the EISY. I've power cycled twice - the last time for 15 minutes. Polyglot still not available. HELP! ~jim
  20. Found it - thanks. I have so many devices, it was buried.
  21. My old ISY994i had a query program for the 3AM resync operation. The EISY doesn't expose the node to do that - or at least not that I have found. I get the Reboot clearing the issue reason. I'm going to install my new USB PLM tomorrow.
  22. I have no sensors like this. Just switches, plug in controllers and dimmers - mostly switches.
  23. I saw that - but never played with it. I am assuming that it only touches the one that I select...??? I haven't tried to control from Console. Good idea - cut the problem in half.
  24. I have the original 2413S (Rev 2.9 4716) and had purchased a backup (cause of where I live) 2413S (Rev 2.5 1619). I installed the backup when I installed the EISY. I also have a 2413U that I bought but never put in service.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.