larryllix

Get an ecobee thermostat and get rid of the Insteon junk!

Put some masking tape over the "beta" word. Most other companies do.

Just hitting the Home Depot chain with a package containing a Door sensor and LampLinc module to show the ignorant public their garage door is open, and then upsell a Hub/Smartbox to notify the cell phone app the garage door was left open, along with all the bells and whistles that could be added, once the cheap public is hooked on the idea. **SIGH** alas! I think Insteon knows garages and Insteon signals would be a losing battle and they don't pursue it. This attitude seems to reflect in all the products they already have and are dropping.

Insteon/Smarthome's record speaks for itself. How many products have Insteon discontinued in the last ten years? 10, maybe 15? How many new products have Insteon created in the last ten years? 3 or 4? How many of those new products were just bug fixes for their defective designs? All, except for the "amazing, new" Siren... a copy of the X10 beeper from 1980? Many other HA companies have produced smart lock, thermostats, talking speakers and devices that take spoken commands etc etc... What has Insteon produced? 0. Insteon shows all the signs of a company slowly folding up and about to go bankrupt. They appear to be living off somebody's daddy's estate money. If the Insteon protocol and their basic initial product offering hadn't been such good quality, they would only be a lingering name to reminisce about and ridicule. Insteon shows all the signs of another one person company, working out of his garage. Insteon isn't a ship without a rudder, it is just a raft drifting over the falls.

Do it exactly the same way in ISY. Use the system functions to get and save the current second since midnight and when the door closes get and save the system seconds since midnight and subtract the former variable value. Massage as necessary in to minutes or hours etc.. Here is a system I used to analyse heating cyles and caught a few problems for me.

Need to know what function you are using, what speed the events happen at, for how long (and signal width) , and what is feeding the signal to it. Usually just an RC input network but both sides of the signal will be delayed somewhat.

I had that same problem a while back and resolved it by using a reserved IP address in the router DHCP reservation table as well as the same static IP address in ISY. Since I have discovered my router would not handle more than about 51 IP addresses (I have 26 WiFi RGBWW bulbs and strips), and I bought a new router that seems to handle 75 devices OK now.

This can happened because you have ISY code that modifies Insteon scenes involving those battery operated devices perhaps. ISY tries to write to the devices and cannot complete it. You need to have the battery powered device write option disabled (button at top of admin console). ISY v5.3.2 is supposed to correct some of this but I have not tested this action yet. ISY will eventually give up, once you turn off the battery writes option and the 1011 flags will turn to brown or dark green. Some devices have an open window for a few seconds after reporting an event, as per @gzaharabove.

I was wondering about a home made? loop-frame/mat mounted on the nearest wall or ceiling. Another thoughts was a centre post with beam detector shining each way and sensors on each wall. Or possibly a centre postwith both ends and a mirror on each wall. Drop a bracket down from the ceiling and you would have power available from the GDO receptacles.

The higher link limit was implemented a few years ago about PLM Rev2.1 IIRC. I never needed on so I didn't pay much attention to the ramblings.

He would need to cut loops into his garage floor for those. I wonder if anybody makes floor mats with loops built in to them instead?

I use CAO Tags but they can be detected over 1 km away sometimes and sometimes you will get a delay before they are detected. A couple of I/OLincs and magnetic sensors could tell you which garage door was opened and closed.

Yes. Battery Insteon devices must be in linking mode to write to them, usually only one at a time.

I thought the PLM Pro was a fantasy that Teken dreamed up and tried to rally support for, in another forum a few years back. It was only a pipe dream then. Next thing you know the fantasy was being tooted in this forum as a reality. (in the classic telephone game style)

1011 indicates there is binary code to be written to the device waiting to be completed.

I doubt I will be buying a PLM again. I have three units now. I got caught with the battery writes update making a mess of my ISY and I thought I had a PLM problem so I ordered a new one months ago and it took a few to get the latest rev. I went back to my original PLM, 7 years and a month old now, that has always worked without problem. Everything is working fine now but I had to put about 5 SwitchLinc dimmers into linking mode, to clear out the ISY update cache traffic jam. None of my SwitchLincs have ever required linking mode before. I need to install this new PLM to test it before the return period is up but I just hate swapping PLMs as it takes a whole day of relinking everything while ISY is cache bound.

hmmmmm. maybe it was Rev2.6. I will have to check in the morning.

I don't understand your point. Insteon created a modified design and produced it after months since the last rev was released. From what I can tell a new PLM unit was all chat room fantasy and never from the mouths of Insteon. I have been using Insteon RF for 7 years now.

Yeah, after waiting for a month and a half I received a PLM V2.5 from aartech.ca. They haven't discontinued progress or the line.

Since Insteon just released a new PLM design, and Insteon has absolutely no use for a separate PLM plug-in, at all, I see this as a vote of support for UDI's ISY/PolyGlot products from Insteon. "It's alive!!" ?

I posted this previously but somehow the link was messed up and disapeared. I link into ISYs clock that is always accurate and needs no maitenance, creating variables that can be used by all programs. to trigger events without any additional hardware or Ethernet links.

I would hook into the ISY clock variables and not use relative timers at all. Any power glitch or other event that can happen, relative timers fail. Over the period of 30 days the likelihood of a relative time timer working is very low. DST and PEC hydro are not your friends. This is an ISY Internet based clock I wrote to use for many programs. It is always as accurate as ISY is.

Sounds like some bad communications there ad you have lost the link that updates the PLM status when it changes. Right click on the device in the admin console device tree and select upload the links from the device (forget the exact syntax). After the chart loads click on the compare button at the bottom. If they disagree, select the device again, and select Restore. Check again. You may need some FilterLincs as GDOs are notorious for creating Insteon noise.

This sounds like you have these programs in a folder that is disabled! I have been caught on this a few times now and wasted many hours wondering WTF s going on. There is no indication that the programs have not run but they don't! I would love to see this logic changed for manual testing of programs.

He posted he did. "5. Changed Test Program 1 to: $State_1 = 1 Else: $State_1 =10 , as well as also using the same values in Test Program 2 (adjusting the action for $INT container of course) Tested both sets of Run Then and Run Else commands but still get no value changes or Last Changed updates. "