paulbates

Were these "disabled" for the winter and subsequently re-enabled now? I disable the older lamplincs I put away with the Christmas decorations till the next year. Maybe factory reset one and re-test to see if that helps. Paul

There is one other thing to try, if the device supports it: 'Communication to the PLM'. Its found by right clicking on a device and picking 'Advanced'. If the device supports it, there will be a drop down to pick the number of retries. I have a few devices on the edge of my network that were problems I tried this on. For keypads, you set it by the key which was handy for me. I started with 2 retries and that seemed to solve it. I'm not really sure of the scope of this feature, and the problem was very intermittent... but the problem has gone away. Its easy to try. Paul

To follow up on Stu's comment, what you've listed is 1/2 of the necessary steps.. .the ISY admin console part. You need to go to my.isy.io, set up and account and associate your ISY's UUID with that portal account. Maybe you've done that but I didn't see it mentioned. Paul

Cool...the rainmachine has the Alexa skill built in... turn in on the RM's web page, use the Alexa discover, nothing to install. I used it once to herd a squirrel from one part of the yard to another . Paul

Jack Ok.. Hope you figure out. Part of me wonders if its the PLM. My experience is that they can fall apart a little bit at a time. Its probably worth looking at the ISY, PLM and Device links. The hydreon has been great! Just had a forum chat about it the last couple of days. My water usage / bills have been way down, which is good because our water is expensive. I've had no problems with it. Other than inspecting and wiping it down at the start of the season in march, it gets ignored. I switched out the ezfloras for a rainmachine a 2 seasons ago. The RM does the bulk of active watering, and cuts back zone time based on WX / forecast data. I push a 48 hour "sleep" to it when the hydreon senses enough water, and also determine if my in-the-sun hot zones... also if its rained enough during an active watering cycle. Paul

