-
Posts
1222 -
Joined
-
Last visited
Everything posted by James Peterson
-
Can someone help me with getting some information on these? Is the REST command structure similar to the Zwave door locks or standard DON/DOF? Which node to I communicate with (_1 or _2) Trying to debug one with out actually having one.
-
Adding node server node returns HTTP error 400
James Peterson replied to Jimbo.Automates's topic in UD Portal
This is exactly what I would need. If this was implemented support for NS would be easy. Without this, do not see it being possible to implement in a 3rd party app. -
Same here. Been getting this error for about a month now. I have also noticed that some of my spokens are not working correctly when it comes to dimming. for example I have lights in my entertainment room that are "theater lights" Google would not recognize the lights when dimming "OK google set theater lights to 50%" unless I put those lights in a room called "theater" and added a nickname called "lights" . This all started happening about the same time so I just assumed it was related.
-
Yes - Google Assistant -> Menu -> Settings -> Home Control I used it this way before I purchased my Google homes
-
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
- 23 replies
-
- 1
-
-
- Agave
- home automation
-
(and 1 more)
Tagged with:
-
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.