jec6613

Option 1) Use ISY launcher. Option 2) Use Internet Explorer. You may laugh, but do you know how many pieces of really expensive (and even pretty new) tech rely on Java or an IE specific extension for administration in the IT world? Keep it to sites on the intranet and off the internet and it's perfectly fine and works well. And it's Windows 7, so you actually have IE on it, unlike the home editions of Windows 10 which lack it.

I push the LED brightness button on all of my 2334's, and this comes up. I have nine of them and they all work the same way. Though I don't actually control it with that, that would be a bit silly, I have programs that adjust the backlights by time of day.

You can also just rig up more normal beams. Most openers have multiple safety inputs for precisely that reason, and if not, you can get an expansion bus pretty easily. Or, if your GDO handles NC, just run them in series.

Mine came with the house. When we had the door and track replaced by UPS (who damaged it) is when I got all of the in-built sensors calibrated and dialed in. Also since we now have a lightweight door and previously had solid wood, we have a massively overpowered GDO, which really helps with the auto reverse sensor. I believe it's a seco-larm curtain sensor, similar to this: http://www.seco-larm.com/sensors/curtain-sensors/E-9622-4B25

Mine is around 5 frames of delay at 15 FPS, so 1/3 of a second, on my LAN. From Joburg it was about 2-3 seconds transiting the undersea cables. But if a child enters under the door path, it stops and retracts due to the curtain sensors anyway, and they'd also have to come from somewhere, which is all camera covered. If a child can run 150m from out of sight to the door in less than 12 seconds when the world record is 9.58 to 100m, then I'm calling Guinness.

Well, for one thing, I have multiple beam sensors crossing the path of the door from a few inches up to 3' off the ground, any one of which will cause an instant reverse. Also, at least on my opener, the sensitivity on the back pressure sensor is as high as it can go - I can stop it with one finger, and have tested this. And living in the sticks on some property takes care of most of the rest, and the cameras the rest, since I have much better visibility from in my house with the cameras than I do inside of the garage using the hardwire button. I could meet the buzzer recommendations as well (not code required around here), and at some point will put that in, but since I can see the interior and exterior of the garage it hasn't been a high priority. See also: the dual Labrador alarm system that would definitely alert me if someone was on the property.

I don't have children, I have labrador retreivers, and multiple sensors on the opener that will bounce the door back, plus a camera. Since there's no way we can see the garage door from inside the house, and no way without walking outside (even though it's a short distance) to close said door otherwise, I use an IOLinc and some keypad buttons. That said, when the existing IOLinc goes, I'll be upgrading to something with even more logic and sensors. As far as running, it sounds like it would run just fine, but it's a bit kludgy. I have my goodnight program set a variable, then use that variable to trigger other programs. Ditto home, away, etc. By doing this, it also lets me change out how the house responds in the middle of the night vs after sundown, including ramp rates and on levels for lights.

"Sincere apologies. This is an aberrant email from our staging server and not the production. Your account is alive and well and you can access it using your email address."

First hard reset the keypad, then restore its settings from the ISY's admin console. If it's still broken, then replace it - a reset and restore only takes a few minutes.

I'm not sure about the portal interface, but when using the Polyglot/Hue Emulator combination to expose them, the spoken name is tagged in the Spoken note of the ISY itself, which gets backed using ordinary methods.

I did this with Polyglot and harmony. Motion normally works, but once the theater is in theater mode, motion sensing is disabled.

It should work just fine on a switched network. Routed over the internet and tunneling through IPSec, on the other hand, may not be an acceptable situation.

Side note: I've done fiber before, run either 6 or 12 strands of singlemode (it'll come as a single cable) and terminate properly to a fiber patch panel, then run to whatever you want. Don't even try and bother with individual pairs, and singlemode can run 100 Gbit later if you ever have the need. Run it properly once and you'll never regret it. Singlemode SFPs aren't much more expensive than multimode, but re-pulling that cable in 10 years is. If you want some multimode to run things other than Ethernet, might as well run 6 or 12 of that as well, and be sure it's OM4. RS232 over fiber, audio over fiber, and so on frequently will only work with multimode due to cost considerations. But the way things are going, you'll probably be better off with just singlemode and dump everything down an Ethernet pipe. And if you want to try linking the two PLMs via RS232, you can get RS232 over Ethernet adapters and just send it over TCP/IP with everything else. Even a reasonably cheap Netgear switch will be more than enough to handle all of that going over it, their cheap evergreen GS716/724T switches will handle AV over Ethernet no problem, and if you need more bandwidth the M4300 series is designed for AV over Ethernet from the ground up with 10/40Gb support. The tiny control signals will be no problem for any of them to handle.

