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. It could be one of several issues. The garage door motor could be causing noise on the power line. Mine does and I had to use a Filterlinc on my garage opener. If you're using CFL bulbs in the opener they can be problematic as they sometimes create noise on the power line. Being that the IOlinc is a power line only devices you might want to add a dual band device, if you don't already have one, near the IOlinc such as a range extender, an on/off module or a lamplinc
  2. The Zwave Aeotec Multisensor 6 is fully supported by the ISY and offers many benefits over the Insteon motion sensor. As mentioned above you'll most likely need zwave range extenders. Take a look at the Aeotec website.
  3. If you have Zwave then there are other options. The only Insteon motion sensor currently being sold is the one you have
  4. This usually indicates a communication issue between the device and the PLM Take a look at these troubleshooting tips https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors
  5. Additionally, make sure that the battery operated device is within RF range of either the PLM or a dual band device so it can communicate with the PLM in order to have its link tables updated/written to.
  6. Anytime you make a change to a device which is also linked to a battery operated device you need to put the battery operated device into the linking mode in order for the changes to be written to the battery operated device. You can only have one battery operated device in the linking mode at any one time otherwise the link tables can get corrupted/cross written.
  7. You have a communications problem between the PLM and your Lamplinc. Take a look at this troubleshooting guide https://wiki.universal-devices.com/index.php?title=INSTEON:_Troubleshooting_Communications_Errors&redirect=no
  8. I'm assuming that you're running 4.6.2 (or earlier) ISY firmware. If so the firmware does not fully support the motion sensor options. This sensor was recently released and replaced the previous motion sensor which the ISY fully supported. The ISY only recognizes a timeout of 30 seconds (on the current MS), thus the need for programs 1 and 2. If the light is turned on from a scene then have program 2 turn on the scene rather than the light.
  9. You'll need two programs Being that the default on time is 30 seconds The first program should call the "then" statement in the second program which will turn on the light. When the motion sensor turns off the 2nd program will continue to run until completion Program 1 IF Control Motion sensor is ON and Dusk is ON THEN Run THEN statement in program 2 ELSE (blank) Program 2 IF (blank) THEN turn on light wait 5 minutes turn off light ELSE (blank)
  10. I'm not sure if 5.0.10 treats the ISY link tables differently or if it's a bug in 5.0.10 I'm running 4.6.2 and the only mismatch I've come across is EA, which shows up on the device link table and can be ignored..
  11. The mismatched link usually shows up in the device link table not the ISY link table. Doing a restore device rewrites the link table stored in the ISY to the device. The ISY link tables shouldn't change unless you reprogramed a device from within the ISY. What version of the ISY firmware and UI are you running?
  12. That seems to make sense for the AA link to appear in the device link table but why would the AA show up in the ISY link table?
  13. I'm not aware of an option to disable the "flash". I believe it's an indicator that the button action was processed.
  14. I've never come across a device with an AA link. It's possible the link was left over from a previous use or a factory test. You could always try a factory reset / restore device to see if that eliminates it. Not sure why it would show up on the ISY link table. Did you buy the device new from Smarthome or from a 3rd party?
  15. Try doing a factory reset then restore device on a device with an AA link table. Let me know if that clears up the mismatch. What type of device is it. What's the 4 digit date code on the device?
  16. Can you take a screen shot of the link with AA in it and post it on the forum
  17. Take a look at the attached Insteon White Paper, it has a detailed explanation of the link tables. AA appears to be used for RF packets (see page 31 of the white paper) If all you devices are working correctly after you installed the new modem then you can probably ignore the "approximate" link count from the calculator. Insteon white paper.pdf
  18. Yes, UUID is the ISY's MAC address
  19. How many devices do you have installed? That link count sounds very low and usually indicates a failing PLM.
  20. The manufacture date is the 31st week of 2009. Do a PLM link count during a period when the ISY is not busy. If the link count is low then it's time to replace the PLM. The new PLM's have updated hardware and firmware.
  21. In the option menu for the KPL set the button to Non Toggle (off)
  22. The Siren is not supported in 4.6.2 firmware. Not sure if its supported in the 5.x.x alpha release.
  23. I'm running 4.6.2 which works with the motion sensor node, but only the MS default options are available.
  24. The motion node is supported, the other nodes are not. Add it to the ISY using the previous motion sensor ID (2842-222) Yes it can be added to a scene or a program
  25. Having dual band devices within close proximity to the motion sensor may help. There will always be a slight delay when turning on a scene.

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.