paulbates

Hi and welcome to the UDI formums! You can try the Start Linking option at the top of the Link Management Menu, and then put the remotelinc in linking mode. I've not specifically tried that with a remotelinc, but it wouldn't take long to find out if it works. Paul

...a nodeserver coming anytime soon???

I'm leaning with Brian, that there is something wrong with it. Call SH and see if they have a suggestion or ask them to replace it

While I haven't had those exact symptoms, I have some keypads the occasionally need a factory reset and followed by arestore device. Even if its new, it normally doesn't take that long. Paul

I don't have the "if all else fails" for everything. After +10 years of Insteon, I've mostly bashed it into submission. I do have an individual program that sees if the Bulb is on but the keypad key is off. If so, it does wait for a few, then a dim, a wait and then an off.. on the bizarre outside chance I'm up there. It sends a pushover message which I haven't seen since setting the default on level to 0%. I'm likely going to delete the program. The Insteon bulb (at least mine) does go on automatically after a power fail... unless you set its default on to 0% and control it with scenes. Then it does not come on. We've gone through several power outages since I did this and it no longer comes on. I'm pretty sure it sends its status, because that's how my program works Paul

I have one insteon bulb in my attic, where I can't keep an eye on it. Its in a scene with a keypad key down below.. but, at times I look at the Admin Console and its been on for no reason. Something that worked for me was setting the On level to 0 for the bulb. Then I use scenes to set a full on scene level with the keypad. You can also turn the bulb on by scene with a program I also have a program that sees if the light is on and turn it back off (slowly) and send me a notice. Since setting the default on level to 0, that hasn't happened. Paul

Cool glad you had one. I have several because I replaced the furnaces with the ECM motors a few years ago and had the installers return those to me. It may be possible to increase the retries of the fanlinc. I wrote about this yesterday here. Look at the last post. Right-click on the fanlinc, advanced, PLM Communications. Some of my devices support it, some don't. I don't have a fanlinc, so not sure. If it works, consider that the bigger the retry number, the more retries, and the longer the perceived response to the command. It kind of depends how noticeable. Its worth experimenting with both and see what works best for you Paul Paul

Yeh, we have skunks, racoons, opossums and a foxes ..amounts descending in that order. There are coyotes and deer that I see when hiking, but they never come in the neighborhood. Ugly as the opossums are, they eat a lot of ticks and other nasties. Glad that its all working the way you want it to now Paul

Yes, good catch.. Stating that its "In line" is a misnomer and a gaff from Amazon... its not inline. Here is the source doc from x10. It wires across hot and neutral and carries no load... easy to wire and no load is carried by the device. Minimal to no risk of it "popping" Paul

Sandry, no, that is the the evidence that was needed. It proves that when Insteon powers the fan, the fan (most likely motor) is injecting line noise back down the circuity and overwhelming the fanlinc. Some type of filter is needed. I've used this with insteon devices that were overwhelmed by ECM furnance motors and transformers. Its very easy to wire to 110vac if you can fit it in the fan body. Paul

Hi Sandry When directly controlling devices, The Insteon device sending the command will try several times to get through. If it doesn't get an acknowledgement from the target (fanlinc), the source will try several times. Three things can happen The command gets through, the device goes on/off, and the response eventually makes it back The command gets through, the device goes on/off, but the acknowledgement doesn't make it back. The fanlinc responds, but the ISY didn't get the acknowledgement, so it doesn't know and has the wrong status The command never gets through, the device doesn't go on/off, and the ISY doesn't get the acknowledgement. The culprit in 2. and 3. is line noise. I'm wondering if the fan is injecting a lot of noise into the power line after its turned on, or at certain speeds. Some power line noise can even overwhelm an Insteon devices ability to accept commands via RF. You can try can to see if a certain state of the fan exhibits the delay behavior more to start narrowing this down Turning it on from off 5 times.. How many successful ons? How many delayed actions Turning it off from on 5 times.. How man successful offs? How many delayed actions .. compare to Ons Same thing for changing speeds. Does changing into a certain speed then cause delayed responses? Paul

Yes. I think Nodeservers are a general purpose HA facility, with the flexibility to define what's needed based on the products that appear. The tool sets exist: We see a lot of nodeserver action with Polyglot / python and other unix tools. io_guy has more the proven the ability/viability of non linux developed frameworks like .net to integrate nodeservers. Right now, we're living under the graces of some smart and generous devs who have integrated the HA products we have to date As more people convert to V5, there'll be more opportunities to integrate more products and even meet additional devs Sooner or later, some configurable type tools will emerge that will make integrating easy things easier.. but they will never be perfect I don't think we can expect some cure all, silver bullet point and click integration tool.. no fault of our own, the market is still too crazy and volatile... no one's going to be able to anticipate it all. Paul