Assuming the second building is smaller than the first by a substantial amount, I'd just use network resources to pass commands so that every single device is effectively controlled from one ISY.

But if Insteon went away tomorrow, I'd also use Lutron for lighting. Z-Wave to replace the Insteon sensors … and neither of them immediately, I'm 95% built out so there's no rush to move to another platform until things stop working. And I have a spare PLM, and a spare USB PLM for when the Polisy eventually takes it all over. The fit and finish on Lutron are even better than Insteon, and Z-Wave aren't there yet. It'd have to be RA2Select though, since Caseta can't handle as many devices as I have. And hopefully if this ever happens, there will be a Lutron NodeServer.

I'm not sure about a thread, but if you install the Hue Emulator it will expose any device with a Spoken from the ISY via a Hue emulation. You can then add that to the Harmony, I've been very successful using it.

Is this an AFI/GFI breaker? It could be going bad if it's giving you nuisance trips. I'd also re-terminate the wires into the breakers themselves if it's AFI/GFI, to ensure you have good connection there. This is the cause of your red light. The simple way to make sure it's not a programming issue is to hard reset the switch, then restore its configuration from the ISY.

The second node is an Off node. Very much like how there's a wet and a dry node on leak sensors, it's just inverted.

I mean, given all of your requirements are just monitoring, why not use somebody like Sensaphone? The ISY is designed for a lot more stuff, but Sensaphone meets all your requirements and has support in a commercial environment with BMS tie-ins. (heck, even an ISY can talk to a Sensaphone).

Of course it has more than just DIY use cases, but though I likely have the requisite skills, I also have a day job, and have been in IT long enough to know that this sort of gig wouldn't pay enough to make it worth the aggravation of dealing with it as a side job.

I would use the Polyglot Ping module and have it ping my ISP's gateway. This means it won't get an erroneous reboot if the ISP has peering issues.

Aside: one thing I'd like either Insteon or a Z-Wave vendor to make is an ELV capable dimmer. The Lutron PD-5NE is the only DIY smart device on the market right now, and though it would be expensive, I'd purchase the heck out of an Insteon version of it.

The counter-argument to this of course is: what's really innovative out of Z-Wave that Insteon doesn't have already? About the only things I've seen are the Aeotec Wall Swipe and various sensors that offer more capability, but Z-Wave is seriously behind in a lot of areas. And the 240V load controllers and door lock controller that are now discontinued, of course. Insteon has both 2-wire and 3-wire dimmers, relays capable of 20A operation, both paddle and toggle style switches, DIN rail, micro modules, and in-line modules, all capable of true N-way operation. Think about that list for a second ... no Z-Wave manufacturer comes close. Even putting two or three together, Z-Wave is still behind, and some functions simply don't exist with Z-Wave at all. And that's not even considering the device limit. I have 214 Insteon devices, not counting the Z-Wave I have as well. That's far too many for a Z-Wave network to support without significant congestion.

I create a scene with just the controllers, assuming the sensors aren't controllers for another scene. Another alternative is to have one program with the sensors and OR statements, then reference it from other programs with an "If True" or park the state in a state variable set to 1 or 0. Edit: one other thing I've done is if the sensors support split nodes for On and Off, just link the On nodes to the scene, then have the off part in a program.

I played around a bit, and none seemed to adjust sensitivity. FWIW, my temperatures are pretty accurate for a PIR device, but I only pull temps for USB powered devices, and use good USB power sources for them.