MWareman

The filter is grayed out. I’ve searched for other iPhone only apps and can find those, so I’m not sure that’s the issue...

I mostly authored the wiki article, so tried most. I settled on Pushover. Multi platform, you can push URLs and do high priority pushes (keep alerting until the phone owner acknowledges). Each event has its own app and icon. And I use groups so a single push can be sent to all family members (for alarm conditions).

One quick question... Does it support ISY Portal? I get no results searching the AppStore on my iPad for ‘hometap’

Insteon devices only send status to one configured PLM. That PLM can be connected to ISY, or it can be the PLM in the Hub. Status cannot be sent to both. This is intrinsic to Insteon. X10 does not have this limitation (because status feedback is an afterthought) nor does zwave (where most devices are ‘controllers’). Get ISY Portal and ditch the hub. IMHO - it’s an either/or choice between the Hub and ISY. Integrating both is an advanced thing. On Q3 - Mobilinc on IOS or Agave on Android are the recommended mobile apps. You can also use a browser shortcut to the Portal in a pinch.

If your ISY has the IP 192.168.1.2 with the subnet mask 255.255.255.0 - it will not be able to talk to a device with the IP 192.168.0.3 - because it’s a different subnet. You must fix the third octet in the IP address to match if you want the devices to talk to each other.

I invested in a managed switch, and have a separate IOT vlan (and SSID). I can apply firewall ACLs to each port... So, my Foscams, Weatherflow Hub, CAO Hubs, Google Homes, FireTVs, Chamberlain controller and Ring cameras are all on a separate network firewalled from my NAS - and firewalled from each other if possible. The IOT ssid is also configured to prevent devices from talking directly to each other (they have to hairpin thru the switch, where ACLs are applied). Combined, if any are ever compromised the attacker cannot get to my data or to other IOT devices. My guest network is completely separate from my IOT and internal network. Simple NAT outbound. I use a coupon system for guest access - each coupon grants two hours access. Added to that, I strictly filter egress for all networks. I use split zone DNS - my internal DNS zone is not accessible from the IOT or Guest networks. For outbound DNS (all networks) - I’m using 9.9.9.9. This is backed by IBMs threat intel database to block most malware callbacks. I can not recommend this enough! It takes time to maintain it though. Worth it to me, since I’m in IT Security professionally and it sure would be embarrassing if my home got compromised. One thing that surprised me, Google Homes ignore the dns DHCP option and forcibly use Google DNS. They didn’t work originally because I was blocking outbound. I try to be surgical with what I allow out, which usually means devices don’t work until I figure out their outbound comm needs and configure my network to allow it - or implement hacks to allow it to work.

Thanks Benoit!

Please can you state what 'ISY Cat' shows in the ISY Portal for the device? I've tested the correct setup (ISY Dimmable Device exposed to Google Home as a 'Light') - and it still does not work. So, I believe that there is an issue in the interaction between Google Home and ISY Portal. However, I do want to ensure you are trying to dim a device and not a scene...

As I mentioned - I usually just assign spokens to Scenes - so I've never expected those to be dimmable... I do know that dimming used to work with discrete devices though. Just to test, I created a test device - linked to a device (not a scene) and pushed to Google Home as a light. I could turn it on or off - but could not get any dim commands to work. Something is definitely borked in the API interaction... I either get 'Sorry, I'm not sure how to help with that' or 'It looks like that device hasn't been setup yet'... Michael.

What does the ISY Portal list the ‘ISY Cat’ as? In my case, all are ‘Scene’ - and my ‘GH Cat’ is ‘Device\Light’. I cannot dim anything, but that’s expected since ISY Scenes are not dimmable via direct dim commands.

I believe switch can only be turned on or off. It needs to be light. What is the ISY Cat?

Do you have the spoken assigned to a device, or a scene? In the portal - is the device exposed to Google as a light, or a scene?

ISY can send most network requests (only exception is some authentication methods, like digest and oAuth). The main question is - do you have an example network call that achieves what you desire that we can use to build the ISY network resource? Once there is an example we will be able to help ‘translate’ to a format for ISY (assuming it does not need one of the authentication methods not supported).

Thanks Benoit. I do have several user accounts - but in my case I’m using only the same Google and Portal account each time (just yesterday, after the issue, I added a Google Home for my Daughter using her own Google and Portal account so as to not confuse them). I’ll keep an eye out to see if I comes up again. Michael.

I disconnected Home from Portal and re-linked. Then I was able to push again. It kind of defeats the purpose if we have to disconnect and rejoin each time the Portal is upgraded though. Is this going to be a common thing? I's a real pain to go thru and re-assign rooms in the Home app each time (though this would be *much* better if you are able to send room info as well.... )

It seems I cannot 'Send spokens' anymore to my Home devices. I get 'Error contacting the Google HomeGraph API.'. I wonder if others are seeing this - or if it's just me...

5.x is alpha - not complete yet. That being said - do you remove and re-add the device since you upgraded? 5.0.11 should support multi-channel in a generic way at least...

I’ve just purchased more of the Aeotec gen5 units. I like logging the temp and humidity as a bonus to motion detection. They are slowly replacing my CAO tags in strategic locations...

Merry Christmas!

Probably just the icon in the app...

You’ll need the network module to do that. Also, make sure you use the real IP of the ISY (rather than 127.0.0.1). There is a issue in ISY that will cause a hard lock if you use the network module to connect to 127.0.0.1.

Likely the icon thats displayed in the Alexa app.... Also, a ‘light’ will accept dim commands, as well as the ability to be queried for status. Other device types do not support this. If you declare an ISY scene as a ‘light’ the dim and status commands will be ignored. (I think switch and outlet can be queried as well, it’s just scene that cannot....)

Thanks! Appreciate it... looking forward to the functionality...

Merry Christmas! (Also, what is the purpose to exposing a Google Home scene/device/program as an Alexa scene - or is the Alexa mention a typo...?)

The Portals username is your email address. It’s not possible to have email addresses without @. Better to have the bug fixed... or try url encoding the @ with %40