Jimbo.Automates

@MWareman has created some good info about using tasker on the wiki, one of them is https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Tasker

Yes, but it currently requires another computer, like a Raspberry Pi running Polyglot: and the camera nodeserver

Just get Tinycam Pro, works with every possible camera you may ever get. Sent from my Pixel 2 XL using Tapatalk

I saw the announcement and tried in mine Saturday but guess I didn't have the update yet. Hopefully will have it when I get home tomorrow! Sent from my Pixel 2 XL using Tapatalk

Sending sound to GH is pretty easy, but it interrupts any music playing and it doesn't continue. There is an assistant-relay nodejs server on GitHub that is supposed to handle it as broadcast which works properly, but I haven't tried it yet.

But when I right click "ISY" and select "Query" it did update the On Level. And that seems to be what my Query All program does, so I'm confused Although, nothing is happening when I run then on my query all, so I'm even more confused.

But when I right click "ISY" and select "Query" it looked like it updated the On Level for all devices? Isn't that the same thing the Query All program does?

Michel, But, as I said, running the Query All did nothing, I edited the program saved it and still it won't Run Then? The Query doesn't happen, I have to run manually. I open the AC and the device "On Level" is blank, so I right click the device and "On Level" goes to 100%. Then GH will properly turn on the device. So I manually ran Query on ISY and now all my "On Level"s and "Ramp Rates" are correct. - Jim

I try to manually run the Query All -> Then and nothing happens? I manually Query the "ISY" and it works. I am running 5.0.13A.

So in the admin console all my devices show blank on level. I had query on restart disabled since installing the new zwave module, but the 3am query all should have fixed it. The program ran this morning so no idea why all the device levels are blank. Sent from my Pixel 2 XL using Tapatalk

Thanks Michel, screenshot attached Sent from my Pixel 2 XL using Tapatalk

Looks like I jinxed myself, I replied to another thread yesterday saying my Google Home's have been working great. Now when I ask to turn on a light, it says the light is being turned on, but nothing happens. If I ask to turn on the same light to 100% it works. Everything that is defined as a switch works fine, it's only lights. Anyone else see this issue or know how to resolve? Sent from my Pixel 2 XL using Tapatalk

My 7 Google homes have been working for a long time, can't remember the last time I got an error, or needed to unlink. I use them for HA a few times every day. Sent from my Pixel 2 XL using Tapatalk

Installed and everything seems to be working fine, have not run a heal, @Michel Kohanim Please let me know if you would like me to run the heal.

Not sure if that reply was meant for me, if so, thanks but I have a pretty robust zwave mesh. Only wondering about best orientation and if a heal should ever be run. Sent from my Pixel 2 XL using Tapatalk

I went out of town the day I received mine, and will finally have time tomorrow to install it. There are a lot of posts to try and surmise. So do the procedure as described in the OP, but don't do the heal. Should a heal ever be run? Orientation of the ISY should be vertical for best coverage, doesn't matter which side is up? Anything else I didn't catch or remember? Sent from my Pixel 2 XL using Tapatalk

Yes, I agree, and it gets more complicated because the motion sensor on these have different states where it detects door opening and closing based on the angle of the device.

Now that the hints are available in 5.0.13A how would I categorize a node that does temperature and motion like the wireless tags? Probably should have made them separate nodes, but didn't want to since I wanted to group them under the hub.

Duh, that was too obvious to see! [emoji3] There are 3 different ones showing in my error log back to 3/10, do I have to delete and re-add them? Or should I try a new sdcard as mentioned? Sent from my Pixel 2 XL using Tapatalk

I'm getting a few of these, never noticed them before but 5.0.13 gives me a popup every time I connect. How do I know which device they come from?

If your provider has a way to send as mms instead of sms it will be delivered as one message. Sent from my Pixel 2 XL using Tapatalk

Have you checked in the GH app My Activity to see that it's hearing what you are saying properly? I use the sync in the portal with no problem. Sent from my Pixel 2 XL using Tapatalk

I don't have this issue either. GH understands Kitchen Table, Kitchen Cans, and Kitchen Island when I address them all individually, or I can say kitchen lights and all turn on. They are all devices in GH so brightness levels can also be controlled. A few weeks ago it would no longer turn on "Jim's lamp" and others on the forum reported similar issues but that started working again recently. Sent from my Pixel 2 XL using Tapatalk

@bmercier or anyone else, Is there a way to define nodes for Alexa A/V device mapping so you can put the nodes in instead of programs or variables like I see everyone doing? I don't use Alexa anymore, but would be nice to make that work properly, and hopefully will work with Google home soon. Just wondering if we can define nodeserver nodes in a way that they can be added directly?

You are welcome, it is a little confusing and I forget some of the details, but describing them here helped to cement it in my brain, until it changes again. Yes, the rooms thing is annoying and made this list: https://www.androidpolice.com/2018/03/14/10-stupidly-simple-things-wish-google-home/ I really hope that gets fixed soon, I think @bmercier mentioned room support between GH and the Portal was coming sometime?