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.

lilyoyo1

Members
  • Joined

  • Last visited

Everything posted by lilyoyo1

  1. lilyoyo1 replied to jkraus's topic in Polisy
    Did you close the admin console and reopen it?
  2. This is why I prefer setting different scenes for each speed vs 1 scene for all speeds. If the speeds are separate scenes, you'd be be able to accomplish what you want to do
  3. The final nail was when insteon shut down....no more products
  4. If you are certain that you set the ramp rate for the devices outside of the scene at .5 and within the scene itself for each controller, I would make sure that your firmware and UI matches to ensure there is nothing funky there preventing the system from working properly
  5. Just the Isy as far as I know.
  6. This is what Michel said once. Sudo pkg delete isy Sudo pkg install isy
  7. It's impossible to future proof yourself as new standards are always being developed. 800 was recently announced and at some point 900 will be announced followed by 1000 series and so forth. The best way to semi future proof yourself would be to buy the latest series devices available and use them with your particular controller. Ditto when upgrading your controller. Should 800 series controller be available a few years from now when you decide to upgrade them you would get that so it's ready for whatever 800 series devices you may add later. All series work together. You just don't get the benefits of the higher series such as longer range of using a lower series controller. If you Google benefits of whatever series, you'll see the only talk about specific zwave capabilities not device specific features. This is because each series change improves zwave communication in itself, not necessarily the individual device features. With that said, once youve established a strong mesh in your home, most of the benefits of a higher series becomes moot since you would have reached network density. Newer devices are faster in generally due to newer processors and other improvements but ultimately the gains in speed isn't enough to warrant ripping everything out and starting over every time a new series comes out. If i had a house full of older 300 series from 10 years ago, I'd probably be willing to do that but not from 500 to 700 series. Zwave is like smartphones. They come out with something new often but the gains are incremental with the times. Will you notice a difference between a galaxy s21 vs a 22. Probably. But is it enough to drop 1k on that new one? Probably not!
  8. Zwave doesn't really have a classification for keypads (that I'm aware of) which means it'll be on the mfg. to design around that limitation. Since it's a race to the bottom in regards to pricing, most probably do not attempt since that means it'll cost them to make it happen for a device that will be limited to a few devices that support it (along with the support calls that'll follow). Keep in mind, most of these devices are geared towards small (less than 10) installations vs whole home automation. While we might be a passionate community that's being left out of in their minds, we are a small minority vs the greater community
  9. It's possible....Apple did win a billion dollar case against Samsung for having a rectangular phone with rounded corners (later overturned)
  10. Are you using polisy? What firmware are you using for that and pg3? You probably should create a separate post for this since the op that started this post meant it as a guide for new users and not necessarily for trpubleshooting
  11. The hub is not compatible with polisy not the isy
  12. I agree with you in regards to installer and prosumer diy homes. Your sentiments are part of the many reasons why I can't fully get on board with zwave. When you talk about basic systems such as smart things and qolsys alarm panels, people are generally looking for basic control of their devices. What we do here with the Isy and other automation controllers do expose the shortcomings of zwave that other basic systems do not. In that regards, zwave works perfect.
  13. He said in his original message he only has zwave. @Valveman clear your Java cache and make sure you use the launcher. Do you have the 300 board (has light in back of Isy) or 500 board (no light). If you have the 500 board, upgrade to 5.3.4
  14. I do the same thing in my bathrooms except they're controlled by a motion sensor. The brightness and ramp rates change depending on the time. At night, its just enough to see to use the bathroom and early morning, its a slower ramp rate on so your eyes can adjust
  15. I don't think so. If it sits for 4 years, why would someone bother resurrecting it? Old users would've moved on by then and new users would have no reason to try it. There just isn't a market for maintenance devices.
  16. lilyoyo1 replied to jkraus's topic in Polisy
    From my experience, if you invest in building a strong mesh throughout your home, zwave doesn't have RF coverage issues. As Geddy stated earlier, depending on your wifi you can potentially have issues as you expand. If that's what you want to use, I'd say go for it
  17. I think they started in 06 so it would be 2026 if that's the case. If that's so, it'll probably depress the value even more since there's only a limited amount of time to capitalize off it and make your money back (either through product or licensing fees. The way I see things, the longer it takes to sell, the less its worth since any buyer is unlikely to recoup their costs
  18. Since you want to create a debate when it has already been clearly established that use of the insteon signal by an unauthorized person would be illegal, i will clarify my statement for you. Any device that has programming ability such as the isy and the multitude of other controllers out there (since none on the market outside of insteon designed hubs has a PLM built in), does not infringe on any patents.
  19. lilyoyo1 replied to jkraus's topic in Polisy
    There's your answer. If you go down the Node server lists, you'll see all currently compatible systems. You would just pick a bulb from one of those
  20. You're splitting hairs. A controller by itself doesn't infringe on their patents. The isy, polisy, homeseer, HA, indigo, etc. are all controllers. In fact insteon provides the commands so that you can use your own software to control insteon devices. A controller would infringe on their patents if they copied the PLM or created their own device built into the controller that sends out the insteon signal directly.
  21. What's the UI? How many devices do you have, what are they, and which ones are you having issues with
  22. As long as it's being actively sold by UDI, I see them updating the 994 though not as often as polisy or with the biggest potential updates which could possibly bog it down. It's worth requesting though. Even if it doesn't happen with the 994, maybe it will with polisy. That way should you upgrade in the future, you'll have what you're looking for
  23. Yes. The same as its always been with the ISYs. You just dont want to pull the plug during a firmware update. You should however try to do a proper shutdown should you need to do so using the system system mechanisms outlined in the posts below
  24. all links reside in the devices so things will continue to work without a controller. Its recommended to factory reset your devices prior to setting up with a new controller to avoid half links and unintended behavior down the road.

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.