Bumbershoot

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.

Yes, you can. Here's a snip of the NR for volume up: Port:1400 Timeout:500 Mode: Raw text POST /MediaRenderer/RenderingControl/Control HTTP/1.1 Host: 192.168.0.29:1400 Connection: Close Content-Type: text/xml; charset="utf-8" Content-Length: 333 SOAPACTION: "urn:schemas-upnp-org:service:RenderingControl:1#SetRelativeVolume" <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <s:Body> <u:SetRelativeVolume xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"> <InstanceID>0</InstanceID> <Channel>Master</Channel> <Adjustment>15</Adjustment> </u:SetRelativeVolume> </s:Body> </s:Envelope> Just set the <Adjustment> value to a negative # for volume down: <Adjustment>-15</Adjustment>

For what it's worth, I installed two of the GoControl branded GDO's just yesterday (I believe these are the exact same device as the Nutone, just with different branding), and they both work as intended. ISY firmware version is 5.0.8. In the Admin Console, the text status of the devices toggles from: Closed --> Opening --> Open or Open --> Closing --> Closed I needed the secure repeater functionality, so I opted for these.

Mine has worked flawlessly through the winter, with temps getting as low as -7ºF (-22ºC). It's in a covered area, so it's not directly exposed to sunlight or water, but it's holding up perfectly.

I was able to turn on/off Christmas decorations using Echo. I had several OutletLincs included in a scene, and I turned them on and off using a spoken for the scene in the ISY Portal.

Try this address in your browser, and it should download the admin.jnlp file to your download folder: http://192.168.1.155/admin.jnlp You might have to navigate to your download folder in Finder, right click on the file, select "Open". A dialogue box might appear the first time you try this that asks if you're sure as this file is from an unknown developer... Glad to hear.

I just tried to run the admin console from Safari, and it appears that I'm having problems doing the things you describe, along with watching the interminable "beachball of death" (the link used in Safari was http://192.168.0.30/admin). Using the admin.jnlp file on the desktop has always worked for me. I'm on firmware version 5.0.8, however.

You're correct that I don't get a location indication, but really I don't care which zone it is, I just want to get the lights turned on and make a huge racket! I have a hearing impaired person living here who often doesn't hear smoke alarms when asleep at night.

Here's the model: Firex I4618 by Kidde. I believe I was typing my response to the OP when when he responded, so I missed the RF comment.

You might want to check this link. I run the Admin Console from an application on my desktop, as described in this link, and I've never had any issues. I'm using a Retina iMac running macOS Sierra.

I took this route, and it works fine. I added one of these First Alert smoke alarms to my setup (all the rest of the alarms are hardwired Kidde alarms). I then added an Insteon Smoke Bridge to my setup. It has always worked as intended during testing, and installation was easy. My ISY now sends alerts, turns on all the lights, turns on my Z-Wave Aeotech Siren, etc. BTW, no hacking of the alarm or Smoke Bridge was necessary. The First Alert alarm uses a differently shaped connector than the Kidde alarms do, but it's easy to swap. My hardwired Kidde and First Alert alarms are compatible, as I can smoke a Kidde alarm (at the other end of the house from the First Alert), and the ISY runs my programs.