Bumbershoot

From the Wiki: Enable/Disable Internet Access In order to achieve remote/internet access, you will need to setup your router for port forwarding. Port forwarding allows the ISY’s port to be seen over the internet. The controller default setting is with internet access disabled. If you would like to enable internet access to the controller select this option. It is reversible and you will be presented with the Disable Internet Access menu option. For a list of supported routers, please see the Supported Remote Access Routers page. If you do not have one of the routers listed above, please contact us and we’ll walk you through setting up your router (port forwarding) manually. Unless you're port forwarding, you shouldn't need to enable this (and I'm pretty sure it's not recommended). You ISY can get out to the Internet (evidenced by your ISY's ability to use your local network to sync the clock) but the Internet can't get in to your ISY.

I concur -- I've got two Polyglot nodeservers involved (Nest2 and LiFX, with the ISY acting as the intermediary), and I get notifications (a couple of lights change colors) within a second or two of "Person" detection as well. That happens prior to getting notification on my Apple Watch. I'm pleased with the performance of these nodeservers.

Mine flip between plausible and implausible values seemingly randomly (meaning I haven't discerned a pattern). I can't rely on that value at this point, so I'm sticking to my CAO Wireless Tags for temperature/humidity. I don't really need great precision, but I need a device that will wake up when it's queried (without an external event) and provide a relatively good value.

Hi Bruce, It looks to me like you're on the right track When/if you're comfortable, you might think about deploying a Polyglot server for your Hue and MagicHome lights (along with a number of other technologies). Polyglot is looming large in the ISY's future as a tool to integrate disparate technologies under the control of the ISY. Polyglot requires beta ISY firmware currently, but it looks to be an important part of the next stable firmware release. The reason I mention this is that running Polyglot may be easier than creating the necessary network resources required to have your ISY control your Hue and MagicHome lights (though Alexa skills may allow you to navigate around the ISY for this). Good luck!

I only have these things powered by battery, so they might act differently under USB power. The only way I've managed to get the "CLITEMP" and "LUMIN" values to change for these devices is to programmatically query the device upon a motion status change (the "DON" event in the ISY event viewer, I believe). Then it seems to work (and you can see the values arriving in the ISY event viewer). MS Master Bath Query - [ID 0101][Parent 0004] If 'Master Bath.1 Motion' is switched On Then Set 'Master Bath.1 Motion' Query Else - No Actions - (To add one, press 'Action') Getting the temperature calibrated properly is a bit of black magic that I haven't mastered, but this seems to update the "CLITEMP" and "LUMIN" values for me. Issuing a query without an a corresponding "DON" event doesn't seem to produce anything on battery power, as I assume the device is asleep. EDIT: I forgot to add that the "CLITEMP" values returned are occasionally way out of bounds. I've gotten values such as 139.9°F for my master bathroom. ?

I have mine running off of battery power. I haven't watched the temperature value change, but it seems to. I suspect it only sends an update to the AC when they're activated by motion, though I don't actually know. If I find some time I'll write a program to notify me of status changes as well as temperature changes. If I do that, I'll report back here. I'd think if you wanted to use them for more-or-less real-time updates, you'd have to run them off of USB power. Hopefully, they'd act like the Aeotec Multisensors that I have on USB power in my garage.

I pressed the "SET" button until it is in linking mode, then queried it from the ISY.

The must have changed the firmware at some point. Mine are battery powered and I have no "as motion sensed" option at all.

It appears that mine are revision 3, so it could be.

I have mine set like the screenshot shows in my laundry room, and it does not shut off the light when the room is occupied, even with a 30 second timeout. I suspect the "Motion | Condition" dropdown menu contains what you need. At least it seems to be working for me... ?

Michel does recommend a heal if communications aren't good. See this post earlier in this thread:

I had to go back to find my own post, but I performed a heal after the upgrade to reestablish the neighbors to my devices. There have been no ill effects that I've noticed, as everything is working just fine here, with no noticable issues at all.

Thanks for this. All I was looking for is a way to get a bit flipped in my ISY so I can manage external lighting, internal notifications, etc. I was able to purchase a Nest Hello for a $30.00 discount which included a free Google Home Mini (which hasn't arrived yet, but I understand will manage some announcements). All good! I've got the Hello installed yesterday, and it appears that you're exactly correct about the "Event - Person" toggling reliably. I'm off to the races with this thing.

Okay, I have the Nest polyglot nodeserver already running and am happy with it. Is the Hello incorporated into that nodeserver (I might have missed something...)?

Any updates on this with the current firmware (5.0.13A)? Thanks.

I don't know much about Z-Wave, but I did an exclude/include on my lock while it was in place, and it included securely. After a network heal, all the neighbors showed up as expected. I don't know what significance the 'association groups' have. Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ---------------------------------------------- Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ZW 002 Schlage Door Lock Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ZW002_1 uid=2 type=4.64.3 mid=59 tid=25409 pid=20548 model=2 Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x22 V1 APPLICATION_STATUS Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x98 V1 SECURITY Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x86 V1 VERSION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Secure Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x5D V2 ANTITHEFT Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x85 V1 ASSOCIATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x20 V1 BASIC Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x80 V1 BATTERY Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x62 V2 DOOR_LOCK Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x71 V3 NOTIFICATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x63 V1 USER_CODE Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - xEF V0 MARK Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Last working route from ISY to Node 2 - ZW 002 Schlage Door Lock Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Node 13 - Master Fan Switch Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Node 12 - East Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Node 2 - ZW 002 Schlage Door Lock has the following neighbors Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 7 - ZW 007 Siren Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 8 - ZW 008 Multilevel Sensor Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 9 - ZW 009 Multilevel Sensor Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 10 - ZW 010 Water Cop Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 11 - West Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 12 - East Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 14 - Office Dimmer Switch Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:46 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION Sun 07/15/2018 17:37:53 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION Sun 07/15/2018 17:37:53 : [ZW-SHOW ] Node 2 - ZW 002 Schlage Door Lock cannot retrieve association groups Sun 07/15/2018 17:37:53 : [ZW-SHOW ] Sun 07/15/2018 17:37:53 : [ZW-SHOW ] ----------------------------------------------

I just had a chance to install the new board this morning. It took 3 attempts to successfully perform a Z-Wave restore, but all is well now. No discernible differences. Edit: If it's interesting, I excluded and included my Schlage deadbolt while it remained in the door, and it appears to have excluded/included just fine. It has a new Z-Wave number, but it seems to be securely included, and as far as I can tell, it's working entirely as intended. I have several Z-Wave repeaters between it and the ISY.

I did something similar with previous versions of Polyglot and the LiFX nodeserver. It worked, though a bit erratically with a two second wait between color switches. Both Polyglot and the LiFX nodeserver have improved significantly since then, so you might have some succcess with the lighting.

This was in the release announcement for the 5.0.9 build: 0000371 - Full support for Insteon Siren 2868-222

Yep, I left one a while ago! Thanks for the skill, too!

I have one of these, only it's a dimmer (Homeseer WD-WS200+, with the 7 LEDs), and solved what I believe is a similar problem using both variables and by disabling/enabling programs. My problem might be slightly more complicated that yours, in that I have to choose which LED to illuminate on this dimmer. The problem was straightforward except that I have two garage doors that I wanted to monitor the status of using the same LED on the dimmer. This proved to be trickier than I initially thought, and it took nine programs for me to accomplish this (I'm sure there's an easier way, but I got it to work so I've left it alone for now). The solution involved setting variables in programs, then disabling/enabling other programs that would set the same variable to a different value, based on which (or both) garage doors are open or closed. This might be an approach you could use.

I've got "brief mode" on as well, but I never turned it on. Alexa chimed in after some command and asked if I wanted to have her turn on "brief mode". I said yes, and it's been that way ever since. Never touched an app.

I've tried to design this installation so that if I take my ISY away, the house will still operate as one would expect any house would operate, meaning that the razzle/dazzle is almost entirely controlled by ISY programs. I might turn off the LEDs on the OutletLincs/SwitchLincs and unplug the ISY if showing the house, but otherwise, things should work almost entirely without surprises if no controller/eccentric husband is around to manage it all (this was an early request from the Mrs.). Folks in my neighborhood are warming up to HA (I thank Alexa, iRobot/Roomba, Nest, security systems, home theater, etc. for that). I see a lot of service trucks from local HA vendors/installers sitting in driveways around here, and new construction seems to always include either a Control4 installation or at least a fancy HA controlled media room. At this point, my only concern is the long-term viability of the gear I've installed. I don't expect that people will be interested in the same gear ten years from now, nor will I still be interested in keeping functional, though obsolete Insteon/Z-Wave stuff around. I expect I'll have to do a periodic swap-out of my HA gear to keep it somewhat current -- I see that as a maintenance expense. It's a hobby, after all, and cheaper than a cellar full of fancy wine or a late-life crisis sports car... I think @larryllix is right, it depends somewhat on the neighborhood and the price of the house. And again, times are changin... Somebody's buying all that gear.

Have fun with this. I've found yet another way to surprise the Mrs. with home automation. She appreciates Alexa notifying her when I'm a few blocks away from home.

Nope, you'll need the 5.x.x firmware for node servers. I'd move to 5.0.12 if it were me -- the latest and greatest, you know. Your ISY world can get a LOT bigger when you start looking into Polyglot and Nodelink.