Jump 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.

Techman

Members
  • Joined

  • Last visited

Everything posted by Techman

  1. You could have a defective breaker Try removing power from your keypad by pulling out the set lever to see if the problem could be coming from that device. I would also take a hard look at your inline devices. Check your wiring to make sure no hot wires are exposed.
  2. Your problem is most likely lack of PLM memory. The current PLM's can hold about 1000 links. About how many devices, programs, and scenes do you have? The PLM link count that you ran is an approximate count. The count can vary depending on ISY activity when the count is run. Try running another count. Deleted links, etc. will remain in the PLM and occupy PLM memory. Doing a factory reset and restore PLM will clear out those dead link tables.
  3. Yes, you should be able to do a restore PLM After the restore take a look at your device tree to see if their are any device with a red !, if do then do a restore device for each one that has the red ! After the restore do a plm link count to verify that links have been written to the PLM. Let me know what the link count shows. If you have battery operated devices, each device will need to be put into the linking mode before you do a restore device. Only one battery operated device should be in the linking mode at any one time. The links for Scenes are contained in the devices. You can disconnect the ISY and a scene should still function. If all else fails I can probably find you a good marriage counselor.
  4. Is your ISY firmware and UI the same version?
  5. Hopefully you DIDN'T do a delete modem prior to adding the new PLM. If you did let me know.
  6. Right click on MY PROGRAMS, the click on copy to clipboard. You can then paste the results into your word processor.
  7. Attached is the procedure for replacing a PLM. NEVER do a delete PLM. Replace ISY PLM.pdf
  8. Techman replied to Eric's topic in ISY994
    I'm using the Somfy ZRTSI zwave to RTS interface. The only options are either open or closed. To use the Somfy dry contact interface you would have to send two control signals, i.e. CLOSE and STOP. That can be done using an ISY program with a WAIT clause between commands. The position the shades stops in could vary depending on various timing conditions. I'm assuming that your Somfy motors are RTS and not hardwired.
  9. Take a look at this thread re: socket error. For the devices you're unable to communicate with do a factory reset on the device then a restore device from the admin console. It's possible that your power outage corrupted the device's memory.
  10. Techman replied to BobMic's topic in ISY994
    This is the one you need. It's the only one compatible with the Insteon Smoke Bridge First Alert SCO501CN-3ST https://www.amazon.com/s?k=sc0501cn-3st
  11. With the ISY 4.7.3 firmware the ISY does not support any of the sensor configuration settings, You should set the jumpers on the motion sensor accordingly. The motion sensor II is fully supported in the 5.0.15A ISY firmware and can be configured via the ISY
  12. Take a look at this link. It's a primer on ISY programming https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order
  13. The code executes from the top down. Sometimes moving a line of code up or down can make a difference.
  14. Also, try removing the lines Sunset to Sunrise for testing purposes. If the lights then turn put the Sunset - Sunrise as the first line of code in your IF statement
  15. That error indicates your SMTP server timed out. Try increasing the timeout value in the ISY email configuration. What email server are you using?
  16. The log looks good. Try removing and reinstalling the Multisensor 6. Then do a heal. If I remember correctly you have the option of installing both devices with security encryption which is supported by the 500 series dongle. You may want to use that option if you haven't already.
  17. The 300 series dongle will work with both 4.7.3 and 5.015A. The 500 series dongle requires the 5.x.x ISY firmware. Based on the distances between your devices everything should be working. It's possible that the update is an issue. You shouldn't have noticed any change in performance with the 300 series dongle between 4.7.3 and 5.0.15A. My guess is that the range extender didn't properly install. If you put the event viewer in level 3 then query the range extender does the extender respond without errors?
  18. Verifying the firmware on the Multisensor 6 is a bit of a process. I wouldn't be concerned with it now. Some forum members have posted that the coverage range with the 500 module is less than the 300 module. Is your multisensory 6 running on batteries or a power supply? How far is the range extender from the multisensory 6. How far is the range extender from the ISY? Your issue appears to be that the Multisensor is not communicating with the range extender. When you moved the repeater did you do a heal each time you moved it, if not try doing that. I have both the range extender and several multisensory 6 devices using the 300 series dongle and have never had a problem. They are quite reliable.
  19. What version of the Multisensor are you using. Do you have it updated to the latest firmware? What device are you using for a repeater? What is your ISY UI version? What version of the ZWave board do you have in your ISY?
  20. Your first problem is that your UI and your ISY firmware are different versions, this can be problematic. Follow the instructions below to update your user interface. After you update the UI then update your ISY firmware to 4.7.3. Be sure to do an ISY backup before and after any updates. Let me know if that resolves your problem.
  21. There's a typo in my suggestion, it should read SMARTPHONE.
  22. The error you're getting is a MAIL SERVER DNS ERROR what parameters do you have set for your email configuration? What version of the ISY firmware and UI are you running?
  23. The Venstar thermostats are reliable and can be controlled via a Smartphone app. All that's required is a internet connection and a/c power. They are totally independent from the ISY. You would also be able to monitor interior humidity and temperature remotely. https://venstar.com/thermostats/colortouch/
  24. Even though 5.015A is a beta release it appears to be quite stable.
  25. Before you do anything you need to update your UI. The UI and the ISY firmware need to be the same version. Click on the link below I would also suggest updating to 4.7.3. then do an ISY backup before you try to update to 5.x.x The new motion sensor will work with 4.7.3, but in a limited capacity. The sensor will default to a 30 seconds on signal and cannot be changed. If you decide to update to 5.015A you'll find a lot of update tips in the forum. You should use the option that includes Insteon and Zwave support.

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.