I have 2 MS on stakes in my back yard as skunk deterrants. One in the corner of the lot, and another pointing under the deck, which has ~ 2ft space under the decking. That one turns on a outletlinc with a floodlight on a stick that floods the area under the deck. I have a program that flashes it on and off a few times and then stays on for 10 minutes. Its been there a few years now and has been pretty effective. We still see them, but don't smell them nearly as much. Paul

Hi If the logic in an ISY Program becomes false, the program will cancel and stop running while in a Wait. In this case, the motion sensor goes back off before the 3 minute wait is up. You have a couple of options. The easiest is using a Control when watching the motion sensor instead of Status If From 10:00:00PM To 6:00:00AM (next day) And Control 'Motion Back Door-Sensor' is Switched On Then ...... Paul

As long as the room temp does not exceed the spec'd operating range for the stat, it should be an ok solution .. 104F is the highest spec'd for it Its not dual band, its RF only, so it needs to be in solid range of another repeating dual band device. Yes, you can easily power it with a plug in 24VAC step down transformer. If you search for that model on the forums here you'll find people don't always get the degree per degree feedback into the ISY that they want, so programs for it could be If gearroom temp => x then set fans on else wait 5 minutes set fans off In my experience automated fans can kick the temp down quickly artificially. I run into this with my attic. I keep the fan going a while after the target temp is sensed. You can calibrate that time up and down to what you find in your room Paul

Hmmm. Don't know either. I re-followed my own directions and got the same value that's the second entry in my finder that I added. I'm not sure how pasting a link in the thick java client finder would cause a download. That sounds more like what happens when you run the ISY's web page from the portal and ask it to install the admin console. Paul

That link documents how to add the portal link to your ISY finder to your existing copy of the admin console... for just that reason.. whatever copy you have on existing your PC is the one you'll use. Paul

Agreed. I was going to also say links table empty or low. When the PLM is dying, it selectively deletes some links and others remain. I only had the insteon tstats for a short while, my older HVAC units overwhelmed them when the igniters fired and then they acted unpredictably or ran heat on continuously. I switched to something else. Paul

That's a sign that the the links table in the PLM, which allows it to decide what insteon network events to receive/send to the ISY, is empty. To find out, Try Tools / Diagnostics / Show PLM Links Table / Start You can try factory resetting the PLM and Restore. Yes - complicated sometimes, but that's the only way I know if the PLM links table is evidence of the problem Unplug both ISY and PLM, Wait 10 seconds Plug in the PLM and hold set button 3 seconds release the set button and wait for the led to light plugin the ISY Restore modem This is the sign of dying PLM, maybe the factor reset will help. Paul

Hey @larryllix, take a look at this post Paul

The idea is that you can close the ports into your house and get rid of dyndns (if you aren't accessing other things with it). That's exactly why I have the portal. My ISY "dials out" to the ISY portal, and I connect to the portal to access my ISY when I'm remote. You can access the ISY web interface and the Home Automation Dashboard (HAD) which is a fancier ISY web page. You can pick between those from the portal. You can also use the portal to access the admin console. Paul

No, it didn't actually get a true open. The door was down, and had been down. Over time it slowly, and only a little, traveled from right to left. It waited until we were 90 miles away at my daughters college to trigger a phantom "up". I guess the point is I spent some time chasing an Insteon phantom that didn't exist, is it was a physical problem. I eventually nailed a shim in so it wouldn't move around. I could see that potentially if something got into the wiring. Paul

Eddie Any chance there is something going on (short, etc) with the wiring on the output contact side from the iolinc to the door..causing it to open? I had a physical related issue when mine false indicated an open when the door would travel a little further away from the contact sensor. Paul

Whatever the 'something else' is has to be a controller in the scene you are using, or, control the scene and not the device. If "something else" is a program or mobile app, have those set the scene on/off and not the device directly. Paul Sent from my iPhone using Tapatalk

Version 3.3.10 FW is the end of the line for the 99i. I don't think you have to have a PLM, you might get errors when it boots up, but it should be ok. The thing to keep in mind is that the network module for 3.3.10 does not support the latest SSL, and specifically TLS. If your network resources are local to your LAN and http://, probably you will be ok. But if you are connecting to cloud services like pushover, or want to use gmail, its not going to work. FWIW, with those vulnerabilities, I would firewall it and keep all activity in the house. Its probably worth an hour or so of experimenting to see what will work. Paul