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 Harold, Please do let me know if you can access locally when you get back. With kind regards, Michel
  2. Hi bigscience, Sincere apologies ... I had it confused with Leak Sensor. Unfortunately, there isn't a hearbeat signal for this device. I am so very sorry. With kind regards, Michel
  3. Hi Harold, Are you using MobiLinc Connect? If not, which part of MobiLinc is not working? Also, when this stops working, can you connect to your ISY locally? And, finally: 1. What's your ISY's firmware version? 2. Do you have Verizon or AT&T/FIOS or DirecTV? With kind regards, Michel
  4. Hi bigscience, You can use the hearbeat node for that (if you have 994 + 4.0.5 and above). With kind regards, Michel
  5. Hi Roger, Just responded to you via PM as well. 16 bytes = 12 + 4 CRC ... as such, please use 12. This said, you MUST see ISY going through Scanning, and then Down status. If you don't get those, please contact me directly via support@Universal-devices.com. With kind regards, Michel
  6. Hello toflaherty None whatsoever! They should all work. From management perspective (ease of figuring what what is forwarded to what) it's best to have both ports be the same (i.e. change ISY's port to the forwarded port). For obscurity purposes, it's best to change ISY's port to an obscure number and choose another obscure number for the public port. I very much doubt this would get you any additional security though. With kind regards, Michel
  7. Hi outsider, It's the same problem as multiple login: http://wiki.universal-devices.com/index ... r_Your_ISY With kind regards, Michel
  8. Hi outsider, I suspect your 99 was excluded from your anti-virus/firewall whereas 994 is not. Here are some instructions for configuring firewalls: http://wiki.universal-devices.com/index ... r_Your_ISY With kind regards, Michel
  9. Hi Harold, thank you and Happy New Year to you as well. Did you enable internet access by doing a File | Enable Internet Access or have you created port forwarding rules in your router? With kind regards, Michel
  10. Hi NNilsen, http://wiki.universal-devices.com/index ... structions. Please note that with Z-Wave, you might need at least 4 to 6 (depending on the sq footage) other Z-Wave devices to create a mesh. With kind regards, Michel
  11. Hi haroldunger, ISY is definitely not defective if your programs continue to work. If you have Verizon FIOS or DirecTV, please upgrade to 4.1.1. Also, as BrianH suggest, if you used File | Enable Internet Access, then - and in all likelihood - your ISY's IP address has changed but the router does not know anything about it. And, in the meantime, please send your Tools | Error Log to support@universal-devices.com. With kind regards, Michel
  12. Hi blartyo, MAC? With kind regards, Michel
  13. Hello wrj0, Is rule 116 the one you are working with. Again, the error code means that ISY could not make a TCP socket connection and therefore I suspect networking issues. That's unless rule 116 is something else. With kind regards, Michel
  14. Hi blartyo, I am so very sorry to hear. Can you please let me know what you mean by "not recognized"? Please note that you need a Zip utility (not Windows compression) to look inside ISY's backup zip file. With kind regards, Michel
  15. Hi apostolakisl, Agreed. With kind regards, Michel
  16. Hi wrj0, According to: http://wiki.universal-devices.com/index ... r_Messages -140002 = HTTP_CLIENT_CONNECTION_TIMED_OUT . This means that ISY is not even getting to the HTTP protocol part since it cannot even connect to the given IP/Port. Is the machine which you run curl on the same network as ISY? With kind regards, Michel
  17. Hi NNilsen, Unfortunately not plans. May I humbly ask why not use Z-Wave versions of the same thermostat? With kind regards, Michel
  18. Hi Noel, Thanks so very much for the update and we'll review the Wiki. With kind regards, Michel
  19. Hi Phil, We do have plans to include such features in our 5.0 framework next year. With kind regards, Michel
  20. Hi chago2013, They come from WeatherBug. i.e. The dashboard goes to WeatherBug and gets and displays them. This is unlike all other WB features that come from ISY. i.e. ISY goes to WeatherBug, collects information, and then uses them in programs. In short, there's no hook between what's in the dashboard and what's in ISY. With kind regards, Michel
  21. Hi chago2013, Thanks so very much for the details. Before we do any more labeling, we will have to talk to SmartHome and make sure their API documentation is accurate. If you don't mind, please send the screenshots of ISY/HL in addition to Event Viewer/Level 3 for the following two scenarios to support@universal-devices.com. HL: Latching = ON, 3 Way = OFF; ISY: Latching = OFF, Single = OFF, 3 Way = ON HL: Latching = ON, 3 Way = ON; ISY: Latching = OFF, Single = OFF, 3 Way = OFF Thanks again and with kind regards, Michel
  22. Yes. It has nothing to do with ISY. With kind regards, Michel
  23. Hi chago2013, Thanks so very much for the details. Indeed appreciated. I tested again and looked at their API documentation and I must say that I think in this case either HL is wrong or the API docs are wrong. As I mentioned in the previous post, those bits are set properly except for Single vs. Dual. So, the question is: should we use what HL says or what the API docs say? Thanks again for your time. With kind regards, Michel
  24. Hi chago2013, The forecasts are pulled directly from the UI and are not included in ISY. 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.