larryllix

Good to hear! I think a few of us have been caught on that one! Thanks for reporting back!

Have you checked your device link tables and compared them to your ISY link tables? Have you tried a factory reset on your devices and then restored them from ISY?

In V5.0.10 you can turn many Insteon devices RF and/or Powerine fuctions on and off from the Admin Console.

Look at the time, sunset and sunrise times in your admin console at the top of the window to see if they are correct.

One factor here in conjunction with what Paul and I posted. Have you set your time zone and Lat/long into ISY properly yet? Having the incorrect settings would cause your sunrise and sunset times to be off.

Your times may be crossed and ISY is smart enough to not even try in those cases. Use a single time. The time frame construct doesn't do anything for you as there is no code in the else section that the "until" time runs. Time frames are tricky. If another trigger is also involved, it can work as a timeframe filter but always also works as a run True (at the from time) and run Else section (at the until time) trigger, in enabled programs.

I find only the first word very significant. If the second word is garbled at all, then the first word is the only one that counts. I have discovered it is best to avoid conflicting devices like "ceiling lights" and "ceiling bright lights" with the same first word. If the words after the first words, are not clearly understood then Alexa will report multiple units found.

Most Insteon beep durations do not work as advertised. ISY just puts it out as it was defined by SH.

Read post #2 You can stop any offending programs with a right click and then edit them.

Need the Network Module, in the remote ISY, send REST command to the local ISY. It could set variables and then programs in the local ISY can trigger to operate what ever you want. You could operate programs or devices directly but the variable allows multiple programs and sequences to work off one event. Two variables could give more security from nuisance. When the local program runs it could just reset the variable flag and/or send back another reset to the remote ISY. More complex and it takes two NR modules.

Moving the PLM to a synthesized AC may not work well. Insteon relies on the locked frequency from the grid to operate, not colliding packets into each other. My UPS systems lock to my grid frequency, so that is not a problem while the grid supply is up. Once the grid supply goes down, the UPS is on it's own frequency (no lock). I can't think of any Insteon things that I run off the UPS supply during an outage though so haven't tried that aspect. They would be fed off the same AC source so that shouldn't be a problem and the grid devices have no power either. Whatever frequency the PLM runs from, should be the same phase locked frequency all Insteon device work from also. Let us know how that works out for you.

Yup.Your ISY is busy! This can be a normal happenning but after an hour it should have cleared. Open up your event viewer and see what is zooming by. Then try to find a less traffic way of doing what you are doing. You may have a program oscillating in itself. This can also be seen in the program tree with a program constantly changing colours. It typically happens when the If section contains the same element that the Then or Else section is affecting.

I use that technique for a lot of my devices. With analogue devices the boot up, out of sync, lie is not a great though, showing 21.5 derees C instead of 22.0C that cahnged while ISY was sleeping. A big advantage is when replacing a device, only one spot has to be changed in one program. This happenned recently when I got a newer, better thermostat for my main room, and the old one got repurposed to another zone. With dozens of an cyclers, monitoring programs, extreme weather draught compensation etc..etc.. it really helped.

I have no idea what mobilinc would have to do with ISY programs. I consider it just another SwitchLinc / MS / Echo / Dot input and monitor of the system. Many of my lights have MSes that trigger them on and ISY turns them off. Almost all have timers that turn them off again. When I write a program that turns on a light it just triggers the same program (mostly) that the MS would do. The timer is already there. When I write manual override programs to bypass the MS system(s) with that light, I write in long term turn off code, due to people expecting automatic lights to usually turn themselves off. Manual operation becomes an unexpected style of operation and then the lights get left on. Always put in a plan B. This is the same for the Echo/Dots.

OK. then you have success with that. You have the workaround/fix. I must have been confused and thought you were posting it didn't work as it was found on various times. My bad there.

Do you not have the usual "If-all-else-fails" turn everything off every 4:00 AM? The LED bulb may not consume much energy but a worn out smart bulb may upset the human. when it is actually needed. Having no Insteon bulbs, does anybody know if and when the Insteon bulbs turns itself on, after a power failure restoration, does it send it's status out, updating the ISY ?

So you have too many probllems or too much money?

I bought the commercial spray before I did my research to find out how to make your own. It comes in a spray bottle, like a Windex windw cleaner spray bottle. I sprayed the staircases leading to the deck. This is a slight odour to it but nothing abnoxious. @lilyoyo My location is shown under my avatar. More southern than Washington state, but in Canada, eh?.

We have a raccoon that likes to sleep on our deck and leave piles of staining remnants. Hot pepper spray cures that for a few years or at least until it rains and washes it away again. Usually the raccoon has found a new resting place by then so we don't see it for a few years. You can buy this commercially mixed in a spray bottle, or make your own. A small bottle of Tobasco sauce in a gallon of water. Other recipies are based on making a steeped tea of cayenne peper and then diluting it about several gallons of water to a cup full of solution. We have skunks that wander right past us when at an evening campfire, in our sideyard firepit area, and coyote packs that stop yipping when we flash our porch lights. They have taken on a few of the neighbourhood cats at times. What a racket! But nobody has complained their cat has gone missing yet, so the cats must do well against a 4 or 5 coyote pups.

Power blinks can do this to many brands of smart bulbs. Hues do this so I have an ISY program set to turn them off upon every ISY power up initialisation and I only have to sleep through a couple of minutes of glaring lights at 4:12 AM. IIRC Insteon bulbs have an option to disable this so-called "feature". I don't have any of the Insteon brand.

Use an overriding long term timer so if the Off signal is not received, the light turns off anyway. Many users disable the Off inside the MS options.

I have to wonder how they can call this "in-line"?

Wink made those implications too. It most likely just connects to your other hubs, increasing your hub count by one. Sent from my SGH-I257M using Tapatalk

Finding this fascinating...doesn't that mean passing a specific node driver code to the other end, making the other end CPU code dependant and the code hardware dependant? OTOH, Perhaps a scripting language that already understands individual box hardware (sound output, video, Insteon PLM, wired siren) is the underlying secret then? That would mean ISY would not really be needing much OS change, just the ISY994X box would get smarter and understand where to send what node signal. ISY would become a smart peripheral to it, somewhat.

Trying to understand your concept, please verify my paraphrasing/analogy. NMM sounds like a definition for a protocol that will allow a device to send a complete device descriptor block to ISY (or other smart device) and ISY can instantly self install node pieces that understand all the given aspect/parameters to be expected from the device. In effect, ISY could start out knowing nothing about any device. When a device first connects to ISY (or other smart device), it sends it's personality and/or configuration. ISY would then configure itself, installing all the styles of node drivers it was told about and now understands the remote device with all it's nuances. On a simpler scale, it would be Plug'n Play, but on a smaller chunk scale (not on a whole device driver scale), to be able to represent any possible new device with many less drivers than one large one for every device produced. Simplified protocol talk DEVICE. "I am a thing-a-ma-jig . I contain an MS=On/Off, Brightness Level=0-100%, Battery Voltage=0-3.5 volts, Angle Detector=0-360 degrees" -----> ISY "OK.... Installed Thing-a-ma-jig.....Ready for values" Thanks Michel