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.

Michel Kohanim

Administrators
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. Hi richardl007, This means: -110014 SD DRIVE CONFIG READ FAILED You will find all our error codes listed here: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages What it basically means is that ISY has a problem reading the configuration file for your INSTEON device with address of "12 EF AE". Two things may contribute to this issue: 1. Corrupted SD Card 2. Corrupted file The first question is: what is this device? If still in your ISY, you may want to remove it, and then add it back. The second question is: do you have more of these errors with other files? If so, then I suspect you have a corrupted SD card With kind regards, Michel
  2. Hi LeeG, Thanks so very much for the feedback and it makes sense. Reason 9 = Cannot determine device link table address So perhaps we are dealing with an older PLM that does not support I2CS? Thanks again LeeG. With kind regards, Michel
  3. Hi Kentinada, Please go to Configuration | Email&Notifications tab. There's a list of recipients at the bottom and 5 is the name on one of the entries. With kind regards, Michel
  4. Hello 416to305, Just a few pointers: From what I see in your posts, I am very much concerned that the issue is not even with ISY/PLM/IOLinc. The reason is that the communication issue is related to the Sensor and not the Relay. ISY does not send any commands to the Sensor node of IOLinc because you really cannot do anything with it (it's read only). So, not only I urge you to contact our tech support but also check your Tools | Log and look for entries for your IOLinc-Sensor node. This will give us clues as to what else maybe trying to control the IOLinc. From over 8 years of experience I can assure you that factory resetting ISY will never solve any issues especially when communications related. Not only that, factory reset will prevent us from figuring out what the root causes are and, in case something starts working (intermittently), it's bound to fail again. And, thus a waste of your time. Factory resetting the PLM is sometimes useful but mostly when the issue is related to a full database on the PLM. I have never seen factory resetting the PLM fix communication issues. So - and to save you time and frustration - I do recommend not factory resetting ISY/PLM without a good reason (see above). With kind regards,
  5. Lee, please contact our tech support. There's a problem with the setup and all the factory reset, moving around, changing things will only exacerbate finding the root cause. With kind regards, Michel
  6. Hello 416to305, Please note that for battery operated devices, they have to be in awake mode otherwise ISY cannot program them. As you can see: TX/ACK but no SRX or ERX: TX - ISY sends a command to PLM ACK - PLM Acks the command SRX - The device Acks the command from the PLM So, please do make sure your battery operated devices are awake before you do anything to them. Also, our tech support is available to help you with all these issues. Please do not hesitate to contact us (links below). With kind regards, Michel
  7. Hi eyost, You do not need to make any VPN connections to ISY. All you need to do is: 1. Make sure you install a certificate (it can be self signed) 2. Always use HTTPS when you access ISY remotely and don't ever open the http port to the outside world 3. Change your password every 6 months With kind regards, Michel
  8. Hello JoeA, Thanks so very much for the details. Yes, you can definitely reboot ISY using our WSDK. This said, please let us go through your logs and fix this issue. It has to be fixed anyway. Thanks again and with kind regards, Michel
  9. Hi telljcl, I am so very sorry to hear. Can you please let me know what's your firmware version? With kind regards, Michel
  10. Hi sparkmedia, Thanks so very much! With kind regards, Michel
  11. Hi LeeG, thanks so very much as always. Hi telljcl, Let me try to clarify: 1. The sequence of execution of each program is based on the order of the programs as you have them listed 2. The issue arises when the program you are calling has interruptible constructs (such as Wait or Repeat) or that it depends on some condition that has not yet been met at the time of the call. Or, it's calling network resources, email notification, updating variables (which may cause other programs that depend on the variable to run), etc. which go in a queue and are processed independently So, if all your programs simply turn on/off a device (WITH a condition that's always true), then the sequence of execution will be the same as you have listed them in your programs. Now, going back to LeeG's comments, and what I have outlined above, it would not be a good practice to depend on the sequence simply because there are too many variables that may contribute to the sequence to be broken. So, of course you can do if $A=5 the set $B=2 ... If A is a state variable, then B is set to 2 as soon as A is changed to 5. Now if B is also a state variable then any programs that depend on B will start getting evaluated and may run. If you need help with your programs, please don't hesitate to contact our tech support (links below). With kind regards, Michel
  12. Hi Joe, Apologies. That's really odd. Would you please take a look at your logs and see if the time actually changed (fell back) on Sunday? With kind regards, Michel
  13. Hi Techman, What's your ISY's firmware. This might be an old bug. With kind regards, Michel
  14. Hi alexmanning, I suspect they disabled SSL due to the POODLE vulnerability. If you have an ISY994, then please upgrade to 4.2.18 and retry: http://forum.universal-devices.com/topic/14420-release-4218-rc8-is-now-avaialble/ If you have a 99, I am afraid you will need to upgrade to a 994. With kind regards, Michel
  15. Hi swnewman, That's perfect! We might need your solution!!! Yes, ST is the correct control to use the value of. With kind regards, Michel
  16. Hi Kevin, Do you have his contact information or can you please do the introductions? With kind regards, Michel
  17. Hi Kevin, Thanks so very much for sharing this information. I do thank Carlo as well ... perhaps we should send him an ISY as a token of our appreciation! With kind regards, Michel
  18. Hi swnewman, Thank you. I suspect whatever you're using as socket framework is immediately closing the socket that's why you do not see any responses in the feedback. With kind regards, Michel
  19. Thanks Mike. Please upgrade to 4.2.18: http://forum.universal-devices.com/topic/14420-release-4218-rc8-is-now-avaialble/. Once that's done, reinstall your certificate. With kind regards, Michel
  20. Hi snewman, As I suspected, -5012 errors: http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages This basically means that ISY tried to publish the events to the client but the client was not there anymore (or didn't respond). Are you immediately going to listen mode after your subscribe? If the log is empty, you get that error. With kind regards, Michel
  21. Hi Gee, If you are still having problems, please do not hesitate to contact our tech support team (links below). With kind regards, Michel
  22. Hi Mike, Have you recently installed a self signed certificate? What is your ISY's firmware version? With kind regards, Michel
  23. Hi pasierbt, 1. Please go to http://isy.universal-devices.com/994i/admin.jnlp... this will install an "ISY994 Administrative Console" on your desktop 2. Once the Admin Console comes up, login, and minimize it 3. On the ISY Finder dialog, click the Add button and enter the URL for your remote ISY 4. Close the Admin Console 5. Click on the "ISY994 Administrative Console" icon and then choose which ISY you wish to connect to from the list With kind regards, Michel
  24. Hi sanders2222, If you create manual port forwarding rules in your router for ISY as well as your cameras, then you won't have any of these issues UNLESS the external IP address changes. And, even then, you can use a Dynamic DNS service (supported by your router) such that IPs always get mapped to a name. For instance, my DLink router has a free service for dlinkddns.com which I use and I have been very happy with it. With kind regards, Michel
  25. And especially the very bright blue LEDs . Thank you all so very much for your sentiments. It does mean a LOT to us all. With kind regards, Michel

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.