Hey Jack, good to hear from you. These things stand out The light is on, switch (a 2876SB Icon Relay Switch) is on (i.e the pilot light is off In admin console, the last run status is correct In admin console, the status of the light shows OFF, until queried In Mobilinc pro, the status of the light is OFF until the actual control page is brought up. Given that its a scene, it can make sense that the admin console (and downstream things that refer to the AC), show things as the ISY believes them to be. This suggests that either the scene command / group cleanup aren't making it to the switch, or, the switch is ignoring it. Any other programs running at the same time? Have you factory reset the switch and restored it? Any chance the settings in the scene or the switch itself have changed Paul

Nothing wrong either way, it depends what you like and work with: Waits The only way to do it if you have hundreds of devices and are low on Insteon links Downside is that it creates a lot of traffic at that time Each scene goes off one at a time, rather than one single "off" (Personally don't like the effect of this) You need to add a bunch of wait statements to one or more programs One Scene Uses a lot of additional links.. ok if you have lots open (I do) Less insteon traffic Ons and offs are coordinated.. everything on or off at one time (My preference) You need to use the Admin Console to drag a bunch of devices and build a big scene Paul

Leon I believe this feature was designed into insteon and in the Insteon whitepaper. This is "working as designed". The messages generated by insteon switches that are associated with "if xxx is switched on/off" are transmitted only when locally and physically tap/double tap/holding the switch. Remotely activating the switch does not send the messages back out, ISY programs won't respond. This applies to linked devices too.. turning on a switch via admin console or ISY program does not turn on linked devices it activates when switching it on locally. What should work in programs is status on/off, no matter how the switch is activated, its status should be detected. Paul

Leon, If you open your ISY Admin Console, find the on/off device and click on it, look at the options at the bottom. Fast On / Off should be there. This is what was recommended to the OP I have several on/offs that I detect being switched locally fast on / off. Attached is a pic of one of my oldest togglincs in the if part of an ISY program. The fast on / off buttons are there and work in the Admin console. Also a sample If statement where the ISY is allow me to detect fast on/off from in a program Its the same double tap speed as any other switch. Paul

Agreed with Stu. "Group Cleanup" messages from a previous Set command are colliding with other Set commands as the program runs. Another way to do this is to create another scene, a master scene that contains all of the devices, and turn only that scene off. This is possible only if you have enough links available in the links table. If you have hundreds of devices my suggestion may not work. Paul

Only dimmers can make functional use of fast on / fast off on their loads -- it overrides a slow dim up or down rate. However, insteon on/off switches support the ability to be locally double tapped fast on/off, and ISY programs can detect that. On/Off switches also send dimming commands to dimmable devices linked scenes when when using "press and hold" of the paddle or keypadkey. ISY programs do not see this and not able to respond to it Paul

Insteon scenes can't be specified by double tap. However, you can get the same results with this: Create a scene where all 3 are Responders only Create 2 programs If switchA is switched fast on or switchB is switched fast on or switchC is switched fast on Then Set SceneAllThree on Create as similar program for off There will be a second or two delay Paul

Stu, it was low voltage landscape lighting. A transformer that worked perfectly for years with an X10 supersocket would overwhelm a single outlet outletlinc in about 20 minutes. It would stop responding and needed a reset using a downstream GFIC. If I left the outletlinc on, and controlled the load with a appliance module it was fine. I tried and extension cord to give the noise room, no go. For a while I used a filterlinc as I described above, but that was not optimal because its an outside enclosed box, and adding the filterlinc caused the box's door to be popped open. Nothing bad happened, but didn't like an outside electrical box being open to the elements. Eventually I replaced the intermatic low voltage lighting system with an Patriot low voltage LED system; which had a transformer half the size. No filter and no problems since then Paul

You need to put the sensor in linking mode by opening the back and pressing the set button. The Led on the front will blink for a few minutes and then set mode will stop. While its in set mode: go to the admin console and click on the motion sensor. Towards the bottom of the screen there will be "options". Under options check the "on commands only" Press the set button again This assumes you set jumper 5 and restarted the MS as discussed in prior posts. You can link the switches and they should turn on fairly quickly. I have an MS covering my driveway and deck, and I'm very happy with how fast everything reacts. Paul

As a frame of reference, I have not upgraded form V2 to V3 yet and everything is working for me.

I think what you are clicking is a weblink to admin.jnlp and not the file itself. Assuming you're using windows, open file explorer and search for admin.jnlp. If java is loaded, it should have the white "cup of coffee" icon. Move that somewhere you want it. If there's more than one you'll need to make sure its the right version.. the only way I know is to execute the file Alternatively you can look here for your your current firmware version and follow step 4a in the first post to download admin.jnlp. That's what you want to use Paul

You don't add these devices to the ISY. They perform their signal bridging and repeating at the point that they are plugged in, and there is nothing to configure or manage Paul

There are a few threads around here discussing it. I have an established Insteon system around 50 devices. I'm happy with it. Downsides of a complete zwave conversion: Losing keypad functionality - This is a deal breaker for me for a 100% Zwave system All Insteon switches report their local status back to the the ISY.. some zwave switches do, some don't..you have to validate Effort and cost of conversion. What's functionally wrong with your insteon system now? Having said that, the ISY offers the advantages of integrating both. There are many sensor product choices onzwave. Many people use both insteon and zwave together successfully. Also, you can't have another one of the interfaces installed in your ISY.. the zigbee / zigbee AMI. Only one card can be plugged into the 994i. I would consider keeping your existing insteon hardware, and adding the zwave card to enhance it. Its more than the $1 software module, there is a zwave card that installs in the ISY was well. Write UDI to ask about that Paul

I found the the outletlincs to be "fussier" about noise from the load than other Insteon devices. I have 4 on the outside of my house and garage and they've had difficulty with the yard lights plugged in. I had to plug a filterlinc into the outletlinc and the yard lights into the filterlinc. Were the Christmas lights plugged in to the outletlinc when you attempted linking? If so, unplug everything and retry. If unplugging the lights work, then yes, plugging the Christmas lights into a filterlinc should do it Paul

especially if the temps dip down and the ms is outside

Hi 2 questions in there: Follow these directions for the "how to" of moving your setup from the 99 to the 994 Browse here and scroll down to "Upgrades" for getting a deal on a 994 as a current user. UDI makes it worth your while to upgrade! Paul

The ISY zigbee support is limited compared with zwave, you'll get more choices with zwave. Paul

The Hops Left=0 for 14.97.2A indicates that the sender and receivers are using up all of their 3 retries to get the message through, and that the insteon signal path is not good It suggests that the underlying Insteon isn't set up ideally... can you confirm one of: The power legs of your house are bridged via Insteon using Insteon dual band devices? (look at page 6, the steps will work for dual band devices including your PLM or do you have an Insteon signalinc bridge in your electrical panel? The other possibility is that the problem device is on an isolated part of your powerline as suggested earlier, and that Insteon RF isn't reaching, or that a dual band device in RF range like a range extender needs to be placed on the same circuit and nearby. If the above didn't solve it, can you describe where the problems devices are located on your powerline..eg futher away from the PLM compared to things that work Paul

This points to line noise (possibly in the vicinity of the CL2R and the load being controlled - LED).... potentially blocking the signal. A log of the communications is needed to further diagnose. In the admin console: Tools, Diagnostics, Event viewer Set to level three Operate the devices in a specific order that you can describe Press the clipboard icon Copy out just the events releated to the test Paste the results back here Paul

Unfortunately it doesn't work that way. When you send a command to a switch, it controls just the switch.. not linked devices The intermittent behavior of scene suggests that load being switched on by the scene is creating enough line noise to compete with the scene message trying to turn it back off What is being controlled by CL2R (LEDs, CFL, ect)? Try removing the load (remove lightbulbs), does the scene work 100% of the time? Test it 5 times with and without the load. If so, the bulbs (or whatever it is) is creating noise. If not, it might be that CL2R is very remotely located on your powerline from the ISY/PLM, as opposed to the keypads. You might need to add a dual band device close to CL2R. I had to do this in my garage. Paul