James Peterson

I use the "rooms" in google home to say for example "turn on the "kitchen" lights" . and it will turn on all the lights I have in the kitchen.

I have not experimented like this, but have you assigned the GH to a room and then assigned the lights to same room?

I can not be sure, but this sounds like something that may have been discussed before. It may have something to do with the stored temp preference. You may have to remove and re-add the device to the ISY portal setup.

Thanks. Working now. Sent from my Nexus 5X using Tapatalk

For me, I have tried switch and light. No change. Sent from my Nexus 5X using Tapatalk

I am having the same issue right now. on/off work just fine, just can't dime any lights via google home.

The only response I get for a dim level is "It looks like that device is not setup yet, go to your google home app to setup devices" arg....!! note: Echo/Alexa works just fine.

I just tried clearing everything out and starting over... no go either... I suck

no work that way either... ???

Standard 2477d switch. Tried on all my switches . Nothing. I must have it setup wrong. Sent from my Nexus 5X using Tapatalk

I can't seem to get google home to accept this command. The On/Off work just fine. Any suggestions?

w00t..w00t!!!! I removed the thermostat and re-added it. Failed. Then I unlinked and relinked the google home account and it seems to be working. CHEERS!

If it will help: here is my node dump of the thermostat: <nodeInfo> <node flag="128" nodeDefId="Thermostat"> <address>11 93 4F 1</address> <name>hvac - Main</name> <type>5.3.146.0</type> <enabled>true</enabled> <deviceClass>1</deviceClass> <wattage>1000</wattage> <dcPeriod>60</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>11 93 4F 1</pnode> <ELK_ID>A07</ELK_ID> <property id="ST" value="146" formatted="73.0°" uom="101"/> <property id="CLIMD" value="1" formatted="Heat" uom="98"/> <property id="CLISPC" value="152" formatted="76.0°" uom="101"/> <property id="CLISPH" value="143" formatted="71.5°" uom="101"/> <property id="CLIHUM" value="0" formatted="0%" uom="22"/> </node> <properties> <property id="CLIFS" value="7" formatted="On" uom="99"/> <property id="CLIHCS" value="0" formatted="Idle" uom="66"/> <property id="CLIHUM" value="0" formatted="0%" uom="22"/> <property id="CLIMD" value="1" formatted="Heat" uom="98"/> <property id="CLISPC" value="152" formatted="76.0°" uom="101"/> <property id="CLISPH" value="143" formatted="71.5°" uom="101"/> <property id="ST" value="146" formatted="73.0°" uom="101"/> </properties> </nodeInfo>

Tried. No go. Sent from my Nexus 5X using Tapatalk

One issue also could be that I am not using a Google Home. I am attempting to use it through Google Assistant. trying now.

I made a small test to set the temp using celcius. It made my thermostat read error. Attached photos. You can see that I set my thermostat to a celcius degree and put in an error state. I think you may need to add a preferred unit option somewhere that the portal can read so that it can send the appropriate values back to the devices. Sent from my Nexus 5X using Tapatalk

A little better but still issues. Attached images. Appears to be a unit conversion issue. Sent from my Nexus 5X using Tapatalk

I keep getting an error when attempting to control our thermostat. I have verified it is in Google home control and have even unlinked and relinked the universal devices account. Any suggestions? Sent from my Nexus 5X using Tapatalk

I do not know about true camera support,but I am thinking about adding an integration where a third party camera viewer can be viewed within agave. There are so many good camera viewers on the market, best to just let them to the heavy lifting. Sent from my Nexus 5X using Tapatalk

Yep. I've done all that before and now. Its a very strange issue. On a special note: If I add an additional port forward bounce in between the router and the ISY it works. ie) Router -> Rpi -> ISY == NUTS!!! Like I said. I think the Router hates my ISY.

Yes. I can access the ISY locally via http and https.

For some reason my ISYs no longer respond via port forward. Everything was fine till about a week ago. I had a problem like this last year but it resolved itself, but honestly this type of issue shouldn't happen. Actual setup: External port 653 : Internal addr:port 10.1.1.154:443 Current setup for testing: External port 81 : Internal addr:port 10.1.1.154:80 . - not working External port 653 : Internal addr:port 10.1.1.154:443 - not working External port 80 : internal Rpi 10.1.1.35:80 - working - I have rotated the forwarded ports with no change to ISY response. ISY responds just fine internally on both HTTP and HTTPS I really think that my router hates my ISYs. Netgear X4S R7800

Great. I have been misinformed for a while then. I always assumed that the ISY skill had to be enabled for Alexa to to the ISY at all. Thx. Sent from my Nexus 5X using Tapatalk

Unfortunately not removing the custom skill negates the security of not having the unlock enabled in the Alexa skill since locks can still be unlocked using the custom skill. Is there anyway to disable the custom skills? Sent from my Nexus 5X using Tapatalk

Good to know. Will the ability to unlock the door be removed from the custom skill?