Bumbershoot

Michel, If I understand you properly, devices such as the Ecobee thermostat or the CAO Wireless Sensors, both of which have cloud based API's, would be appropriate candidates for the development of UDI portal node servers? If so, then this nicely extends the idea of the node server, providing a significant extension for the ISY development community, and a clear win for ISY users. Thanks.

I did the exact same thing, and it worked perfectly the first time. It's nice that we don't have to run Polyglot to get these nodes, and it makes me wonder what other other plans UDI might have for incorporating node servers into the portal. I can imagine Polyglot running on the portal servers...

Indeed, there is a Nest node server, built by forum member einstein42. It runs on Polyglot, and allows your ISY to control your Nest and extends your Nest to control other devices on your ISY. I use ISY programs to change the heating/cooling mode when I'm away and return, to stop heating/cooling when a door or window is left open, to start/stop ceiling fans when heating/cooling modes change, etc. A good example use of the occupancy node in the ISY portal would be to use it to adjust your Nest when your home becomes unoccupied or occupied. Node servers are a bit of work to set up, but they'll help to keep your investment in the ISY relevant.

The calibration on mine seems pretty good. Before the Nest, this house had an ancient (1999) Carrier thermostat that varied from the security system temperature sensor by up to four degrees (they're actually about three inches apart, so they're easy to compare). After I installed the Nest, the two almost always agree, and I've never noticed them diverging by more than one degree Fahrenheit. I don't actually know if either one are accurate, just that they agree. Also, and also maybe more importantly, I can't dispute the high WAF score that Nest achieves. It's gorgeous hardware, if nothing else, and the Mrs. like to tell Alexa to, "Set the Family Room to 70". Happy wife, happy life. The Nest was my first venture into HA, and it created a small reservoir of spousal good will for future projects. I agree, it's not a device that completely gets out of the way and lets you tinker. For example, the API doesn't seem to expose a way for me to adjust the settings for my humidifier (that I've discovered, anyway). And yeah, the "learning mode" does me no good at all. All in all, I like it, and the Mrs. loves it. Win.

Wow, you guys work hard at this! I'm kinda lazy, so I let Nodelink running on my Rpi handle the heavy date/time lifting. Thanks io_guy!

I've had this happen a couple of times. Deleting the device from the ISY, air gapping it then re-adding it has resolved the problem. Fortunately, I haven't had this happen to devices that are used in a great number of scenes, programs, etc. If you are able to extract the needed file from the backup.zip, I don't understand how you would get the file back into the ISY's file system, other than with a system restore or through the "Configuration | Networking | Web Server" Tabs, which only exposes "/USER/WEB", not "/CONF", if that's even the correct path. Maybe there's a method using telnet (it looks like there's "List files/directories" command), or some REST command? I couldn't find it, and gave up.

You can also control Sonos using network resources. I find that using the node server to do the ordinary stuff is quite a bit easier to set up than network resources, though the possibilities are more limited. The screenshot shows your options when using the Sonos node server.

Nodelink provides devices, with properties, to the ISY that you can use in programs, scenes, etc. It is similar to Polyglot in usage on the ISY, though Polyglot requires Python and Nodelink requires the mono libraries (on an Rpi). The Nodelink binary is a Windows executable (Nodelink.exe), and the mono libraries provide a Windows run-time environment on Unix variant hosts. IMHO both Polyglot and Nodelink provide similar functionality to the ISY by working with the new Node Server functionality built into the 5.x.x firmware series -- they extend your ISY to interact with devices that the ISY wouldn't otherwise support. You are no longer limited to Insteon devices, Z-Wave devices, ELK devices or devices that you can interact with using network resources. I think it's huge for the ISY to have this, and I also think the work of the Nodelink and Polyglot developers is equally huge in keeping this platform relevant in the HA marketplace. I've attached a screenshot of the node server directory on my ISY. Polyglot provides: Hue, Nest, Sonos, IP Camera and LIFX control. Nodelink provides: RainMachine and ISY Data. Simply having better and precise control of my irrigation (RainMachine) has saved enough money (water's expensive where I live) to pay for at least pieces of my HA habit. The developers of Nodelink and Polyglot are unpaid, as far as I know, other then through voluntary PayPal donations. I hope this helps...

Thanks, I'd never poked around in the Ecobee developer site before. I see that all API calls use: https://api.ecobee.com That's too bad, though it might make their firmware easier to maintain and update. I appreciate the info...

PurdueGuy, I apologize if I'm intruding or suggesting the obvious, but I notice in your signature that you're using running DSCLink on a Rpi. If/when you run ISY firmware > 5.0.4, you would be able to run io_guys Nodelink on your Rpi, allowing local data for both DSC and your Ecobee with one node server. The benefit may be that there's no more reliance on the cloud. I have neither DSC nor Ecobee, so I can't speak as to how well they work, but Nodelink seems rock solid in my Rpi. Edit: added screenshot showing Nodelink supported devices.

The Nest is nice, and it has a high WAF, so I'm happy. Polyglot isn't bad to set up, but you'll need another device to run it on. Currently, I'm running it on an Rpi, but it runs well on my Mac mini. I recommend firmware version 5.0.9 if you're interested in that route. I have no real issues with the Nest at all.

You might want to look here for some information on Insteon thermostat compatibility with your heat pump. The Insteon thermostats that I installed are not on an ISY, but an Insteon Hub. The screenshot shows how a thermostat appears in the iOS Insteon app. Note however that this screenshot is from a thermostat that is in a home with a furnace and air conditioning, not a heat pump. I don't recall if the Insteon thermostat will control a whole home humidifier, though it certainly reports humidity. EDIT: The Insteon thermostat is an RF only device IIRC, so you may need a dual-band Insteon device somewhere in the vicinity.

If you're not averse to running Alpha firmware on your ISY (version > 5.0.4), then there are more options with Nodelink and Polyglot node servers. Running Polyglot, you can directly control Nest thermostats (which I'm using), and with Nodelink you have the ability to control at least three options: Venstar, Ecobee or Honeywell TCC. The Nest (see screenshot of Nest as a Polyglot node) operates just fine for me, and it plays well with Alexa. Were I to replace the Nest, I would likely go with Ecobee (I like the remote sensors) and control it using my ISY and Nodelink. I also installed two Insteon thermostats at a relatives house, and they've been entirely issue free (they've been installed about a year). All that said, I've had no problems at all with my Z-Wave devices, once I established a sufficient Z-Wave mesh. There are loads of Z-Wave thermostats (at least on Amazon), if you're willing to build the network.

