xlurkr

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

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

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

@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

@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

@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

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

You guys are torturing me with your success stories with Alexa. -Tom

Thanks for trying to help out Geddy. It's a Polisy I have. I don't think adding a Z-Wave MS to it would help, because the problem is in getting UDI's Google Home integration to allow me to identify a node as a sensor and having Google Home recognize that and allow me to use it to set up the trigger. It doesn't matter what protocol is used in connecting the device to the Polisy. I can't use a motion-controlled light because the light is outside the closet, in the entryway, and I only want to have it go on when I open the closet door, but also want to control it normally from the switch. I could do that with a MS inside the closet, or an open/close sensor, which I'd prefer. Google added the trigger capability in November of last year, so old posts aren't relevant. I've attached the device categories for the Google Home integration. None of them cause the device to show up as something that can trigger a routine, as far as I can tell. The "open/close" one allows you to control it with those words - like a shade, for example. But when I chose that for my sensor, its state didn't change in GH when I opened and closed the door. Without changing state, it can't act as a trigger. I guess I'm the only UDI customer who uses GH integration. Guess I'd better not say that too loud, or they'll deprecate it.🤐 -Tom

I have never seen Google be so unhelpful about...Google. I can't find a list of devices that are supported in Google Home as triggers for routines, nor even any useful individuals reporting how they got a sensor to work as a trigger. The closest thing, apparently, is someone reporting the use of Hue motion sensors. Great. I don't want to buy yet another motion sensor. I don't even want to use an MS - I want to use an Insteon open/close, door/window, whatever you want to call it. Can no one help me? @bmercier, where are you? -Tom

Yes, I'm aware. But it's the only information that a Google search for "Insteon motion sensor google home" returned. I took it as a sign that maybe it's impossible. or too hard, or not worth it, or something, to support these devices as triggers for routines in Google Home. As an aside, I also have Lutron occupancy sensors, and they don't support them as devices in Google Home through their Connect Bridge either, as far as I have been able to determine. Maybe it's time to tag someone like @bmercier. -Tom

Is it possible this isn't possible? The Insteon website says MS and open/close sensors aren't supported in their Google Home integration for their hub. But Google says motions are supported. Depends on the service's implementation? -Tom

Could one of you smart people walk me through how to set up a Google Home routine to be triggered off an Insteon sensor? I have everything set up for voice control in Google Home, but now I want to have a light come on when my entryway closet is opened. It has no light, and the entryway light (Z-Wave) is controlled by another service (SmartRent - I live in an apartment and can't change the switch). So I want to install either an Insteon open/close sensor (preferred) or motion sensor and have its state trigger a Google Home routine that turns on the SmartRent light and turns it off when the door closes or the motion times out. It doesn't seem like the portal Google integration lets you designate a node as a sensor type. Using an Insteon open/close sensor, I've tried "switch" and "open/close", but neither seems to create a Google Home device that has its state change when I trigger the sensor - though it does change state in the AC, so I know it's working. Please help. -Tom

I haven't moved to your nodeserver yet, but I might in the future. These nodes you currently create: would they allow one to control X10 devices set up on the Elk? This is something I'd like to be able to do, since X10 support is falling away at UDI and Insteon.

That's singularly good performance. -Tom

I'm not a programmer, but it seems to me that if you think of eisy/Polisy as an appliance (once set up), and focus on the software interfaces it provides, its OS becomes largely irrelevant. If you want to program a Pi in Linux to do something with the devices that are controlled by your eisy/Polisy, you are more than welcome to. And if you set up your networking right, it should be nearly as fast as if it were all running in the same box. -Tom

Agree. Twice now I've had to use SSH and sudo to get up to date, when I wouldn't have had to if I'd been installing every update as it became available. But pick your poison. I have no doubt both Polisy and eisy will reach a state where you can skip updates most of the time if you don't need the fixed functionality, like the 994i did.

I have a vague recollection of trying this myself years ago, and you're right, those buttons can't do anything except control the Insteon devices linked to that remote. No programming. -Tom

Not helium - Helium. And no, it's not all mine. I think I'll take a pass. -Tom

Thanks to your post, I'm now aware of the existence of Helium mining. Just when I thought life couldn't get any weirder... -Tom

@Geddy: Just deleted the .state file, and that half fixed the problem. My Polisy, like your eisy, isn't automatically found. And I guess you can't tell me why, b/c if you knew how to make it work you'd be able to find your eisy automatically. I will start another thread asking for help with automatic finding. -Tom

Allow me to commit a minor hijack. Can someone explain to me how the entries in the Finder get automatically populated, and how to troubleshoot issues with that process? I just replaced my old Policy with a newer one. When I launch the Finder, it stays empty for about 10 seconds, and then a lone entry shows up - the old Policy, which is no longer powered up (or connected to the network, obviously). I have added the new one three or four times, and after the last time I finally saved the configuration. But I have to load it every time. How can I get back to the days of yore, when my 994i was always automatically found every time, and no ghosts of UDI past haunted me? Are the entries cached somewhere? Is my router blocking some necessary snooping protocol? Is there a box I need to check in the AC? -Tom

I'm going to give a shout out to ee. I use the arrow keys to navigate and can always see what I'm doing. I use it to put a # in front of things I want to hide, or change one letter or number at a time. -Tom (clearly not a developer)

I'd be careful recommending this. Note how old that post is. I did just a little googling recently and found a lot of more recent posts lamenting the poor support for HA on FreeBSD. Not claiming I'm an expert, though. -Tom

Same