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.

upstatemike

Members
  • Joined

  • Last visited

Everything posted by upstatemike

  1. I don't currently have a need to go to PG3 and a lot to lose if my current configuration gets messed up. My architecture consists of multiple controllers (Polisy, Homeseer, Hubitat, Home Assistant, Alexa Routines, Stargate Events, Yolink Rules, Elk Rules, etc.) plus multiple Technology Bridges/Services (Hue, Lutron, Alexa Voice Input, ISY994 Insteon, Weatherflow, Yolink LoRa, Elk M1, Nest Thermostats, etc.) and because I am very audio/TTS centric I have multiple announcement sources (Multiple Homeseer speaker clients, Elk voice output, Stargate voice output, Alexa announcements, Yolink voice hub, Hubitat via Sonos, Home Assistant via Sonos, etc.) Because many controllers will access the same Technology Bridge at the same time I am reluctant to change a bridge because then I have to reconfigure the integration on all affected controllers. I will need a strong reason to move from the ISY994 to IoP because it would affect not just Polisy but also my Elk integration, Homeseer integration, Home Assistant integration, Alexa integration, etc. Effort vs benefit just isn't there yet.
  2. Not that complicated. I hit update and it did. Checked for additional updates and none were found. Removed the Lifx Node Server that I no longer use. Updated the Hue Node Server to reflect extensive changes there. Not doing much with the Sonos and Weatherflow Node Servers at the moment so ignoring those. No plans to use Z-Wave. The other main thing I use is Elk motion sensors but they communicate directly with the ISY994 so not affected by Polisy. I think I am good to go.
  3. It says version 2.2.8. It says there is a 2.2.11 available, is that what you mean?
  4. OK that worked! It told me it was not a secure connection but let me proceed. Don't know why it refused http if it is not secure but whatever. Thanks for the help... I'll write it down so I don't forget again.
  5. No, I'm trying to get to the PG2 GUI where you start and stop Node Servers etc. I am running a few Node Servers for Hue, Lifx, and so on but not using IoP as I still use an ISY994.
  6. Yes the light is correct. I have verified that Polisy is actually at the expected address. Ping responds fine.
  7. I'm not using IoP. I'm just trying to log into Polisy.
  8. This also gives me Connection Refused
  9. Thanks but using port 3000 still gives me connection refused
  10. I haven't needed to log into Polisy for awhile and now I can't recall how to do it. I looked at the Wiki and it said to add Polisy to ISY finder: This results in I tried replacing "policy" with the actual IP address and get the same response. The IP address is reserved and shows as online and active in my router. I tried entering https://192.168.0.10:8443/desc in my browser and get "connection refused". I know my brain function is rapidly deteriorating but I used to know how to do this... What am I forgetting?
  11. He said they had set up a refurbishing program for hubs and are looking at doing the same for PLMs. Overall a fairly positive call with the promise of some products coming available again pretty soon (days or weeks rather than months).
  12. Did anybody get into this? Sounds like ISY was discussed quite a bit during the session.
  13. Maybe they didn't get enough hub subscriptions to stay viable until they had products to sell.
  14. Just an update to my own post. I completed the transition back to Insteon and the result is better than I expected. Everything is configured the way I want (not even possible with Z-Wave) and it just works. Everything is link based so it will keep on working even if my ISY goes offline for some reason. This is what I expect from a lighting system. Hopefully Matter will do as well in this regard.
  15. I didn't mean Matter will fix Z-Wave (I am convinced now that it is unfixable). I am just saying Matter will not have the same problems that Z-Wave has. Matter switches and keypad buttons will all work as controllers regardless of manufacturer. You will be able to backup a controller from one manufacturer and restore it to a controller from another manufacturer. Direct association will work as expected between all devices and all buttons on keypad devices regardless of what mix of manufacturers you are using. There will be no popcorn effect when controlling groups of devices. Latency will be imperceptible under all conditions. Etc. etc.
  16. Looking forward to Matter to solve this kind of nonsense.
  17. Even if the Nokia hubs were available the initial quantity produced must have been small so it doesn't sound like it would be a sustainable solution in any case.
  18. So there are instuctions for fixing bad PLMs but is there a DIY way to upgrade them? Besides caps I am thinking overclocking, added RAM, tweak the power supply to broadcast a stronger signal, etc.
  19. Hopefully the PLM Pro will be an Insteon device similiar to what the XTB-II was for X-10 http://jvde.us/xtb/xtb-iir.pdf
  20. Is Hub Pro the same as PLM Pro? We don't really need a hub, just an updated PLM.
  21. Z-Wave is widely available but so are Caseta and Hue... neither of which waste my time the way Z-Wave does. And Insteon is still working for me with plenty of second-hand stuff around so I'll probably continue to criticize Z-Wave (and Matter for that matter) in the hopes they will improve/introduce better products as a result.
  22. Just one of the reasons I love Z-Wave so much!

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.