I use MobiLinc on iOS and am quite happy with it. Since you're an Andriod user, you might look at Agave, which is written by an active member of this forum. People seem enthusiastic about it.

Oops, 4.5.4 doesn't support decimals in variables, as far as I know. You'll need to do some math on the values prior to sending them to your ISY. Edit: I don't think I changed the original formula for the voltage values in my app, which needs a variable precision of three. You'll need to change the formula for firmware 4.5.4, I suspect. Sent from my iPhone using Tapatalk

Hi Joe. See the screenshot in post 52 of this thread and you'll see how the voltage variables are displayed on my ISY, and the bold print in post 54 for a possible solution to the missing data for your second tag - this tripped me up similarly. Sent from my iPhone using Tapatalk

I'm not home do I can't post a screenshot, but I have my voltage variables set to a precision of three, in order to get them to display correctly. Firmware version is 5.0.8.

I've been able to remotely open the door a few times for unexpected guests, so I haven't made extensive use of the Z-Wave features, other than the notification abilities through the ISY. That is big when you need it, but I don't need it daily.

I had a large house remodel over the summer, so I used the locks to allow access (and keep track of) the various contractors who were coming and going (they all had unique codes, and I got notified every time they came and went). I didn't want to give out keys... Since then, the locks have been useful for house guests and family. I'm very pleased. Plus, I can take to dog for a walk without having to locate my keychain, and the dog appreciates spontaneity...

Yes, you'll need to configure the tags for monitoring those values. Also, I *think* (I don't actually recall) that they only update when the value changes, so maybe wait a bit?

