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.

xlurkr

Members
  • Joined

  • Last visited

Everything posted by xlurkr

  1. Revisiting in a rare moment of spare time. I currently have an Insteon open/close sensor on the entryway closet door triggering an Insteon Appliancelinc with nothing plugged into it, and its state triggers a Google Home routine that turns on/off the entryway light that is controlled by the SmartRent app via Z-Wave. It's working about as well as you'd expect - like dog poo. Has anyone found a good, cheap sensor for triggering open/close events for use in Google Home routines, or even better, found a way to trigger Google Home routines with Insteon sensors? -Tom
  2. Last night I finished the training for RA3 and downloaded the Designer software. Sure enough, it still lacks sophisticated logic programming. -Tom
  3. I can imagine an installer would typically propose this, if most or all of the gear in place is compatible with the RA3 processor. But you could probably also insist on the installer only adding new ClearConnect Type X devices (if any) to the RA3 processor. I'm not sure that would buy you anything, though, if you want to automate it all with a single solution. btw, I don't have any experience with the RA3 processor or the software to program on it, so everything I'm saying with any certainty pertains to RA2, its repeater, and Inclusive software. -Tom
  4. Lutron's software offers few options for automation. They have timeclocks and vacation/holiday modes and motion sensors and garage opener controllers, but that's about it. That's why everybody controls it with another hub or software solution, or at least voice assistants, which increasingly have their own automation. -Tom
  5. I'd bet that Home Assistant can also support multiple Lutron repeaters, just like Hubitat can. If so, you could support your existing RA2 (even beyond 200; that limit is for two (max) repeaters in the Lutron software) and add everything new as RA3. -Tom
  6. I'm not a pro, but I do have a suggestion. If you want a good DIY solution for controlling your Lutron lighting, I can heartily recommend adding a Hubitat hub. It's only about $150, has no mandatory recurring fees, and can be 100% local after setup if you want. A couple of its developers have DIY Lutron RA2 lighting in their own houses, so they've added a lot of great functionality for it. And there's a nodeserver for Hubitat that will allow you to bring everything into ISY as nodes, so you can automate things the way you're used to. The Hubitat can also support multiple hubs and can therefore mix and match RA2 and Caseta devices. The only caveat is that Hubitat, like most smaller players, doesn't have access to the LEAP security in the new RA3 hub. Some others do, like Home Assistant, but I think it's based on a reverse-engineering of LEAP that could break at some point? Not sure. -Tom
  7. xlurkr replied to Don's topic in ZMatter
    I have a really old dimmer and a really old thermostat and neither work. Just letting you know you're not alone. I would bet most newer devices do work, but I don't own any. -Tom
  8. This is my observation, too. ElkRP blocks, but multiple simultaneous connections from other apps are possible. I've got the NS and HA connected atm. -Tom
  9. vbPhil showed the safest way (which I did not know about. Thanks!) The way I do it is to ssh in and run uname -a My Polisy Pro is still at 13.1 Which is another not great thing that I documented earlier. When I attempted the update for the second and third times I got a message informing me that it was going to update FreeBSD from 13.1 to 13.2, which Michel had earlier stated had been backed out of the update for the Polisy. That both confused and scared me. All is OK now though. -Tom
  10. Last night. And someone can correct me if I'm wrong, but you shouldn't need to clear the cache before upgrading. You need to do so afterwards and load the latest AC, which has been well documented before. I did that, but still had lots of problems. I think the second power cycle is what made the difference for me, but we'll never know for sure. -Tom
  11. Just got home. Cleared the Java cache, downloaded and launched start, launched the AC, and all is good on my Polisy Pro 5.7.0 -Tom
  12. Do you mean do it again? I did it once, at the beginning of this saga. The AC I launch now says it's 5.70, as does my firmware. -Tom
  13. I hope I'm not out of line for posting this, but I'd advise Polisy owners to wait. The first time I tried it yesterday I got something similar to what's described above: it said the version was still 5.64. And after the Jave cache clearing it dished up an AC that wouldn't connect, because it was newer than the firmware version - a first for me. I tried again, and this time it told me it was going to update FreeBSD, and it would take a long time - which probably wasn't really going to happen, based on Michel's earlier post. But what it did do was return with an infinitely repeating "Initializing" gauge (I forget the exact wording). All devices were still present, but none would respond - nor would NS's - and all my programs were missing. I power cycled and kept getting the same behavior. I let it run overnight and saw the same behavior this morning. So I power cycled again this morning, and when I left for work, it appeared to have recovered somewhat based on some programs working and UD Mobile working. I was afraid to launch the AC, but I will when I get home. First time I've ever had a problem this bad with anything UDI. -Tom
  14. xlurkr replied to pkauf's topic in ZMatter
    I know one that doesn't work: GE/Jasco 45852. I'd report this in a thread for non-working Zigbee devices, but I don't think there is one. If I cared enough about making it work, I'd log a ticket. -Tom
  15. Rebooting did it. Thanks @Geddy! Doesn't recognize my GE Zigbee plugin dimmer, though. More troubleshooting ahead. -Tom
  16. OK, I'll try the power cycle. I forgot to mention that Z-Wave is still working, and I've never had a problem with it. -Tom
  17. Anyone know how to fix this? Polisy with an internal ZMatter board. -Tom
  18. I got it to work by swapping the two on/off modules. Now I have an Insteon open/close sensor triggering the "hubitat" "outlet", which has nothing plugged into it. Its state triggers, in Google Home, the light I want to have come on when I open the coat closet door. The "phantom" module is now located where the "hubitat" one was (it is used to power cycle my Hubitat in emergencies). I'd still like to understand why I can't seem to add anything new and have it show up as a trigger. Some day I might need to. -Tom
  19. Someone please help me make sense of this. As the pics show, I have two outlets linked to Google Home. Both of them show up as devices in Google Home. Only one of them is selectable as a trigger for an automation why???? -Tom
  20. Maybe a bigger problem is that I can't get the dimmer module to show up as a trigger. It's weird, because I also have an on/off module (that I actually use for something) and it DOES show up as a trigger. I'll try to add another on/off module next. -Tom
  21. @bmercier I'm really frustrated with this integration. It occurred to me that if I can't get a sensor to show up as a trigger, maybe I can use an open/close sensor to turn on a device and use the device as a trigger. But I can't get Google Home to reflect the correct on/off state of a dimmer module I installed just to be the "statekeeper", unless Google Home changes its state. Is this how it's supposed to work? Isn't the ISY supposed to tell Google Home whenever a device changes state, no matter how it happened? I have tried unlinking and relinking UDI to Google Home several times, with no change. Please help me. -Tom
  22. xlurkr replied to Don's topic in ZMatter
    @PatPendLet's work together to get @bpwwerto port the Hubitat NS to PG3, and support it going forward. He has ported a couple of ST's PG2 NS's already, I think. I just bought the new C-8 so I have an older C-7 I could send him to develop with. -Tom
  23. xlurkr replied to Don's topic in ZMatter
    @PatPendAre you using the ST-Hubitat NS for PG 2.0? That's what I'm using now for RA2, and I'm concerned it may not be a good long-term solution. We can take this to IM or another thread if this is considered drift. But since it's a possible "right now" solution for Zigbee, I feel like it's still on topic. -Tom
  24. Nothing, other than return here and update if you find a way to make it work. Thanks for trying. This isn't urgent, merely frustrating. And I could use Alexa; I have plenty of those devices around. I just chose to go with Alexa in my permanent home and GH in my temporary work home. For variety. And apparently, frustration. -Tom
  25. You guys are torturing me with your success stories with Alexa. -Tom

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.