Bumbershoot

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.

There's a nice sample Kumoapp in post # 169. I modified it to my application and things are now working fine. Edit: attached screenshot of ISY variables updated by the Kumoapp.

I'm in the process of getting this set up. The easiest method (so far) has been to use the "Custom URL Calling" feature of the tags. Here's a link to the post that at least partially explains how I got them to work.

I used a hardwired SA521CN to link to a Smoke Bridge, and it works fine (at least it tests that way - no actual fires). The rest of my smoke detectors are FireX (rebranded Kidde detectors), and are all hardwired / interconnected. I don't get any announcement of which zone is in alarm, but I am able to use the ISY to turn on every light in the house and make additional noise if any detector is set off.

Huzzah! Thank-you, kind sir!

This is interesting to me is because I cannot regain the use of Polyglot and Nodelink node servers without a factory reset of the ISY with no restore of a recent backup. A factory reset along with a restore of a recent backup does not work, as that restores whatever corruption causes the node servers to fail. I have to go back to an early backup of 5.0.4 to get Insteon, Z-Wave and node servers to all display in the UI. Sadly, on releases subsequent to 5.0.4 I've added a ton of Inseton and Z-Wave devices to my installation (big remodel that couldn't wait, so forward we march...). It was clearly a poor decision on my part keep installing devices after the node server problem surfaced, but I had contractors trying to do actual work on an actual schedule with an actual budget, so here I am. A rebuilding of my Insteon network should be too bad, with the Topology report, the ability to export/import programs and the "restore device" functionality. The Z-Wave network is the problem, as I have devices stuck in difficult locations as secure repeaters (crawl space, attic and garage ceiling, etc) that can't be re-included easily. This network would be a PITA to recreate in place, though it could be done with a long extension cord, a laptop and WiFi - don't have a laptop, though. If I could factory reset my ISY, get my node servers back in operation, restore Z-Wave only (without the corrupt node servers), then I could recreate the Insteon network over a weekend when the Mrs. is busy. This is the third best possible solution that I can foresee, but the only one that takes no interaction from UDI. I took the risk of running Alpha software (the node servers were too hard to resist), and UDI provides great support for their released software and hardware. I just like to have escape routes...

Now that the snow has finally receded from my yard, I spent the day raking, pruning and hauling debris, while also scouting for good locations to place a 1/2 dozen or so CAO water/moisture sensors in the garden. With these, along with my rainmachine, my upcoming WeatherFlow weather station and my ISY, I'm going to nail my irrigation requirements this year. Water is expensive in the high Oregon desert, and irrigation is the single area that I've found where data driven automation pays for itself in a short amount of time.

Interesting conversation. I've been avoiding rebuilding my ISY specifically because it would be difficult to re-include Z-Wave devices that are in inconvenient locations, especially as secure repeaters. I've done a few factory resets of the ISY, however, and a couple of Aeotec Multisensors that I have on a quick report cycle always show up in the device tree immediately without being re-included (ultimately, I've always restored from backup and haven't done a deliberate test, prior to restore, to find out what's going on with my Z-Wave devices). That makes me think that you're correct in what you say above, which is encouraging.

Doh! I never thought to use load sense for this! I keep my espresso machine inside an appliance garage in the kitchen, so I've always been careful to shut the OutletLinc off overnight and when we're away, but this is way better. Thanks for the idea!

No, I didn't touch a thing with either Nest or Alexa. It "just worked"™.

As of 2/25, this appears to be working with Nest thermostats. When queried, "Alexa, what's the temperature of Family Room", here's how Alexa responds, "According to Family Room, it's currently 65 degrees". Thanks for the notice. One more thing to help improve the WAF...

Thanks, I appreciate the info.

If you're referring to the disappearing node server problem, and 5.0.8T1 providing a fix, then I'm even more anxiously awaiting 5.0.9. Regardless, thanks for the continuous improvements/extensions/enhancements to the platform!

I fiddled with it this morning ( firmware 5.0.8 ) to no productive end. I get "HTTP error 401" when I attempt "Upload nodes definitions", in the Configuration menu (I'm only speculating on what this means in this application). I've got other node server issues, so I pretty much got what I expected. I'll be curious to hear how this works for others, going forward.

Thanks for the clarification. I've never noticed this with my Christmas LEDs / OutletLincs, but now I'll look for it.

I'm running 5.0.8, and in the Admin Console you can select the OutletLinc, click on the "Options" button and you'll be presented with a dialogue that presents you with the ability select/deselect load sensing for either outlet. Sorry, but I don't recall if this is the case with earlier firmware/UI versions.

I was hoping I could stash an audio file in the web space on my ISY and somehow cajole a NR and Sonos to play the file from there. I haven't figured out how to configure an http resource to have Sonos grab the file, as Sonos always coughs up a "permission denied" response. Maybe this can't be done, as I haven't found a shred of documentation on what that NR would look like. I'd like to eliminate the NAS on my network, and just let the ISY web server serve up the audio file. If anybody has an idea on how to make this work, I'd love to hear it! I'm waiting for this bug, noted in the 5.0.7 release notes to be resolved: Cannot recreate reported problems: 0000314 – Node server disappears after restart I've got Polyglot running anyway, and Sonos, Nest, Camera and Nodelink items all appear in my logs, but there's nothing in the ISY Admin Console that allows me access to the devices. I loved it when it worked!

You can have any speaker play with an independently set volume. I haven't tried to play a specific file, but the following NR will allow you to play a Sonos Playlist: POST /MediaRenderer/AVTransport/Control HTTP/1.1 Host: 192.168.0.29:1400 Connection: Close Content-Type: text/xml; charset="utf-8" Content-Length: 801 SOAPACTION: "urn:schemas-upnp-org:service:AVTransport:1#StartAutoplay" <s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <u:StartAutoplay xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"> <InstanceID>0</InstanceID> <ProgramURI>file:///jffs/settings/savedqueues.rsq#2</ProgramURI> <ProgramMetaData><DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upup="urn:schemas-upnp.org:metadata-1-0/upnp/" xmlns:r="urn:schemas-rinconnetworks-com:metadata-1-0/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/"><itemid="SD:2" parentID="SD"</ProgramMetaData> <Volume>8</Volume> <IncludeLinkedZones>0</IncludeLinkedZones> <ResetVolumeAfter>8</ResetVolumeAfter> </u:StartAutoplay> </s:Body> </s:Envelope> The magic is in this line: <ProgramURI>file:///jffs/settings/savedqueues.rsq#2</ProgramURI> If you edit "savedqueues.req#2" to request another queue: "savedqueues.req#3" could allow you, conceptually, to create playlists with one file in them, and create a distinct NR for each one. I believe that Sonos sequentially creates a new savedqueues.req# for each playlist, though I haven't definitively discovered the relationship between these numbers and each playlist. I don't believe that deleted playlist numbers are reused by Sonos, to if you've fooled with your playlists extensively, this may be become difficult. There must be a better way, though I don't know what it is at the moment.