I have two of them, powered by USB, that I bought primarily to use as secure repeaters for my locks. They've been very good for the nine months I've had them. There have quite a bit of functionality. My ISY firmware version is 5.0.8, which may make a difference. I cant speak to the Glass Break Alarm, Tamper Alarm, Intrusion Alarm functionality, and I don't run any programs that use the "Luminance" value, so I can't help you there. You have the ability to calibrate this device, and set a variety of parameters, so they're highly configurable. For my 2¢, they're quite useful.

Another thought: I had to "Reset State" on my tags before they started to send data. You might give that a try if still no success. See this post.

The first question is if your variables are STATE variables. This line in the code sends updates to STATE variables: var isy_RESTcall = "http://"+isy_user+":"+isy_password+"@"+isy_ip+"/rest/vars/set/2/" If you have INTEGER variables, then the line would need to look like this: var isy_RESTcall = "http://"+isy_user+":"+isy_password+"@"+isy_ip+"/rest/vars/set/1/" Also, did you make sure to include your tags in the selection list while configuring the app? Otherwise, I don't see anything obvious.

These use the REST interface, and there are two ways to get data to your ISY. One way is to create a Kump App, and you can see one here written by larryllix. A second method is "Custom URL Calling", and you can see an example of that here. Here are a couple of recent forum topics that discuss these tags: http://forum.universal-devices.com/topic/8818-cao-sensors-support/ http://forum.universal-devices.com/topic/21076-postal-notification/

You can leave the code as it is and the Kumoapp will prompt you for the values when you first run the app, so you don't need to hard code the values. I believe that's what the tags <%value%> prompt the Kumoapp to do. I haven't written any Javascript in better than ten years, but this is certainly what it looks like. From your Wireless Tag List page, press the "Kumo Apps" button on the bottom of the page. That will take you to a "Kumo Apps" page, and click on the "Write Your Own App" button on the right side of the black bar you see. Paste in your code in the code editor and fill in the correct info in the app. Click the "Create/Update App" button, then the "Get Link to Install" button, copy the link, go back to the Kump Apps page, then install the app. You'll probably need to click on the "Search All Apps" link at the bottom of the install page, but that will take you to a page where you can find your app. You'll then be taken to a "Configure the App" bate where you'll see input fields for you IP address, Username and Password when you first run it. It's important, on this page, to select all the tags you wish to include "Add/remove one or more"... Here is how I modified larryllix's code for my application (note that I'm only using soil water/moisture detectors, as seen in the variable "tags" -- var tags = <#tags_[32]_N#> ) var tags = <#tags_[32]_N#>; var isy_ip=<%ISY IP Address%>; var isy_user = <%ISY username%>; var isy_password=<%ISY password%>; var isy_RESTcall = "http://"+isy_user+":"+isy_password+"@"+isy_ip+"/rest/vars/set/2/" tags.forEach( function (tag) { tag.updated = function () { var cur_name = tag.name var valid_device = true switch(cur_name) { case "HerbPlanter": var isy_variable_humi = 27 var isy_variable_battV = 28 break; case "EastPlanter": var isy_variable_humi = 13 var isy_variable_battV = 29 break; case "FrontMaple": var isy_variable_humi = 14 var isy_variable_battV = 30 break; case "EntryPine": var isy_variable_humi = 25 var isy_variable_battV = 31 break; case "FrontPlanter": var isy_variable_humi = 26 var isy_variable_battV = 32 break; default: var valid_device = false } if(valid_device==true){ var tag_moisture = Math.round(tag.moisture); KumoApp.Log("Humidity for "+cur_name+" ("+isy_variable_humi+") updated to "+tag_moisture); KumoApp.httpCall(isy_RESTcall+isy_variable_humi+"/"+tag_moisture, "GET"); var tag_battV = Math.round(tag.batteryVolt * 1000)/1000; KumoApp.Log("BatteryV for "+cur_name+" ("+isy_variable_battV+") updated to "+tag_battV); KumoApp.httpCall(isy_RESTcall+isy_variable_battV+"/"+tag_battV, "GET"); } else { KumoApp.Log("Data from non-configured device: "+cur_name); } }; } ); Good luck! Screenshots attached.